117
edits
Fr/How the FlightGear project works: Difference between revisions
Jump to navigation
Jump to search
Fr/How the FlightGear project works (view source)
Revision as of 10:21, 16 January 2016
, 16 January 2016no edit summary
No edit summary |
|||
| Line 27: | Line 27: | ||
== Passion == | == Passion == | ||
( | (à traduire) | ||
Honestly, we are all part of this community because we appreciate some things about this open source flight sim named FlightGear. So we are always sorry whenever our tone becomes inappropriate or even harsh. | Honestly, we are all part of this community because we appreciate some things about this open source flight sim named FlightGear. So we are always sorry whenever our tone becomes inappropriate or even harsh. | ||
| Line 33: | Line 33: | ||
== Welcome to the club == | == Welcome to the club == | ||
( | (à traduire) | ||
To tell the truth: Most of us have been in that situation at some point. To most of us, the way FlightGear works as a project has been somewhat irritating and confusing in the beginning. So, we may actually share your initial confusion, because most of us went through the same process at some point. | To tell the truth: Most of us have been in that situation at some point. To most of us, the way FlightGear works as a project has been somewhat irritating and confusing in the beginning. So, we may actually share your initial confusion, because most of us went through the same process at some point. | ||
| Line 50: | Line 50: | ||
== Proposing changes == | == Proposing changes == | ||
( | (à traduire) | ||
This is not to say that things are set in stone, but the current development model is the result of a certain evolution, and it's exactly this what has enabled FlightGear to survive and grow for over a decade already, without relying on commercial backing, funding organizations or formal project management. | This is not to say that things are set in stone, but the current development model is the result of a certain evolution, and it's exactly this what has enabled FlightGear to survive and grow for over a decade already, without relying on commercial backing, funding organizations or formal project management. | ||
| Line 59: | Line 59: | ||
== Ideas getting ignored or rejected == | == Ideas getting ignored or rejected == | ||
( | (à traduire) | ||
Let's be honest: Not every suggestion made in the forum or on the devel list is good. While no one deserves to be belittled, a fair share of suggestions deserve to be ignored (unless you feel you are entitled to 30 minutes time from, say, a 3d rendering specialist who explains to you in detail why your idea really doesn't work in non-technical terms). | Let's be honest: Not every suggestion made in the forum or on the devel list is good. While no one deserves to be belittled, a fair share of suggestions deserve to be ignored (unless you feel you are entitled to 30 minutes time from, say, a 3d rendering specialist who explains to you in detail why your idea really doesn't work in non-technical terms). | ||
| Line 78: | Line 78: | ||
== Lack of feedback == | == Lack of feedback == | ||
( | (à traduire) | ||
Lack of feedback - same thing. Go out into the forum, download interesting addons, talk to the people who provide them, let them know what you think. If you want feedback for your own work, start by giving feedback to the work of others. That's how it works. And yes, lack of recognition is sometimes a problem. Basically, you have to do things because you want to, and you have to be enthusiastic enough to pull others along so that they can see and appreciate your vision of how things could be. Again, requires a lot of patience. I wish that many things here would be different. I wish people would collaborate on projects more often, instead of everyone developing his own pet project and half of them dying for lack of interest. But I've come to realize that it's not going to happen because I wish it to happen - things are only happening my way if I slowly work towards it, talk to people an unholy amount of time and try to convince them that I am serious and have a case. | Lack of feedback - same thing. Go out into the forum, download interesting addons, talk to the people who provide them, let them know what you think. If you want feedback for your own work, start by giving feedback to the work of others. That's how it works. And yes, lack of recognition is sometimes a problem. Basically, you have to do things because you want to, and you have to be enthusiastic enough to pull others along so that they can see and appreciate your vision of how things could be. Again, requires a lot of patience. I wish that many things here would be different. I wish people would collaborate on projects more often, instead of everyone developing his own pet project and half of them dying for lack of interest. But I've come to realize that it's not going to happen because I wish it to happen - things are only happening my way if I slowly work towards it, talk to people an unholy amount of time and try to convince them that I am serious and have a case. | ||
| Line 98: | Line 98: | ||
== Users vs. contributors == | == Users vs. contributors == | ||
( | (à traduire) | ||
We have here two groups of persons (with blurry boundaries): The first group takes something for free, which is a flight sim which you download from servers for which someone probably pays real money. The second group gives something, which is their time to create the simulation. | We have here two groups of persons (with blurry boundaries): The first group takes something for free, which is a flight sim which you download from servers for which someone probably pays real money. The second group gives something, which is their time to create the simulation. | ||
| Line 111: | Line 111: | ||
== Lack of Support and Backwards Compatibility == | == Lack of Support and Backwards Compatibility == | ||
( | (à traduire) | ||
FlightGear is a volunteer effort and no one is paying several thousand dollars a year for software and related support each year. Since legacy support is expensive (IE. time/effort) one of the ways a project like FlightGear deals with this is to limit legacy support. If this were not the case then time/effort would be expended on legacy support that could be used for new features and bug fixes. Like most things there are trade offs involved. Which do you want - more advanced FlightGear and aircraft or better support for older versions? This is a common issue for open source software and most prefer to look forward rather than looking back. | FlightGear is a volunteer effort and no one is paying several thousand dollars a year for software and related support each year. Since legacy support is expensive (IE. time/effort) one of the ways a project like FlightGear deals with this is to limit legacy support. If this were not the case then time/effort would be expended on legacy support that could be used for new features and bug fixes. Like most things there are trade offs involved. Which do you want - more advanced FlightGear and aircraft or better support for older versions? This is a common issue for open source software and most prefer to look forward rather than looking back. | ||
| Line 120: | Line 120: | ||
== Priorities in bug fixing == | == Priorities in bug fixing == | ||
( | (à traduire) | ||
{{cquote|I stopped filing bug reports after too many instances of our omniscient developers denying a problem exists, or telling me to fix it myself (yeah, right). Bug reports are a waste of time. You'll have a hard time convincing me that anyone cares about fixing bugs that don't bother them personally. I'm really glad some folks are writing free software for me, but you gotta admit, most of them are pretty arrogant about it.}} | {{cquote|I stopped filing bug reports after too many instances of our omniscient developers denying a problem exists, or telling me to fix it myself (yeah, right). Bug reports are a waste of time. You'll have a hard time convincing me that anyone cares about fixing bugs that don't bother them personally. I'm really glad some folks are writing free software for me, but you gotta admit, most of them are pretty arrogant about it.}} | ||
| Line 144: | Line 144: | ||
== Number of aircraft vs. quality of aircraft == | == Number of aircraft vs. quality of aircraft == | ||
( | (à traduire) | ||
{{cleanup}} | {{cleanup}} | ||
| Line 176: | Line 176: | ||
== Fictional Aircraft == | == Fictional Aircraft == | ||
( | (à traduire) | ||
FlightGear is developed by a community of volunteers from all over the world, we contribute in whatever way we see fit, if you disagree with the way FlightGear development is going, your best chance to affect it, is by starting contributing yourself. FlightGear could only progress so far without any commercial backing for over a decade, because of FlightGear contributors and their very passion for turning their own ideas into FlightGear features. | FlightGear is developed by a community of volunteers from all over the world, we contribute in whatever way we see fit, if you disagree with the way FlightGear development is going, your best chance to affect it, is by starting contributing yourself. FlightGear could only progress so far without any commercial backing for over a decade, because of FlightGear contributors and their very passion for turning their own ideas into FlightGear features. | ||
| Line 202: | Line 202: | ||
== You need development guidelines == | == You need development guidelines == | ||
( | (à traduire) | ||
You might have made general statements like 'There should be clear development guidelines', 'the project should not depend on a single person being around' or 'the developers should pay more attention to the users'. In theory, all these are beautiful - and who would object that these are all good things? | You might have made general statements like 'There should be clear development guidelines', 'the project should not depend on a single person being around' or 'the developers should pay more attention to the users'. In theory, all these are beautiful - and who would object that these are all good things? | ||
| Line 217: | Line 217: | ||
== Telling volunteers what to do == | == Telling volunteers what to do == | ||
( | (à traduire) | ||
Posted by MAKG: | Posted by MAKG: | ||
| Line 255: | Line 255: | ||
== FlightGear is a meritocracy == | == FlightGear is a meritocracy == | ||
( | (à traduire) | ||
FlightGear, as best as we have managed to understand the somewhat opaque workings in core development, is a meritocracy - your influence is proportional to the amount of work you do for the project. It's not closed, i.e. you can, if you invest a lot of work into the project, work yourself into a position where you have a lot of influence even starting today from zero. | FlightGear, as best as we have managed to understand the somewhat opaque workings in core development, is a meritocracy - your influence is proportional to the amount of work you do for the project. It's not closed, i.e. you can, if you invest a lot of work into the project, work yourself into a position where you have a lot of influence even starting today from zero. | ||