<html>
<head>
<meta content="text/html; charset=GB2312" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Paul,<br>
<br>
On 05/20/2014 12:09 PM, Paul Verest wrote:<br>
</div>
<blockquote cite="mid:SNT147-W77633C33FF9F68D6AD812A863D0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
<div dir="ltr">I suggest to lobby that Eclipse would recognize
non-Eclipse.org projects under EPL license as valuable part of
Eclipse eco-system</div>
</blockquote>
MarketPlace was done to fulfill this goal and it works pretty well.
Some non Eclipse.org project have been pretty successful thanks to
MarketPlace and MarketPlace client. I think those should thank the
Foundation for that.<br>
<br>
<blockquote cite="mid:SNT147-W77633C33FF9F68D6AD812A863D0@phx.gbl"
type="cite">
<div dir="ltr">
<div>that Eclipse project committers should be aware of, give
and take help.</div>
<div>e.g. <a moz-do-not-send="true"
href="https://github.com/eclipse-color-theme/eclipse-color-theme"
target="_blank">https://github.com/eclipse-color-theme/eclipse-color-theme</a><br>
</div>
</div>
</blockquote>
The issue with the multiplication of projects out of Eclipse.org is
that you end up with different process to contribute and don't have
the guarantee a contribution would be appreciated and considered.
Being on GitHub is not a proof of an open development process, it's
"just" OSS code. That's why it makes sense for
contributors/consumers (like us) to encourage projects to become
official Eclipse projects. Eclipse Foundation has set up rules that
ensure a really open development process and that guarantee that a
project can't be locked, and that encourage contributions over
forks. It makes things safer.<br>
<br>
<blockquote cite="mid:SNT147-W77633C33FF9F68D6AD812A863D0@phx.gbl"
type="cite">
<div dir="ltr">
<div>Something like open letter from Eclipse Foundation to
Eclipse plugins authors.</div>
</div>
</blockquote>
That's probably a good idea.<br>
Maybe the Foundation (or the community in general) should make it
more official that projects on GitHub/MarketPlace are welcome to
become official Eclipse projects and explain to authors that being
an Eclipse.org project is a sign of real openness and a generator of
success.<br>
<br>
But in any way, I can fully understand from the Foundation POV and
from our "consumer" POV, that there is and will always be a
distinction between Eclipse.org and non-Eclipse.org projects. The
Foundation rules are definitely something good, that make a
difference.<br>
<br>
<blockquote cite="mid:SNT147-W77633C33FF9F68D6AD812A863D0@phx.gbl"
type="cite">
<div dir="ltr">
<div>
<div>Please also help to connect to Red Hat China managers or
marketing.</div>
</div>
</div>
</blockquote>
Unfortunately, I don't know anyone in Red Hat office in China. Maybe
Rob (Stryker) can help.<br>
<br>
<blockquote cite="mid:SNT147-W77633C33FF9F68D6AD812A863D0@phx.gbl"
type="cite">
<div dir="ltr">
<div>
<div>@Angelo Would this email get into jbosstools-dev list?</div>
</div>
</div>
</blockquote>
Yes, it's on. And this answer too. Check you CC list before sending
mails ;)<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>