I have no issues with it being added to part of SVN. I won't go over the different points raised in the conversation, but just some quick thoughts:
- Within crossfire, there has never really been any standard set of programs that must be supported. So just the fact it gets added to SVN hardly means that all developers need to support it, and in fact, there are various pieces right now where that really is not the case. - If over time/through lack of support it does no longer work, it can always get removed. - It's impossible to force anyone to work on anything when folks are contributing their time freely. While there may be 'better' things to work on (and different people may have different ideas what should be worked on), getting them to do it may not be possible. If the user doesn't have any interest in working on that, it just won't happen. - With that above note, it means that all that crossfire can really limit is if it is in SVN or not. Raphael can continue to work on it in either case. And for that matter, could create another project on sourceforge to hold the editor. It's not clear to me that is any better than having it under the crossfire tree. Documentation stating is current state could be included. If other folks use it, it would seem worthwhile. _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
