Re: [python-committers] Mentoring Office Hours - the idea, and a question

[Mariatta Wijaya]

I've started a PR in the devguide adding the office hours of core devs that
I know of.
https://github.com/python/devguide/pull/402

Please add your own office hours in there, or create new PRs.

I think we can leave it to each core devs of how they want to do their
office hour.
For myself, a fixed weekly schedule works for me, but others might have
more flexible schedule.

Mariatta


On Thu, Jun 14, 2018 at 4:58 PM Mariatta Wijaya 
wrote:

> Thanks for starting this, Brian.
>
> As such, it needs a person/persons/list to contact should something arise
>> in this context that needs to be handled. What/who should that be?
>
>  * Suggestion 2: Create some new list with a few key people on it.
>>  * Suggestion 3: List some direct names. Who?
>
>
> I personally prefer knowing names. If it will be a mailing list, I'd like
> to know who are in the mailing list.
>
> Related, I believe there is a new Code of Conduct working group within the
> PSF, but I don't know what is the scope of that working group.
> https://mail.python.org/pipermail/psf-community/2018-April/000488.html
>
> Perhaps to start it could just be some of us who wants to volunteer and do
> it?
>
> I can set aside 1 hr each week Thursday as my office hours, between 7 PM -
> 8 PM Pacific.
>
>
>
> Mariatta
>
> On Wed, May 16, 2018 at 3:08 PM, Victor Stinner 
> wrote:
>
>> 2018-05-16 11:31 GMT-04:00 Victor Stinner :
>> > I'm usually available between 10:00 and 16:00 in the French timezone
>> > (currently, it's CEST = UTC+2).
>>
>> Oh, let me be more specific:
>>
>> 10:00-12:00 and 14:00-16:00, Monday to Friday
>>
>> Yeah, in France we take our time to eat ;-)
>>
>> Victor
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>
> ᐧ
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Mentoring Office Hours - the idea, and a question

[Victor Stinner]

2018-05-16 11:31 GMT-04:00 Victor Stinner :
> I'm usually available between 10:00 and 16:00 in the French timezone
> (currently, it's CEST = UTC+2).

Oh, let me be more specific:

10:00-12:00 and 14:00-16:00, Monday to Friday

Yeah, in France we take our time to eat ;-)

Victor
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Mentoring Office Hours - the idea, and a question

[Brian Curtin]

Yep, this is something I'm adding directly in the devguide so it's right
where new contributors are already going to be looking for help and
information.

As for how those mentors and mentees actually do the work, to start with I
think it's something that each person should just do what they're
comfortable with and have access to, and then once we have some data to
work off of, maybe then we prescribe some specific ways of doing it. I'm ok
to do video things, but some might not be, so in getting this started I
wanted to just begin with names, days, times, and contact information on an
official website. If someone wants mentorship and they're available when
I'm available, they reach out to me and we find a way to talk.

On Wed, May 16, 2018 at 11:31 AM Victor Stinner  wrote:

> Hi,
>
> I'm usually available between 10:00 and 16:00 in the French timezone
> (currently, it's CEST = UTC+2).
>
> A few months ago, I wrote a tutorial and a list of available core
> developers... currently it's just me :-D
>
>http://cpython-core-tutorial.readthedocs.io/en/latest/getting_help.html
>
> Maybe this list should be moved in the developer guide?
>
>https://devguide.python.org/help/
>
> I chose to put it in my tutorial, since it's less official, and I was
> not sure if I should put myself in the official guide ;-)
>
> --
>
> I also heard the idea of pair-programming using a chat, a video
> conference, or something else.
>
> For example, when you work on a bug, do it with a contributor to show
> how you work. I never did that before, but I may try ;-)
>
> Victor
>
> 2018-05-16 9:52 GMT-04:00 Brian Curtin :
> > Hey all,
> >
> > At the Language Summit last week, after Mariatta's talk we had a
> > conversation around diversity and how to grow our contributor base, which
> > led to someone (Steve Dower?) suggesting we post a sort of "Office Hours"
> > list. This would be a list of current core developers who are interested
> in
> > being available at set time(s) for helping mentor newer contributors in
> our
> > community through our process and, if they're interested, mentoring them
> > through the process of becoming core developers themselves.
> >
> > This "Office Hours" concept is a type of thing that has worked well
> > elsewhere, including around the software world, and we have some people
> > interested in offering said mentorship, so I would like to move on to
> > getting this list up somewhere so we can start doing it.
> >
> > With that said, before I go make a PR to the devguide to start iterating
> on
> > the implementation, an important question:
> >
> > As this is both an event similar to an in-person meetup and an event
> meant
> > to be a safe space for those getting started, it will explicitly mention
> the
> > code of conduct. As such, it needs a person/persons/list to contact
> should
> > something arise in this context that needs to be handled. What/who should
> > that be?
> >  * Suggestion 1: use the already in-place
> core-mentorship-ow...@python.org,
> > though I can't tell who's on there.
> >  * Suggestion 2: Create some new list with a few key people on it.
> >  * Suggestion 3: List some direct names. Who?
> >
> > As for implementation, there are some tools out there we could possibly
> use,
> > but in the interests of getting something out there I'm just going to
> make a
> > table and fill in some common information, starting with my own. Calendar
> > apps and other integrations can come as we figure them out.
> >
> > Brian
> >
> > ___
> > python-committers mailing list
> > python-committers@python.org
> > https://mail.python.org/mailman/listinfo/python-committers
> > Code of Conduct: https://www.python.org/psf/codeofconduct/
> >
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Mentoring Office Hours - the idea, and a question

[Victor Stinner]

Hi,

I'm usually available between 10:00 and 16:00 in the French timezone
(currently, it's CEST = UTC+2).

A few months ago, I wrote a tutorial and a list of available core
developers... currently it's just me :-D

   http://cpython-core-tutorial.readthedocs.io/en/latest/getting_help.html

Maybe this list should be moved in the developer guide?

   https://devguide.python.org/help/

I chose to put it in my tutorial, since it's less official, and I was
not sure if I should put myself in the official guide ;-)

--

I also heard the idea of pair-programming using a chat, a video
conference, or something else.

For example, when you work on a bug, do it with a contributor to show
how you work. I never did that before, but I may try ;-)

Victor

2018-05-16 9:52 GMT-04:00 Brian Curtin :
> Hey all,
>
> At the Language Summit last week, after Mariatta's talk we had a
> conversation around diversity and how to grow our contributor base, which
> led to someone (Steve Dower?) suggesting we post a sort of "Office Hours"
> list. This would be a list of current core developers who are interested in
> being available at set time(s) for helping mentor newer contributors in our
> community through our process and, if they're interested, mentoring them
> through the process of becoming core developers themselves.
>
> This "Office Hours" concept is a type of thing that has worked well
> elsewhere, including around the software world, and we have some people
> interested in offering said mentorship, so I would like to move on to
> getting this list up somewhere so we can start doing it.
>
> With that said, before I go make a PR to the devguide to start iterating on
> the implementation, an important question:
>
> As this is both an event similar to an in-person meetup and an event meant
> to be a safe space for those getting started, it will explicitly mention the
> code of conduct. As such, it needs a person/persons/list to contact should
> something arise in this context that needs to be handled. What/who should
> that be?
>  * Suggestion 1: use the already in-place core-mentorship-ow...@python.org,
> though I can't tell who's on there.
>  * Suggestion 2: Create some new list with a few key people on it.
>  * Suggestion 3: List some direct names. Who?
>
> As for implementation, there are some tools out there we could possibly use,
> but in the interests of getting something out there I'm just going to make a
> table and fill in some common information, starting with my own. Calendar
> apps and other integrations can come as we figure them out.
>
> Brian
>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/