User:Callahanp: Difference between revisions

===== Pie in the sky? You decide...  =====

In fact, we have an excellent example happening right now in the Spring of 2018. It's Edward's work on unit testing and the restructuring of the subsystem manager.  If you're interested in how big changes come about I'd suggest reading everything related to this effort rather closely and following the ongoing discussion over testing.  Look not just for the technical details, but for the way Edward limited the scope of his current activity and for the quality of the interactions between the interested parties.  I think its a model for anything major anyone wants to undertake in Flightgear.  In fact this kind of interaction is nothing new in the flightgear project.  Other examples abound. Everything from the adoption of OSG to QT has gone through a similar process.

Those of us who want to be involved in ''big changes'' need to know this process well.  So read the mailing list entries in detail and notice the choices people are making and the reasons why.  The last thing we want is divisive discussion over direction or choices already made. Especially where the root of the discussion is a misunderstanding or refusal to recognize how the project actually works over a period of time.

So now here's my take on a big Flightgear code change - [[Multicore Processing and Clusters]].