[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [technology-pmc] Asking for Approval of Jubula 1.0.0 Graduation/Release review
|
On 5/12/11 4:24 PM, Konstantin Komissarchik wrote:
A negative vote on graduation should not be taken as implying the project is
in bad shape. It is simply a statement that more work is required in
developing open source process maturity, which is what the incubation phase
is for.
Is there a particular reason that rushing graduation is warranted in this
case? A project can do releases while in incubation, it can contribute to
the release train, etc. Rushing graduation simply to be able to do a 1.0
release does not seem to be in spirit of EDP.
- Konstantin
I'm in agreement with Konstantin on this. While I appreciate the great
efforts made by the Jubula team to clean the code and begin to alter
their process, there seems to be little public evidence of those process
changes (other than this discussion). We must uphold the standards that
other Eclipse projects have had to satisfy; in my opinion there simply
can not be an exception made if we want to maintain credibility. It
sounds harsh, but there's a lot more to becoming a true open source
project (the way that Eclipse defines it) than just releasing source code.
-1 on graduation.
Jubula team: have you explored the idea of releasing a separate
commercial product (along with professional services to support it) that
is based on the open source code? That way your customers can get the
warm and fuzzy feeling of having a >0.x release as well a company behind
it. I worked at a company that did that a few years ago.
Eric
-----Original Message-----
From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
Sent: Thursday, May 12, 2011 1:06 PM
To: Technology PMC
Subject: Re: [technology-pmc] Asking for Approval of Jubula 1.0.0
Graduation/Release review
Hi All,
It seems that we are in the middle of a great discussion. I love to see
such an amount of activity on our list.
Frankly, I think there are many things to consider for making a
decision. Converting an existing commercial project into an open source
project is a tough but the right thing to do. From my experience it's a
tremendous amount of effort (if not impossible) to also convert an
existing community.
Judging project openness from the traffic on a dev list and newsgroups
isn't the right approach in this case. Eclipse is about community. But
Eclipse is also about commercial adoption. IMHO is just natural that any
user base which uses commercial support won't post to any open
forum/newsgroup but call/mail their support contact. Thus, I think it's
fair to say that the forum/newsgroup will likely represent only those
users which use the open source project (either converted from a
commercial version or really new users).
The dev list could likely need some love by sending regular meeting
minutes. I'm not sure that this has to be on a daily base. There are
many major Eclipse projects which don't publish regular meeting minutes.
BTW, there is a great article on community development here:
http://wiki.eclipse.org/Community_Development_for_Eclipse_Projects
Am 10.05.2011 14:01, schrieb Achim Lörke:
we are planning to release the 1.0.0 of Jubula (...) as part of
the Indigo release train. With this release we also want to
leave the Incubation state.
Reading through the article referenced above I don't think that Jubula
is in such a bad shape that it justifies a negative vote. Over time the
Jubula team has demonstrated some very good progress in understanding
and adopting the Eclipse processes. The amount of
information/documentation they have on the website, wiki and in Bugzilla
is quite good (IMHO).
Their code base definitely deserves a 1.0 release. The rules are that
this also requires graduation. Graduation does not, however, mean
project mentors are gone. Especially for graduating projects staying in
Technology we will be their to answer questions.
Oh and we'll also do project reviews. If in a year from now the silence
on the dev list still exists, then we can reconsider our options.
Thoughts?
-Gunnar
