We had our first meeting on 23rd April (16:00 GMT) and largely discussed what Design & UX OSS sustainability means to each of us and some of our key, personal concerns. We have a notes docs I’ll drop here.
Generally, though, the work of Design/UX + OSS Sustainability was advocacy (OSS <-> Design community both ways), funding, processes, mentoring, resources and structures. Largely things the WG have been grinding on for a while.
We’ll use the #open-design-discussions channel in the Open Collective slack to chat there.
Hey Sustain Design & UX folks, we have a meeting booked in this week on Thursday (11.00 EDT, 16.00 BST 17.00 CEST). I can’t edit the meeting invite but here’s the Google doc link for notes:
Any agenda item suggestions plz?
My one is:
Let’s talk about documentation and overlap with any/all of the other Sustain working groups.
User + Developer documentation > Design Documentation
Communication norms
Information Architecture of Docs
(@Erioldoesdesign) What if there was open source design docs like the default code of conducts? Things that are like, copy-a-ble or ‘start your repo with asking for design help’
E.g. Memo’s helped with information architecture of docs hub when funded to work on docs and it was well
received by the team.
Our Open Source Design conference organisation thread for Fosdem 2020:
Credit & Design in Open Source
(@jwf) Aside: Related to Bernard’s point, different demographics have different experiences with receiving appropriate credit for their work
Collab: Licensing WG on things like outreach materials about Creative Commons licenses for designers? (might be a stretch…)
Often women but also other underrepresented demographics have different experiences with asking for and receiving credit
(@jwf) How to talk about Open Design to open source developers
“Advocate kit”-esque tool to help build better understanding and context for what goes into Design work and to help the wider development community get more visibility into Design work
x-posted from the open-design-discussion channel on the open collective slack
For our next SustainOSS Design + UX WG meeting I have an agenda item/topic to propose/discuss.
Designer + Developer relations - what is needed, observed and can be done about the gaps between these ‘functions’ or ‘jobs’. The corporate world has plenty(?) of advice/resources for this but how does the dynamic play out in OSS and how can it be better sustained?
Raised because I had a great follow up conversation with https://twitter.com/codeekage who I met at the Open Source Africa festival and we talked for an extended period of time about how to build better bridges of understanding between devs+design.The ? after ‘plenty’ is because I see these existing resources as mainly accessible and written for a western, European, American audience and it is less available in other countries not privileged with a certain pov on design
Designer + Developer relations - what is needed, observed and can be done about the gaps between these ‘functions’ or ‘jobs’. The corporate world has plenty(?) of advice/resources for this but how does the dynamic play out in OSS and how can it be better sustained?
Raised because I had a great follow up conversation with https://twitter.com/codeekage who I met at the Open Source Africa festival and we talked for an extended period of time about how to build better bridges of understanding between devs+design.
The ? after ‘plenty’ is because I see these existing resources as mainly accessible and written for a western, European, American audience and it is less available in other countries not privileged with a certain pov on design.
What are the resources that people in new roles need to work with design + open source - How do I talk ‘open source to designers when they don’t know open source’
Docs + Design + Open Source
The docs team are being more inclusive and understanding of design so we’re sustaining design and ux in the docs WG
In the next Working Group call, I can give a tour of how to use the Taiga board as an admin, but for now, it would be great for folks to create new cards for some of the different ideas we’ve been discussing the past few months.
Also if you want an invite to the board, please send me a message with your Taiga.io email address!
@Erioldoesdesign This would be immensely helpful! I figure in our next meeting, we can dedicate time at the start to review the board and add anything we think is missing. But having some base content there will make it easier for us to jump right in for our next call.
So there are some epics and issues/user stories for overarching themes and granular resources.
I started tagging some of the epics and issues/user stories but that’s the next thing to focus on…well as well as creating/searching for some of the resources that don’t exist yet!
I added some upvotes and a few comments to specific user stories, and did a quick look at everything you added. I think this will be super helpful for our monthly meetings. Maybe we could even get in a habit of using Taiga for card-specific discussions. All good things to explore in our next meeting when we get a chance to review this with everyone.
Also, just a call-out to this card specifically (Credit & Design in Open Source):
Related, there is a focus group on “Credit” as part of a Building Trustworthy Data Practices effort this Tuesday (2020-08-25 @ 13:00 U.S. EDT). It is a 90 minute focus group and led by excellent folks connected with various open science efforts. I could pass along an invite to anyone interested.
pretty?
isn’t as lovely as the sustain green brand colour
