>It was in an SednaX communication from Craig Boyd on 10/20/05.

>... SednaX is primarily a place for the Visual FoxPro Community to create open source add-ons and such for Visual FoxPro that complement the Sedna efforts by Microsoft. But, it is also a place where you can provide a free scaled-down (or lite) version of your Third Party Tools that will provide added functionality (value) to Visual FoxPro for the developers that use it. This gives your component/tool/or whatever additional exposure and could result in a significant number of paid for upgrades to the full version of your product.
>
> ...Shareware, or anything that has a time limit will not be considered, but freeware that has limited functionality is welcome. ....

Thanks John. I see that further down (from what you originally quoted) is the part above that says, "Shareware, or anything that has a time limit will not be considered..."

I think much of the discussion here is because the admins weren't sure whether the proposed software was freeware or shareware, and also that the issue of source code not being provided was not in keeping with traditional open-source projects. I notice that Craig did not specifically say that the provision of source code was a requirement with freeware submissions.

Things evolve and change over time.

As SednaX has grown perhaps the admins have found it wise to narrow the scope of the SednaX collection on GotDotNet to only community-owned "traditional" open-source projects. After all, there are many other repositories of freeware and shareware FoxPro code elsewhere such as here on the UT where many post links to their own websites as entries in the Downloads section. Also, perhaps the SednaX admins have found it wise to limit the scope of the SednaX collection on GotDotNet to projects related to interoperatibility with .NET 2005, SQL 2005, and other Microsoft technologies, as described in the VFP Roadmap.

Perhaps the best end to this whole discussion would be for the SednaX admins to come out with a statement to the effect that since SednaX has grown so much that they find it necessary to more specifically define appropriate SednaX projects, and make suggestions on where/how to share projects they feel are not appropriate for SednaX.