Again to recap we had 35 responses and the leading choice to 'spend our time, attention and money as a community was: ‘Open Source Design internship program. Collaborate with Outreachy or a similar OSS internship program to fund an ‘OSS Design’ specific program’ with 18 votes.
What I’d like this forum post to do is capture thoughts about what an Open Source Design internship program could look like so here are a few guiding questions if you want to use them.
What would you want to get out of an Open Source Design internship/fellow program?
What would you be willing to give to a Open Source Design internship/fellow program? (e.g. X hours per month, mentoring, office space, review applications, review OSS projects, plan the design work for the intern/fellow etc.)
How would you like the program to gather OSS projects that could benefit from the fellowship/internship?
Is there a kind of Open Source Design we want to prioritise?
Should we spend some of our Open Collective funds on this and if yes, how much?
How long should a Open Source Design internship/fellow program last?
Could the Open Source Design internship/fellow program include participating in OSD’s community as part of the project? e.g. a FOSDEM talk, articles for the OSD website? and what is appropriate to ask?
There’s lots more we can discuss but hopefully, these start the conversation
As a beginner, what I would like to get out of an open source internship is to be well equipped to be able to contribute to projects, be grounded on the technical aspect of git & GitHub.
I also think we could reach out to big companies in the tech community to get involve in the internship program, showing them the reason why they should invest in design and OpenSource Design as the bigger picture.
Lastly, (I apologize for suggesting a lot…lol) I think the internship should last for 2-3 months.
A big problem is getting a design implemented. Developers in open source projects pick according to what they want to work on (or what their bosses want them to work on) and these are rarely user facing improvements.
One thing we could do to support a designer and a developer as a team working on a small project. I see several interesting advantages here:
The improvements will actually be part of the software instead of likely staying in plans and mockups.
Which is also something directly helpful to open source projects increasing motivation for mentoring both designer and dev.
Have both participants learn to work with a designer/dev, respectively.
Working closely together also decreases incentives for big-plan-upfront design (or coding!) making it an interesting case for close collaboration
Could yield some great reflections and experiences that help us in future projects.
Now, two people is twice the money needed. But…
I think it would be relatively easy to get the dev funded by someone other org.
The gain gets more graspable for tech orgs who can fund. If we have the collaboration build in we can sell it not as design being produced but as bringing well desiged features to a software project.
Just like we are, funding orgs will likely to be interested in the collab aspect more than in the mere design aspect.
If people apply directly in groups there is a higher chance that they can work together already and get along.
If people apply alone and are matched later we do not know how well they work together. On the other hand, most work will happen online and both dev and designer need to work with people from the open source project they do not know before, anyway.
We could also combine both: Present project partners, have a matching phase where people can form groups and then have an applications phase where groups apply.
Would you mind if I looped Sage from Outreachy back into this conversation? I don’t think they are on this forum so it’d probably be email/twitter DM but i’d love to see what they think of our proposal re. designer + developer team
@Erioldoesdesign Find a time that works between interested folks from Simply Secure & @jdittrich and other fellow/intern interested folks
@Erioldoesdesign and @ei8fdb and @SaptakS to find time to do a ‘hack day’ with a spreadsheet and go through all known internship/fellowship FLOSS programs and make a ‘matrix’ of what happens in these typically and what we think we want to leverage.
I’m currently a mentor for a design internship for an OSS. I can speak on my experience, if that helps OSD form their own design internship.
The internship is focused on making Real Time Collaboration (RTC) tools more accessible. The long-term goal is to take these findings and make JupyterLab’s RTC more accessible.
The internship work itself is more about user research than visuals. Focused on gathering the pain points of current RTC disabled user experience. Our intern conducted interviews and audits with volunteers. The volunteers were a mix of OSS developers and from the disabled community.
The end-result will be a written document with these findings. With the 3 month span of the internship, there’s isn’t time to implement these findings. However, we want to spread these findings and help OSS developers make more accessible OSS. One possibility is that these findings be implemented and work in tandem with JupyterLab accessibility grant.
1 hour meeting once a week
3 months long
2 co-mentors and 1 mentee
Compensation: $1000 USD/month (for full-time at 40 hrs/wk) - our intern is a student and part-time
There’s been more focus recently in having non-code internships! In the application, it states “We are also actively working on the technical writing design, and accessibility spaces and welcome applications from folks interested in these areas.”
In this case, we have a company as a middleman between the projects and interns.
There is an Internship Coordinator who reviewed and interviewed applicants before matching with an existing internship opportunity.
Unusually, in this case, a UX/UI student approached the company about doing an internship. At the time, we didn’t have a design internship available. But our Internship Coordinator asked a designer at Quansight and we made one, based on JupyterLab’s accessibility aims.
So a design internship was created by an intern asking for one, but there was a larger framework to move that forward (company internship program). I don’t think the internship may been created with a less direct request or existing internship framework, such as a forum post in an OSS project.
I could speak more about this in the next OSD monthly call, if anyone’s interested. I was at this month’s call and saw the recent agenda on internships, which led me here.
Here’s what I’m thinking. We hold a BootCamp - using the word BootCamp for lack of better words, where interested designers are shown the way around GitHub by fellow designers . Could be held monthly, perhaps. Could be in batches of 10 designers. Designers who complete the brief exploration course could be instructors for the next iteration. That way our reach broadens. Do we have a discord group or slack?
During such meetings, Open Source Project maintainers could be invited to give a walkthrough of their projects where help could be offered. In that time, Open Source design would have put together a form of contribution heuristics for opensource projects, could even help such projects establish a pipeline to encourage designers to come onboard.
Hello Joshua. Great idea, we have some of these plans written down and are working towards actualization. If you don’t mind we can have a call and discuss some of your ideas and how they align with ours. We can begin working on programs like this for open source designers