Hi fellow wiki editors!
I have tried to keep the template short, but meaningful. /Johan G
If this experiment is meant to become a community experience, for both developers and users, how about enabling mob access, too ? There are often people that are neither core developers, nor aspire to become one, but who are technical users who'd like to more easily submit patches. While most long-term FlightGear users know about the fact that "FlightGear life" takes places on the mailing lists, many others often just end up sharing patches via the forums, sf.net patch trackers or even via IRC. So, this would be an extremely easy way for potential contributors to more easily share local modifications with fellow users, without having any effect on any of the trusted main branches or organizational burden on the project lead, so it would sort of become a "sandbox" environment with "wild" code. Core developers could more easily keep track of patches submitted this way, too.--MILSTD 07:29, 4 February 2009 (EST)
The mob branch idea is intriguing, but it is so easy for anyone to set up their own forked flightgear repositories, especially on repo.or.cz, that I don't think it's necessary to enable the mob branch. It's really more useful to be able to say "pull the foo branch in my repository" than "pull my cool commit out of the mob branch."--Timoore 05:24, 5 February 2009 (EST)