Hi, as LiClipseText was cited, I thought about answering ;)
Personally, I don't think adding it under eclipse.org
is much better than having it on Github (for me, the bar for contributions is lower on Github, and in general things are more streamlined for me -- but I also know this is a matter of taste -- although neither in LiClipseText nor in PyDev there are any native components... if there were native components, then *maybe* adding to eclipse.org
could be justified for the infrastructure).
I don't agree with the argument of higher density of developers with more relevant skills (i.e.: developers contribute to where the code they're interested in exists -- unless there's a general guideline for specific companies, but for instance, RedHat has no issues in contributing to PyDev, which is on Github).
So, all in all, yes, I don't have interest in moving LiClipseText nor PyDev to eclipse.org
, and I also think that it shouldn't matter. i.e.: I personally think that the number of people under eclipse.org
is not big enough to support all that's in place already -- if eclipse.org
just focused on moving SWT forward to be a modern UI framework and keeping the platform well supported enough, there would be more than enough work already -- but I also know this is not how it works and everyone has its own agenda -- including myself ;)
Regarding providing plugins from marketplace in eclipse.org
packages, I don't see any issues... and as a note, if a textmate editor is created in eclipse.org
itself (which I'm also fine if someone wants to do BTW, even more if the code will be well done and properly supported), you still have to get the grammars (which are scattered over github) if you want to add support for those out of the box (as I don't think you'll want to recreate all those grammars).