On 10/16/20 3:29 PM, Tal Einat wrote:
(Context: Continuing to prepare for the core dev sprint next week.
Since the sprint is near, *I'd greatly appreciate any quick comments,
feedback and ideas!*)
Following up my collection of past beginning contributor experiences,
I've collected these expe
> My suggestion: create the developers by creating group(s) of
> mentors
Do you know about
https://mail.python.org/mailman3/lists/core-mentorship.python.org/
and if you do, why isn't that what you suggest?
___
Python-Dev mailing list -- python-dev@
I was impressed by the good ideas put forward, however, some what not full
solutions.
My position: I have free time now and I want to contribute to open
source/freeware. But I don’t have great software in depth experience, however,
I’m willing to learn.
I was think of contributing to Python but
On Sat, Oct 17, 2020 at 7:31 AM Tal Einat wrote:
>
>
> 4. Encourage core devs to dedicate some of their time to working through
> issues/PRs which are "ignored" or "stalled". This would require first
> generating reliable lists of issues/PRs in such states. This could be in
> various forms, suc
Hi Tal,
Thanks for driving such research, it's really interesting. Sadly, I'm
not surprised by the results, since I'm already aware of these issues.
IMHO the most promising way to get more review is to create groups
where developers work on the same topic and review each other.
Also, mentoring i
On Mon., Oct. 19, 2020, 12:33 Tal Einat, wrote:
> On Mon, Oct 19, 2020 at 9:24 PM Brett Cannon wrote:
>
>> I think the other way to help is to really lean into automation so
>> reviewing is even lighterweight than it is now. Now this can be as simple
>> as to remind people when they need to rege
On Mon, Oct 19, 2020 at 9:24 PM Brett Cannon wrote:
> I think the other way to help is to really lean into automation so
> reviewing is even lighterweight than it is now. Now this can be as simple
> as to remind people when they need to regenerate a file like 'configure'
> via a status check, sim
I think the other way to help is to really lean into automation so
reviewing is even lighterweight than it is now. Now this can be as simple
as to remind people when they need to regenerate a file like 'configure'
via a status check, simply telling people when their PR failed a status
check, or go
