Yes, we can have multiple package maintainers. For example, we have about 6
people that manage sympy.physics.mechanics and have a group in the github
org for them. But they mostly play and informal role, reviewing
occasionally, submit some PRs, etc. Because it is informal, things slip
past the radar, pr's linger for years, issue's aren't closed, etc. I'm fine
with toning down the responsibilities, but the whole point, in my mind, was
to make some responsibilities more formal. I see this as both an
empowerment to the maintainers and spreading the formal load of managing
this project to more parties. I'd personally like to see one main point
person for each package, but there can be a group of people maintaining the
package. The point person would simply take on the role of monitoring for
things that slip past the informal group of maintainers and be the first
point of contact for anyone who doesn't know who to ask questions about the
code. We can have another column that lists the package "group" or
something.

Also note that we could have per module maintainers to if that module is
large or we can group packages together. I don't really know the size and
complexity of the packages, feel free to modify the table to fix that.


Jason
moorepants.info
+01 530-601-9791

On Mon, Jul 13, 2015 at 7:21 AM, AMiT Kumar <[email protected]> wrote:

> I totally agree with Kalevi, associating a group of interested people with
> a
> package in a less formal way, would be much better.
>
> BTW, Solvers is a huge domain categorized as a single package, It includes:
>
> * Solvers (Equation solvers)
> * ODE
> * PDE
> * Diophantine
> * Recurrence solver
>
> I expect at-least 6-7 people taking up, as interested for helping out with
> the responsibilities in a non-formal way.
>
>
> *AMiT Kumar*
>
> On Monday, July 13, 2015 at 5:18:54 PM UTC+5:30, Kalevi Suominen wrote:
>>
>>
>>
>> On Monday, July 13, 2015 at 4:11:30 AM UTC+3, Jason Moore wrote:
>>>
>>> After discussions at SciPy, we decided to try out a new idea to help
>>> delegate maintenance responsibilities to a broader group of people. In
>>> particular, we'd like to have a volunteer maintainer for each substantial
>>> package in SymPy. I've typed up a page here about this new explicit
>>> responsibility:
>>>
>>> https://github.com/sympy/sympy/wiki/Package-Maintainers
>>>
>>> Please read over it and give some feedback. Also, if you'd like to
>>> volunteer for a package or packages, please fill in the table I've started.
>>>
>>> I'll follow up in a few days after we discuss this a bit.
>>>
>>> Keep in mind this is a experiment and if it does not help we can drop it.
>>>
>>> Jason
>>> moorepants.info
>>> +01 530-601-9791
>>>
>>
>> Hi,
>>
>> The list of responsibilities seems a bit daunting to me. The step from a
>> contributor to a package maintainer
>> would be rather high. Perhaps it could be possible to associate a group
>> of interested people with a
>> package in a less formal way.
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/sympy.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/bf2aa6d6-be97-449f-9604-3ba9e7697514%40googlegroups.com
> <https://groups.google.com/d/msgid/sympy/bf2aa6d6-be97-449f-9604-3ba9e7697514%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sympy.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/CAP7f1Ai4vEPtgU%3D2Jt92VbjU9K-BoUnVz-046U54J-doTerjDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to