You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In preparation for a Django-focussed hack day (#18), identify suitable active projects in the WHFNP GitHub account that can participate in the day, and communicate with project leads in order to organise their GitHub repos so that there are tickets volunteers can easily pick up on the day, and that mentors can easily assist them with.
This will also help us experiment with streamlining some of our GitHub flows (e.g. labels, README formats, pull request process, etc) across projects, thus working towards a better method of linking new and existing volunteers to pieces of work they can pick up without too much overhead.
Tasks
Whoever picks this up, feel free to create separate tickets and reference this one for each of below if needed
Make a list of WHFNP projects that are Django-based and active enough to participate in the day: Ticket 21
Contact PMs / project leads and help them identify + create isolated GitHub tickets that both team members and other volunteers can pick up on the day, labelled by skill level required, type of work + any other handy labels. These issues could be UX-based, code-based, or things that need review as some examples.
As part of these findings, create a wiki page in our WHFNP wiki that documents this way of organising GitHub tickets and links to example repos for reference. Can also include collaboration process HOWTO, e.g. open a pull request, code review etc
The text was updated successfully, but these errors were encountered:
Relates to #18 (Host Django-focussed event)
What
In preparation for a Django-focussed hack day (#18), identify suitable active projects in the WHFNP GitHub account that can participate in the day, and communicate with project leads in order to organise their GitHub repos so that there are tickets volunteers can easily pick up on the day, and that mentors can easily assist them with.
This will also help us experiment with streamlining some of our GitHub flows (e.g. labels, README formats, pull request process, etc) across projects, thus working towards a better method of linking new and existing volunteers to pieces of work they can pick up without too much overhead.
Tasks
Whoever picks this up, feel free to create separate tickets and reference this one for each of below if needed
The text was updated successfully, but these errors were encountered: