Jan-Christoph Borchardt

For everyone who doesn’t know what exactly we do, this is a short intro to our collective: We work to raise the profile of good design in open source software, and connect developers & designers to make it happen.

We run an Open Source Design community forum, organize design tracks at well-known events like FOSDEM (hello 🙋), FOSSASIA and OpenTechSummit, have a job board to get designers involved, provide open design resources to developers & designers, and more.

We will also take our GROUP PHOTO during this session! 😊

A few of our activities from last year include:

👩‍💻 Lots and lots of posts on our Open Source Design job board! https://opensourcedesign.net/jobs/ 2️⃣ Organization of our second Open Source Design Summit in Tirana! https://opencollective.com/opensourcedesign/events/open-source-design-summit-2018-371ev 💸 Sponsored by Sticker Mule, Mozilla & phpList and supported by Open Technology Fund, Ura Design, Red Hat & Nextcloud 📑 More activity on our Discourse forum! https://discourse.opensourcedesign.net

Things we are working on or need to work on:

💬 Attending a bunch of events and giving talks related to Open Source Design https://discourse.opensourcedesign.net/c/events 🎨 Attendance at more mainstream design events! ⭕ Still working on becoming an Open Source Initiative affiliate https://github.com/opensourcedesign/organization/issues/53 👥 We need to do more on the meetup front: https://discourse.opensourcedesign.net/c/meetups – NYC is active, but we can improve elsewhere 💻 Another work in progress is the website, we are looking into improving the design. ;)

✨ Probably lots more we forgot to list! :)

For everyone who doesn’t know what exactly we do, this is a short intro to our collective: We work to raise the profile of good design in open source software, and connect developers & designers to make it happen.

We run an Open Source Design community forum, organize design tracks at well-known events like FOSDEM (hello ;), FOSSASIA and OpenTechSummit, have a job board to get designers involved, provide open design resources to developers & designers, and more.

We will also take our GROUP PHOTO during this session! :)

A few of the news from last year include:

• Organization of our first Open Source Design Summit in Berlin! https://opencollective.com/opensourcedesign/events/opensourcedesign-summit
• Another year of organizing the Design/Art/Community track at FOSSASIA: https://2017.fossasia.org/tracks.html#2017-03-19-Design,Art,Community
• First time organizing an Open Source Design track at OpenTechSummit Berlin-Potsdam: https://2017.opentechsummit.net/programm/tracks.html#2017-05-25-OpenSourceDesign
• Setting up our community discussion forum: https://discourse.opensourcedesign.net/
• Kicking off new local meetups: https://discourse.opensourcedesign.net/c/meetups – among them a very active one in NYC!
• Attending a bunch of events and giving talks related to Open Source Design https://discourse.opensourcedesign.net/c/events
• Lots more work on the website, like integrating comments into the job board, and adding subsites for resources and projects
• OpenDesign.io joined forces with us! :) https://twitter.com/OpenDesignIO/status/923990916758691841
• Becoming an FSFE associated organization: https://fsfe.org/associates/associates.en.html
• Getting a 1000 $ donation from Discourse https://twitter.com/discourse/status/928591869763883008
• Getting funding from Wikimedia Germany for our Summit and stickers, posters & cards!
• Probably lots more we forgot to list! :)

For everyone who doesn’t know what exactly we do, this is a short intro to our collective: We work to raise the profile of good design in open source software, and connect developers & designers to make it happen.

For that, we organize design tracks at well-known events like FOSDEM (hello ;) and FOSSASIA, have a job board to get designers involved, provide open design resources to developers & designers, and more.

We will also take our GROUP PHOTO during this session! :)

Designers are not allergic to open source – it often is just quite difficult and frustrating to get involved. Gladly there are some easy methods to make UX & UI folks feel welcome and get them contributing! :) This talk will show the methods we use at Nextcloud – which successfully helped us build an active and welcoming design team.

Some of these methods include: - Describe clearly what your project does - Being welcoming to designers - Involving design from the start - Using design tags in the issue tracker - Have an easy landing page to get involved - Cultivating a culture of design-driven decisions - and more! :)

If you are maintainer or contributor of an open source project which needs design love, this is the right place!

Everyone who has a project can just quickly present it, show the website and state where they need design help. Either we find a match directly there in the room, or we’ll add it to the Open Source Design job board at http://opensourcedesign.net/jobs/

I’ve been working with several design universities now to get the students involved and working on open source projects. Especially for usability testing this is very little investment with a huge benefit for the project, professors and the students.

I’ll present the collaborations I did so far and how we can push it forward more.

Design and good UX gets more and more important in open source projects. We need to work together, across projects, to deliver the best experience.

In the spirit of open source and sharing code, we should also share our design work. We need to gather, share ideas, exchange how we approach problems, what works and what doesn’t.

Some of the topics we should connect about and also build a body of knowledge for other projects:

• How to get started
• Unique challenges in open source as designers
• How to work together with developers
• Building a design team
• How to make it easy for others to get started
• Resources: tools, blogs, websites, …

And outreach we can do:

• Open Source conferences to attend and present at
• Cross-invitations to conferences of other projects
• Help projects which need design help
• Work with universities to get students working on open source design

Unhosted is a non-profit project defining a standard to separate web applications from data storage. The web apps are pure client-side Javascript, fully inspectable and thus enable truly free software on the web. It also allows app developers to enter the web market a lot faster by not needing to care for any data storage. At the same time, users have their data in one place and can use all the apps with just one account and data storage.

Usually, web applications always come with storage attached to it. You can not choose where an app stores the files you use, it’s just their server. Put plainly: You get their app, they get your data. We want to improve the web infrastructure by separating web applications from your data. You have one remote storage where your data and user account resides. In apps, you identify with your user address which then connects to your remote storage and loads your data locally in the app – nothing leaking to the app server. This makes it easier for users because they only need one account and place to have their data – a "My Documents" for the web. App developers don’t need to bother about storing user data or scaling their applications – because it all runs in the user’s web browser. The applications can be Javascript apps using localStorage, like many web apps already. Just include the remoteStorage.js library and search/replace localStorage with remoteStorage – and the app enables people to use their own remote storage for it. To act as a remote storage, a platform needs to provide WebFinger for discovery, OAuth for authorization and Cross-Origin Resource Sharing (CORS) for cross-domain AJAX calls: ownCloud is already compatible and we work on making CouchDB, Wordpress and Google Drive compatible.

Why Webfinger is so important, why BrowserId is so important, and how to combine the two.

The federated social web needs to be a tool-agnostic web. A user should be able to interact with other users, regardless of whether the other user is using xmpp-based tools, or OStatus-based tools, even SMTP, and maybe even SMS. But there is one central corner stone of socializing: user addresses. These can be email addresses, Jabber ID's, or webfinger account URIs. In this talk I'll discuss some of the challenges of enabling people to own their user address. In particular, I will discuss our experiences in both the LibreDocs project and the Opentabs project, about why Webfinger is so important, why BrowserId is so important, and how to combine the two.