On 27 Oct 2011, at 10:35, Heiko Schulz wrote: >> 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.
Problem is, as you already realised - *I* don't know who you asked, or what their reasons were. And I (me, personally) would like to make it easier for people to contribute. So you know the criteria *I* use, but there is no formal policy or document. > 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? Exactly as you say, it's a problem to agree such things. > 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.... Yes - in your situation I would ask repeatedly - in fact that's exactly what i did, to get commit access a couple of years ago :) >> try to avoid copy-and-pasting when you can share files or scripts >> >between aircraft > > 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. Sorry, of course in the case you describe it's fine to copy. My problem is often 80% (or 99%) of the file is the same, and really the solution is to make three files - a new 'generic' version that lives in Generic/, and then two (tiny, the 1% that's not generic) aircraft-specific files that customise the generic version for each 'installation' in a particular aircraft. Of course, this means changing the original aircraft, and hence, communicating with its author, which is slower, and more work than just copying the file! This is a recurring problem in all software development :) Anyway, this is a side discussion. > And who makes sure and decides that those people really keeps to all those > rules? Always the problem - 'no one' and 'everyone' and 'the people who shout loudest'. But hopefully in the end the result is acceptable, or people will complain. James ------------------------------------------------------------------------------ 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
