From what I've read, I think less than 10% of what is part of SednaX will be related to .NET, and in those cases it would be on VFP interop with .NET classes. Web is important, and if there is a need and demand for an open source project for a VFP web tool, one can be created anytime by anyone.

I wish you'd read what I actually said.

1) This is about web stuff. And a self-styled "community" open source initiative.

2) VFP does not offer web stuff natively.

3) The VFP community does care about web stuff.

4) If this web enabling tool does not belong in the community open source initiative, will the community open source initiative have some other web offering, since we obviously care about it.

5) If not, then people may wonder why not. Based on the atmosphere in the VFP community for a decade, they may draw unfortunate conclusions about why VFP doesn't have such technology and why a community open source project blocks it and why you are answering questions about it.

That's it. It is a shame we didn't immediately hear about the acid test "can the initiator walk away and have it managed by somebody else". That would have put it back on CF to meet that test. Instead we got weird explanations that did not rebut CF's suggestions that something stinks. That's all I said and I challenge you to find anything else in my post.