14
edits
Talk:FGAddon: Difference between revisions
Jump to navigation
Jump to search
→Request for “Contributing” section: new section
(→Request for “Contributing” section: new section) |
|||
| Line 66: | Line 66: | ||
: [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:32, 14 May 2016 (EDT) | : [[User:Bugman|Bugman]] ([[User talk:Bugman|talk]]) 11:32, 14 May 2016 (EDT) | ||
== Request for “Contributing” section == | |||
The page deals with using, and then with developing aircraft. But there is a very important middle-ground: people who like to fly this for a bit and then that for a bit, find issues and want to report those issues and possibly have a simple patch worth a couple of lines to fix it. Such people (like me) are not really interested in setting up development branches nor getting commit access. They just need: | |||
# A documented, '''on this page''' and the sourceforge project page, and reasonably simple way to report those issues that is preferably: | |||
## Consistent across all the aircraft. I.e. it shouldn't be this email for one aircraft, that forum thread for second and another github repo for third. If that is the status quo and can't be improved on, at least there should be one place where the correct way for each aircraft could be found: not all aircraft have wiki pages, not all have README, etc. | |||
## With public record. Bug tracker is best, but forum or mailing list are fine as long as it does not depend on one maintainer who might have gone MIA without anyone noticing. | |||
# Similarly documented best practice how to prepare and send patches to maximise the chance that the repository maintainers will accept and merge them. | |||
Would anybody please be able to add that info before the [[http://wiki.flightgear.org/FGAddon#Aircraft_development Aircraft development]] section? Or at least give me hint where to find such information so I could copy it over here? | |||
Thanks | |||
<small>Note: This is, for me, benefit of the FGMEMBERS—it is clear that the appropriate channel is the github issue tracker for each aircraft. However I worked in many settings and don't mind the particulars. Whatever works for the core team is fine be it a mailing list, forum or whatever kind of tracker. It just needs to be obvious and in case of FGAddon (and to large extent FlightGear itself too) it never was to me.</small> | |||
—[[User:JanHudec|JanHudec]] ([[User talk:JanHudec|talk]]) 10:03, 26 July 2016 (EDT) | |||