Alex Riesen <raa.lkml@xxxxxxxxx> wrote: > > * How mentors and representatives of development communities can > > help one another > > Maybe by having a knowledge base with a well-known location of the > issues related to mentoring. For Git, it seemed that almost no one > knew what the GSoC participants actually did. It would be interesting > how the other GSoC project dealt with the transparency. Yea, that's a valid point. I think we were quite lucky on our selection of students, Luiz and Carlos did some great work and really didn't cause any sorts of mentoring issues like some of the other organizations have had. Dscho and I both developed good relationships with them and never really had an issue with them wandering away, producing garbage code, etc... Both of our students kept git.git forks on repo.or.cz, and I know they both pushed their work out there on a regular basis. For Luiz and I that was one of our primary means of communication, was me reading through his recent changes on repo.or.cz after pulling it locally to a git.git clone. So it wasn't an issue of the information not being made public, it was more an issue of it not being *advertised*. Git is however very centered around this mailing list. A lot of the communication between mentor<-->student was done by private email and IRC. That means that a lot of the traffic was not really visible in the medium that our community expected to see it in. Perhaps it was our mistake as mentors (Dscho and I) to not have moved many of the discussions (especially later in the GSoC period once our students were comfortable with Git) onto the mailing list. This is one thing I'm interested in talking to some of the other orgs about. I know a lot of them have kept blogs, mailing lists, etc. In larger orgs (say KDE) making a GSoC specific mailing list almost makes sense. But many times when you find these mailing list archives most of the postings are just status reports from the students, with almost no (if any) discussion. So even though the information is there the community doesn't follow up on it, doesn't care, etc... -- Shawn. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
