Simplify checklist for weekly participation
I know this is already somewhat covered in the guide already, but I think we need to make sure we have it simplified somewhere what is needed for tracking weekly progress of the contributors.
-
A single specific https://openbeagle.org/gsoc repository that shows daily commits with comments -
Tracking issues in that repository -
An issue that tracks hardware required to execute the project, such that it is always clear if the student has the hardware yet or not -
Submodules or other suitable links to related source projects (submodule updates can include comments to help track development in one place) -
Work-in-progress feature branches if attempting to keep main
clean with daily commits -
Some kind of CI such that we don't have to ask how the project code is built -
The weekly report should be submitted on-time such that mentors can review the status ahead of the weekly all-hands meeting -
A mirror of any significant code repositories should be setup on github.com -
Mainline submissions should have milestones and links to submissions (mailing list archive or public pull request) should be included in the weekly reports
Overall group issues can be tracked via https://openbeagle.org/groups/gsoc/-/issues
Overall group activity can be tracked via https://openbeagle.org/groups/gsoc/-/activity
These should be heavily utilized to know what is happening. If a student goes a few days without a commit, it needs to be known ahead of time and excused that they are taking time off.