2,733
edits
Fr/How the FlightGear project works: Difference between revisions
Fr/How the FlightGear project works (view source)
Revision as of 16:59, 18 March 2016
, 18 March 2016Fix a templates
Red Leader (talk | contribs) m (Fix a templates) |
|||
| (9 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Working together}} | {{Working together}} | ||
Comme d'années en années FlightGear devient de plus en plus populaire, nous avons pu voir nombre de controverses sur les rouages du projet FlightGear. Il est un fait bien connu parmi les contributeurs de longue date que le modèle de développement de FlightGear peut sembler irritant au premier abord et il est connu pour provoquer des confusions ou même des frustrations parmi les nouveaux contributeurs qui peuvent déjà avoir une expérience de contribution dans d'autres communautés de Flight Sim ou même d'autres logiciels OSS. Alors, voici une collection de réponses destinées à clarifier pourquoi les choses sont mises en place de cette façon. Les personnes qui désirent s'impliquer dans la communauté FlightGear et de contribuer d'une manière ou d'une autre, sont encouragés à lire ceci et comprendre comment FlightGear a pu être couronnée de succès, malgré le fait qu'il n'a pas de support commercial ou un modèle de développement vraiment structuré. | Comme d'années en années FlightGear devient de plus en plus populaire, nous avons pu voir nombre de controverses sur les rouages du projet FlightGear. Il est un fait bien connu parmi les contributeurs de longue date que le modèle de développement de FlightGear peut sembler irritant au premier abord et il est connu pour provoquer des confusions ou même des frustrations parmi les nouveaux contributeurs qui peuvent déjà avoir une expérience de contribution dans d'autres communautés de Flight Sim ou même d'autres logiciels OSS. Alors, voici une collection de réponses destinées à clarifier pourquoi les choses sont mises en place de cette façon. Les personnes qui désirent s'impliquer dans la communauté FlightGear et de contribuer d'une manière ou d'une autre, sont encouragés à lire ceci et comprendre comment FlightGear a pu être couronnée de succès, malgré le fait qu'il n'a pas de support commercial ou un modèle de développement vraiment structuré. | ||
Une version plus succincte de cet article peut être trouvé à: http://forum.flightgear.org/viewtopic.php?f=42&t=15267 (c'est une très bonne introduction, les personnes intéressées par plus de détails, peuvent examiner le texte ci-dessous). | Une version plus succincte de cet article peut être trouvé à: http://forum.flightgear.org/viewtopic.php?f=42&t=15267 (c'est une très bonne introduction, les personnes intéressées par plus de détails, peuvent examiner le texte ci-dessous). | ||
== | == Contexte == | ||
Comme FlightGear devient de plus en plus populaire, nous voyons, chaque semaine, de nouveaux utilisateurs fréquenter notre forum et suivre la liste de diffusion. Beaucoup d'entre eux souhaitent contribuer à FlightGear d'une manière ou d'une autre et s'impliquer dans notre communauté. | Comme FlightGear devient de plus en plus populaire, nous voyons, chaque semaine, de nouveaux utilisateurs fréquenter notre forum et suivre la liste de diffusion. Beaucoup d'entre eux souhaitent contribuer à FlightGear d'une manière ou d'une autre et s'impliquer dans notre communauté. | ||
| Line 11: | Line 12: | ||
Il y a de multiples façons de vous impliquer dans FlightGear, de sorte que les compétences de chacun peuvent s'exprimer. | Il y a de multiples façons de vous impliquer dans FlightGear, de sorte que les compétences de chacun peuvent s'exprimer. | ||
S'il vous plaît, ne pensez pas que vous ne pouvez pas participer au projet, parce que vous ne savez pas programmer ou parce que vous ne pouvez pas concevoir des modèles 3D. La création d'un simulateur de vol est une entreprise énorme et il y a beaucoup de tâches qui peuvent sembler moins évidente pour les étrangers, comme aider à maintenir le wiki, modérer | S'il vous plaît, ne pensez pas que vous ne pouvez pas participer au projet, parce que vous ne savez pas programmer ou parce que vous ne pouvez pas concevoir des modèles 3D. La création d'un simulateur de vol est une entreprise énorme et il y a beaucoup de tâches qui peuvent sembler moins évidente pour les étrangers, comme aider à maintenir le wiki, modérer le forum, signaler des spam, trier le bug tracker, examiner les rapports de bugs, aider d'autres utilisateurs et ainsi de suite. | ||
== Irritations == | == Irritations == | ||
( | (à traduire) | ||
However, sometimes we get to see some irritations among new community members and more seasoned members, because people may have certain expectations and assumptions on contributing to FlightGear. This has frequently caused some heated discussions, sometimes even flame wars on both, the devel mailing list and the forums. | However, sometimes we get to see some irritations among new community members and more seasoned members, because people may have certain expectations and assumptions on contributing to FlightGear. This has frequently caused some heated discussions, sometimes even flame wars on both, the devel mailing list and the forums. | ||
| Line 27: | Line 28: | ||
== 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 34: | ||
== 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 51: | ||
== 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 60: | ||
== 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 79: | ||
== 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 99: | ||
== 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 112: | ||
== 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 121: | ||
== 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 145: | ||
== Number of aircraft vs. quality of aircraft == | == Number of aircraft vs. quality of aircraft == | ||
( | (à traduire) | ||
{{cleanup}} | {{cleanup}} | ||
| Line 176: | Line 177: | ||
== 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 203: | ||
== 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 218: | ||
== Telling volunteers what to do == | == Telling volunteers what to do == | ||
( | (à traduire) | ||
Posted by MAKG: | Posted by MAKG: | ||
| Line 255: | Line 256: | ||
== 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. | ||
| Line 337: | Line 338: | ||
== Community interactions == | == Community interactions == | ||
(à traduire) | |||
What can be done in a forum? First off, speak the same as if you were standing in front of the person you are talking to. If you _really_ do get up in their face when you speak, take the gold chains off for a minute and lose the Jersey accent. Respect goes a long way. Respect also goes _both_ ways. If you get an email from someone, respond to it, even if it's saying that "no, I can't help". | What can be done in a forum? First off, speak the same as if you were standing in front of the person you are talking to. If you _really_ do get up in their face when you speak, take the gold chains off for a minute and lose the Jersey accent. Respect goes a long way. Respect also goes _both_ ways. If you get an email from someone, respond to it, even if it's saying that "no, I can't help". | ||
| Line 364: | Line 367: | ||
== Conclusion == | == Conclusion == | ||
(à traduire) | |||
There's simply no use in complaining that FlightGear isn't the community you'd like it to be - but there is use in working to make it the community you like it to be. It's just requires more effort | There's simply no use in complaining that FlightGear isn't the community you'd like it to be - but there is use in working to make it the community you like it to be. It's just requires more effort | ||
| Line 369: | Line 374: | ||
== To be discussed == | == To be discussed == | ||
(à traduire) | |||
* don't like this conceptual division between users and developers. A user is just a developer who hasn't popped the hood on their car yet. | * don't like this conceptual division between users and developers. A user is just a developer who hasn't popped the hood on their car yet. | ||
| Line 439: | Line 446: | ||
* Today, with much infrastructure available for free or easy obtainable, forking a project has become easier than ever. You might end up in a position to fork Flightgear to support your own pet projects, perhaps your own little business based on said pet projects. The thing to keep in mind is that it is quite hard to keep up with the latest developments. Be prepared to spend lots of hours just to add all the new features being developed in the mainline. However, it can also be a very satisfying experience, especially if you base your own fork on a slightly older code version, and try as hard as you can to keep it stable. A successful fork is hard to achieve and maintain over time, but you may be in a situation where this is required. Do not hesitate to try it. Always bring your contributions to the attention of upstream. They might get merged and save you some trouble in the future. | * Today, with much infrastructure available for free or easy obtainable, forking a project has become easier than ever. You might end up in a position to fork Flightgear to support your own pet projects, perhaps your own little business based on said pet projects. The thing to keep in mind is that it is quite hard to keep up with the latest developments. Be prepared to spend lots of hours just to add all the new features being developed in the mainline. However, it can also be a very satisfying experience, especially if you base your own fork on a slightly older code version, and try as hard as you can to keep it stable. A successful fork is hard to achieve and maintain over time, but you may be in a situation where this is required. Do not hesitate to try it. Always bring your contributions to the attention of upstream. They might get merged and save you some trouble in the future. | ||