"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > 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. I do not think this was a mistake at all. It is like you and Luiz and/or Dscho and Carlos wored as two teams --- the discussion among the team members done in order to come up with the best possible submission that can be presented to the cummunity does not have to be made public. Think of a case where such a team happens to consist of a single person --- we do not expect all the "thinking aloud" that goes inside that person's head to come to the list to be commented upon. The fact that the teams had more than one person in them does not mean their "thinking aloud" should be done publicly on the list. You can send out "this is still a rough idea and still not ready for inclusion, but..." feelers to ask help from the community, but you do not have to if you do not want to. That applies to both "one person" teams and "more than one person" teams. After polishing what to be presented internally inside the team, the team's representatives (Carlso and Luiz) presented their material to the public on the list, and from then on they had to defend, adjust to public comments, and improve what they presented, just like everybody else. And both teams did exactly that as expected, probably surpassing the community standard. In the early days of git when I was feeding patches to Linus, something similar happened, too. The last round of diff-raw format specification was done almost completely offline between Linus and I by accident. But the process after the submittable drafts were prepared, they went through the usual "list to mbox to application after discussion" procedure like any other patch series. - 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
