There is no such thing as contributing a component or product that is so called "complete" and no work is involved. Any code base that is contributed and accepted requires work to manage the source, manage the installation, and of course keep it updated. The entire point of having an open project like SednaX is to evolve (enhnace) the code bases ongoing. Why is it not good enough for you to just see Claude post the source files to ActiveVFP on his own web site and label them open source? Then if someone or some group wants to evolve the code base and make enhancements, they will need to create and contribute to an open project online to do that. My idea with SednaX was a place to take VFP XSource code, FFC classes, and the source included with the upcoming Sedna project and post updated versions of them in the future. If the project adminitrators want to take their time to add other components (requires review, project management, testing, etc.) for the overall SednaX project, then that is great. But there will be lots of VFP source code that won't make it into the SendaX project, and if those components can reside online on some web site like here on the UT Downloads or the author's own personal web site. Then if someone or a group wants to see them updated, they have to do it in some form, like a new open project.