...
To participate in Dev Days, the project needs to have a few things set up to make it easy for participants to identify issues and work on how to get engaged with the project.
Tag issues
...
for Dev Days participants
...
To have an issue be marked for Dev Days participants to choose from, make sure that the issue...
...
- Specific build instructions ( you might already be able to reference this in documentation, but you could also detail any first-timers' gotchas ).
- Communication preferences for the project ( is it best to ping on Slack? Mailing Lists? What times are other project members generally available? )
- Anything non-obvious about the project or not well documented that would confuse a first-timer.
Choose A Dev Days Project Lead
Participating projects should have a member of their TSC specified as Dev Days Project Lead. This person will be responsible for organization on the project side, as well as communication between the Project and the Dev Days team. This person should fill out to project registration form below!
Register as a participating project.
...
The two days of Dev Days can be a whirlwind! Even with good planning, expect bumps along the way with participants having technical issues, questions, etc. Be empathetic with these participants; most have good intentions and are participating in open source for the first time. This article is a good read that will help you understand the journey from first-time contributor to maintainer in an open source project. We expect participating projects to plan for having at least one core developer available at a time to answer participant questions and review PRs.
After Dev Days
Once Dev Days wrap up, hopefully, you will have some solid contributions to your projects. If you have a few that are close but aren't quite there, help the participant finish things up.
...