| Re: [technology-pmc] [ice-dev] Committer vote for Andrew Bennett has been vetoed by the PMC |
Okay, great. Will do. Thanks!
Jay
Jay,
Figure 3 as the starting point does sound correct. Also, I suggest creating bug reports in Bugzilla for the "unreported" bugs that he's fixing (basically, change them from unreported to reported) so his fixes can be attached to those bug reports (via Gerrit).
Once his contributions have been reviewed and committed, you can re-nominate him and include the Bugzilla/Gerrit links that show the contributions.
Eric
On 11/18/2014 12:00 PM, Jay Jay Billings wrote:
Gunnar,
I emailed him and yes, I can confirm that each class is less than 1000
lines.
It required much less than I thought in fact. The exact totals are:
IPSReader : 454
IPSReaderTester : 155
IPSWriter : 263
IPSWriterTester : 215
CaebatModel : 464
CaebatModelTester : 236
So we will go ahead with path 3?
Jay
On Nov 18, 2014 11:05 AM, "Gunnar Wagenknecht" <gunnar@xxxxxxxxxxxxxxx
<mailto:gunnar@xxxxxxxxxxxxxxx>> wrote:
Hi Jay,
Sounds like multiple different things. If each review is below 1000
lines of codes (not counting deleted lines) then a CQ might not be
required.
Please have a look here:
https://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf
Based on what you are saying, I believe figure 3 does apply. Can you
confirm?
-Gunnar
Am 18.11.2014 um 16:30 schrieb Jay Jay Billings
<jayjaybillings@xxxxxxxxx <mailto:jayjaybillings@gmail.com>>:
Gunnar,
Yes. He has four new classes to add, two src and two tests for our
I/O bundle, that he wrote over the past two weeks. He also has
several minor fixes for unreported bugs that he found. Probably a
few thousand lines in all.
Next week he is going to rework two small bundles, probably 10-20
files total.
Jay
On Nov 18, 2014 10:11 AM, "Gunnar Wagenknecht"
<gunnar@xxxxxxxxxxxxxxx <mailto:gunnar@xxxxxxxxxxxxxxx>> wrote:
Hi Jay,
Thanks for the update. The best way to get him starting
contributing to your project is via Gerrit. After signing the
CLA, he can push reviews right away, which can be merged by
another committer.
Is there existing code he wrote that should go into your code
repository? If yes, how large it?
-Gunnar
Am 18.11.2014 um 16:04 schrieb Jay Jay Billings
<jayjaybillings@xxxxxxxxx <mailto:jayjaybillings@gmail.com>>:
Hi everyone,
I emailed Wayne to figure out how I could get in touch with
Gunnar/the PMC to talk about the vote to make Andrew Bennett
a committer.
I'm sorry; I should have been clearer in my nomination.
Andrew is employed by us on this project and he should have
been listed as a committer on the proposal (in Feb.) because
I knew he was switching to ICE. It just slipped my mind. He
is currently working on ICE full time and has a boat load of
code to commit. He was a committer on the Sourceforge.net
<http://sourceforge.net/> project too for eleven months.
Wayne suggests that the code probably needs to come in
through a CQ. I'm fine with that (and it would give us the
opportunity to learn more about the process). This won't be
the last of Andrew's work though. What do we need to do to
get him committing?
Jay
>
> Hi Jay.
>
> The best way is to just engage via the PMC mailing list.
Transparency and all...
>
> The entire PMC interpreted your nomination criteria as
being motivated by employment status.
>
> I recommend that you, after explaining the situation to the
PMC, restart the election citing that Andrew already has a
record of contribution to the project.
>
> Another consideration is that the "boat load" of code that
he has to contribute has been written outside of the context
of the project and likely cannot be reasonably considered to
have been developed "under the supervision of the PMC". Even
if Andrew had been a committer from the beginning of the
Eclipse project, that code would likely have to go through
the IP due diligence process.
>
> As a general rule, a contribution is considered to be
developed "under the supervision of the PMC" if the
contributor was a committer before writing a single line of
code, and the functionality is "in plan" (either explicitly
in the project plan or has an associated bug).
>
> So the alternate recommendation is that you put the
contribution in a CQ (which I believe that you need to do
anyway) and immediately start the election citing the
contribution as the nomination criteria. The PMC will accept
that the code comes with a committer.
>
> HTH,
>
> Wayne
>
>
> On 18/11/14 05:41 AM, Jay Jay Billings wrote:
>>
>> Wayne,
>>
>> Do you know how I can get in touch with Gunnar? I need to
talk to him about this.
>>
>> Andrew is employed by us on this project and he should
have been listed as a committer on the proposal because I
knew he was switching to ICE. It just slipped my mind. He is
currently working on ICE full time and has a boat load of
code to commit. He was a committer on the Sourceforge.net
<http://sourceforge.net/> project too for several months
after switching.
>>
>> Jay
>>
>> ---------- Forwarded message ----------
>> From: "portal on behalf of Gunnar Wagenknecht"
<portal-noreply@xxxxxxxxxxx <mailto:portal-noreply@eclipse.org>>
>> Date: Nov 18, 2014 1:24 AM
>> Subject: [ice-dev] Committer vote for Andrew Bennett has
been vetoed by the PMC
>> To: <ice-dev@xxxxxxxxxxx <mailto:ice-dev@xxxxxxxxxxx>>
>> Cc:
>>
>> technology.ice Committers,
>> This automatically generated message marks the PMC's veto
of the vote for
>> Andrew Bennett's full Committer status on the
technology.ice project.
>>
>> The PMC's comments were: Jay,
>>
>> Committership at Eclipse is not bound to employment. In
order to become a
>> committer, a developer must demonstrate merit through
contributions to the
>> project. Those contributions are typically patches
submitted via Bugzilla
>> and/or Gerrit. Please reference them when nominating
committers.
>>
>> -Gunnar
>>
>> If you have any questions, please do not hesitate to
contact your project
>> lead, PMC member, or the EMO <emo@xxxxxxxxxxx
<mailto:emo@xxxxxxxxxxx>>
>>
>> _______________________________________________
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc
_______________________________________________
technology-pmc mailing list
technology-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/technology-pmc