I guess someone has written in a management book something like
"Don't drive anybody into a project management tool that you are not using currently yourself." :)
On 05/09/2013 11:51 PM, Yury Katkov wrote:
What tools do you use for a small tasks in Google Summer of Code? I mean the tasks like "prepare the working environment", "learn gerrit", "write a blogpost", etc.? I thin that bugzilla is too heavy for this purpose.
The Bugzilla reports are there only for the usual Bugzilla workflow, hoping to get RESOLVED FIXED & VERIFIED by the end of the program.
What about the project wiki page? It's _just_ a project done by one student in about 4 months. It seems a sensible default: light and easy to learn, no extra registration required, transparent for anybody willing to watch and follow, free software, etc.
Also can we use microblogging for reporting the current progress (in addition to posts in a blog one in 2 weeks )? I tried that once and it was very fun and efficient.
"Fun and efficient" should be indeed the motto. For different people this means different ways of reporting, though.
The Wikimedia Engineering team has a discipline of monthly reporting and this is the minimum we are going to require to our GSoC / OPW interns, starting with the monthly report for June. Every participant will be asked to provide a URL to their monthly report, to be included in the Mentorship programs report that we publish at https://www.mediawiki.org/wiki/Mentorship_programs/status
That URL can point to wherever the student prefers: a section in the project page, a comment in the Bugzilla report, a post to the relevant mailing list, a blog post...