On Mon, Mar 9, 2015 at 2:57 PM, Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> wrote: > Christian Couder venit, vidit, dixit 07.03.2015 08:18: >> Hi, >> >> On Fri, Mar 6, 2015 at 6:41 PM, David Kastrup <dak@xxxxxxx> wrote: >> >>> At some point of time I think it may be worth reevaluating the toxic >>> atmosphere against freelancers doing Git development. >> >> My opinion on this is that the Git community has not been good >> especially lately at promoting its own developers. >> > > I guess we have at least 3 kinds of people here: > > A) Paid to do Git development, at least as part of their job. > B) Freelancers who don't get paid directly for "doing git" but hope to > profit from their git efforts directly or indirectly. > C) Doing it in their freetime (or as minor, inofficial part of their > non-programming job). > > I'm in camp C and honestly wasn't aware of camp B until now. > > I consider camp A to be beneficial for all of us, and I don't think > specific employer interests have pushed the project in specific > directions, or specific features (OK, maybe one, but not as a rule). > > I do see that remuneration is an issue for camp B. First thank you for responding to my email. It is great to see that some developers are interested in talking about this. I am in camp C and I think the people in all the camps are beneficial for all of us. >> Some facts: [...] I don't want to write again about each of these points now. I am more interested in discussing a good strategy to try to revert the sad trend of Git developers being promoted less and less, because I think that it is really very important. >> None of these facts is a big issue in itself for me, but I think the >> trend is very sad, and I would be happy if we could discuss here or at >> the Git Merge (or both) about ways to improve in this area. > > There should be a good occasion, after we see how it went, and hopefully > also to sort out any apparent misunderstandings from the past that have > resurfaced in this thread. > > Maybe, all we need is badges? [1] > > [1] https://badges.fedoraproject.org/ My opinion is that the big issue is that we should all realize how important it is to promote the Git developers. There are people who say out there that GitHub succeeded mostly because they easily allowed developers to build a portfolio. I think there is some truth in that. And I think GitHub also says to developers that it's good for them to have a nice GitHub portfolio and to employers that it's good for them to hire people who have a nice GitHub portfolio. This shows that the success of GitHub (and so of Git too) is based in part on promoting Open Source / Free Software developers. So why don't we try to do it more (instead of less) and how could we do it more (instead of less) for the Git developers? Yesterday evening I attended a Docker meeting in Paris [1] where Jérôme Petazzoni a Docker developer working for Docker gave a talk about Docker storage drivers. In the middle of his talk there were at least 2 slides dedicated to thank some developers who helped make Docker work with different filesystems or operating systems. And Jérôme did stop at least twice to thank these people in the middle of his talk. Wouldn't his talk have been smoother if he had not done that? So why did he do that? This reminded me about the following great talk by Julien Barbier the Community and Marketing guy at Docker: http://www.slideshare.net/julienbarbier42/community-marketing-42674728 I had seen this talk last december at another Docker meetup in Paris (and I think it really worth reading the slides or attending the talk if Julien gives it again and you can go). The slides and the talk keep repeating some sentences because they are worth repeating. Some of these sentences are: * It is about what you can do for your community * Belonging, recognition, respect, love * Add more links to your community * Your product is not what you say it is, it is what THEY say it is * It's all about people It is especially interesting to have a look at slide 5 where they say that "Community is the new marketing" and that Community is 80+% of their marketing. And it's true that they are really doing a lot for their community. For example the meeting yesterday evening was the 19th docker meeting in Paris in two years. And then there is slide 20 about "Content Strategy" where there is: * Encourage your community to build content - Say thank you, repost, post, upvote, RT, include them in your newsletter, itw them, … - Belonging, Recognition, Respect, Love * Your team is your community too! - Say thank you, gamify, hall of fame, tweet, post, recycle, etc… - Belonging, Recognition, Respect, Love So we can see that "saying thank you" is a big part of their content strategy. And are they successful? Yes, they are very successful as an open source project [2] and as a company. Now it's up to us, either we keep coming up with excuses not to promote developers, or we decide to do something about it. Best, Christian. [1] http://www.meetup.com/Docker-Paris/events/220891955/ [2] http://stackshare.io/posts/how-docker-manages-its-massive-open-source-project -- 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