Hey Yaron,
On Thu, Nov 3, 2016 at 5:34 PM, Yaron Koren <yaron(a)wikiworks.com> wrote:
But I hope that there's a better solution for it
other than essentially
requiring potential students to become detectives, trying to find
interesting coding challenges that no one has proposed for GSoC etc. Maybe
the solution is for you and others to do this work yourself - talking to
MW/WMF developers to find more tasks and drum up enthusiasm among potential
mentors - essentially what you did before, but now as an administrator and
not a potential student.
Thank you for the trust Yaron, but here we are talking not only about new
tasks being up in Phabricator for students to charge upon, but to increase
the quality of students itself before they start working on the project.
Performance report of a student in that kind of a program even can make it
easy for a mentor to better evaluate his/her proposal (considering past
contributions matter). More than that, this would be one good option for
post-GSoC students to still stick with the community too - as they can
either participate, or even be mentors again.
Yeah - we are trying to solve actually two problems here - (a) better
community code review and codebase aware students before GSoC (b) making
students stick back with Wikimedia after they complete their project.
Thanks,
Tony Thomas <https://www.mediawiki.org/wiki/User:01tonythomas>
Home <http://www.thomastony.me> | Blog <https://tttwrites.wordpress.com/> |
ThinkFOSS <http://www.thinkfoss.com>