Le 07/10/2017 à 22:29, Paul Hemans a écrit :
But even if they decided to stop it someone could pick up the code and go on. With VFP we were simply stuffed. 'Open source' means the source is available.
Well, theorically true, very difficult practically.
As I mentioned earlier, all major contributors are Microsoft employees or close to, and have been working on that project for years, probably full time if you take a close look at the contribution graphs.
Language translaters are a difficult matter that require a strong academic background and daily involvement in the project.
That's why I can't see how 'simple' users could take over the project if Microsoft decided to withdraw.
If you fork the project, your contribution can go into the mainstream releases ONLY if you issue a 'pull request' and if the project manager(s) accept it and merge it into the main branch. If Microsoft removes resource from this project without transferring the lead to someone else, and if no one's forked branch really becomes a leader, there is no real way to gather contributions into a fruitful manner.
You could theoretically imagine to make your fork become a TypeScriptBis with its own release cycle and register it into bower, chocolatey, grunt and the like, however that looks like a ScFi scenario IMO.
Thierry Nivelet FoxInCloud Give your VFP app a second life in the cloud http://foxincloud.com/ _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/87278c09-1bf0-8032-b8e8-469ed65b3...@foxincloud.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
