On Tue, Sep 29, 2015 at 7:32 AM, Travis Oliphant <tra...@continuum.io> wrote:
> I'm in a situation now where at least for 6 months or so I can help with > NumPy more than I have been able to for 7 years. > great news! > 1) 1 year of inactivity to be removed from the council is too little for a > long-running project like NumPy > I always read this as "activity in council matters", not "activity in commits to the code". If that's not what is meant, then we should re-write that. So no, Travis is not ineligible for the council, as there has been no council to be active on. And in that case, my vague memory is that Travis has popped his head into architecture discussions on this list at least once a year essentially forever, so there is every indication that he has been and will be active in that sense. --- somewhere between 2 and 4 years would be more appropriate. I suppose > 1 year of inactivity is fine if that is defined only as "failure to vote on > matters before the council" > exactly. -- I wld expand "activity" to mean more than voting, but that's the idea. More like active participation in discussions / issues, and/or attending meetings, if there are any. > 2) The seed council should not just be recent contributors but should > include as many people as are willing to help who have a long history with > the project. > again, I don't think we need so much emphasis in the "seed council" that is only needed to have SOME way to start. Though I guess as long as we're having the discussion, we should have an outline of the expectations for the council in general, which should indeed include a couple members with long history. > 3) I think people who contribute significantly generally should be able to > re-join the steering council more easily than "going through the 1-year > vetting process" again --- they would have to be approved by the current > steering council but it should not be automatically disallowed (thus > requiring the equivalent of an amendment to change it). > Sure -- give the Council Flexibility to keep the council current. However, the idea here is that we want some continuity -- not have people popping on and off the council on short time spans as their schedules allow. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
