Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: > And regardless of the danger, if I look around me, I see almost only > people working with shared archives, and a few projects (including Git, > obviously) using the "one commiter per repository" workflow (I teach Git These days, you do not have to even go to kernel.org to find people and projects that use "publish to be pulled" model. I hear that there is a popular site called GitHub where people create their own fork, publish their work there and ask the project they forked from to pull their work. By the way, don't we ask the workflow used by the users in the annual user survey? > 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", I would count that as a datapoint that represents one project among thousands of projects that use Git. I am also curious to learn a bit more about "a complete disaster", 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. -- 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