[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-community] Initial Committer Lists & Project Meritocracy

John,

Most of them have not signed the ECA, so they won't show as committers once the project is approved. That includes even Nigel who was the Spec Lead of JMS, but since he seems to have other duties like Project Fn (https://github.com/fnproject/fn/graphs/contributors) I can't tell, if he will contribute or others at Oracle. Ivar, who not only was in the JMS 2.1 EG but while he did something in the JMS 2.1 repositories likeÂhttps://github.com/jms-spec/jms-examples/graphs/contributors, he or David have taken duties like the EE4J PMC, so it's hard to tell, if they can contribute to individual projects. Contribution to MicroProfile shows, those duties hardly left them enough time to contribute.
I guess it's similar with members of the Apache Board and their ability to contribute to actual projects ;-)

Werner


On Sun, Dec 3, 2017 at 6:00 PM, <ee4j-community-request@xxxxxxxxxxx> wrote:
Send ee4j-community mailing list submissions to
    ee4j-community@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
    https://dev.eclipse.org/mailman/listinfo/ee4j-community
or, via email, send a message with subject or body 'help' to
    ee4j-community-request@eclipse.org

You can reach the person managing the list at
    ee4j-community-owner@eclipse.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ee4j-community digest..."


Today's Topics:

 Â1. Initial Committer Lists & Project Meritocracy (John D. Ament)
 Â2. Re: Oracle Java EE8 Issue Tracker Abandonment (reza_rahman)


----------------------------------------------------------------------

Message: 1
Date: Sun, 03 Dec 2017 15:19:29 +0000
From: "John D. Ament" <john.d.ament@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: [ee4j-community] Initial Committer Lists & Project
    Meritocracy
Message-ID:
    <CAOqetn9NdeSN=O8x91fW-anWM2fz0CdTLLwR5oXbgp=kXq+fbw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

All,

I want to raise a comment on one of the proposals to this group, to make
sure its not lost and see if PMC members or other committers have any
comments on it.

Mark Thomas raised a comment about Initial Committers, and how they seem to
be missing some Expert Group members:
https://projects.eclipse.org/comment/252#comment-252

I'm wondering, as well, are expert group members encouraged to sign up?
Should they be explicitly solicited to join the projects?

Likewise, for the RI projects, how are the initial committers gathered? As
a for instance, if I compare the OpenMQ contributor list and initial
committers:

https://github.com/javaee/openmq/graphs/contributors
https://projects.eclipse.org/proposals/eclipse-openmq

They seem to be misaligned. In other organizations, I recommend new
projects to limit initial committers to those who are actively working on
the project, and work on community building to add potential new
contributors to the project after the fact; typically after they've
established a level of meritocracy on the project.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171203/322709c0/attachment.html>

------------------------------

Message: 2
Date: Sun, 03 Dec 2017 11:48:38 -0500
From: reza_rahman <reza_rahman@xxxxxxxxx>
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker
    Abandonment
Message-ID: <mailman.18.1512320409.28791.ee4j-community@xxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

To be clear, it's not the migration any one is really worried about. It is what happens to each of these technologies after the migration is complete that pretty much every customer is worried about.
What would help is a simple list of which major vendor is committed to moving which technology forward and when they would like to see a new revision, ideally. It is legitimately unnerving for people to have technologies that their business applications depend upon be subject to high levels of uncertainty.
I have no honest answers at the moment. That is highly problematic for anyone advocating Java EE. The community will take care of it is not a credible answer long term.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------From: Markus KARG <markus@xxxxxxxxxxxxxxx> Date: 12/3/17Â 3:03 AMÂ (GMT-05:00) To: 'EE4J community discussions' <ee4j-community@xxxxxxxxxxx> Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker Abandonment
Reza,?be assured, behind the scenes people do work on the migration. At least I do know that for some of the projects, in particular Jersey. A first bunch of projects is currently in progress, other bunches will follow. But yes, certainly it would be really great to have a weekly updated web site showing the content that is currently moved and the particular progress (like "Jersey: xx%") so this is publicly trackable. I CC'ed PMC head Ivar Grimstad about this, maybe he can trigger the Eclipse Foundation to set up such a web site??-Markus??From: ee4j-community-bounces@eclipse.org [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Reza Rahman
Sent: Samstag, 2. Dezember 2017 19:36
To: EE4J community discussions
Subject: Re: [ee4j-community] Oracle Java EE8 Issue Tracker Abandonment?This is a very real concern for many customers. We heard the same concern at JavaOne during EE4J discussions. As I have said for a while now, the best way to address this is a realistic roadmap for EE4J including some kind of commitment, hopefully including from Oracle, as to who is taking ownership of moving which Java EE specification forward. Simply continuing to say it will take time to figure out risks people continuing to worry more and more about the future of Java EE.?At least a simple list of who wants to move which specification forward should not be so hard for a technology and market as mature as Java EE.

Sent from my iPhone
On Dec 2, 2017, at 1:20 PM, Eric Taylor <etay5995@xxxxxxxxx> wrote:Does anyone want to address the issue of the abandonment of the Issue Trackers for major EE8 specifications? Specifically the Jersey and Yasson issue trackers seem to be dead or dying. I briefly corresponded with Dmitry Kornilov regarding the state of the Jersey issue tracker, and essentially he told me that most of the original employee developers are no longer contributing or even working at Oracle any more. He told me he was working on finding new developers, but this was over a month ago and frankly I have begun to think that Java EE8 is heading down the neglected path that EE7 was on. Issues are piling up and there is no communication between developers to even help facilitate patching and submitting pull requests. Does Oracle have any responsibility left in this, or have they just dumped Java EE8 in the Eclipse Foundation's hands and said "Good luck!"??Is there a central point of contact regarding EE8 or is comm
Âunication fragmented across each specification? Should I abandon server side Java and just start using server side _javascript_ (node.js)? Just kidding on the last part. ;)?Thanks,Eric_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/ee4j-community/attachments/20171203/e0f0894e/attachment.html>

------------------------------

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community


End of ee4j-community Digest, Vol 4, Issue 31
*********************************************