I also vote in favour of Claude becoming a Merger! Andrew
On Tuesday, April 21, 2020 at 4:28:41 AM UTC-6, Markus Holtermann wrote: > > I vote in favor of Claude becoming a MERGER. > > Cheers, > > Markus > > On Thu, Apr 16, 2020, at 10:31 PM, charettes wrote: > > 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 > > < > 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-d...@googlegroups.com <javascript:>. > > 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>. > > > -- 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-developers+unsubscr...@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.
