[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [modeling-pmc] VIATRA2 is not operating as an Eclipse open source project
|
Dear Wayne,
CQ 6703 was submitted today. That CQ is for a code contribution.
This appears to be a significant contribution of code. It is the
first contribution in more than two years to the project. In
comments on that CQ, the project lead indicates that the
contribution is "the newest combined release of the VIATRA2 model
transformation framework" and that "In each iteration, we compile
the contributions from the developers and push the code to
Eclipse.org."
This runs counter the open source rules of engagement set out in the
Eclipse Development Process [1]. Specifically, the project is not
operating in an open and transparent manner leaving little
opportunity for others to join the project. The project has been
established for some time, and should be operating fully at
eclipse.org.
a few details to clarify, as I believe there are some misunderstandings.
There are several developers listed in the contribution. Based on
the amount of contribution, I believe that each of these developers
should become committers and do all future work directly in the
eclipse.org code repository.
It is important to emphasize again that "the amount of code in the contribution" equals to the "original plus the delta". Nevertheless, I do completely agree with you that each of the developers should be promoted to committers; to my knowledge, this has not been possible under the GMT umbrella.
The project website [2] indicates that there have been numerous
releases of the project, including statements like "The VIATRA2
Release 3.1 has been approved by Eclipse.org!". AFAICT, the project
has not undergone a single release review as required by the Eclipse
Development Process. The project must plan to undergo a formal
release as soon as possible.
I think the error is on our part in this case. The word "release" has been historically used to mark milestones in VIATRA2 development, and is *not* intended to imply that this is a "release" in the Eclipse.org sense.
The project is--according to my records--in incubation. Incubation
branding must be provided on the download page and in downloads. I
have marked the project as "incubation-non-conforming"; the project
cannot benefit from parallel IP until the incubation branding issues
is resolved.
Is there a guide somewhere on how to do this? I'd really like to resolve all problems as soon as possible.
Istvan
--
Istvan RATH, PhD
Research associate
Budapest University of Technology and Economics
Fault Tolerant Systems Research Group
