Monthly Open Source Design call

March 03 2021

Mini intros round! for new people :slight_smile:

Jobs page update

Some ideas for the jobs page improvements:

    1. Many projects give emails or issue links/repos but plenty of designers still reply to forum threads wanting to contribute. We need a clear and single way for designers to start the job process and it needs to be super clear for the job poster that they need to engage in X way with designers.
    1. We could encourage a discourse forum post immediately after the job post PR is accepted to get better responses.
    1. Deadlines are really useful for our own admin purposes. Some job posts have them included but I think it’d be good to ask job posters for an idea of deadline.
    1. We could also be: Keep for X weeks or so. Does not need to be called deadline
    1. Or “Receiving submissions/applications until”
    1. Categories for the jobs posting form and forum
    1. Support to write your design needs via a call @scottjenson suggested this.
    1. ‘I’m a designer that can do X,Y and Z. Contact me to ask for help’. Create a profile from scratch? do we help designers make a github profile.
  • Could we pay someone to do some of what we want to happen across OSD.net and the jobs page?

AP: Eriol to start a new thread on forum to gather jobs page ideas and work. DONE

Questions?

  • How do we deal with deadlines that have past?
  • Is the job board successful?
  • Shall we do an article for the successful jobs postings from over the years?
  • How can we push forward @Kai 's showcase design for homepage?
  • AP: Eriol can start to collect the successful projects and doing writing.
  • Closed successfully or closed unsuccessfully?
  • Do we want to assign metrics/analytics?
  • Do we want to think about matomo? Hosting and privacy investigation needed.
  • Sorting the job forum posts via views most?
  • Why are visuals/logos etc ‘easier’ to fill? or filled more?
  • Collect opinions of designers that have contributed and ones that haven’t.

Conferences

FOSDEM 2021

  • Open Action: Someone can do a round-up article/page of FOSDEM 2021
  • AP Eriol: Check videos are all online and approved
  • We did it! yay! we had 247 in the dev room at one point!

FOSS Backstage - UX Clinic

  • Went well! not as busy but still interesting

Mozfest 2021 - UX clinic

Donations

-All the casinos backed out lol.

2 Likes

Oh no I missed it :frowning:
This month’s ideas and suggestions could be really great additions, especially stronger deadline guidelines and improvements to the jobs page experience for interested designers.

We should get on it, possibly open GitHub issues to start a discussion on implementation for some of these.

1 Like

Just saw our jobs repo trending on GitHub!

image

5 Likes

That is so cool :smiley:

Monthly community call tonight at 18.00 GMT and 19.00 CET!

Not sure yet what we’ll be talking about but probably the regular updates and topics we’ve been covering for a while!

1 Like

March 03 2021

Mini intros round! for new people :slight_smile:

Jobs update

Webpage updates

  • Updates have been worked on by Saptak & Anxehlo

  • Job page design: Eriol is doing some design work on the Figma files and will post of discourse once done

  • Scott: willing to have a few chats with people that have requested Icons/Logos and have a conversation. Wants to do some deeper interviews with requesters and see what they are looking for from OSD jobs request. Know our user better. Between 2-6. Write up the results!
    AP: Get access to Bernard’s survey results DONE
    AP: Eriol can compile email responses and potential good people to speak to (good as in responsive to emails) DONE and DM’d to Scott :slight_smile:

  • Also, the idea of doing a consultation call for potential requesters so they can book a chat with a designer like the UX clinic.

Branch re-naming

  • The repo structure will be re-named from ‘master’ when these updates have been done

Budget in Open Collective

Conferences

  • Any coming up?
    • All things open?
  • FOSDEM 21 round-up needs writing - Who wants to do this?
  • FOSS Backstage round-up needs writing - Who wants to do this?
  • Mozfest UX Clinic round-up needs writing - Who wants to do this?
    Eriol has started these here: Riseup Pad

Github chats

  • Vic and Eriol talked about Open Design and open-source design

Mentoring

  • Eriol helped a designer wanting to do contributions to Libre lingo figure out how they want to do that via a 1-2-1 call about good first design issues and tasks as well as just generally how to start being involved. There’s a video zoom recording here
    Passcode to view is: RPjeb&3X

Linux Health SIG quick update

  • How can I fund someone at half time to help on this because 1-8 hours is tricky.
  • Eriol is gonna share some rough onboarding processes they use with Mutual.aid and open food network
2 Likes

Crap, missed… again.

1 Like

Oh it’s that time again! the monthly call is tomorrow Wednesday the 5th of May at 18.00 GMT UK time and 19.00 CET EU time!

check here for a link to the jitsi video room we chat in:Open Source Design monthly call - Open Source Design

Everyone is welcome! you don’t have to have been to a meeting before and we welcome new folks to join and chat! : )

You can scroll back up in this thread to get an idea of what we typically chat about.

1 Like

May 5th 2021

Mini intros round!
Briefly intro’d the core group: Open Source Design core team

Jobs

  • Eriol is now gonna close jobs that haven’t responded to the emails re. jobs being closed

  • The github bug is becoming more of a problem: Bug when inputting GitHub handle (?) · Issue #321 · opensourcedesign/opensourcedesign.github.io · GitHub can we pay to have it fixed?

  • Is there an easier way to create job requests? Posting jobs is a bit hard for people still - Can we spend money improving it and making it easier?

  • The pull request after submitting the form is pretty invisible to the job poster.

  • Is there an open source job board tool?

  • We like that it opens a discourse post on the forum to build community.

  • We want for Jobs:

    • Structure of a form.
    • x-post to the forum
    • Easy way to see status of job for poster of job.
    • Easy way to update for the poster of job.
    • Review stage for the job so that abuse is avoided.
  • AP: Eriol will make a github issue for the jobs page ‘wants’ and also make a discourse post < DONE

We could spend money on this to be improved! > Add to the spending money discourse thread: Let's spend some money! 🤑️

Nextcloud for OSD

Website updates

  • No big updates, people are working on the things in previous meeting notes
  • Core group discussed Matomo and analytics and metrics: Some differences in thoughts, Mention of for non-tracked, anon info. 'We would like to know info like ‘we had 600 visitors in May 2021 etc.’
  • So maybe an “investigation into how we can get basic (to be defined) analytics…with the possibility (if people agree) to put into place basic metrics”.
  • https://github.com/opensourcedesign/opensourcedesign.github.io/graphs/traffic
    https://matomo.org/
  • AP Eriol: Open up a dedicated forum thread about this analytics conversation. < DONE

Conferences

Spending money

  • Shall we spend a whole meeting on spending money?
  • Request that we be hyper-specific on what we want to spend it on. $5k
  • Spending on individuals vs. the collective.
  • What incentives do we need to give to have the website worked on.

PenPot

  • Import/Export in penpot.app is not supported yet.
  • Jan has set up a team and if you send your email to him then he’ll add you
  • Eventually, move the designs from Figma
1 Like

itttttttts Monthly call time again!

This call the core team would really like to focus on what we can do with our Open Collective funds https://opencollective.com/opensourcedesign

We started the thread here: Let's spend some money! 🤑️ - #8 by Erioldoesdesign

Would be great to see folx there, especially the @core-group (sorry for the ping!) :see_no_evil:

1 Like

Yup, yup, I’ll be there assuming nothing mad happens. :laughing:

I wrote some things that we might be able to use our funding for, I’ve posted them in the Let's spend some money! 🤑️ - #8 by Erioldoesdesign thread.

1 Like

Jenkins community experience of how they spend their funding

  • they’re similar to OSD - most infra is sponsored, they get donations and for the scale of the project (thousand of users) it’s tiny
  • they use their funding to pay for the projects own needs
  • they are covered in project roadmap, outreach programmes (targeted mentorship) or swag

The alternative is to use funding for covering infrastructure costs, day-to-day (subscriptions)

About mentorships, and outreach, they’ve had experience with Hacktoberfest

https://www.jenkins.io/event

  • Last year Hacktoberfest lead to ~ 400k pull requests as an event

Oleg’s comments are Hacktoberfest is good for one time contributions (you probably won’t get long term).

His recommendations are more towards mentorships/Summer of design/Halifax Mentorship (GSOC as a service).

June 2nd 2021

Mini intros round!
Briefly, intro’d the core group: Open Source Design core team

How to spend money

Additional thoughts on spending money

Open Source Design program

  • Summer of open-source design might only be able to be funded for 1-2 years
  • Eriol is talking to folks at Sim Sec re. Underexposed: Building a Movement for Secure UX – Simply Secure as a template of design internships
  • Conferences and companies ask us to deliver sessions and curate tracks so why don’t we reach out for funding to manage the continuing of this kind of work.
  • Summer of usability program was time consuming and expensive: (PDF) OpenUsability.org: Usability and Open Source
  • openusability.org
  • Outreachy is expensive £6k for an intern
  • GSoC could grow more design.
  • Can we dedicate time into this?
  • Partnering with another OSS project and pitch in part of the funds - umbrella org approach

Alternative to internship

  • Pick jobs on board and pay to have them done.
  • Complications around mentoring, coaching, choosing jobs and choosing who fills them.
  • Bounties are complex - are they contributions? or ‘Freelance jobs’ are you really ‘part of the project’ doesn’t work with a design process. Project doesn’t gain a new

New jobs board iteration

  • Funding the design & development of the new jobs board iteration
  • Scope for the jobs page
  • Fund that process that we advocate
  • Could we even do this before the whole website redesign?
  • Submission flow & Staticman
  • Then how jobs are displayed
  • AP: Eriol will look at the issues that already exist about web page design, job page improvements and then start to build a collaborative brief. DONE

Accessibility review of website

  • Producing educational material of this
  • Could detail the issues that we don’t have on accessibility add them to the repo
  • Scoped well and not too scope creepy

Other potentials from the doc

  • From the idea doc there are:

  • Open Source Design summit

  • Sponsor designers to go to OSS conferences + travel grants if in person events

  • Sponsor conferences on behalf of Open Source Design

  • Investigate providing infrastructure/proof of concept infrastructure for designers? tools etc.

  • Carry out some research on design in FOSS

  • AP: Eriol: Will set up an anon poll so everyone can choose what they would like to see funded and we can re-convene next month to see whether we are content wth a majority vote or not! < DONE

Mini intros round!
Briefly, into the core group: Open Source Design core team

Finished and updates on AP’s from the last meeting:

  • Sapatak is still working on a few PR’s and issues re repo merging and also redesign work.

  • Eriol: Will set up an anon poll so everyone can choose what they would like to see funded and we can reconvene next month to see whether we are content with a majority vote or not! < DONE

  • AP: Eriol will look at the issues that already exist about web page design, job page improvements and then start to build a collaborative brief. DONE

How to spend money

  • Some votes on the poll and there was some clarification on the options that Eriol made edits to
  • How long to keep it up? We loosely agreed another month and a half and review in August’s community call and September’s call can be the final one.
  • There are a couple of spending options that are ‘time sensitive’ e.g. collaborating with outreach on a fellowship/internship but they do two rounds per year so we won’t miss out, just have more time to prep.
  • Our money won’t disappear or be wasted if we don’t spend in a particular time frame so we can wait.
  • Eriol fixed the poll link in Nextcloud (sorry it was not public!) Vote on the poll by clicking here please!
    - AP: Eriol will create a discourse post for just the poll to vote on money spend and we could decide to tweet it too?

Repo stuff

  • Eriol cleaned up some issues, closed some old ones, commented on some, added a couple of new issues, responded to comments and request to pick up issues and started creating epics for collections of issues (using Zenhub extension)
  • lots of people want to pick up issues which is great! but we need more folks to lead on certain issues and tasks to guide and approve and review.
  • Should we look at ‘recruiting’ more code-related helpers to review PR’s and other things that are more code based?

Articles

  • Eriol has written 3 articles so far which you can read here:
  • Article wrap up from FOSS Backstage in PR form here and the first on the riseup document here
  • Mozfest 2021 UX Clinic wrap up second on the riseup document here (scroll down)
  • An article about the history of open-source design in response to this issue (also on the riseup document)
  • An outline of 'How to create a successful job on Open Source Design and get healthy contributions**

Jobs update

  • Eriol has messaged ALL JOBS! this is all people that have ever posted a job on opensourcedesign.net
  • See the google spreadsheet here
  • All jobs authors that have not responded by Saturday the 11th of July will be closed!
  • Eriol is working on the Jobs page epic here via a Figma file here (which will eventually be migrated to our penpot.app open source design team).
    - AP: Someone needs to check the jobs repo listing that are ‘closed’ match those listed on our jobs page live.
    - AP: Eriol will migrate this google spreadsheet to the open-source design nextcloud account at some point soon.
1 Like

Mini intros round!
Briefly, into the core group: Open Source Design core team

Finished and updates on AP’s from the last meeting:

AP: Eriol: Will set up an anon poll so everyone can choose what they would like to see funded and we can reconvene next month to see whether we are content with a majority vote or not! < DONE
AP: Eriol will look at the issues that already exist about web page design, job page improvements and then start to build a collaborative brief. < DONE
AP: Eriol will create a discourse post for just the poll to vote on money spend and we could decide to tweet it too? < DONE
AP: Someone needs to check the jobs repo listing that are ‘closed’ match those listed on our jobs page live. <DONE
AP: Eriol will migrate this google spreadsheet to the open-source design NextCloud account at some point soon. < DONE

Jobs postings and automatic discourse posts

  • Jobs postings and automatic discourse posts that are default as ‘unlisted’
  • AP: Eriol - Double check with Jan, open an issue to investigate if agreed.

How to spend money

  • Leave poll up until the end of August 2021
  • Is it the top 3 or top 1 that get chosen? How do we decide on the winner?
  • Concern about one option using ‘all’ of the budget and some options only using ‘some’ budget.
  • Outreachy have timelines so we need to consider timing if we did want to collab with outreachy.
  • AP: Eriol Post on the final deadline - logistics what happens afterwards with chosen ‘winner’
  • Currently winning is the ‘internship’
  • Existing discourse posts about spending money: Let's spend some money! 🤑️ - #10 by Erioldoesdesign

Articles

Jobs update

  • Since the beginning of the year eriol has gone through each existing job post, cataloged on a google spreadsheet OSD Open Jobs - Google Sheets (to be move into Open source design’s NextCloud account asap) and then emailed all job posters asking if they want their jobs kept open. Some conversations and feedback happened on email and many people did not respond within 2 weeks so those were closed.
  • Now all old jobs are closed and the only jobs visible on our jobs page are those still ‘open’ and receiving contributions.
  • AP: Anyone Two wrap up pieces of writing have been requested one that is about the processes and a second that is around metrics and some case studies of jobs that have or haven’t been filled.

UX & Agile

  • What are resources for designers in OSS to do better Agile
  • Basic stuff is still relevant - user-centric and testing etc.
  • Short cycles rather than front-loading

Academic work about non-devs in OSS

  • AP: Eriol will start something (Disocurse or a repo?) about papers/experiences of designers in OSS.
  • Autoethnographic pieces exists about experiences in tech and OSS but so much from a dev perspective.
  • We need more writing/content from designers in OSS’s perspective
  • Suggestions on doing live streams of design work and ideas have also been pitched in other OSS + design groups and in conferences. Video content could be made? @amit.lzkpa was running sessions like this for a while, mini ‘talks’ sessions just about what we’re working on at that moment (if not NDA restricted)

Mini intros round!

Briefly, into the core group: Open Source Design core team

Finished and updates on AP’s from the last meeting:

  • DONE AP: Core team - Double check with Jan, open an issue to investigate if agreed: Issue was opened here: https://github.com/opensourcedesign/opensourcedesign.github.io/issues/359
  • DONE AP: Eriol Post on the final deadline - logistics what happens afterwards with chosen ‘winner’
  • Currently winning is the ‘internship’
  • DONE AP: Eriol will start something (Discourse or a repo?) about papers/experiences of designers in OSS. → Eriol has started collecting papers in a notion page here for their PhD. They aren’t all about Designers exp in OSS but they are connected to design + OSS in some way. Eriol is going to move this to Github at some point but for now…Notion is a bit easier to populate a table :see_no_evil:

Not finished AP’s from the last meeting (SORRY):

  • AP: Anyone Two wrap-up pieces of writing has been requested one that is about the processes and a second that is around metrics and some case studies of jobs that have or haven’t been filled. Rise up etherpad here

How to spend money

  • Meeting with outreachy: Read the notes from the meeting here: Riseup Pad
  • Conversations finances
  • Conversations around mentoring
  • We need to have a series of conversations and session on what internship/mentorships could look like and map our options well!
  • We need to think about spending this not as a one time activity but as an ongoing process
  • partner for where we provide mentors to help them I’m 100% onboard with Outreachy
  • We happen to have a bit of money and are thinking about what to spend it on
  • If we do it the other way around, like fundraise for something specific, we can have goals etc
  • Just a thing to keep in mind regarding Outreachy: If we spend it on it, we basically donate it to an open source project, cause usually they need to front the money.
    And another option in the poll is “Select jobs from jobs board to assign paid bounties to them for OSS designers to complete” – which as far as I remember we didnt really want to do
  • I think we also never tried raising money. So if we spend and say we want to spend if we raise money, maybe we will get the $6k quicker next time?
  • maybe putting in the funding amount for something that grows the open source design community. not sure what could be those 1-2 aspects - branding, more community engagement, etc
  • Big question: What do we generally want to do (if money is no object)?

Other mentoring programs of note

Choosing OSS projects to join → how to decide

  • Jobs page is a good place to go
  • Most OSS get a little defensive when they get contributions!
  • Eriol’s paper recommendations: Paper Usability in OSS Alternate a web article Paper Gatekeeping
  • Sometimes jobs get posted but they aren’t 'ready to hear what it really means
  • A document of questions to ask to test how ready an org is would be useful. Susan (in a design community) wrote this doc for when you’re interviewing with design orgs
  • Most OSS orgs are very happy to receive contributions.
  • Good docs are a good signal. Especially if there’s a design specific docs
  • Chat channels and platforms to discuss the tool and ask for help.
  • No mention of anything user-related it’s probably not very ‘mature’
  • Find a docs writer or a product person or a design-friendly person.
  • I use the existence of documentation/a documentation group/discussion about documentation as a good proxy.
  • Discussing ways to “how to document the crazy UI” they’re at least thinking about it.
  • If 90% of the chat is about regex (or some tech-heavy language), even as a developer, I am going to get out of there
  • I think my favourite advice was just talk to the maintainers.
  • Having a good ‘first step’ into the OSS and figure out where the key areas to contribute is.
  • Look at a roadmap and where the org is headed to make sure that your contributions are ‘useful’
  • Some orgs don’t want contributors to be involved in the delivery pipe for important work due to bad impressions of how long contributors stay volunteering and how quickly they do work.
  • Bernard explained his approach: Do desk research on a project, lurk on the chat rooms for about a week, then ask user-related questions, depending on how they respond they decide to stay or leave. Most of the time people want you to do that work, then you get the ‘ohh this is hard’
  • Belén (another OSD member) says “open source is the slow food of software”. Inspired by ethnography - Research - Belén Pena
  • Saptak S (he/him) says: Apart from the chats (like IRC, etc.), documentation, etc. I always think looking at the issue tracker is also a good place to get an idea how much keen they already are about design
  • Who are the decision-makers in a project? find that out and engage. Talk to the right people.

Conferences!

Website OSD improvements and PR’s

  • Re. new design for OSD: Saptak is looking into restructuring more, so gonna take some time for the implementation of designs to finish, but fully welcome any design help.
    All the designs are by me based on some suggestions by Elio (another person from OSD), so I am sure needs lot of help. But everything is in penpot and open.

Cool Projects people talked about

Ahead of next weeks community call I just want to note that I reached back out to outreachy to give them the results of our poll and that we’ll start community conversations about what internships and fellowships for designers in OSS, supported by open Source Design will look like going forward.

Mini intros round!

Briefly, into the core group: Open Source Design core team

Finished and updates on AP’s from the last meeting:

Not finished AP’s from the last meeting:

  • AP: Anyone Two wrap-up pieces of writing has been requested one that is about the processes and a second that is around open source design jobs including some case studies of jobs that have or haven’t been filled. Please write directly in the Rise Up pad if you have ideas and don’t be shy! the doc is open and welcome to ideas. Rise up etherpad here

  • AP: Anyone: mini-guide on what design processes are needed within an org at high-strategy level and then individual products/services level → if anyone wants to start this guide writing go for it! :smiley:

Open Topic: Design cycle of a project via Abhishek

  • A cycle for design?
    • When a PR for a small feature is merged it can be ‘done’ but not done-done as there can always be improvements on the feature.
    • How are further feature requests gathered and included?
  • Does an OSS product ever have a design ‘finished?’
  • What does the continuous design process?
  • What does the design person do after things are finished and usable?
  • The inherent answer to “does a company need Design” is usually YES (just like “do you need excellent system engineering”, the answer is often the same = YES). The ‘what kind of Design’ is the finer detail… would be good to draft a mini-guide (I’m sure it’s been done before). I know that the Linux Foundation could use such a decision tool, and the LF Public Health arm specifically needs it.
  • A lot of good design work I have seen folks do almost always starts and involves a lot of user research
  • Marie Nordin re. great open-source design in Red Hat.
  • Can we use a real project as an example?
  • Products evolve over years design tools was used as an example? What level are you coming in at?
  • it’s more like the feature is done for this iteration
  • MedicMobile is a good example of continual funding model of OS

Open Topic: UX maturity in OSS

  • We took some time to read this Maturity scale that Eriol created
  • “Design has an ‘output’” I think this point applies to development as well sometimes, depending on the team and manager.
  • User Lead = is that The PInnacle → the philosophical bend, yes but as a selling point of Design. it’s the value of the process at the exec level. Where of course, the human that’s using a service, is the atomic unit.
  • What maturity is it when Design is Written into the Ethos/Company Rules of Engagement?
  • Feedback: After point 5 the progress is too steep and needs work so point 6-8.
  • I’m also seeing your curve of engagement.
  • Absent vs misunderstood is pretty interesting → described as when an OSS org has a misconception of design as a certain ‘thing’ e.g. you are a designer and you make UI only. Stage 0 describes an OSS that has no or minimal pre-concieved notions of what a designer or design does.
  • Feedback: Nimisha mentioned a part of the OSS design process where some maturity stages are impossible or next to impossible so how do we surface this as a consideration within the maturity resource.

Poll results: Open Source Design fellowship/internship

  • We’ll talk about this next time! :slight_smile:

Cool project we mentioned

  • MedicMobile is a good example of continual funding model of OS

We have our community call next Wednesday 3rd November at 19.00 CEST :smiley:

Mini intros round!

Briefly, into the core group: Open Source Design core team

Finished and updates on AP’s from the last meeting:

Not finished AP’s from the last meeting:

Open Topics:

Hacktoberfest

  • Merge requests not being valuable in exchange for schwag
  • Does hacktoberfest work for open source design? talk topic!
  • Not just a hacktoberfest problem a general design problem.
  • Linux Foundation is struggling with the same concept, just not in 1 month but overall
  • How can design work outside of hacktoberfest too
  • How big is the project? how aligned is the “new” design? (ie context of contribution also matters)
  • We talked about how Eriol had onboarded designers in OFN
  • Opening up research and insights into design thinking can help designers contribute more legitimate and informed design work rather than design work not informed by the realities of. the project. Eriol shared an example of when this happened in OFN.

##FOSDEM Dev room

FOSS Backstage

Open Source Design fellowship/internship

  • Short meeting today so this is pushed back
  • AP: Eriol still has some comms and wrangling to do on this topic

Cool projects