Topic on Talk:Outreach programs/Possible projects

I suggest we scope the featured code-related ideas at about 6 weeks of coding work to ensure we dedicate enough time (out of the 3-month period) to bugfixing and code review. Past proposals often allotted either no time or about 2 weeks for merging with trunk, pre-deploy code review, and integration. That's not enough. If skilled developer thinks that a project might take about 2 weeks for a skilled developer to code, then that's a good sign, in my opinion. Students run into lots of problems, and your 2-week project is someone else's whole summer or winter.

Just a reminder. :-)

Yes, indeed. I will add this to the lessons learned, which is also the checklist for future programs.

This post was posted by Qgil-WMF, but signed as Qgil.

See "The core tasks shouldn't take more than 50% of the available time." at Mentorship programs/Lessons learned. Thank you again.

This post was posted by Qgil-WMF, but signed as Qgil.