Hi, On Thu, Jun 13, 2013 at 12:19 PM, Thomas Adam <thomas@xxxxxxxxxx> wrote: > > So these guidelines gain the community nothing, and only serve to punish > those who are already following them, without them being written down, > because the root-cause of the problem is still here, and isn't going to go > away, no matter how much referring to these guidelines might help. > > That is why I think this is the wrong thing to do. I don't know if some guidelines will gain the community anything, but there might be another solution to the current problems in the community along the following lines: - decide that later this year (for example next october or september) there could be a developer meeting/conference/merge/gittogether/whatever somewhere in North America - ask many developers who contributed to Git significantly, including those involved in the last flamewars, if they could come and if they would need financial help to come - ask some companies to sponsor the meeting by providing money, space, food, beer, accomodation, whatever they want - maybe ask Git developers or users living neer the meeting place if the developers coming could crash at their place - announce the meeting, thanks the sponsors, by the way thanks a lot GitHub for the git merge 2013 last May in Berlin - meet, discuss stuff, have a lot of beers together, write stupid joke patches together and send them to the list - reimburse the developers who came for their travel and if needed accomodation expenses - thank everyone for coming and having a good time together and thank the sponsors again, by the way thank you guys who came to the git merge 2013 and thank you again Github, for organizing it and Uber and Google for sponsoring it It might not work but it might be a nice try :-) Thanks, Christian. -- 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