> Hope so ;-)
>
> With the current setup you can for example commit (and accept merge
> requests) for your EC130:https://gitorious.org/flightgear-aircraft/ec130
>
> But I want to give commit rights to my wife to my repo, without asking
> you, can I do that ? Why not ? What gives "the team" the right to decide
> if my wife could be contributor in my aircraft project or not ?!
>
>>
>> When you start on a new aircraft and would like to have its repository
>> >>under the FlightGear Aircraft project, you
>> do have to ask one of the people from "the team":
>> https://gitorious.org/>>+flightgear-aircraft
>
> For every single aircraft ? Hm, everyone ?
>
>> You also have to contact that teammembers when you'd like to get access >>to
>> an existing repo (or give someone
>> else access to your aircraft's repo).
>
> "Sorry, Peter is not here since six months, but Paul - ok, he does not
> know a lot about your project - but he will give access to Alex, to
> update Sabins repo permissions."
Hmmm... yep, that are indeed some good arguments.
It would even allows to have duplicate aircraft, maybe even under different
licences.
The possible disadvantage I see with hangars is, that people might have
problems to find their aircraft they want to have.
User want to have a specific aircraft would have to dig through several hangars
with a big mix of different aircraft- Unless we find a way like a search engine
(like AVSim.com or X-Plane.org uses) where people just type in their wishes and
get a list of possible matching resultats.
>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 :)
Aha, really?- in the 5-6 years I'm contributing to FlightGear-Project I did
this twice. I never got an answer. And until now I can only guess what was the
reasons for. Maybe I didn't produce 5 cheap aircraft a week? ;-)
Or maybe there had been more serious reasons, but without knowing them I had
never the chance to change it.
At the end I could live with it. Martin Spott was always kind enough to commit
my work, and even reviewed it. But like Gary already said, we also do know that
they have own real life, own projects and with all that only limited time....
>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.
That are your rules. And what rules does the other FGFS-Project-maintainer has?
And what do you understand under moderate quality? What do others understand
under?
>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.
Submitting merge requests wasn't bad, in fact that gave the chance to get the
work reviewed and checked. But very often no one felt responsible for! And
sometimes it needed more than 4 weeks until a merge requests was handled. And
then it was already not up to date anymore....
>'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 :)
Excuse me, what do you mean with the last one? Aircraft A has one feature which
developer of Aircraft B wants to use in his project as well. He copy and paste
it but makes sure that it works on his aircraft as well- that wouldn't be
allowed? I guess I misunderstand something here.
And who makes sure and decides that those people really keeps to all those
rules?
Heiko
still in work: http://www.hoerbird.net/galerie.html
But already done: http://www.hoerbird.net/reisen.html
------------------------------------------------------------------------------
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
