>What's unfortunate is you are the one here on the UT 'clarifying' what the SednaX 'VFP Community Owned and Operated' site is about (or not about).

Actually no. I'm here clariying what an open/shared source project is. SednaX as one example.

>I, for one, mistakenly interpreted the meaning of 'VFP Community Owned and Operated' as referring to a wider group of 'owners' and 'operators' rather than simply being 'not Microsoft'. Nothing wrong with a basically one or two man 'administrator' selecting and organizing some projects but the advertising and initial open calls for ideas made it seem the intentions were bigger than that.

SednaX appears to be mainly about enhancing Xbase components that are included in VFP, but has taken on selective areas (like menus and such) to build new components. In the end, it will include whatever the core members prioritize on. Things not included may need to involve a new open project. The intial and existing overview of SednaX says "The code, classes, and libraries made available here will complement Microsoft's continuing efforts to improve and extend Visual FoxPro with the code named Sedna project which is outlined in the Visual FoxPro Roadmap.". I read that is saying it is focused on enhancing and evolving the Xbase components that Microsoft releases for VFP and Sedna. It is not about 'everything that is a VFP add-on total'. But other projects can be created for other VFP add-ons and products at anytime by anyone.

>It is interesting that there 'seems' to be so many developers who would be interested in an open source development forum with more breadth. I think we like the independence factor but don't want to be the one to do the admin work... lol

Yes, I've been saying this indirectly in a few of my posts by asking a few people why they haven't or don't go create a new open project. Each component in any project requires time from volunteers, and each thing done takes away from other things that could be done (priorities).

Open projects only succeed when there are volunteers willing to enhance the source code of the project. Can you list for me all the names of the VFP developers are now ready to spend their free time enhancing the ActiveVFP source code to keep the project evolving? If not, then why would it be part of an open/shared source project instead of just being a free download like it is now? Shared and open source projects only succeed by evoloving, and they only evolve from people volunteering to contribute to it.