On Feb 15, 2011, at 1:52 PM, Christian Boos wrote: > Hello Roman, > > On 2/15/2011 12:09 PM, Roman Prykhodchenko wrote: >> (snip) >> There some big advantages in such collaboration for all participants: >> - You get a contributor that is interested in working on your project. >> - The student gets the experience in working on a real project. >> - If Trac is interested to student he will continue working on it >> after the science project is finished. > > Well, I'm not really convinced. Working on a project like Trac means you have > a genuine interest in moving it forward, mainly because you're using the > software, and care for it. Getting a good mark is certainly some kind of > motivation, but perhaps not the fittest. Now if the student himself knows and > is interested in Trac, maybe. But then...
Getting good mark is a good motivation of course but not the only one. I'm going to show them some projects and every of them will chose one project that is interested to him or her. Students already know what the project tracker is and what tasks it allows to solve so there can be one who would like to work on some project tracker. I will give students a chance to work on a specific project only if it is interesting for him. > >> I will not require any payments for the student. > > !!! > > The fact that you even raise this point is troublesome at best. We're all > volunteers here, and don't make any money by working on Trac. I may be wrong > but it seems to me you're not very familiar with how open source projects > work. > I understand that Trac is built by volunteers as well as I understand the importance of the opensource community. My idea is to give students the opportunity to become the part of the community to understand why does this community exist and why it is very important to bring own contribution to it. I wrote about payment to make you sure that the students know that all projects they will be working on are developed by the community for free. > What IMO would be a better alternative approach to what you proposed is that > you and your students could *use* the Trac software for managing the software > projects of your students, that you would then *adapt* it to your needs or > add some features (if you don't know where to start, there are lots of ideas > you could find on trac.edgewall.org, eventually starting with the "bitesized" > tickets), and if successful, contribute back what you did. This doesn't > prevent any kind of collaboration between more seasoned Trac developers and > your student(s), like we try to do for any other contributors (as time and > interest permit). > > -- Christian > > -- > You received this message because you are subscribed to the Google Groups > "Trac Development" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/trac-dev?hl=en. > - Roman -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
