<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hello Max & All<br><br>Answering inline.<br><br><div>> From: manderse@redhat.com<br>> To: paul.verest@live.com<br>> CC: angelo.zerr@gmail.com; mistria@redhat.com; jbosstools-dev@lists.jboss.org<br>> Subject: Re: [jbosstools-dev] Nodeclipse IDE (or components) in JBoss Tools?<br>> Date: Wed, 21 May 2014 11:01:50 +0200<br>> <br>> On 20 May 2014, at 12:09, Paul Verest wrote:<br>> <br>> > Hello All<br>> ><br>> > First the should be message from Eclipse to remind developers to have <br>> > Help pages (e.g. easily created with <br>> > http://marketplace.eclipse.org/content/github-flavored-markdown-viewer-plugin)that <br>> > references to their project web site.<br>> <br>> Not following what you mean here ?<br><br>Some plugins are missing home page references.<br>It should be recommended by Eclipse to add one Help page with project introduction<br><br>One of way to easy add Help page is using GFMV<br><a href="https://github.com/satyagraha/gfm_viewer/blob/master/plugin/src/site/markdown/adding-help-to-eclipse-plugin.md" target="_blank">https://github.com/satyagraha/gfm_viewer/blob/master/plugin/src/site/markdown/adding-help-to-eclipse-plugin.md</a><br><br>As User I had experience several times before when I could not recall plugin name or find it.<br><br><br>> <br>> > I found that plugin developers sometimes event don't have marketplace <br>> > entries (and helped/pushed with about 6-8 )<br>> <br>> Yes that is a good thing overall. The problem is many plugins don't even <br>> do basic UI interaction well. i.e. litter the context menu<br>> with actions, not integrating with the existing eclipse infrastructure <br>> etc. it results in a very fragmented experience unfortunately ;/<br>> <br>> >> Should we consider putting some parts of it on Central ? or even in <br>> >> JBDS ?<br>> >> Should we try to lobby with some authors to move projects to <br>> >> Eclipse.org ?<br>> > Could discussion is to get started.<br>> > I suggest to lobby that Eclipse would recognize non-Eclipse.org <br>> > projects under EPL license as valuable part of Eclipse eco-systemthat <br>> > Eclipse project committers should be aware of, give and take help.e.g. <br>> > https://github.com/eclipse-color-theme/eclipse-color-theme<br>> <br>> I'm not following what you mean/expect here ? When have eclipse not seen <br>> non-eclipse.org projects as valuable ?<br> <br>OK. I expressed myself not well.<br>What about <br>- have announces for plugin developers on main eclipse.org page<br>- have essential tutorials, links collected under one link, give list of generally helpful open-source project<br><br>In the case of <a href="https://github.com/eclipse-color-theme/eclipse-color-theme" target="_blank">https://github.com/eclipse-color-theme/eclipse-color-theme</a><br>I dialog starting from any Eclipse leader would help,<br>as the project is in uncertain state because of what Eclipse 4 Editors APIs are or would be.<br><br>> Problem I have is that if it projects don't participate in eclipse <br>> release train nor want to honor eclipse API guidelines they become <br>> something that is really really hard to rely on. Thus we can't include <br>> everything just because it exists.<br><br>Yes, they are of varying quality.<br><br>> <br>> > Something like open letter from Eclipse Foundation to Eclipse plugins <br>> > authors.<br>> <br>> What should that say that is not already happening ?<br>> <br>> > By the way looking for (remote) speakers for Eclipse DemoCamp <br>> > Beijinghttps://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Beijing<br>> <br>> You should do that in a separate mail thread instead of mingled in here. <br>> Becomes more visible that way.<br>> <br>> You can post on the community forums too if you prefer.<br>> <br>> > Please also help to connect to Red Hat China managers or marketing.<br>> <br>> Send me mail directly on what you are looking for and I can put you in <br>> contact.<br><br>Will do.<br><br>> <br>> /max<br>> http://about.me/maxandersen<br></div> </div></body>
</html>