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-developers+unsubscr...@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.
