Re: [sage-devel] Looking for volunteers

[David Roe]

We've received several nominations, but if you have been on the fence about
suggesting someone I encourage you to write to us.  The nomination period
will close tomorrow night.
David

On Wed, Feb 28, 2024 at 10:52 AM David Roe  wrote:

>
>
> On Wed, Feb 28, 2024 at 10:51 AM Dima Pasechnik  wrote:
>
>>
>>> We propose the following voting system.
>>> 1. A nomination period of 1 week, where any Sage developer can nominate
>>> someone to serve on the committee by emailing
>>> sage-ab...@googlegroups.com.  You are allowed to nominate yourself (and
>>> we encourage it); if you nominate someone else we will email them and ask
>>> if they are willing to serve.  To be eligible you should have
>>> a. Contributed code to Sage at some point in the past
>>> b. Not been subject to a complaint to the committee at any point.
>>>
>>
>> b. sounds way too broad to me. Should it say in addition something like
>> "The complaint in question only qualifies if it was ruled valid by the
>> committee." Note that these complaints were misused in the past.
>>
>
> Sure, that seems reasonable.
> David
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_%3D-T3iKgi5f55JDpJh43ZFA2fMeJs_F%3DTC8KYpO4Rz-VA%40mail.gmail.com.

Re: [sage-devel] Looking for volunteers

[David Roe]

On Wed, Feb 28, 2024 at 10:51 AM Dima Pasechnik  wrote:

>
>> We propose the following voting system.
>> 1. A nomination period of 1 week, where any Sage developer can nominate
>> someone to serve on the committee by emailing sage-ab...@googlegroups.com.
>> You are allowed to nominate yourself (and we encourage it); if you nominate
>> someone else we will email them and ask if they are willing to serve.  To
>> be eligible you should have
>> a. Contributed code to Sage at some point in the past
>> b. Not been subject to a complaint to the committee at any point.
>>
>
> b. sounds way too broad to me. Should it say in addition something like
> "The complaint in question only qualifies if it was ruled valid by the
> committee." Note that these complaints were misused in the past.
>

Sure, that seems reasonable.
David

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_nJ-TfF2E1LOkf5YiJVfTC1F_60H7tbS5i0W5D1sOhSkg%40mail.gmail.com.

Re: [sage-devel] Looking for volunteers

[Dima Pasechnik]

On Wed, Feb 28, 2024 at 3:20 AM David Roe  wrote:

> Hi Sage developers,
> As some of you may be aware, there has been more conflict in the last
> several months than normal, including multiple violations of our Code of
> Conduct.  Sage's mechanism for moderating conflicts and addressing such
> violations is a committee, reachable at sage-ab...@googlegroups.com.  I
> announced the membership of this committee a few days ago in another
> thread; since then one member has resigned and another has expressed
> willingness to be replaced.  The current membership is
> William Stein
> John Palmieri
> David Roe
> Vincent Delecroix
> David Joyner
> As a group, we believe that this committee would benefit from new members,
> so we are opening a process to add and/or change the membership (the five
> of us will go through the same process described below as anyone else
> interested in serving on the committee).
>
> We propose the following voting system.
> 1. A nomination period of 1 week, where any Sage developer can nominate
> someone to serve on the committee by emailing sage-ab...@googlegroups.com.
> You are allowed to nominate yourself (and we encourage it); if you nominate
> someone else we will email them and ask if they are willing to serve.  To
> be eligible you should have
> a. Contributed code to Sage at some point in the past
> b. Not been subject to a complaint to the committee at any point.
>

b. sounds way too broad to me. Should it say in addition something like
"The complaint in question only qualifies if it was ruled valid by the
committee." Note that these complaints were misused in the past.



> During the nomination period, you may also write to sage-abuse with names
> of people who you believe should not serve on the committee; if one of
> these people is nominated we will write to you asking for more
> justification.  If you have a reservation about someone already on the
> committee, you should feel free to write to us individually.
> 2. After the nomination period, we will announce nominees on sage-devel,
> and ask for votes (which will also be sent to sage-ab...@googlegroups.com).
> Voting will be by approval voting (you can select an arbitrary number of
> people to vote for, unordered).  The committee will include at least the
> top 5 candidates, and will be enlarged to include all tied candidates if
> there is a tie for 5th place.
> 3. After a week of voting, we will announce the new composition of the
> committee.
>
> We're aware that this process is not optimal (and welcome suggestions for
> improvement).  But we'd like more help, soon.  So we will open nominations
> in parallel to discussion of the process.  We anticipate running this
> process every 3 years to refresh membership.
>
> Qualities that we're looking for are
> 1. Tactfulness and judgement in moderating conflicts and addressing abuse
> 2. Willingness to put time and effort into repairing some of the problems
> that we've seen in our community.
> If you have any questions, feel free to reach out to us individually, or
> as a group.  We will be following this with some proposed changes to the
> Code of Conduct, as well as a new document describing how we handle reports
> (following the example of SciPy and NumFocus).  Thanks,
> David
> for the sage-abuse committee
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CAChs6_kDCa8TYWnQ10pLtpOewSKaCQBFkhb6w3hZ%2BLbQEgsN2A%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0m%2BX3uT30W2Zxfu%2BuNphKvLLRuM7RQZOL2qDBtXSOLhA%40mail.gmail.com.

[sage-devel] Looking for volunteers

[David Roe]

Hi Sage developers,
As some of you may be aware, there has been more conflict in the last
several months than normal, including multiple violations of our Code of
Conduct.  Sage's mechanism for moderating conflicts and addressing such
violations is a committee, reachable at sage-ab...@googlegroups.com.  I
announced the membership of this committee a few days ago in another
thread; since then one member has resigned and another has expressed
willingness to be replaced.  The current membership is
William Stein
John Palmieri
David Roe
Vincent Delecroix
David Joyner
As a group, we believe that this committee would benefit from new members,
so we are opening a process to add and/or change the membership (the five
of us will go through the same process described below as anyone else
interested in serving on the committee).

We propose the following voting system.
1. A nomination period of 1 week, where any Sage developer can nominate
someone to serve on the committee by emailing sage-ab...@googlegroups.com.
You are allowed to nominate yourself (and we encourage it); if you nominate
someone else we will email them and ask if they are willing to serve.  To
be eligible you should have
a. Contributed code to Sage at some point in the past
b. Not been subject to a complaint to the committee at any point.
During the nomination period, you may also write to sage-abuse with names
of people who you believe should not serve on the committee; if one of
these people is nominated we will write to you asking for more
justification.  If you have a reservation about someone already on the
committee, you should feel free to write to us individually.
2. After the nomination period, we will announce nominees on sage-devel,
and ask for votes (which will also be sent to sage-ab...@googlegroups.com).
Voting will be by approval voting (you can select an arbitrary number of
people to vote for, unordered).  The committee will include at least the
top 5 candidates, and will be enlarged to include all tied candidates if
there is a tie for 5th place.
3. After a week of voting, we will announce the new composition of the
committee.

We're aware that this process is not optimal (and welcome suggestions for
improvement).  But we'd like more help, soon.  So we will open nominations
in parallel to discussion of the process.  We anticipate running this
process every 3 years to refresh membership.

Qualities that we're looking for are
1. Tactfulness and judgement in moderating conflicts and addressing abuse
2. Willingness to put time and effort into repairing some of the problems
that we've seen in our community.
If you have any questions, feel free to reach out to us individually, or as
a group.  We will be following this with some proposed changes to the Code
of Conduct, as well as a new document describing how we handle reports
(following the example of SciPy and NumFocus).  Thanks,
David
for the sage-abuse committee

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAChs6_kDCa8TYWnQ10pLtpOewSKaCQBFkhb6w3hZ%2BLbQEgsN2A%40mail.gmail.com.