My main point (or thought) is just that if we are going to push forward with
this split, then we need to go the whole way and make it work reasonably for
everyone. The people pushing this and doing the initial work, can't just
take it half way and then leave it because their personal concerns are dealt
with. They need to consider the broader user and developer base and make
sure our new approach and structure isn't a significant regression or
inconvenience for people. It's one thing when you are in your own sand box,
but this is the whole playground we are redoing, so their is a much more
significant responsibility for making this work really well for everyone.
I was reacting to the series of emails that indicated the split was done,
everything is finished, nothing more to see here, every one move along --
but I'm sitting here with zero aircraft and a major hassle to get them all
back and keep them updated. Gijs has indicated that we are going to have a
do-over which is fine -- I've done enough sys admin stuff to know that it
usually takes a couple tries to catch all the lose ends. When I install a
new OS on a PC, I'm usually in it for 6-12 attempts before I get all the
partitioning and configuration options just the way I want without messing
something up critically in the process. ;-)
I just want to make sure that we are considering the different issues and
concerns; that the process and end results are being thought through
carefully; and that those doing the leg work on this (and pushing the change
strongly) don't leave it half baked because we ran into a problem that no
one considered and no one knows what to do about it, and the original people
are happy enough with only a 1/2 dozen aircraft to play with.
Thanks!
Curt.
On Wed, Oct 19, 2011 at 12:41 PM, Jari Häkkinen wrote:
> I actually lost track of who is doing what in the splitting of fgdata
> but there is a tremendous response pointing out issues related to the
> split. I want to express support for the splitting team.
>
> I support the split if only for the reason that aircraft maintainers
> will get commit rights to their private spheres in fg-land (if I
> understand things properly). With the previous monolithic fgdata only a
> selected group of people had commit privileges.
>
> Once the dust settles I think we will see the benefits of giving
> aircraft developers direct access to "their" repos. At least the need
> for setting up other repos will decrease (assuming that not all aircraft
> developers are anti-GPL) because I think one major reason for setting up
> external repos are (lack of) commit privileges in fgdata.
>
>
> For those of you who are impatient with the progress, is the now frozen
> fgdata unusable? Why not stay with it until the new fgdata is to your
> liking? I haven't pulled the latest fg-state lately so I don't know if
> this is possible to stay old-school?
>
>
> Cheers,
>
> Jari
>
>
> ------------------------------------------------------------------------------
> 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@Ciosco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
> _______________________________________________
> Flightgear-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Curtis Olson:
http://www.atiak.com - http://aem.umn.edu/~uav/
http://www.flightgear.org - http://gallinazo.flightgear.org
------------------------------------------------------------------------------
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@Ciosco Self-Assessment and learn
about Cisco certifications, training, and career opportunities.
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
