Junio C Hamano <gitster@xxxxxxxxx> writes: >> to 200 students and several colleagues every year, I've tried teaching >> the "one public repository per developer" and it was a complete disaster). > > Interesting. I have a couple of questions. > > Who are these 200 people and what do they do with Git? If the > answer is "They work on a class assignment project, 20 teams of 10 > members each", Teams are smaller, but that's essentially that, yes. I'm not saying it's representative, my point just that I do have experience teaching Git to new users. > I am also curious to learn a bit more about "a complete disaster", There are several points: * It is often the case that one of the member of a team is more knowledgeable than others. Then, this user can set up a shared archive, and other users do not have to. When your project is open-source, it's rather easy to click GitHub's web interface and create a fork, but when it's a private project (and you don't want to pay), you have to do some kind of magic with ACLs or so to create a new repository. Doing this magic just once saves a lot of trouble. In practice, when working with colleagues (all being computer scientists), if I don't set up a shared repository, they just send me their files (yes, their files, not their patches :-( ) by email and ask me to do merges if needed. * Users like to know where "the latest version" is. They are already confused by the fact that the last local revision may not be the same as the last remote one, and having multiple public repositories adds to the confusion. > even though this question (and its answer) would not be directly > relevant to this topic, as nobody is trying to convert projects to > use the "publish to be pulled" model when the "push to the shared > central repository" model is more appropriate for them. Sure. I'm not saying in any way that the "shared repository" is superior. Just that it's easier to grab for newbies. -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- 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