AFAICT, the Eclipse Fennec project has no actual
code. The project has been around for a bit, but is
obviously stalled.
In this sort of false-start situation, there's really
no way for a contributor to build merit and do things
the right way, so the EMO tends to use the powers
granted by the EDP to appoint a committer when asked by
the project lead.
For completeness, when a project has code and active
committers, we require strict adherence to the rules
regarding committer elections. When a project has code,
but no active committers, the EMO will work with the PMC
to sort out a resolution.
Assuming there is no objection from the PMC, the EMO
can make the appointment.
Wayne
Hi
Ed,
I
understand where you are coming from, and I was a
bit unsure myself as I wrote the recommendation.
It may have been a bit hasty.
A bit
of background, so we might find a solution:
We
are still in the initial setup phase for the
Project. We moved the first Project and, due to
too much workload, stagnated after that. The only
thing that is missing right now, is the final
polishing on the build and deployment process via
GitHub actions. This is usually a trial and error
process with commit and pray.
Peter
will take care of this. He furthermore will do
more work on the different projects in the future,
and we consider him Part of the initial Team for
the Project. As we made the proposal, Peter was
not really on our radar, despite us knowing him
for quite some time.
Long
Story short: He might be able to do what he
intends to do in a PR, but testing different
scenarios like SNAPSHOT releases to sonartype on
the snapshot branch and maven central releases on
the main branch are easier to achieve and test if
he gets committer status. So we thought, we could
take the easy route via a committer election. I
guess I should have written all this in the
recommendation, now that I think about it.
I
suggest sending all this as an amendment to the
Mailing list for clarification, or do you have
different ideas?
Thanks,
Jürgen.
Am
26/02/2025 um 18:40 schrieb Ed Merks:
Jürgen,
I hate being a stickler for details, but even if
I were to approve this vote, the EMO would
reject it.
During initial project creation you could
specify any set of initial committers. But now
you must justify adding a committer to a project
based on demonstrated contributions to the
project, e.g., accepted pull requests. It's
really not a high bar, everyone should
understand how to create a pull request, and
it's easy for any committer to approve one.
Once you have that, we can proceed.
Sorry,
Ed
On 26.02.2025 13:33, Eclipse Foundation via
modeling-pmc wrote:
A Committer election for
Peter Kirschner on project Eclipse Fennec
(modeling.fennec) was started by Jürgen Albert
with this criteria:
Peter Kirschner is a long standing and active
member of the OpenSource
community.
He will take an active role in maintaining
Eclipse Fennec and help the
various Projects to start flying.
It is my pleasure to nominate Peter Kirschner
as a committer on Eclipse
Fennec.
Eclipse Fennec project committers can click
the election link below to vote.
Election: Election for Peter Kirschner as
Committer on Eclipse Fennec [1]
Project: Eclipse Fennec [2]
[1]
https://projects.eclipse.org/projects/modeling.fennec/elections/election-peter-kirschner-eclipse-fennec
[2] https://projects.eclipse.org/projects/modeling.fennec
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/modeling-pmc
--
Jürgen Albert
CEO
Chair Eclipse OSGi Working Group Steering Committee
Data In Motion Consulting GmbH
Kahlaische Str. 4
07745 Jena
Mobil: +49 157-72521634
E-Mail:
j.albert@xxxxxxxxxxxxxxx
Web:
www.datainmotion.de
XING:
https://www.xing.com/profile/Juergen_Albert5
LinkedIn:
https://www.linkedin.com/in/juergen-albert-6a1796/
Rechtliches
Jena HBR 513025
​
--
The Eclipse Management
Organization | Eclipse Foundation