Python SIG on-boarding issue

[Dhanesh B. Sabane]

CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks we have identified is re-writing the Python SIG wiki page to make it more beginner-friendly. I was assigned with this particular task which is now complete [2] [3].  We received some feedback from mhroncok today during the CommOps meeting and following points were discussed:

1. Splitting Python SIG in two FAS groups: 
1.1 *python-sig* for newcomers and interested members who hang out and help with Python on Fedora
1.2 *python-packagers* for proven members of the community / packagers who will also receive security-related bugs. Promising members from *python-sig* group can be promoted to *python-packagers* given that they have contributed to the package's git.

2. Python Features section on the wiki page needs some love.

3.  Targeting specific information for newcomers to include in their self-introductions that would be helpful for SIG members to know where someone fits in the Python community and what their expertise is.

We would like to hear your feedback on the draft and also on the aforementioned points. Everyone is welcome to leave a comment on the ticket[1].

[1] https://pagure.io/fedora-commops/issue/84
[2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
[3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join

---
Dhanesh B. Sabane

[Charalampos Stratakis]

From a fast look at the page it seems pretty awesome. Nice job. I will check it through the next days and provide a more comprehensive feedback.

Regards,

Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat

----- Original Message -----
From: "Dhanesh Bhalchandra Sabane" 
To: [e-mail]
Sent: Tuesday, September 6, 2016 8:42:37 PM
Subject: Python SIG on-boarding issue

CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks we have identified is re-writing the Python SIG wiki page to make it more beginner-friendly. I was assigned with this particular task which is now complete [2] [3].  We received some feedback from mhroncok today during the CommOps meeting and following points were discussed:

1. Splitting Python SIG in two FAS groups: 
1.1 *python-sig* for newcomers and interested members who hang out and help with Python on Fedora
1.2 *python-packagers* for proven members of the community / packagers who will also receive security-related bugs. Promising members from *python-sig* group can be promoted to *python-packagers* given that they have contributed to the package's git.

2. Python Features section on the wiki page needs some love.

3.  Targeting specific information for newcomers to include in their self-introductions that would be helpful for SIG members to know where someone fits in the Python community and what their expertise is.

We would like to hear your feedback on the draft and also on the aforementioned points. Everyone is welcome to leave a comment on the ticket[1].

[1] https://pagure.io/fedora-commops/issue/84
[2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
[3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join

---
Dhanesh B. Sabane
_______________________________________________
python-devel mailing list
[e-mail]
https://lists.fedoraproject.org/admin/lists/[e-mail]...

[Nick Coghlan]

On 7 September 2016 at 04:42, Dhanesh Bhalchandra Sabane
 wrote:
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks we have identified is re-writing the Python SIG wiki page to make it more beginner-friendly. I was assigned with this particular task which is now complete [2] [3].  We received some feedback from mhroncok today during the CommOps meeting and following points were discussed:
> Splitting Python SIG in two FAS groups:
>
> 1.1 *python-sig* for newcomers and interested members who hang out and help with Python on Fedora
> 1.2 *python-packagers* for proven members of the community / packagers who will also receive security-related bugs. Promising members from *python-sig* group can be promoted to *python-packagers* given that they have contributed to the package's git.

+1 that sounds like an excellent idea :)

Cheers,
Nick.

[Abdel Gadiel Martínez Lassonde]

+1

2016-09-06 13:42 GMT-05:00 Dhanesh Bhalchandra Sabane <
[e-mail]>:
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and
> one of the tasks we have identified is re-writing the Python SIG wiki page
> to make it more beginner-friendly. I was assigned with this particular task
> which is now complete [2] [3].  We received some feedback from mhroncok
> today during the CommOps meeting and following points were discussed:
> Splitting Python SIG in two FAS groups:
>
> 1.1 *python-sig* for newcomers and interested members who hang out and
> help with Python on Fedora
> 1.2 *python-packagers* for proven members of the community / packagers who
> will also receive security-related bugs. Promising members from
> *python-sig* group can be promoted to *python-packagers* given that they
> have contributed to the package's git.
>
> Python Features section on the wiki page needs some love.
>
> Targeting specific information for newcomers to include in their
>
> self-introductions that would be helpful for SIG members to know where
> someone fits in the Python community and what their expertise is.
>
> We would like to hear your feedback on the draft and also on the
> aforementioned points. Everyone is welcome to leave a comment on the
> ticket[1].
>
> [1] https://pagure.io/fedora-commops/issue/84
> [2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
> [3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join
>
> Dhanesh B. Sabane
> _______________________________________________
> python-devel mailing list
> [e-mail]
> https://lists.fedoraproject.org/admin/lists/python-devel@
> lists.fedoraproject.org

[Dhanesh B. Sabane]

Aloha Python-SIG!
I was wondering whether it is a good time to make the new pages official. Also, I would like to know whether the idea of splitting the SIG into two FAS groups is acceptable so that we can start taking necessary actions.
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks
> we have identified is re-writing the Python SIG wiki page to make it more
> beginner-friendly. I was assigned with this particular task which is now complete [2] [3].
>  We received some feedback from mhroncok today during the CommOps meeting and following
> points were discussed:
> Splitting Python SIG in two FAS groups:
>
> 1.1 *python-sig* for newcomers and interested members who hang out and help with Python on
> Fedora
> 1.2 *python-packagers* for proven members of the community / packagers who will also
> receive security-related bugs. Promising members from *python-sig* group can be promoted
> to *python-packagers* given that they have contributed to the package's git.
>
> Python Features section on the wiki page needs some love.
>
> Targeting specific information for newcomers to include in their self-introductions
>
> that would be helpful for SIG members to know where someone fits in the Python community
> and what their expertise is.
>
> We would like to hear your feedback on the draft and also on the aforementioned points.
> Everyone is welcome to leave a comment on the ticket[1].
>
> [1] https://pagure.io/fedora-commops/issue/84
> [2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
> [3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join

---
Dhanesh B. Sabane

[Miro Hrončok]

On 13.9.2016 19:27, Dhanesh Bhalchandra Sabane wrote:
> Aloha Python-SIG!
> I was wondering whether it is a good time to make the new pages official. Also, I would like to know whether the idea of splitting the SIG into two FAS groups is acceptable so that we can start taking necessary actions.

Yes and yes.
> > CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks
> > we have identified is re-writing the Python SIG wiki page to make it more
> > beginner-friendly. I was assigned with this particular task which is now complete [2] [3].
> >  We received some feedback from mhroncok today during the CommOps meeting and following
> > points were discussed:
> > Splitting Python SIG in two FAS groups:
> >
> > 1.1 *python-sig* for newcomers and interested members who hang out and help with Python on
> > Fedora
> > 1.2 *python-packagers* for proven members of the community / packagers who will also
> > receive security-related bugs. Promising members from *python-sig* group can be promoted
> > to *python-packagers* given that they have contributed to the package's git.
> >
> > Python Features section on the wiki page needs some love.
> >
> > Targeting specific information for newcomers to include in their self-introductions
> >
> > that would be helpful for SIG members to know where someone fits in the Python community
> > and what their expertise is.
> >
> > We would like to hear your feedback on the draft and also on the aforementioned points.
> > Everyone is welcome to leave a comment on the ticket[1].
> >
> > [1] https://pagure.io/fedora-commops/issue/84
> > [2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
> > [3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join
>
> Dhanesh B. Sabane
> _______________________________________________
> python-devel mailing list
> [e-mail]
> https://lists.fedoraproject.org/admin/lists/[e-mail]...

[Tim Orling]

On Tue, Sep 13, 2016 at 10:36 AM, Miro Hrončok  wrote:
> On 13.9.2016 19:27, Dhanesh Bhalchandra Sabane wrote:
> > Aloha Python-SIG!
> > I was wondering whether it is a good time to make the new pages official.
> > Also, I would like to know whether the idea of splitting the SIG into two
> > FAS groups is acceptable so that we can start taking necessary actions.
>
> Yes and yes.

+1
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and
> > > one of the tasks
> > > we have identified is re-writing the Python SIG wiki page to make it more
> > > beginner-friendly. I was assigned with this particular task which is now
> > > complete [2] [3].
> > >  We received some feedback from mhroncok today during the CommOps
> > > meeting and following
> > > points were discussed:
> > > Splitting Python SIG in two FAS groups:
> > >
> > > 1.1 *python-sig* for newcomers and interested members who hang out and
> > > help with Python on
> > > Fedora
> > > 1.2 *python-packagers* for proven members of the community / packagers
> > > who will also
> > > receive security-related bugs. Promising members from *python-sig* group
> > > can be promoted
> > > to *python-packagers* given that they have contributed to the package's
> > > git.

This will make the intent much clearer :)

[Charalampos Stratakis]

+1 on everything

Charalampos Stratakis
Associate Software Engineer
Python Maintenance Team, Red Hat

----- Original Message -----
From: "Dhanesh Bhalchandra Sabane" 
To: [e-mail]
Sent: Tuesday, September 13, 2016 7:27:48 PM
Subject: Re: Python SIG on-boarding issue

Aloha Python-SIG!
I was wondering whether it is a good time to make the new pages official. Also, I would like to know whether the idea of splitting the SIG into two FAS groups is acceptable so that we can start taking necessary actions.
> CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks
> we have identified is re-writing the Python SIG wiki page to make it more
> beginner-friendly. I was assigned with this particular task which is now complete [2] [3].
>  We received some feedback from mhroncok today during the CommOps meeting and following
> points were discussed:
> Splitting Python SIG in two FAS groups:
>
> 1.1 *python-sig* for newcomers and interested members who hang out and help with Python on
> Fedora
> 1.2 *python-packagers* for proven members of the community / packagers who will also
> receive security-related bugs. Promising members from *python-sig* group can be promoted
> to *python-packagers* given that they have contributed to the package's git.
>
> Python Features section on the wiki page needs some love.
>
> Targeting specific information for newcomers to include in their self-introductions
>
> that would be helpful for SIG members to know where someone fits in the Python community
> and what their expertise is.
>
> We would like to hear your feedback on the draft and also on the aforementioned points.
> Everyone is welcome to leave a comment on the ticket[1].
>
> [1] https://pagure.io/fedora-commops/issue/84
> [2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
> [3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join

---
Dhanesh B. Sabane
_______________________________________________
python-devel mailing list
[e-mail]
https://lists.fedoraproject.org/admin/lists/[e-mail]...

[Dhanesh B. Sabane]

> I was wondering whether it is a good time to make the new pages official. Also, I would
> like to know whether the idea of splitting the SIG into two FAS groups is acceptable so
> that we can start taking necessary actions.

As instructed by jflory7, I've opened up a ticket on the Fedora-Infra Trac[1] for proposing two FAS groups. Also, the wiki pages [2][3] are live and I request all the active members of the SIG to make any changes if necessary.

[1] https://fedorahosted.org/fedora-infrastructure/ticket/5478
[2] https://fedoraproject.org/wiki/SIGs/Python
[3] https://fedoraproject.org/wiki/SIGs/Python/JoinSIG

--
Dhanesh B. Sabane
[e-mail]

[Dhanesh B. Sabane]

> CommOps is currently working on the Python SIG On-Boarding ticket [1] and one of the tasks
> we have identified is re-writing the Python SIG wiki page to make it more
> beginner-friendly. I was assigned with this particular task which is now complete [2] [3].
>  We received some feedback from mhroncok today during the CommOps meeting and following
> points were discussed:
> Splitting Python SIG in two FAS groups:
>
> 1.1 *python-sig* for newcomers and interested members who hang out and help with Python on
> Fedora
> 1.2 *python-packagers* for proven members of the community / packagers who will also
> receive security-related bugs. Promising members from *python-sig* group can be promoted
> to *python-packagers* given that they have contributed to the package's git.
>
> Python Features section on the wiki page needs some love.
>
> Targeting specific information for newcomers to include in their self-introductions
>
> that would be helpful for SIG members to know where someone fits in the Python community
> and what their expertise is.
>
> We would like to hear your feedback on the draft and also on the aforementioned points.
> Everyone is welcome to leave a comment on the ticket[1].
>
> [1] https://pagure.io/fedora-commops/issue/84
> [2] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python
> [3] https://fedoraproject.org/wiki/User:Dhanesh95/SIGs/Python/Join
>
> Dhanesh B. Sabane

There is some serious discussion happening on the Infrastructure ticket[1] about establishing two FAS groups. pingou has suggested that we involve some more admins from the Python SIG group to arrive at a feasible solution. I request all senior persons to give their feedback so that we can cross this task off the list.

[1] https://pagure.io/fedora-infrastructure/issue/5478

Dhanesh B. Sabane
[e-mail]

[Dhanesh B. Sabane]

> There is some serious discussion happening on the Infrastructure
> ticket[1] about establishing two FAS groups. pingou has suggested that we involve some
> more admins from the Python SIG group to arrive at a feasible solution. I request all
> senior persons to give their feedback so that we can cross this task off the list.
>
> [1] https://pagure.io/fedora-infrastructure/issue/5478
>
> Dhanesh B. Sabane
> dhanesh95(a)fedoraproject.org

Friendly reminder to all sponsors to go through the ticket[1] and sponsor your sponsored users to the new group so that we can get this closed and make people happy! ;)

[1]https://pagure.io/fedora-infrastructure/issue/5478

[Dhanesh B. Sabane]

A friendly reminder that the on-boarding issue [1] isn't resolved yet.  Please sponsor your sponsored members to *python-packagers-sig*.

If all the members have been sponsored, I can request for editing the groups and switching pkgdb to use *python-packagers-sig* instead of python-sig.[2]

[1] https://pagure.io/fedora-commops/issue/84
[2] https://pagure.io/fedora-infrastructure/issue/5478#comment-39359

Regards,
Dhanesh B. Sabane [dhanesh95]