Working group membership is not required to make contributions to the Sparkplug specification project or even to become a committer on it.
Strictly speaking, this is true. That is, it is mostly true, and only with a very specific interpretation of "become a committer". :-)
The first part is completely true. To contribute to a specification project, one must sign the ECA. With this in hand, a committer can accept your contributions.
It's the "becoming a committer" part where I'm splitting hairs. You don't need to be a member of a working group to be nominated as a committer, but once the election is complete, working group membership is one of the agreements that needs to be in place before one can be granted actual committer status.
For most working groups, we have both a company working group participation agreement (WGPA) and an individual WGPA. Individual WGPAs do not require a paid membership.
At this point in time, the Sparkplug Working group doesn't have an individual WGPA. But, AFAIK, Ian is working under contract by an organization that has, so we're pretty sure that we can make that work.
Currently, the Sparkplug WG charter does not include the concept of a committer member; however, this is something the steering committee could add to accommodate cases like yours. I wonder if this is something that working groups should add automatically when they add specifications to their scope.
This is something that we should take up with the working group.
Wayne: I think there is some confusion here about specification projects, specification committees and working groups. Do you think we should hop on a call with Ian Skerrett and Ian Craggs to understand what they are looking for and suggest a way forward?
Sure. Let's take that offline.
Wayne
Best,
Frédéric DESBIENS
Program Manager, IoT and Edge Computing | Eclipse Foundation, Inc.
I confess to not being familiar with the Eclipse specification
process, so I'm not sure how things are expected to work. The
principal reason that Dominik nominated me was to take advantage
of my experience of working on the MQTT and MQTT-SN specifications
at OASIS. I was secretary as well as a voting member for the MQTT
5.0 specification and am currently co-chair of the MQTT-SN
specification committee. Apart from my experience in the
specification process, SparkPlug is also related to MQTT so there
are two levels of connection.
The main goal is to allow my full participation in the
specification process for SparkPlug, attending working group
meetings, and being able to vote on any resolutions, as well as
contributing documentation updates and software.
I looked at the membership prospectus for the working group
(https://f.hubspotusercontent10.net/hubfs/5413615/sparkplug-member-prospectus%202020.pdf)
and concluded that I could join as an individual participant
member for the fee of $500 (and signing the participation
agreement). But then Ian Skerrett checked with the Eclipse
organization (I don't know who), and suggested this committer
election route as a result.
Obviously I don't need to be a committer to submit PRs to the
project, which I am quite happy to do. It is membership of the
working group that I'm aiming for. I don't know if those are
different things or not.
Ian
On 09/12/2020 03:52, EMO EMO wrote:
There is precedent for using established expertise
in a related field as the criteria for a committer election.
This is, IMHO, especially true for specification projects. As
specification projects are industry expert groups, past
contributions elsewhere that establish an individual's
credentials in the domain area should be taken into
consideration when determining merit.
I am having a bit of concerns approving this request.
I am definitely not doubting the achievements of Ian
when it comes to MQTT, as listed in the nomination in a
transparent manner.
However, these are not contributions to the Sparkplug
project. As far as I understood the nomination, you expect
Ian to contribute to Sparkplug "in the future".
As "future" contributions don't count, for me that
would be a reason to reject the request for a normal
Eclipse project. However, to my understanding, Sparkplug
is more a specification project. So let's discuss if that
should be treated differently.
Red Hat GmbH, https://de.redhat.com/
Registered seat: Grasbrunn, Commercial
register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian
Klemm, Laurie Krebs, Michael O'Neill