On 27 Oct 2011, at 01:28, Gary Neely wrote:
> The #1 reason I haven't added my projects (MD-81, Grumman Goose,
> Edgley Optica, Velocity XL RG) to the repository is that I have no
> ability to perform my own commits. Possibly I haven't earned the right
> and I can understand that. But I would like to learn and understand
> the procedure for how one earns these rights, and maybe others would
> too.
The procedure is to ask :)
Actually, that's not quite accurate, but, the procedure is to ask, *having
demonstrated yourself to be a sane and reasonable person who's likely to stick
around longer than four weeks*. I'm a bit more liberal in this regard, but
essentially anyone who's contributed a moderate quality aircraft, or provided
10+ 'good' patches to existing aircraft, I'd be happy to grant them access.
I'm aware that the bar *appears* to be set higher than this, but personally I'm
happy to liberalise it a bit - the problem is keeping the sense of etiquette
that other contributors assume and rely upon. So a period of indoctrination is
good, of submitting merge requests and getting some feedback, but it can become
a habit, when it doesn't need too.
'we' (the infamous FlightGear we) should probably write a wiki page of
aircraft-contributor-etiquette, so we have grounds to revoke people's access if
they break the rules. Though just about the only rules I'm aware of :
keep it GPL;
don't modify other people's work without asking, or trying to ask;
try to avoid copy-and-pasting when you can share files or scripts
between aircraft
... and I only stuck the last one in because it's a pet hate of mine :)
James
PS - Gary, in case it wasn't obvious, send me your Gitorious username details,
and I shall sprinkle the magic fairy dust...
------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
