Starting off the discussion with some of the ideas from March 2021’s community call discussion:
Some ideas for the jobs page improvements:
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.
We could encourage a discourse forum post immediately after the job post PR is accepted to get better responses.
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.
We could also be: Keep for X weeks or so. Does not need to be called deadline Or “Receiving submissions/applications until”.
Categories for the jobs posting form and forum e.g. Logo, UI, UX, Research.
Support to write your design needs via a call Scott Jenson suggested this.
‘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 and the jobs page out of the OSD open collective funding pot?
How will maintenance happen?
Should we rename it from ‘Jobs’ to something else? Like ‘Contributions’, ‘Tasks’ or ‘Opportunities’?
Small point: is there a default title for postings? This is a shot from the jobs page just now. If so, just remove it to they have to type something a bit more descriptive?
These ideas are a great starting point.
I do however have some different concerns around this redesign:
Since I cannot fully understand the context, I am not sure that I can contribute something which is “on point.”
I would suggest defining a list of the users as well as problem statements.
Who are the main users?
What problems does this page solve for them?
What value does this page offer?
It would be interesting to define this to be reused in the actual jobs (challenges?) themselves.
There can be several advantages to this:
It will help contributors align and know what to design for
It will make design feedback clearer
It will help newer members get acquainted with a more basic design process (a single but focused page seems perfect for this)
Evaluation will also be easier later on
Let me know if you agree, and we can look at this more in-depth.
I completely agree, in terms of streamlining contributions. I believe we can pick up pointers from the current home page and manifesto to inform decisions about the end users.
I just saw Scott’s reply on the other thread, where the discussion is around doing some research on the interested org’s side and defining their needs. @scottjenson perhaps we could combine these?
Apologies, I’m happy to let Eriol take the lead here. I was more or less offering my services to run the calls, write up the notes (if that was helpful) Eriol, if you’d like some help during that week of 31 March, just let me know
I was talking with @milapbhojak about improving the Jobs page this morning and he mentioned his thoughts around the fact that designers new to open source really could benefit from a more consistent mentoring relationship.
We chatted briefly about each job needing to have a designer assigned as a mentor so they can ‘shepherd the process’ from submission to contribution. I’m doing this with my job for the OFN: Jobs - Design contributors wanted
But what about job postings that don’t have designers on the team to look to to ‘shepherd?’
