On 20 May 2014, at 12:09, Paul Verest wrote:
Hello All
First the should be message from Eclipse to remind developers to have
Help pages (e.g. easily created with
http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-pl...
references to their project web site.
Not following what you mean here ?
I found that plugin developers sometimes event don't have
marketplace
entries (and helped/pushed with about 6-8 )
Yes that is a good thing overall. The problem is many plugins don't even
do basic UI interaction well. i.e. litter the context menu
with actions, not integrating with the existing eclipse infrastructure
etc. it results in a very fragmented experience unfortunately ;/
> Should we consider putting some parts of it on Central ? or even
in
> JBDS ?
> Should we try to lobby with some authors to move projects to
>
Eclipse.org ?
Could discussion is to get started.
I suggest to lobby that Eclipse would recognize
non-Eclipse.org
projects under EPL license as valuable part of Eclipse eco-systemthat
Eclipse project committers should be aware of, give and take help.e.g.
https://github.com/eclipse-color-theme/eclipse-color-theme
I'm not following what you mean/expect here ? When have eclipse not seen
non-eclipse.org projects as valuable ?
Problem I have is that if it projects don't participate in eclipse
release train nor want to honor eclipse API guidelines they become
something that is really really hard to rely on. Thus we can't include
everything just because it exists.
Something like open letter from Eclipse Foundation to Eclipse plugins
authors.
What should that say that is not already happening ?
You should do that in a separate mail thread instead of mingled in here.
Becomes more visible that way.
You can post on the community forums too if you prefer.
Please also help to connect to Red Hat China managers or marketing.
Send me mail directly on what you are looking for and I can put you in
contact.
/max
http://about.me/maxandersen