> Should we now track the paternity of every single file and humbly cry > for permission from the *main Developer* (with a capital 'D') of the > aforementioned file for every single commit ? Or do we want to be > pragmatic and accept that once a file is committed under GPL in git, > any contributor has the same rights (no more but no less) than the > original author ? What we used to have - and I hope we still do, is a "network of trust". I trust all of our main contributors that, whenever they spot a bug or some stupid mistake in my work they take responsibility and either fix it immediately or drop me a note and let fix it myself. Within this "network of trust" there is no need to ask for permission. I'd like to keep it that way. I think it worked well in the past and I'm convinced it will do so in the future.
Torsten ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
