>I think you didn't read there too much.
>
>See:
>
>http://www.masfoxpro.com/Masfoxproletter
>
>quoted "We ask you to continue future Visual FoxPro development, if this cannot fit with Microsoft needs, you can go for this two other possibilities that would fit for the community (in order of relevance):
>
>* releasing it to Open Source (even restricted in any way) the Visual FoxPro full source code
>*doing an agreement with a third party so that this third party can continue Visual FoxPro development"
>
>If you never shoot the duck, you never eat duck.
>
>Visual FoxPro as open sorce wouldn't be a good thing? You showed your joy about the open shared source Sedna in your blog. What it makes different from the full source code? and licensing to a company also not?


Pablo,

I think you did not read Microsoft's announcement in detail then. Microsoft said there will be no VFP10. The core VFP9.EXE will not be updated past SP2 unless there is a major bug. They will not release it as open source because there is too much intellectual property involved. You or I may not like it, but that is their decision and has been told to use in the Roadmap two years ago. Why then not complain at that time? MasFoxpro.com is now too little, too late.