New Merger nomination.

[Mariusz Felisiak]

I nominate Claude Paroz to a new MERGER for 8 years of contributions to Django, including triaging tickets, reviewing PRs, and serving as the Django translations manager. Claude is one of the most  active contributor with outstanding impact on Django. He was also awarded the 2017 Malcolm Tredinnick Memorial Prize (https://www.djangoproject.com/weblog/2018/jan/22/2017-malcolm-tredinnick-prize-claude-paroz/).

Best,
Mariusz Felisiak

[charettes]

I second this nomination.

[Carlton Gibson]

Seconded. 

 

Claude is one of the few existing committers who still uses and needs his commit access. He handles the translation updates for each release, and we’d be (not lost but) lost without that help. 

 

Kind Regards,

 

Carlton

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/891fb3f3-c969-4d3e-8d92-89d58c998d40%40googlegroups.com.

[Adam Johnson]

Big +1 from me, Claudes contributions are solid.

--

You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/607e208d-2307-4f5e-8e94-029ebbcac612%40googlegroups.com.

--

Adam

[Tom Forbes]

+1 from me! Seems like a no-brainer to make Claude a merger, his past and present contributions have been fantastic.

[James Bennett]

A quick refresher on this since DEP 10 governance is still quite new:

Mergers have no special decision-making privileges -- being a Merger,
while important for the project, is not equivalent to the former
"committer"/"core" status, and is not used as an honor or as a reward
for past service or contributions.

The process for appointing a Merger or Releaser is:

* Anyone may suggest a candidate
* However, only a member of the Technical Board can formally nominate
someone to be a Merger or Releaser
* The nomination is then confirmed or rejected by public vote of the
Technical Board
* Because an election of the Technical Board has been triggered (by
acceptance of DEP 10), any appointment made by the current Technical
Board expires after the election unless the newly-elected Technical
Board confirms it

[James Bennett]

So I guess it's worth walking through how to do this.

The first step would be a member of the Technical Board deciding
Mariusz' suggestion is a good one, and nominating Claude to be a
Merger, putting the question to the full Technical Board for voting:
"Shall Claude be appointed a Merger?"

The Technical Board would have one week to cast their votes (+1, 0, or
-1) on the question. Those votes must be cast publicly.

If the result of that vote is 3 or higher, Claude would be appointed a
Merger, though the appointment would be a temporary one because of the
pending Technical Board election (an outgoing Technical Board can only
make temporary appointments under DEP 10). Once the election is over,
the new Technical Board could make the appointment permanent.

[Tom Forbes]

Thanks for that James! Out of interest what is the exact implementation of the public vote? Is that performed at a meeting, via the mailing list or via the same/similar software used to elect the DSF board?

Tom

[Claude Paroz]

Hey! Thanks for suggesting me as a merger!

However, I'd like to clarify that I'm not requesting this commit bit. If the project thinks it's good that I get it, I'll accept that and do my best to use it as the new DEP suggests. If not, I can certainly continue to contribute as I've done in the past.

Cheers,

Claude

[Markus Holtermann]

Thanks James for summarizing the process. Thanks Mariusz for the suggestion.

Let's make it official, then. I'd like to nominate Claude Paroz (https://github.com/claudep) to be a Merger for the Django project and ask my fellow Technical Board members to cast their votes.

Claude has been contributing to Django for almost a decade. His roles in i18n related matters has been a constant help to the project. Providing Claude with commit access to github.com/django/django and giving him the MERGER role will allow him to continue his work and maintain an up to date translation base in the project, especially in the days leading towards a release.

I vote +1

/Markus

> --
> You received this message because you are subscribed to the Google
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-develop...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/django-developers/a3ae8f2e-b6a8-4d93-8c62-954dc1646b3d%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/a3ae8f2e-b6a8-4d93-8c62-954dc1646b3d%40googlegroups.com?utm_medium=email&utm_source=footer>.

[James Bennett]

On Sat, Mar 14, 2020 at 5:00 AM Markus Holtermann
<in...@markusholtermann.eu> wrote:
> Claude has been contributing to Django for almost a decade. His roles in i18n related matters has been a constant help to the project. Providing Claude with commit access to github.com/django/django and giving him the MERGER role will allow him to continue his work and maintain an up to date translation base in the project, especially in the days leading towards a release.

Again, I need to point out this is not how DEP 10 works.

The Merger role is not just a new name for "committer". If Claude is
appointed a Merger, he will be forbidden to do what you are saying --
a Merger cannot push their own contributions directly into Django!

DEP 10 says:

"[A] Merger MUST NOT merge a Minor Change primarily authored by that
Merger, unless the pull request has been approved by another Merger,
by a Technical Board member, or by the Django Security Team."

The reason for the Merger role is that we need people with the ability
to merge pull requests when the decision-making process says it is
time to merge them. Mergers have some power to use judgment on what
PRs get merged, but it is not the power to judge what is or isn't a
good technical change to make to Django -- it is the power to judge
when something does or does not need more discussion on the public
forums.

Mergers are not technical leaders. Their job is to serve the community
by keeping a specific part of the project -- merging pull requests
according to community decision process -- flowing properly. The role
of Merger is also not a reward or a way to recognize someone's past
accomplishments or contributions. Honoring and recognizing and
rewarding people's work is the DSF's job. We do not use "let's give
him commit access" for that anymore.

This is not to diminish the importance of the role, because it is
important. But it is important in a very different way than the old
"committer" role was, and has very different responsibilities and very
limited powers. Since the vote has been asked for, I urge the
Technical Board members to read DEP 10 carefully and be sure you
understand what a Merger does (and what a Merger doesn't do!) as you
consider your votes. Django probably should have only a very few
Mergers -- DEP 10 only requires that there be three of them -- because
the role of Merger is only to do very specific things to keep the
project working smoothly.

If the worry is about ensuring translations are brought in regularly
and smoothly from Transifex, the Technical Board has authority for
that that and can work with the translation team to set the process
(there is a whole section in DEP 10 about interaction between
different teams within the Django project, for this reason). Which
might end up being "Claude initiates the pulls from Transifex" (though
a process that depends on one specific person is a bad process), but
that is not a justification to make someone a Merger. If the worry is
about i18n code in Django itself, Claude already has the same power
anyone else has to open and review and comment on pull requests, start
discussions on the mailing list or forum about the best approaches,
and so on. But even if he is made a Merger, he would not have the
power to write code and commit it directly into Django, because that
is not a power of a Merger.

[Carlton Gibson]

I don't know if this got blocked in the now-obsolete use of cognates of "commit"?

> The Merger role is not just a new name for "committer". If Claude is

> appointed a Merger, he will be forbidden to do what you are saying --
> a Merger cannot push their own contributions directly into Django!

Claude hasn't, and wouldn't, "commit" directly to Django here. He's always opened a

PR with the translations updates, which has then been reviewed, and which then, yes, he has

merged, and forward/backported as necessary — which IS the Merger role. (IIUC)

In the Merger role, Claude would also be able to approve and Merge other PRs.

Beyond this important translations case, we do need a third Merger, and I cannot think of a better candidate.

(The two most active contributors are Claude and Simon, and Simon cannot serve as a Merger because of his

role on the Technical Board.)

I would ask the Technical Board to proceed with the nomination, as, bar the loose language, I think it is in line with the DEP.

Kind Regards,

Carlton

[Adam Johnson]

This has fallen by the wayside, let's try restarting.

As Carlton points out, Claude hasn't been merging in code without others reviewing it. But as I understand it is useful to keep translations moving that he can merge in his or others' (accepted) PR's. It gets us to the minimum of three mergers, and Claude has stated he's willing to do his best in the role of merger. And I hope Claude can help inform us what we can do to make i18n more smooth.

I nominate Claude as a merger.

Technical board, please post your votes.

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/14af7b19-bcd3-4462-9e25-606f30ff6eda%40googlegroups.com.

--

Adam

[charettes]

I cast my vote in favor of Claude's nomination as well.

Le jeudi 16 avril 2020 16:16:31 UTC-4, Adam Johnson a écrit :

This has fallen by the wayside, let's try restarting.

As Carlton points out, Claude hasn't been merging in code without others reviewing it. But as I understand it is useful to keep translations moving that he can merge in his or others' (accepted) PR's. It gets us to the minimum of three mergers, and Claude has stated he's willing to do his best in the role of merger. And I hope Claude can help inform us what we can do to make i18n more smooth.

I nominate Claude as a merger.

Technical board, please post your votes.

On Thu, 19 Mar 2020 at 07:59, Carlton Gibson <carlto...@gmail.com> wrote:

I don't know if this got blocked in the now-obsolete use of cognates of "commit"?

> The Merger role is not just a new name for "committer". If Claude is

> appointed a Merger, he will be forbidden to do what you are saying --
> a Merger cannot push their own contributions directly into Django!

Claude hasn't, and wouldn't, "commit" directly to Django here. He's always opened a

PR with the translations updates, which has then been reviewed, and which then, yes, he has

merged, and forward/backported as necessary — which IS the Merger role. (IIUC)

In the Merger role, Claude would also be able to approve and Merge other PRs.

Beyond this important translations case, we do need a third Merger, and I cannot think of a better candidate.

(The two most active contributors are Claude and Simon, and Simon cannot serve as a Merger because of his

role on the Technical Board.)

I would ask the Technical Board to proceed with the nomination, as, bar the loose language, I think it is in line with the DEP.

Kind Regards,

Carlton

--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.

To unsubscribe from this group and stop receiving emails from it, send an email to django-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/14af7b19-bcd3-4462-9e25-606f30ff6eda%40googlegroups.com.

--

Adam

[Markus Holtermann]

I vote in favor of Claude becoming a MERGER.

Cheers,

Markus

> >> To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/14af7b19-bcd3-4462-9e25-606f30ff6eda%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/14af7b19-bcd3-4462-9e25-606f30ff6eda%40googlegroups.com?utm_medium=email&utm_source=footer>.
> >
> >
> > --
> > Adam

>
> --
> You received this message because you are subscribed to the Google
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send

> an email to django-develop...@googlegroups.com.

> To view this discussion on the web visit

> https://groups.google.com/d/msgid/django-developers/c13e6529-0e75-4e04-8ea6-501982420504%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/c13e6529-0e75-4e04-8ea6-501982420504%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Andrew Godwin]

I also vote in favour of Claude becoming a Merger!

Andrew

> https://groups.google.com/d/msgid/django-developers/c13e6529-0e75-4e04-8ea6-501982420504%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/c13e6529-0e75-4e04-8ea6-501982420504%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Aymeric Augustin]

Hello,

I trust Claude to act as a Merger as described in DEP 10. I vote in favor.

With apologies for the late answer!

-- 

Aymeric.

To unsubscribe from this group and stop receiving emails from it, send an email to django-develop...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/15a11b73-d6dd-4ea4-af42-0919e75a5147%40googlegroups.com.

[Carlton Gibson]

Hi all, thanks.

I think that's everyone, so I'll add Claude to the team.

💃

Kind Regards,

Carlton