Developers looking for designers? Pitch your project! [Group]
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Barros Pena, Belen
The day has been filled by designers doing all the talking, but here we switchand give the stage to software developers. This is a chance to pitch your project to the designers in the room and askthem to contribute. You will be given some time to explain what your projectis about, why it's important, and what design work needs to be done. No needto book in advance: just turn up! We have done this session for the past 2 years, and everyboy seems to like it.So we are doing it again.
 So this is the last session basically. And so we have been doing this since the first open source design dev room. And it's basically just, as you could see on the schedule, just a session to pitch your own project and to ask for design help. So if you have an open source project where you need any design help whatsoever, like a logo or some interaction design or just a design review or something like that, yeah, this is your chance now to pitch your project. It's just, yeah, voluntarily anyone who comes up. I know some people who already want to show their project, right, you, for example. And so you just have three minutes. Just quickly explain what you're doing. Yeah, it's hardcore. So we don't have a lot of time. So just quickly, be concise, describe what your project does. You can come up here and just open your website or your GitHub or any repository or whatever. Just quickly explain what your project does, how you need design help, and how to contact you. And you have three minutes. That would be cool. And also, if you come up here and present your project, we also ask you to, if you didn't do that already, afterwards, go to our jobs page and submit that what you presented as a job posting. So it's also there for anyone who doesn't attend right now. OK, so who wants to go first? Koala? OK. OK, so who else also wants to go? I saw some hands, show of hands. OK, cool. OK, nice. OK, you want to go first? Oh, OK. All right, yeah. I will just hold this here. OK, who has the time? Does someone have you have the time? OK, great. I'll hold it for you. OK, so this is about Koala. Koala is like a meta-linter. So you may know linters is usually one tool doing one specific kind of analysis on one language. So you usually need more of those. And you don't want to use multiple of those tools. Koala is like a meta-linter. And it basically uses those tools for you. It's one unified user interface for 66 programming languages and usually more than one analysis available for every language. We need design help in terms of usability. What we basically want to do is a usability test. So all that you get from me right now is koala.io. That's our website. And I want you to set that up for a project to do something reasonable with it and figure out if it works for you or not. Especially if it doesn't work for you, you can fill in the results at koala.io slash usability. Or you can just file us an issue. So it's very simple. Go to koala.io and later to koala.io slash usability. Thank you. Thank you. Thank you. OK. Remember to also put that in the jobs board. Yeah. Very cool. So at koala.io slash usability, there will be a questionnaire. Yeah, it's a Google form. OK, cool. I mean, it's not cool that it's a Google form. Sorry. But I guess it's OK. Just email me. Just ask for my card or I don't want to spend on yours. OK. Who's next? Do something. Yeah? Good koala. So that's the project building up on koala. So maybe it would make sense to get it right now. Maybe yes. Yes. So whoever wants to come, just come up. I don't pay attention to who raised their hand. Just come up. So you've got a rough idea of koala now. Just sit down here. There is no more letters on it. Yeah, sorry. I made the letters blank and I'm really hacker. Account type. Oh, it's a German keyboard too. I'm sorry. Is it? Is it? Oh, yeah. Maybe don't open this tiny URL. I don't know where they need to be. I'm just searching for my answer. All right. So you've got a rough idea of koala now. And so you haven't seen anything of, OK. Thank you. So you've got a rough idea of koala. With koala, there's something we want to do. Like we want to integrate it into GitHub. So it's actually usable. It's very, so I can have a seamless integration to GitHub. And now I can see the comments which are by the linters produced by koala are right in GitHub. So the idea is that it would look like something like that. So that's the product we want to do. Oh my god, you can't see it at all. Ta-da. Here it is. So that's the eventual outcome. So not much design work to be done there because it's GitHub basically. But what we are thinking about is how to do a nice configuration. And so that's our approach for the configuration so far. Yeah, we're not designers. It's basically not pretty nice. We just tried something. But we really would need some feedback on that and how to make a good experience for the users on that point. So there will be a question area at. At koala.io.slashgitmate. At koala.io.slashgitmate. And if you have any feedback on that, if you would like to contribute this time, I would be very happy to see at koala.io. Slashgitmate or visit us at gitmate.io. Thank you very much. Cool. Just go there and open the project page. I'll do so. I'll just close that maybe. OK. Just go there and open the project page. I'll do so. Just close that maybe. Yeah. Yeah, or just open it there. Yeah. You need to click. It's a bit. Can you hold this? Yep. I'm Michael from Fremdika. Fremdika is a decentralized social network. We are here. Well, we exist for several years. You might know diaspora. We can talk to them as well. We are open source based on PHP and Co. And we really desperately need help for designers. For example, this homepage here is kind of ugly shit. It's totally old. And we tried to do a new homepage that looked, really rewrote everything and it looks even uglier. Because it's just, yeah, hey, like. And so we really need people who are willing to help us just do the, just for new users, for people who are interested in it, so that they don't see this mess and say, what the fuck? So, yeah, so that they can do the first step can see, oh, yeah, that's looking nice. And, yeah, and this is one of the things other things would be, maybe if there are people who are good in user experience stuff and so, could have a look as well at our system, could try. Like in one of the other talks where people, this was where one could ask people for testing why people are creating an account, but never come back and this whole stuff, this would be totally appreciated. So where to dive in? How to contact you? Where is your code or your? Our code, yeah, these are all some weird, ugly things. I don't know where the mail addresses point to. So best would be on GitHub. The keyboard is really cool. I painted it black, I'm sorry. Yeah. No, German. And it's almost. German. Yeah, but most things. So this is the address, so I'm going to go to your website, and we could be reached over, of course, contacting here with issues and so on. And of course, I will try to add a job entry as well. Cool. Thanks. I can also type for you. Yeah, disregard my history or whatever. I hope you didn't see anything incriminating. Sorry? Oh, yeah, there's a video. Hello, I'm Heuder from the Reproducer Builds project. Reproducer Builds are about free software as nice, because we can modify the sources, share the sources, edit the sources, and pass them on. But nobody uses sources, we use binaries, and we need to believe that a binary comes from a given source. And the way to overcome this belief is enable everybody to rebuild this exact same binary. So this is Reproducer Builds. It's a technical project, and we are looking for a logo. And so I'm Heuder from Debian, but involved is Arch Linux, BASEDROCK, BITCOIN, Qooboo, Debian, FDROID, FreeBSD, Fedora, Geeks, Lead, NetBSD, NixOS, OpenSousa, OpenWRT, T-Tails. So we are looking for a logo for this Reproducer Builds project for everybody, and we have a page describing the logo, which is the Heuder and the Key. So we have a page in the Debian we can just search for Reproducer Builds logo, which is not the right page. So there are 16 ideas for Reproducer Builds logos. Some are usable as logos, some are not. Some are for the Olympic Games. So I think I like this idea, but it's not a logo. This is also nice. Or this. Or the reddit, because we're producing. I don't know. You can name me. My name is Heuder from Debian. Thank you. Cool. Nice. Thank you. And just one question. How long are you looking for a logo? Because you have all these ideas already? No, I mean since how long? Since when the webpage was like two months or a month. Oh, OK. All right. OK. So it's reasonably fresh. OK, cool. Flash. Oh, the flash is, I think, here. Yeah. It wouldn't be so bad, but all the keys have the symbols rubbed off so you can't see what you're typing. It's because I'm a real hacker. What is this? Custentrise or online presence? What good is that? I need to show off this. Whatever. That's not helpful at all. OK, so this is me, Daniel Quinn. Anyone here played with a game called Guala? Do you remember it? It was a while ago. No? It was a great game. I fell in love with it. And then they sold out to Facebook, and Facebook was like, screw you guys. And they just closed the whole company, stole the staff, and imported them. So when it died, my friend and I got very upset, and we wanted to bring the game back. But we were going to make it better. And my friend, she had this brilliant idea. She was going to come up with this really cool game and she was like, oh, I'm going to be a good player. And then she came up with this idea. And basically years later, some other company came along, came up with something you may have heard of it, Pokemon Go. Between the time that she had the idea and the time that they came out with it, I started writing it. And I swear to God, like four years ago, I had a fully functional API. It was the coolest game ever if you really liked talking to JSON APIs. But it was this cool game where you could walk down to the water, and you could see the stars and change the monsters near you based on that. There was leveling, there was upgrades, and all kinds of stuff. It's still there. It's all on GitHub. You can play with it if you like. But it's just an API. It's really ugly. I need it to be sexy. I need pictures. I need illustrations. And I need anything that's prettier than an API. So you're raising your hand. I'll go ahead. Oh, no, not at all. Because copyright. Yeah, well, that's the other thing. Pokemon is kind of the problem because the creatures themselves are limited. The way the game is designed for us is they're designed to just be we can add new breeds of creatures based on other aspects that we can get. So for example, right now, with your Latin longitude, I can get the position of the stars in the cosmos. I can get the current weather where you are. I can get the historical weather you are. So figure out whether or not it's colder than it used to be and generate a different cold monster or not. The region you are nationally, so the monsters all have regions, they call there's also like one in 100 chance that you may pick up a tourist. So you're in the UK and you're collecting monsters and they all have little UK flags on them. But every once in a while, one's from Japan. And now you get this idea, you want to go all around the world and collect monsters from all around the world. So all of this stuff is, it was fun for people like me who like to collect things. So I want to just make the game so I can play the game. But if any of you guys would also like to play the game or perhaps make you some money if we can actually make it into a functional object, that would be awesome. But yeah, come and get ahold of me. My contact info is hidden by that totally useless thing at the bottom. So just look at me. I'm Daniel Quinn.org. Go to my website there and you can contact me through that. Thanks. Cool. Thank you. Let me know if you need help tapping. The T is here. You can just open it in the tab. It's controlling. Oh, it's controlling. Oh, OK. It doesn't change. Dot. Yeah. Hi. I'm Christian Frisson. It means Shiva in English or Fibrefrost in German. Anyway, I'm a researcher in human computer interaction at Inria in Lille. And I'm developing a tool to help UX researchers and IHCI researchers to observe how people use their own apps. So I'm going to introduce it by two use cases. Some time ago, I was working on a project consisting in observing how sound designers find sounds, explore sounds, if it was like in grids or lists. But if the tools that are available to record this are like a quick time player or other tools, but you cannot get the click and like input from the keyboard. You cannot extract it as a separate file for analysis. So it's not convenient to annotate everything by hand. And so we wanted to develop another solution. Like it's going to be really small, but it's a browser that combines similarity of sound based on tags and based on the sound itself. So to evaluate it, for usability, we wanted to do quantitative analysis. And then we had to compare this application with another one that they used. And maybe some of you might have recognized, but I guess that is too small. This is Pro Tools from DigiDesign.avid. There are no user logs available, so we had to reverse engineer some. So at last, this is the app I'm working on. It's called Inspector Widget. There is a reference to a famous animated series back in the days. So the idea is this is the recording of the desktop of anybody's computer. And by using a scratch like language, we can program annotations and then browse the video synchronized to these annotations. For instance, this is the file browser of Pro Tools. How can we see when people are browsing for sounds, making some queries to find sounds, playing back? So if we don't have access to the DOM for web applications or the structure of widgets, how can we do that? So we select regions and we extract them from the video. How do you need design help? So I would need people that would help for the design of the application. But more so users that are designers themselves that might use this tool for contextual inquiries or usability testing. I would want them to try it. For now, I mean, almost the only developer of it. It's only available for Mac, sorry, but I would need help from the developers as well. And the time is up, but thanks. If you want to reach me, the project is on GitHub. If you browse this website, my contact is going to be visible somehow. Thank you. Hi, everybody. My name is Rio and I'm from the Daisy program. Basically, we try to build the Internet of Energy and make energy as a common, basically. We're a team of something like today, 10 people. It's an open design program for people who consider energy as a common. And what we're trying to do basically is to work on three levels. One level is the hardware level, how you can monitor the consumption and the production of energy and make it sensible or has a representation for it for the users and for the people who are directly in touch with energy. Let's say this is the first level. The second level is the software level. So we worked on with kind of blockchain technology called Ethereum, basically. What we're trying to do is basically how you, let's say, design an infrastructure for people to share, to directly share or sell energy to each other instead of, let's say, selling their energy to the grid or to another producer. So this is basically the project on which we're working on. We are looking for help from designers. First of all, for the design of the contributions, because we like, well, this project is open source, so we like people to get involved in both the design of the interaction between the people and the energy, actually. So this is the first thing. The second thing is that we need design help to basically design the governance of the energy. What we are trying to do is basically to build a micro scale or micro grid energy grid. And one of the things that is quite complicated is how you deal with the local marketplace, actually. And this local marketplace has to be, let's say, designed as to have governance that is rightly designed for interaction between the peers. That is to say, the producers, the media operators, the citizens, et cetera, et cetera. Thank you. Okay, thanks. Okay, your last one, I guess. Okay. Yeah. Okay, nice to go. I can now just hold it. I can just hold it. Go ahead and get my this up now. You should go already. Yeah, thanks. It's not the clever one. Yeah, bye. Why is this strange? Okay. So, hi, I'm Tigi. We are working on the GNU Taller project, which is a free software project for implementing a payment system that allows anonymous payments, but receiving the money is not anonymous. So we have this website, Taller.net. You can find the developers page on. Yeah, it's here. It suggests very briefly the system looks like the way you would use it. You have a bank account with, for instance, euros, you withdraw coins into your wallet, which is running your browser or mobile phone. These are anonymous coins that each represent a euro, or it can be tied to dollars or whatever else as well. So this system is not a currency, but just a payment system. So it is intended to replace credit cards and PayPal and similar systems. So what happens in the system is that you have your bank and exchange, exchanges your currency to anonymous coins and you pay with your anonymous coins to merchants, and the merchants can go back to the exchange and get back the euros or whatever currency you have. And so what we started doing, we have started implementing the whole system and we have a browser extension using the web extensions API. And what we need help with is designing the layout and the design of the extensions pages. We have these browser popups in the corner usually. So we have, we need to display the current balance and the confirmation pages for payments and things like this. So all the layouts, so it's HTML, CSS, basically, design work that we need help with. And so if you go to tarot.net on the developers page, you can find the contact information. We have a mailing list. So yeah, discussion. So we have this mailing list. You can send a message there. And if you would like to have the design of the web extensions. That's what it's mainly and thanks. Okay, so that was it. So everyone who, who, yeah, asked for design help now, please go to open source design.net slash jobs and there's a link to post the job. And it's basically just adding like a markdown file to a repository. So you just put in the info there. And I think we even have the, we have this form up already. Okay, yeah, so it's even a form not not a markdown file and blah, blah, blah. Oh yeah, okay, okay. Yeah, exactly. And right. And basically, like kind of also a job or if you want to contribute like we're an open, open collective. So we're on github.com slash open source design. If you want to get involved. Yeah, it's all open to contribution. And just a quick question. Do you think it's a good idea also next year to have this kind of the room for open source design. So thank you so much. So yeah, thanks a lot. So hopefully see you next year. And yeah, if you want to give a talk, just handed in and check us out on Twitter also.
 So this is the last session basically.  And so we have been doing this since the first open source  design dev room.  And it's basically just, as you could see on the schedule,  just a session to pitch your own project  and to ask for design help.  So if you have an open source project where you need any  design help whatsoever, like a logo or some interaction  design or just a design review or something like that,  yeah, this is your chance now to pitch your project.  It's just, yeah, voluntarily anyone who comes up.  I know some people who already want to show their project,  right, you, for example.  And so you just have three minutes.  Just quickly explain what you're doing.  Yeah, it's hardcore.  So we don't have a lot of time.  So just quickly, be concise, describe what your project does.  You can come up here and just open your website  or your GitHub or any repository or whatever.  Just quickly explain what your project does,  how you need design help, and how to contact you.  And you have three minutes.  That would be cool.  And also, if you come up here and present your project,  we also ask you to, if you didn't do that already,  afterwards, go to our jobs page and submit  that what you presented as a job posting.  So it's also there for anyone who doesn't attend right now.  OK, so who wants to go first?  Koala?  OK.  OK, so who else also wants to go?  I saw some hands, show of hands.  OK, cool.  OK, nice.  OK, you want to go first?  Oh, OK.  All right, yeah.  I will just hold this here.  OK, who has the time?  Does someone have you have the time?  OK, great.  I'll hold it for you.  OK, so this is about Koala.  Koala is like a meta-linter.  So you may know linters is usually  one tool doing one specific kind of analysis on one language.  So you usually need more of those.  And you don't want to use multiple of those tools.  Koala is like a meta-linter.  And it basically uses those tools for you.  It's one unified user interface for 66 programming languages  and usually more than one analysis  available for every language.  We need design help in terms of usability.  What we basically want to do is a usability test.  So all that you get from me right now is koala.io.  That's our website.  And I want you to set that up for a project  to do something reasonable with it  and figure out if it works for you or not.  Especially if it doesn't work for you,  you can fill in the results at koala.io slash usability.  Or you can just file us an issue.  So it's very simple.  Go to koala.io and later to koala.io slash usability.  Thank you.  Thank you.  Thank you.  OK.  Remember to also put that in the jobs board.  Yeah.  Very cool.  So at koala.io slash usability, there  will be a questionnaire.  Yeah, it's a Google form.  OK, cool.  I mean, it's not cool that it's a Google form.  Sorry.  But I guess it's OK.  Just email me.  Just ask for my card or I don't want to spend on yours.  OK.  Who's next?  Do something.  Yeah?  Good koala.  So that's the project building up on koala.  So maybe it would make sense to get it right now.  Maybe yes.  Yes.  So whoever wants to come, just come up.  I don't pay attention to who raised their hand.  Just come up.  So you've got a rough idea of koala now.  Just sit down here.  There is no more letters on it.  Yeah, sorry.  I made the letters blank and I'm really hacker.  Account type.  Oh, it's a German keyboard too.  I'm sorry.  Is it?  Is it?  Oh, yeah.  Maybe don't open this tiny URL.  I don't know where they need to be.  I'm just searching for my answer.  All right.  So you've got a rough idea of koala now.  And so you haven't seen anything of, OK.  Thank you.  So you've got a rough idea of koala.  With koala, there's something we want to do.  Like we want to integrate it into GitHub.  So it's actually usable.  It's very, so I can have a seamless integration to GitHub.  And now I can see the comments which are by the linters  produced by koala are right in GitHub.  So the idea is that it would look like something like that.  So that's the product we want to do.  Oh my god, you can't see it at all.  Ta-da.  Here it is.  So that's the eventual outcome.  So not much design work to be done there because it's  GitHub basically.  But what we are thinking about is how to do a nice  configuration.  And so that's our approach for the configuration so far.  Yeah, we're not designers.  It's basically not pretty nice.  We just tried something.  But we really would need some feedback on that and how to  make a good experience for the users on that point.  So there will be a question area at.  At koala.io.slashgitmate.  At koala.io.slashgitmate.  And if you have any feedback on that, if you would like to  contribute this time, I would be very happy to see at koala.io.  Slashgitmate or visit us at gitmate.io.  Thank you very much.  Cool.  Just go there and open the project page.  I'll do so.  I'll just close that maybe.  OK.  Just go there and open the project page.  I'll do so.  Just close that maybe.  Yeah.  Yeah, or just open it there.  Yeah.  You need to click.  It's a bit.  Can you hold this?  Yep.  I'm Michael from Fremdika.  Fremdika is a decentralized social network.  We are here.  Well, we exist for several years.  You might know diaspora.  We can talk to them as well.  We are open source based on PHP and Co.  And we really desperately need help for designers.  For example, this homepage here is kind of ugly shit.  It's totally old.  And we tried to do a new homepage that looked,  really rewrote everything and it looks even uglier.  Because it's just, yeah, hey, like.  And so we really need people who are willing to help us just do the,  just for new users, for people who are interested in it,  so that they don't see this mess and say, what the fuck?  So, yeah, so that they can do the first step can see, oh, yeah,  that's looking nice.  And, yeah, and this is one of the things other things would be,  maybe if there are people who are good in user experience stuff and so,  could have a look as well at our system, could try.  Like in one of the other talks where people,  this was where one could ask people for testing why people are creating an account,  but never come back and this whole stuff, this would be totally appreciated.  So where to dive in?  How to contact you?  Where is your code or your?  Our code, yeah, these are all some weird, ugly things.  I don't know where the mail addresses point to.  So best would be on GitHub.  The keyboard is really cool.  I painted it black, I'm sorry.  Yeah.  No, German.  And it's almost.  German.  Yeah, but most things.  So this is the address,  so I'm going to go to your website,  and we could be reached over, of course,  contacting here with issues and so on.  And of course, I will try to add a job entry as well.  Cool.  Thanks.  I can also type for you.  Yeah, disregard my history or whatever.  I hope you didn't see anything incriminating.  Sorry?  Oh, yeah, there's a video.  Hello, I'm Heuder from the Reproducer Builds project.  Reproducer Builds are about free software as nice,  because we can modify the sources,  share the sources, edit the sources, and pass them on.  But nobody uses sources, we use binaries,  and we need to believe that a binary comes from a given source.  And the way to overcome this belief is enable everybody  to rebuild this exact same binary.  So this is Reproducer Builds.  It's a technical project, and we are looking for a logo.  And so I'm Heuder from Debian,  but involved is Arch Linux,  BASEDROCK, BITCOIN, Qooboo, Debian,  FDROID, FreeBSD, Fedora, Geeks,  Lead, NetBSD, NixOS, OpenSousa, OpenWRT, T-Tails.  So we are looking for a logo for this Reproducer Builds project  for everybody, and we have a page describing the logo,  which is the Heuder and the Key.  So we have a page in the Debian we can just search  for Reproducer Builds logo, which is not the right page.  So there are 16 ideas for Reproducer Builds logos.  Some are usable as logos, some are not.  Some are for the Olympic Games.  So I think I like this idea, but it's not a logo.  This is also nice.  Or this.  Or the reddit, because we're producing.  I don't know.  You can name me.  My name is Heuder from Debian.  Thank you.  Cool.  Nice.  Thank you.  And just one question.  How long are you looking for a logo?  Because you have all these ideas already?  No, I mean since how long?  Since when the webpage was like two months or a month.  Oh, OK.  All right.  OK.  So it's reasonably fresh.  OK, cool.  Flash.  Oh, the flash is, I think, here.  Yeah.  It wouldn't be so bad, but all the keys have the symbols  rubbed off so you can't see what you're typing.  It's because I'm a real hacker.  What is this?  Custentrise or online presence?  What good is that?  I need to show off this.  Whatever.  That's not helpful at all.  OK, so this is me, Daniel Quinn.  Anyone here played with a game called Guala?  Do you remember it?  It was a while ago.  No?  It was a great game.  I fell in love with it.  And then they sold out to Facebook, and Facebook was like,  screw you guys.  And they just closed the whole company, stole the staff,  and imported them.  So when it died, my friend and I got very upset,  and we wanted to bring the game back.  But we were going to make it better.  And my friend, she had this brilliant idea.  She was going to come up with this really cool game  and she was like, oh, I'm going to be a good player.  And then she came up with this idea.  And basically years later, some other company came along,  came up with something you may have heard of it, Pokemon Go.  Between the time that she had the idea and the time that they  came out with it, I started writing it.  And I swear to God, like four years ago,  I had a fully functional API.  It was the coolest game ever if you really liked talking to  JSON APIs.  But it was this cool game where you could walk down to the water,  and you could see the stars and change the monsters near you  based on that.  There was leveling, there was upgrades,  and all kinds of stuff.  It's still there.  It's all on GitHub.  You can play with it if you like.  But it's just an API.  It's really ugly.  I need it to be sexy.  I need pictures.  I need illustrations.  And I need anything that's prettier than an API.  So you're raising your hand.  I'll go ahead.  Oh, no, not at all.  Because copyright.  Yeah, well, that's the other thing.  Pokemon is kind of the problem because the creatures themselves  are limited.  The way the game is designed for us is they're designed to just  be we can add new breeds of creatures based on other aspects  that we can get.  So for example, right now, with your Latin longitude,  I can get the position of the stars in the cosmos.  I can get the current weather where you are.  I can get the historical weather you are.  So figure out whether or not it's colder than it used to be  and generate a different cold monster or not.  The region you are nationally, so the monsters all have regions,  they call there's also like one in 100 chance that you may pick up  a tourist.  So you're in the UK and you're collecting monsters and they all  have little UK flags on them.  But every once in a while, one's from Japan.  And now you get this idea, you want to go all around the world  and collect monsters from all around the world.  So all of this stuff is, it was fun for people like me who like  to collect things.  So I want to just make the game so I can play the game.  But if any of you guys would also like to play the game or perhaps  make you some money if we can actually make it into a functional object,  that would be awesome.  But yeah, come and get ahold of me.  My contact info is hidden by that totally useless thing at the bottom.  So just look at me.  I'm Daniel Quinn.org.  Go to my website there and you can contact me through that.  Thanks.  Cool.  Thank you.  Let me know if you need help tapping.  The T is here.  You can just open it in the tab.  It's controlling.  Oh, it's controlling.  Oh, OK.  It doesn't change.  Dot.  Yeah.  Hi.  I'm Christian Frisson.  It means Shiva in English or Fibrefrost in German.  Anyway, I'm a researcher in human computer interaction at Inria in Lille.  And I'm developing a tool to help UX researchers and IHCI researchers  to observe how people use their own apps.  So I'm going to introduce it by two use cases.  Some time ago, I was working on a project consisting in observing how sound designers  find sounds, explore sounds, if it was like in grids or lists.  But if the tools that are available to record this are like a quick time player or other tools,  but you cannot get the click and like input from the keyboard.  You cannot extract it as a separate file for analysis.  So it's not convenient to annotate everything by hand.  And so we wanted to develop another solution.  Like it's going to be really small, but it's a browser that combines similarity of sound  based on tags and based on the sound itself.  So to evaluate it, for usability, we wanted to do quantitative analysis.  And then we had to compare this application with another one that they used.  And maybe some of you might have recognized, but I guess that is too small.  This is Pro Tools from DigiDesign.avid.  There are no user logs available, so we had to reverse engineer some.  So at last, this is the app I'm working on.  It's called Inspector Widget.  There is a reference to a famous animated series back in the days.  So the idea is this is the recording of the desktop of anybody's computer.  And by using a scratch like language, we can program annotations and then browse the video  synchronized to these annotations.  For instance, this is the file browser of Pro Tools.  How can we see when people are browsing for sounds, making some queries to find sounds, playing back?  So if we don't have access to the DOM for web applications or the structure of widgets, how can we do that?  So we select regions and we extract them from the video.  How do you need design help?  So I would need people that would help for the design of the application.  But more so users that are designers themselves that might use this tool for contextual inquiries or usability testing.  I would want them to try it.  For now, I mean, almost the only developer of it.  It's only available for Mac, sorry, but I would need help from the developers as well.  And the time is up, but thanks.  If you want to reach me, the project is on GitHub.  If you browse this website, my contact is going to be visible somehow.  Thank you.  Hi, everybody. My name is Rio and I'm from the Daisy program.  Basically, we try to build the Internet of Energy and make energy as a common, basically.  We're a team of something like today, 10 people.  It's an open design program for people who consider energy as a common.  And what we're trying to do basically is to work on three levels.  One level is the hardware level, how you can monitor the consumption and the production of energy  and make it sensible or has a representation for it for the users and for the people who are directly in touch with energy.  Let's say this is the first level.  The second level is the software level.  So we worked on with kind of blockchain technology called Ethereum, basically.  What we're trying to do is basically how you, let's say, design an infrastructure for people to share,  to directly share or sell energy to each other instead of, let's say, selling their energy to the grid or to another producer.  So this is basically the project on which we're working on.  We are looking for help from designers.  First of all, for the design of the contributions, because we like, well, this project is open source,  so we like people to get involved in both the design of the interaction between the people and the energy, actually.  So this is the first thing.  The second thing is that we need design help to basically design the governance of the energy.  What we are trying to do is basically to build a micro scale or micro grid energy grid.  And one of the things that is quite complicated is how you deal with the local marketplace, actually.  And this local marketplace has to be, let's say, designed as to have governance that is rightly designed for interaction between the peers.  That is to say, the producers, the media operators, the citizens, et cetera, et cetera.  Thank you.  Okay, thanks.  Okay, your last one, I guess.  Okay.  Yeah.  Okay, nice to go.  I can now just hold it.  I can just hold it.  Go ahead and get my this up now.  You should go already.  Yeah, thanks.  It's not the clever one.  Yeah, bye.  Why is this strange?  Okay.  So, hi, I'm Tigi.  We are working on the GNU Taller project, which is a free software project for implementing a payment system that allows anonymous payments, but receiving the money is not anonymous.  So we have this website, Taller.net.  You can find the developers page on.  Yeah, it's here.  It suggests very briefly the system looks like the way you would use it.  You have a bank account with, for instance, euros, you withdraw coins into your wallet, which is running your browser or mobile phone.  These are anonymous coins that each represent a euro, or it can be tied to dollars or whatever else as well.  So this system is not a currency, but just a payment system.  So it is intended to replace credit cards and PayPal and similar systems.  So what happens in the system is that you have your bank and exchange, exchanges your currency to anonymous coins and you pay with your anonymous coins to merchants, and the merchants can go back to the exchange and get back the euros or whatever currency you have.  And so what we started doing, we have started implementing the whole system and we have a browser extension using the web extensions API.  And what we need help with is designing the layout and the design of the extensions pages.  We have these browser popups in the corner usually. So we have, we need to display the current balance and the confirmation pages for payments and things like this.  So all the layouts, so it's HTML, CSS, basically, design work that we need help with.  And so if you go to tarot.net on the developers page, you can find the contact information. We have a mailing list.  So yeah, discussion. So we have this mailing list. You can send a message there.  And if you would like to have the design of the web extensions.  That's what it's mainly and thanks.  Okay, so that was it.  So everyone who, who, yeah, asked for design help now, please go to open source design.net slash jobs and there's a link to post the job.  And it's basically just adding like a markdown file to a repository. So you just put in the info there. And I think we even have the, we have this form up already.  Okay, yeah, so it's even a form not not a markdown file and blah, blah, blah.  Oh yeah, okay, okay.  Yeah, exactly.  And right. And basically, like kind of also a job or if you want to contribute like we're an open, open collective. So we're on github.com slash open source design.  If you want to get involved. Yeah, it's all open to contribution.  And just a quick question. Do you think it's a good idea also next year to have this kind of the room for open source design.  So thank you so much. So yeah, thanks a lot.  So hopefully see you next year. And yeah, if you want to give a talk, just handed in and check us out on Twitter also.
Developers_looking_for_designers_Pitch_your_project_Group_0_131.png Developers_looking_for_designers_Pitch_your_project_Group_132_6947.png Developers_looking_for_designers_Pitch_your_project_Group_6948_7559.png Developers_looking_for_designers_Pitch_your_project_Group_7560_7607.png Developers_looking_for_designers_Pitch_your_project_Group_7608_7859.png Developers_looking_for_designers_Pitch_your_project_Group_7860_10727.png Developers_looking_for_designers_Pitch_your_project_Group_10728_13079.png Developers_looking_for_designers_Pitch_your_project_Group_13080_14303.png Developers_looking_for_designers_Pitch_your_project_Group_14304_15431.png Developers_looking_for_designers_Pitch_your_project_Group_15432_15539.png Developers_looking_for_designers_Pitch_your_project_Group_15540_15947.png Developers_looking_for_designers_Pitch_your_project_Group_15948_16055.png Developers_looking_for_designers_Pitch_your_project_Group_16056_16355.png Developers_looking_for_designers_Pitch_your_project_Group_16356_16931.png Developers_looking_for_designers_Pitch_your_project_Group_16932_17027.png Developers_looking_for_designers_Pitch_your_project_Group_17028_17087.png Developers_looking_for_designers_Pitch_your_project_Group_17088_17243.png Developers_looking_for_designers_Pitch_your_project_Group_17244_24131.png Developers_looking_for_designers_Pitch_your_project_Group_24132_24275.png Developers_looking_for_designers_Pitch_your_project_Group_24276_25043.png Developers_looking_for_designers_Pitch_your_project_Group_25044_25127.png Developers_looking_for_designers_Pitch_your_project_Group_25128_25247.png Developers_looking_for_designers_Pitch_your_project_Group_25248_26183.png Developers_looking_for_designers_Pitch_your_project_Group_26184_29315.png Developers_looking_for_designers_Pitch_your_project_Group_29316_29903.png Developers_looking_for_designers_Pitch_your_project_Group_29904_31259.png Developers_looking_for_designers_Pitch_your_project_Group_31260_31319.png Developers_looking_for_designers_Pitch_your_project_Group_31320_33215.png Developers_looking_for_designers_Pitch_your_project_Group_33216_34139.png Developers_looking_for_designers_Pitch_your_project_Group_34140_34235.png Developers_looking_for_designers_Pitch_your_project_Group_34236_35879.png Developers_looking_for_designers_Pitch_your_project_Group_35880_36779.png Developers_looking_for_designers_Pitch_your_project_Group_36780_39389.png