On 2011-10-27 10.24, James Turner wrote: > 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. > > 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. > > '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
One could have a section like (changing references to subversion to git of course) the one below. We use it it some of the open source projects I am a part of, w.r.t. fg I am still a spectator cheering and booing from the stands. I want to contribute Please send an email to the flightgear-devel@lists.sourceforge.net mailing list! If you are not subscribed to the list, you should first register your email address. Tell us what you want to do, download the source using git and hack away. Copied from the Subversion book: If you think that your work is usable for the rest of the community, you should donate your changes to the project. After making your modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your Subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges (permission to make new revisions in the Subversion source repository) will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of Subversion, programming competency, and a "team spirit", you will likely be awarded that permission. 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@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
