Cool. Thanks Wayne,
So Nick and Brian, I think we can conduct an orderly transfer of powers if so desired. I think the first step should be to remove the other inactive commiters so we can properly do elections. That can be done by the current project lead or by me, if I
could ever remember where that remove inactive committer panel moved to...
Doug.
From: Wayne Beaton [wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, June 18, 2019 10:50 PM
To: Doug Schaefer
Cc: Nick Boldt; Brian Payton; Tools PMC mailing list; Jean-Francois Maury; DTP development mailing list
Subject: Re: RE: [tools-pmc] DTP committer election failed: only 1 out of 3 committers voted.
Per the EDP:
The election process begins with an existing Committer on the same Project nominating the Contributor. The Project’s Committers will vote for a period of no less than one week. If there are at least three (3) positive votes and no negative votes within the
voting period, the Contributor is recommended to the Project’s PMC for commit privileges.
If there are three (3) or fewer Committers on the Project, a unanimous positive vote of all Committers is substituted.
If the PMC approves, and the Contributor signs the appropriate Committer legal agreements established by the EMO (wherein, at the very least, the Developer agrees to abide by the Eclipse Intellectual Property Policy), the Contributor becomes a Committer
and is given write access to the source code for that Project.
The move to an Eclipse Tools subproject did happen. Apparently, we didn't quite update the project metadata completely. I've fixed it.
Wayne
Thanks Wayne,
If Brian hands over leadership to Nick and Nick removes all inactive committers, including Brian, can we then redo the election? It's just not clear how elections works when there are less than three active committers.
Also, was DTP ever moved under tools officially? The PMI says it's still a top level project.
Doug.
From: Wayne Beaton [wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, June 18, 2019 2:08 PM
To: Doug Schaefer
Cc: Nick Boldt; Brian Payton; Tools PMC mailing list; Jean-Francois Maury; DTP development mailing list
Subject: Re: RE: [tools-pmc] DTP committer election failed: only 1 out of 3 committers voted.
I need the PMC to document their decision on an open forum, give sufficient time for the community to respond, and then ask the EMO to make the changes.
I leave the definition of "sufficient time" to the PMC's discretion. IMHO, the discussion in this forum constitutes reasonable documentation of the decision.
HTH,
Wayne
That would be easiest. The Tools PMC can reboot the project, but I imagine there's more paperwork for that. Though Wayne would know for sure.
Doug.
From: Nick Boldt [nboldt@xxxxxxxxxx]
Sent: Tuesday, June 18, 2019 1:39 PM
To: Brian Payton
Cc: Doug Schaefer; Tools PMC mailing list; Jean-Francois Maury; DTP development mailing list
Subject: Re: RE: [tools-pmc] DTP committer election failed: only 1 out of 3 committers voted.
Brian,
If you're happy to appoint me as lead, so that I can delegate some work to Jeff, please make it so.
Thanks,
Nick
If I resubmit the election, and only get your and my votes, it'll still fail as it needs 3 votes to pass.
But if I'm project lead, then I can simply delegate someone as a committer, right?
Nick
Sorry, just saw these emails.
Nick, if you want to restart the committer election, I'll watch for it and vote.
And if you would like to take over as DTP project lead, that would be fine with me. (I really haven't touched anything Eclipse-related for years now.)
Regards,
Brian
Brian Payton
Senior Software Developer
IBM Analytics
Doug Schaefer ---06/12/2019
01:14:41 PM---Thanks Wayne, I know. Just waiting to see Brian's response or a timeout to get triggered. ;) Doug.
From: Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
To: Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
Cc: Jean-Francois Maury <jmaury@xxxxxxxxxx>, Brian Payton <bpayton@xxxxxxxxxx>,
DTP development mailing list <dtp-dev@xxxxxxxxxxx>
Date: 06/12/2019 01:14 PM
Subject: [EXTERNAL] RE: [tools-pmc] DTP committer election failed: only 1 out of 3 committers voted.
Thanks Wayne, I know. Just waiting to see Brian's response or a timeout to get triggered. ;)
Doug.
From:
tools-pmc-bounces@xxxxxxxxxxx [tools-pmc-bounces@xxxxxxxxxxx] on behalf of Wayne Beaton [wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, June 12, 2019 4:12 PM
To: Tools PMC mailing list
Cc: Jean-Francois Maury; Brian Payton; DTP development mailing list
Subject: Re: [tools-pmc] DTP committer election failed: only 1 out of 3 committers voted.
FWIW, when a PMC declares a project dysfunctional, they get some pretty broad powers to make whatever changes they'd like to the project team.
The PMC can decide to retire or appoint specific committers or project leads. It's a power that should be used rarely as it circumvents the community process.
So... you don't actually have to retire any committers, or appoint Nick as an interim custodian (you can just appoint Nick's candidate if that makes sense to you). You should also appoint that candidate as a committer while you're
at it (one role does not imply the other).
HTH,
Wayne
On Wed, Jun 12, 2019 at 3:47 PM Nick Boldt <nboldt@xxxxxxxxxx>
wrote:
Brian,
I'm trying to elect a colleague into the DataTools project so I can pass on some responsibility to him, as my time to maintain DTP is becoming increasingly stretched thin and his core function depends on DTP continuing to work (mine
no longer does).
I submitted an election for Jeff (Jean-Francois) Maury last week, but no one other than myself voted. There are supposedly only 2 active committers in DTP right now (other than myself), but I don't see any commits since 2015 or
2016, suggesting that neither yourself or Yulin are still active.
Could you resubmit the nomination? Or would you like me to take over as project lead?
Thanks in advance,
Nick Boldt
On Sat, Jun 8, 2019 at 2:51 AM Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
wrote:
On Fri, Jun 7, 2019 at 11:17 PM Nick Boldt <nboldt@xxxxxxxxxx>
wrote:
Hey, Tools PMC:
I tried to elect a colleague into the DTP project (since he's helping me maintain it) and the other 2 remaining committers on the DTP project failed to vote +1, -1, or 0.
Can you declare the project dysfunctional? I can submit the nomination again if you'd like them to have a second chance to respond.
Did you try to contact the project lead? Please do so and add the PMC list on CC. If we get not reply in 2 weeks and no one else objects on the list I propose that we(the PMC) ask foundation to make you project lead so you can handle
retiring inactive people, rerun voting and do the general handling of the project.
Regards,
Alex
Nick
On Thu, Jun 6, 2019 at 2:14 PM Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
No. I cannot. The rules require that, in the case of a project with three or fewer committers, that all committers vote.
There are two workarounds:
- Have the project lead retire those committers and rerun the election; or
- Have the PMC declare the project dysfunctional and request that add/remove committers and project leads.
I'm thinking that we might be leaning towards the later.
Note that Project Lead and Committer are two separate roles. While it generally makes little sense for somebody to be a Project Lead but not a Committer, this is precedent. If you want them to have both roles, they'll need to be
elected (or appointed by the PMC if we go the dysfunctional route) to both.
I've cleaned up the bogus PMC relationships. They should disappear from the "who" page shortly.
Wayne
On Wed, Jun 5, 2019 at 10:50 PM Nick Boldt <nboldt@xxxxxxxxxx>
wrote:
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt / http://nick.divbyzero.com
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
--
Nick
Boldt
Principal
Software Engineer, RHCSA
Productization
Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
http://nick.divbyzero.com
“The Only Thing That Is Constant Is Change” - Heraclitus
--
Nick
Boldt
Principal
Software Engineer, RHCSA
Productization
Lead :: JBoss Tools & Dev Studio
IM: @nickboldt / @nboldt /
http://nick.divbyzero.com
“The Only Thing That Is Constant Is Change” - Heraclitus
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information
by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission
by unintended recipients is not authorized and may be unlawful.
--
Wayne Beaton
Director of Open Source Projects |
Eclipse Foundation, Inc.
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information
by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission
by unintended recipients is not authorized and may be unlawful.
--
Wayne Beaton
Director of Open Source Projects |
Eclipse Foundation, Inc.
--------------------------------------------------------------------- This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
|