Thanks for your comments and suggestions. In the first place, I need to tell you that personally, I'm a "free software guy", and I agree that the best possible solution is always the GPL license. But this is personal.
BTW, you can find information about IVAO at www.ivao.aero, for those that asked. The reason why I wanted to start a discussion about this was to achieve a project proposal or roadmap that we can hand to IVAO Softdev directors for approval. I know their preference is to use the INL library, that's why I suggested this. What I really want is the IVAO approval, and with the use of the INL I think that was guaranteed. But I'm not a salesman; my only interest is just get FG and IVAO join, whatever means that please all. So, as the INL library poses a few important problems, and I see your preference (and my personal one as well) is to go for an open solution, I think we should work on this idea. The thing is, whatever solution is finally pointed out, I'd like to hand them a document about this best solution, well reasoned and clearly explained, so that it helps convince not only software development directors, but the board of governors as well. So yes, the solution that some of you have pointed out of opening a different gateway inside IVAO servers for FG users, had crossed my mind as well time ago. But I need a bunch of arguments and explanations to convince the rest of IVAO that this is the best solution possible. I know Softdev directors are really interested in getting FG join the network, so if we can hand a good explanation there shouldn't be any problem (I'm always optimistic). Regarding why IVAO keeps their protocols closed being a free community, what I've been always answered is that's for security reasons. So explaining them that the mentioned open gateway for FG wouldn't be a security issue is crucial. Developing it in a way that takes security into consideration would be important. I need to tell them how security issues will be addressed. I think the best way to proceed, after reading your posts, is to focus on this solution: a different (open) protocol for FlightGear inside IVAO servers. So what I'd ask you is a set of reasons why we should go for this solution and forget the INL: techical reasons (security-related above all), license reasons, etc. Please help me prepare an interesting proposal. I'm aware the worst hurdle to overcome will be this agreement between two communities with different points of view, but if we could address this specific issue successfully, I'm sure the outcome would be very interesting for the community in general. I'll be waiting for your answers. Best regards, Pep. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
