> The fact that we have now 3 different threads about the same topics: > DC3, licence violation and cooperation in an OpenSource project, makes > it difficult to see where the real problems are.
There's a number of separate issues here. * license violation of some commits -> this is a real problem, but I see no need to discuss this - it's brought to the attention of the people who have the rights to address this on the repository, if it's not obvious at this point that it needs to be dealt with, then why should further discussion help? * allegedly (I haven't checked) insults exchanged between people working on the same aircraft, followed by insults which I have witnessed -> this is childish behaviour and should not be discussed on this list at all - adult people in the same project should be able to communicate in a professional manner with a basic level of politeness, regardless of personal disagreements. Certainly piling new insults on top of old ones, or mixing any other grievance with a person or the project at large isn't going to help * unfinished aircraft in the repository -> seems useful to be to point out that there is a rational for having them * unfinished aircraft offered for download to end users -> I am one of the people who nag and push for a rating, but these days I see the issue being addressed, maybe not as fast as I would like, but the world isn't perfect - certainly a soft of consensus has been reached and re-opening the issue won't help * misunderstanding about the nature of the GPL license -> this is somewhat counter-intuitive and has been explained properly * unwritten rules for who is author and who decides what gets committed -> tend to lead to problems, but this can be sorted out in a reasonable way, if necessary by forking. My personal impression is that original authors try to retain far too much control - anyone working closer to the core has to live with what others do and co-ordinate efforts. Case in point - weather radar development in the forum: This heavily relies on the weater system writing out the right info, you can't do it alone. So who is author in the end? Doesn't matter to me. * dislike of certain FDMs by certain people -> simply don't use it, if I think a particular aircraft is bad/unfinished/whatever I don't fly it, likewise if I think a bit of scenery is badly done I don't go there - maybe I offer constructive criticism or try to improve it, but I don't think trashing someone's work in public will do any good whatsoever. Likewise, if you don't like to develop for a certain FDM, then don't do it. Above all, the problems shouldn't be mixed together. If there is a problem, that should be addressed, but not by creating a new problem. If a person has reacted improperly in some context, it doesn't give grounds to calling his work worthless in public. If the Flightgear project offers half-finished aircraft for download to the end user, that is not the fault of people commiting unfinished work to GIT. I don't think it's particularly difficult to see where the real problems are. I just think there are some personal grudges obscuring their identification. Cheers, * Thorsten ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
