| | |
---|
OMRS17 | Â | |
OCL Module | @raff | |
Modulus server being decommissioned | @Darius Jazayeri | |
Reference Application | @Stephen Senkomago Musoke | |
Platform | @Irene Nyakate, @Wyclif Luyima, @Burke Mamlin | |
GCI | @Ivange Larry Ndumbe | Leaned a lot on a few mentors who were doing the heavy lifting for GCI task review Could have used more mentors with technical skills this year Mentor team was limited to previous GSoC & GCI students and mentors Many mentors were too busy during GCI Have moved on to curated tickets Students have blown us away For future GCI: Experienced mentors Understand availability of mentors ahead of time Be clearer with expectations Consider having mentors sign up for specific hour(s) It would help if mentors could be assigned to particular types of tasks Try to find ways to motivate mentors for availability.
Some mentors seem to get tired along the way. Expectation: 20% of mentors active, 40% fairly active, 40% not active or unseen Did not have statistics to help getting started How many tasks needed up front? What types of tasks are needed? e.g., some tasks (like video tasks) can be done by many students; however, coding tasks cannot easily be taken by many students without creating confusion How many mentors are needed?
Start preparing for GCI 1-2 months earlier (before announcement) to get more coding tasks prepared Consider creating a document like So you want to be a GSoC admin? for GCI admins.
|
Andela | @Daniel Kayiwa | Â |
pmtool | Â | Â |
Scrum of Scrums | Â | |
PM Activities | Â | |