Hi Ramy > Are there any plans to enhance Flarm support in XCSoar to catch up with the > rest of the soaring software available?
I don't think there is much to catch up, to be honest. The Flarm Radar in XCSoar has been working very fine for over three years now. Sure there are things that could still be improved, but I don't see any other application being much better about it either. > With the introductory of Powerflram > other vendors are rushing to add exciting functionality to increase safety, > situational awareness as well as tactical decisions. I don't quite understand this view. You are probably well aware that the Flarm has been in use in Europe for quite some time now and it is not a big innovation here anymore. I don't see any vendors rushing into anything here. All that functionality has been there already, but is now activated because the PowerFlarm is finally available in the US. > I opened the following > related enhancements which were all moved to wishlist: 2283, 2322, 2516, > 2517, 2546. Without those (and other) enhancements, XCSoar is lagging behind > other vendors in regard to flarm support. see above > Now, I completely understand that XCSoar developers have limited time and > capacity to address everyone's request, and they are doing fantastic job > fixing bugs and keeping the software remarkably stable, which should be the > absolutely highest priority, but I am questioning the process used to > address requests. the current process is to drop to the wishlist bucket any > request which at first look seem complicated or perhaps low priority to the > developer. Once this happen, based on my observation, the request remains in > wishlist indefinitely. So my questions are: > 1 - Do we, the users, have any say on what we think should be high priority? > There is currently no mechanism to support this. A voting option would be > great. Well there is certainly nothing that could "force" us to work on a particular thing. All you can do is lobbying and ultimately finding a developer who cares enough about the topic in question himself to implement it. Voting won't help with that either. > 2 - If something must be pushed down due to lack of time/resources, can it > be pushed down to be considered for next release instead of wishlist? yes, I usually do this for tickets that I consider a valid goal for the next milestone release. > 3 - Is it ok for the creator of the ticket to move it out from wishlist once > work on next release starts? if you find someone who is willing to work on it: yes > Once again, I am aware of the limited resources and appreciate the > fantastic job XCSoar developers are doing. This post is about how to > prioritize the work you doing. > If my coding skills were not rusted and outdated I would have been more than > happy to join the developers circle. I am surprised that with so many > talented users around, there are so few developers. I am quite surprised by that fact too. XCSoar on the other hand is quite a complex project due to the use of portable, multi-platform code and stuff like that. I guess most people are simply sacred off by it. I am happy to help any potential developers by giving guidance for their first steps though. And I don't consider "rusted and outdated" skills an issue. I've personally never developed in C++ before I joined the XCSoar team, and I've learned pretty much all I know from learning-by-doing on the project. Turbo ------------------------------------------------------------------------------ Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 _______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
