Hi, good to see some more factual discussions. Let me emphasize that anyone is
welcome to add/edit
concerns/questions/answers/solution to the wiki:
http://wiki.flightgear.org/FlightGear_Git:_splitting_fgdata
> Those who have commit rights are already busy with their own stuff. For a new
> aircraft it is o.k. to ask them-
> but when I want to update my work? For each small update asking and stealing
> time of those people?
No matter what aircraft-split we end up with, aircraft authors will always be
able to update their own aircraft at
any time. With the current setup you can for example commit (and accept merge
requests) for your EC130:https://gitorious.org/flightgear-aircraft/ec130
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
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). We could implement Yves' idea (giving
teams access to repos, rather than individuals) in the FlightGear aircraft
project. But I don't think it is worth most of the trouble. I think it would
make things even more un-clear when
there are hundreds of teams...
But I might be wrong of course.
Cheers,
Gijs
------------------------------------------------------------------------------
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
