|
Werner,
Unfortunately, it's not automatic. You can use Manage My
Subscriptions in your profile settings at Eclipse.org. It's
probably best to sign up for all -dev lists you are interested in.
-- Ed
On 8/28/2018 8:35 AM, Werner Keil
wrote:
I am a committer, but I’m
not sure, if I’m subscribed t that list yet.
Sent from Mail for Windows 10
Werner,
If you haven't, you might also reach out on the developer
list -- openmq-dev@xxxxxxxxxxx. I believe
it's an open list (as they all are), any Eclipse member can
join and you don't need to be a project committer.
-- Ed
On 8/28/2018 8:21 AM, Werner Keil wrote:
Ed,
Should e.g. Payara who has strong
ties to Glassfish be interested, that could be an
option, but like in other cases should a double lead
also be an option, I could help here. I am project lead
of another Eclipse project and I know despite some other
trends and approaches for asynchronous message handling
JMS/MQ are often a key part of Enterprise
infrastructures across industries.
Werner
Nigel may be on holiday. His role in Eclipse Open MQ
was intended to be transitional. He has approved PRs
that have come up but there haven't been many. I don't
know why he isn't shown as Lead.
If someone has an interest in this project, we will
try to make a transition happen smoothly. I am trying
to line up some support -- if that's what you would
like.
-- Ed
On 8/28/2018 7:43 AM, Werner Keil
wrote:
Wayne,
Thanks for the update also to
the contributors page. Based on being Spec Lead
earlier that makes sense, but we may have to
discuss in the project list for OpenMQ, whether
or not Nigel's new roles and duties inside
Oracle still allows him to lead the project as
he did with the JSRs.
While the API/spec probably
makes sense and has relevance to David the
strong Apache ties of Tomitribe may mean a
little less relevance to them compared to
ActiveMQ, hence he is not even a committer there
at the moment.
Any committer can
initiate a vote to add a new committer or
project lead. Any nomination should include
a statement of merit which will become part
of the public record. Existing project
committers must then vote on the nomination.
If after a week, we have at least three
positive votes and no negative votes, the
election is declared successful. Note that
the PMC needs to approve all votes; their
main role is to ensure that the process has
been correctly followed.
There's more
information in the handbook.
On Tue, Aug 28, 2018 at
8:39 AM, Werner Keil <werner.keil@xxxxxxxxx>
wrote:
So can
any committer initiate such vote after
asking potential candidates?
According to EF
rules any committer can
apply for leadership, or
nominate others for
leadership. If a project
has no lead, you should
ask the committers to
elect (at least) one.
Dmitry,
I'll create
tickets especially for
OpenMQ in areas that
seem unclear or need
verification.
Btw, is
there a concept behind
some projects like
OpenMQ being without a
lead, while others
(e.g. JMS) have
Tomitribe/David, and
at least one other
project even has 2 or
more project leads?
(not looking
at EE4J top level,
where sharing this
could be a strategic
decision)
Dmitry,
Thanks
for the update.
Especially for the
C client and
packaging module
it has to be
confirmed, if they
work in the JIPP.
For
others I created
issues and saw
these confirmed,
so I will prune
some of these
jobs.
@Dmitry
is this also
the view by
PMC, Steering
Committee or
Eclipse
officials?
We
would love to
see some
consistency,
but we also
respect
projects teams
decisions.
IMO, what
Markus is done
is fine.
I
made two
builds work in
OpenMQ, but
there could be
special
requirements
e.g. native
build jobs
that have to
be verified,
if the
necessary
slaves are
available. I
helped a
highly
distributed
Automotive
project with
their Jenkins
infrastructure, there special slaves e.g. for a particular compiler etc.
were a key
aspect. It may
be a little
less complex
here (maybe
for IoT there
are similar
needs at
Eclipse ;-)
but MQ is
among the
projects that
have native
build-chains
and also tight
integration
with the
Glassfish
project, which
may need to be
done in its
JIPP rather
than OpenMQ.
Thanks,
Werner! Does
it mean that I
can mark the
build task for
OpenMQ as
done?
Every
project is
free to do it
as they
please. There
is no need for
consistency
among
projects, and
consistency
even might be
an obstacle to
some extend. A
project not
even needs to
have CI at
all. At JAX-RS
we only have
two jobs in
JIPP: Nightly
build (pushed
into EF's
Nexus) and
Release build
(pushed into
OSSRH's
Nexus).
-Markus
What
about Jersey?
(OpenMQ
has 5, but for
the sake of
consistency,
I'd like to
get the
*-continuous
build to run
without errors
for now)
Unfortunately
the OpenMQ
jobs were set
up entirely
different, one
or more point
to
repositories
that don't
seem to be in
Eclipse-EE4J
at all.
Are
there multiple
pipelines for
JAX-RS?
Yes
please mark it
as done.
Markus,
can I mark
JAX-RS release
CI/CD pipeline
task as done
here:
—
Dmitry
I
requested a
JIPP earlier
this year for
our Nightly
Builds and
simply set up
an additional
job for
staging on
OSSRH.
Did
you request
the JIPP for
that or was it
there already?
JAX-RS
API: Release
pipeline done,
Github Task
closed,
Release 2.1.1
for EE4J_8 is
staged on
OSSRH. Next:
Filing release
review.
Here
is the latest
state of CI/CD
pipelines
work:
There
is a little
progress since
last week
(almost
nothing). If I
missed
something
please report
your progress
here. There
are still a
lot of
projects
waiting for
volunteers. I
am requesting
the community
to be more
active.
I'm
traveling this
week with lots
of meetings,
but next week
I'll start
working on it.
|
