Hi Barry,
I gave the bug triage permission to:
Mark Sapiro: https://bugs.python.org/user2507
Abhilash Raj: https://bugs.python.org/user18684
I use the links to profile, so you can double check that I picked the
right person :-) For example, Raj has a second account (latest update:
2014, whereas
On May 14, 2019, at 00:46, Antoine Pitrou wrote:
> Barry, if you trust
> Mark's and Abhilash's competence, it should probably be easy for you to
> merge their first PRs (and guide them along the way).
I do, and that works for me. Can we give them triage rights on bpo now?
-Barry
Working on email package under Barry mentorship looks like a good idea
and a first step to promoting Mark and Abhilash.
Also, we can give them bug triaging privilegy to help with managing
existing 150+ email related bug reports right now, it doesn't hurt.
After some mentorship period, we can
I think Mark and Abhilash would be the perfect choice to (help) maintain
the email package.
They have done a great job on making sure Mailman
works for us and know from real world experience what the issues
are you face nowadays with email (such as having to deal with the
wonderful technology
Le 14/05/2019 à 01:19, Gregory P. Smith a écrit :
>
> I think these two make sense as email module maintainers from a
> demonstrated domain expertise point of view.
>
> But you'll probably have an easier time convincing others who want to
> see some PRs first if you just go ahead and have them
On 5/13/2019 7:11 PM, Barry Warsaw wrote:
On May 13, 2019, at 01:14, Victor Stinner wrote:
I'm no longer sure myself that I can define them. I prefer to repeat
what others say :-) Basically, a core developers is someone who
produces commits :-) That's one definition.
But, IMHO not a correct
On Mon, May 13, 2019 at 4:11 PM Barry Warsaw wrote:
> On May 13, 2019, at 01:14, Victor Stinner wrote:
>
> > I'm no longer sure myself that I can define them. I prefer to repeat
> > what others say :-) Basically, a core developers is someone who
> > produces commits :-) That's one definition.
>
On May 13, 2019, at 01:14, Victor Stinner wrote:
> I'm no longer sure myself that I can define them. I prefer to repeat
> what others say :-) Basically, a core developers is someone who
> produces commits :-) That's one definition.
But, IMHO not a correct one. The full quote from PEP 13:
Le 13/05/2019 à 10:14, Victor Stinner a écrit :
>
> I would prefer to first see them more involved upstream, before
> starting to discuss promoting them. They are other contributors who
> are way more active than them.
>
> In the meanwhile, they don't have to be core devs to help to maintain
>
Hi,
To be honest, my first reaction is the same than Andrew and Antoine: I
don't know these 2 contributors. I didn't see them around the bug
tracker, reviews, nor in commits.
The definition of what is a core developer is still a work-in-progress
:-) The PEP 13 tries to define it:
I'd like to second Andrew's request.
Regards
Antoine.
Le 09/05/2019 à 21:14, Andrew Svetlov a écrit :
> A link to a list of CPython commits (Pull Requests) for both these
> guys would be greatly appreciated.
>
> On Thu, May 9, 2019 at 1:59 PM Barry Warsaw wrote:
>>
>> If you like the way
A link to a list of CPython commits (Pull Requests) for both these
guys would be greatly appreciated.
On Thu, May 9, 2019 at 1:59 PM Barry Warsaw wrote:
>
> If you like the way mail.python.org and Mailman (both 2 and 3) Just Work, and
> are about as reliable as any service can be, we have our
If you like the way mail.python.org and Mailman (both 2 and 3) Just Work, and
are about as reliable as any service can be, we have our wonderful postmasters
to thank. Mark has been a postmaster for years and is currently maintaining
GNU Mailman, both as a project and as a service on mpo.
13 matches
Mail list logo
