Implementing new features for FlightGear: Difference between revisions

Jump to navigation Jump to search
m
m (remove Template:Note because it doesn't quite fit)
Line 67: Line 67:


... point out how your idea will make FG a better simulation.
... point out how your idea will make FG a better simulation.
... make a point out of what you would be willing to do if only XY were available.
... make a point out of what you would be willing to do if only XY were available.
... be as concrete as possible, point out what precisely you would like to see changed.
... be as concrete as possible, point out what precisely you would like to see changed.
... demonstrate that you have looked at the relevant information and know what you're talking about
... demonstrate that you have looked at the relevant information and know what you're talking about


Line 74: Line 77:


... demand anything from anyone.
... demand anything from anyone.
... be rude or angry if people are critical - it's part of the process.
... be rude or angry if people are critical - it's part of the process.
... point out how bad FG is going to be or how it will fail if your idea is not implemented.  
... point out how bad FG is going to be or how it will fail if your idea is not implemented.  
... say you can't do anything, because you don't understand C++ - the human mind can learn
... say you can't do anything, because you don't understand C++ - the human mind can learn
Compare 'Wouldn't it be cool if we had better-looking cities like X-Plane?' with 'Would it be possible to make the random building shader configurable such that it loads a pre-defined set of 3d models and assembles them in naturally looking groups by a placement mask of this and that format? I would then take care of the buildings and textures, but I'd need some help with the code. Here's a picture of how FG could look like.' - which of the two proposals would you support?
Compare 'Wouldn't it be cool if we had better-looking cities like X-Plane?' with 'Would it be possible to make the random building shader configurable such that it loads a pre-defined set of 3d models and assembles them in naturally looking groups by a placement mask of this and that format? I would then take care of the buildings and textures, but I'd need some help with the code. Here's a picture of how FG could look like.' - which of the two proposals would you support?




Even good proposals have a fair chance of failing to get any support. The reason is that experience has shown that the majority of people who say that they would do X if only feature XY is implemented do in fact not do X afterwards. Which is to say, before starting to join a project, developers want to be reasonably sure that their work will not be in vain because you lose interest and walk away. The magic words here are 'track record' and 'proof of concept'.
Even good proposals have a fair chance of failing to get any support. The reason is that experience has shown that the majority of people who say that they would do X if only feature XY is implemented do in fact not do X afterwards. Which is to say, before starting to join a project, developers want to be reasonably sure that their work will not be in vain because you lose interest and walk away. The magic words here are 'track record' and 'proof of concept', you can help improve you signal/noise ratio significantly by ensuring that you follow up on your commitments and do the necessary behind-the-scenes networking to implement a new feature or project. It is this combination of having a track record, "credit" and a good signal/noise ratio that will ultimately give you certain ''leverage'' when interacting with other contributors.
Overall, time spent contributing to the project really '''is''' our "currency-it shows dedication and discipline and it demonstrates to potential collaboratos that you are serious about your commitments, and that teaming up with you is not a waste of their time. If properly done, such networking can be a great multiplier/lever.


If you already have a history of bringing projects to a conclusion, people are far, far more likely to support you. If you have not, because you're just starting out, the best thing you can do is a proof of concept. Perhaps something should really be in C++ for performance reasons - but you can make a simple proof of concept in Nasal scripting space. Once people see that you're actually investing time and work rather than talk, and once they can see what you want to do, you're again more likely to get support.
If you already have a history of bringing projects to a conclusion, people are far, far more likely to support you. If you have not, because you're just starting out, the best thing you can do is a proof of concept. Perhaps something should really be in C++ for performance reasons - but you can make a simple proof of concept in Nasal scripting space. Once people see that you're actually investing time and work rather than talk, and once they can see what you want to do, you're again more likely to get support.

Navigation menu