On Tue, Sep 29, 2015 at 7:32 AM, Travis Oliphant
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
On Fri, Sep 25, 2015 at 7:15 AM, Thomas Caswell wrote:
> To respond to the devils advocate:
>
> Creating this organizational framework is a one time boot-strapping event.
> You could use wording like "The initial council will include those who have
> made significant
Thanks for the candid discussion and for expressing concerns freely.
I think Nathaniel's "parenting" characterization of NumPy from me is pretty
accurate.I do feel a responsibility for the *stuff* that's out there,
and that is what drives me. I do see the many contributions from others
and
On Fr, 2015-09-25 at 14:15 +, Thomas Caswell wrote:
> To respond to the devils advocate:
>
>
> Creating this organizational framework is a one time boot-strapping
> event. You could use wording like "The initial council will include
> those who have made significant contributions to numpy
On Fri, Sep 25, 2015 at 7:25 AM, Marten van Kerkwijk
wrote:
[...]
>
> p.s. Independently of rules, I don't see how Travis would not qualify even
> from current work, given that he has just committed to actively try to
> improve/generalize dtype.
Just to clarify what's
On Thu, Sep 24, 2015 at 10:45 AM, David Cournapeau wrote:
>
> On Thu, Sep 24, 2015 at 10:45 AM, Sebastian Berg
> wrote:
>>
[...]
>> About using the commit log to seed, I think there are some old term
>> contributers (David Cournapeau maybe?), who
[Travis: sorry for writing all this referring to you in third person
-- I guess it might feel a bit awkward to read! You're certainly part
of the intended audience, but then it felt even more awkward trying to
write in second person... this is clearly a bug in English.]
Hi all,
On Wed, Sep 23,
To respond to the devils advocate:
Creating this organizational framework is a one time boot-strapping
event. You could use wording like "The initial council will include those
who have made significant contributions to numpy in the past and want to be
on it" or "The initial council will be
Hi Nathaniel,
Piping in again from the outside: being on council would certainly seem to
be a job not a privilege, and I suspect it will be hard enough to find
people willing to actually put in work to worry about restricting
membership overly.
Given this, my suggestion would be to have a
On Mi, 2015-09-23 at 19:48 -0500, Travis Oliphant wrote:
>
>
> On Wed, Sep 23, 2015 at 6:19 PM, Charles R Harris
> wrote:
>
>
> On Wed, Sep 23, 2015 at 3:42 PM, Chris Barker
> wrote:
> On Wed,
On Mi, 2015-09-23 at 17:08 -0600, Charles R Harris wrote:
>
>
> On Wed, Sep 23, 2015 at 3:21 PM, Travis Oliphant
> wrote:
>
>
> Regarding the seed council, I just tried to pick an
> objective
>
On Thu, Sep 24, 2015 at 10:45 AM, Sebastian Berg wrote:
> On Mi, 2015-09-23 at 17:08 -0600, Charles R Harris wrote:
> >
> >
> > On Wed, Sep 23, 2015 at 3:21 PM, Travis Oliphant
> > wrote:
> >
> >
> > Regarding the seed council, I
>
>
>
> [1] Sorry to "footnote" this, but I think I am probably rudely repeating
> myself and frankly do **not want this to be discussed**. It is just to
> try to be fully clear where I come from:
> Until SciPy 2015, I could list many people on this list who have shown
> more direct involvement in
[splitting this out from the thread-o-doom]
On Wed, Sep 23, 2015 at 8:47 AM, Chris Barker - NOAA Federal
wrote:
[snip]
> So here is what I think is on the table:
>
> We have the steering council. Which leaves two questions:
>
> -How big should it be?
> -Who will be on the
On Wed, Sep 23, 2015 at 12:40 PM, Nathaniel Smith wrote:
> > However, that had been contentious enough that it would probably be a
> > good idea to hash out some guidelines about the council membership.
>
> We actually do have some of those already -- dunno if they're perfect,
>
>
> Regarding the seed council, I just tried to pick an objective
> criterion and an arbitrary date that seemed generally in keeping with
> idea of "should be active in the last 1-to-2-years-ish". Fiddling with
> the exact date in particular makes very little difference -- between
> pushing it
On Wed, Sep 23, 2015 at 2:21 PM, Travis Oliphant
wrote:
> As the original author of NumPy, I would like to be on the seed council as
> long as it is larger than 7 people.That is my proposal.
>
Or the seed council could invite Travis to join as its first order of
If I were to be included in the steering council I suspect my main
contribution would be to occasionally remind everyone that we are all
committed to the success of the open scientific stack.
Tom
On Wed, Sep 23, 2015 at 3:40 PM Nathaniel Smith wrote:
> [splitting this out from
On Wed, Sep 23, 2015 at 3:42 PM, Chris Barker wrote:
> On Wed, Sep 23, 2015 at 2:21 PM, Travis Oliphant
> wrote:
>
>
>> As the original author of NumPy, I would like to be on the seed council
>> as long as it is larger than 7 people.That is my
For what it is worth, I'm +1 on including any of the "founding fathers"
(and uncles!) that wish to be included in the committee, or council, or
however we ended up calling it. I'm also OK with singling out Travis as
creator of NumPy in the wording of the document.
Especially since the
On Wed, Sep 23, 2015 at 3:21 PM, Travis Oliphant
wrote:
>
>
>> Regarding the seed council, I just tried to pick an objective
>> criterion and an arbitrary date that seemed generally in keeping with
>> idea of "should be active in the last 1-to-2-years-ish". Fiddling with
>>
On Wed, Sep 23, 2015 at 5:41 PM, Jaime Fernández del Río <
jaime.f...@gmail.com> wrote:
> For what it is worth, I'm +1 on including any of the "founding fathers"
> (and uncles!) that wish to be included in the committee, or council, or
> however we ended up calling it. I'm also OK with singling
On Wed, Sep 23, 2015 at 6:19 PM, Charles R Harris wrote:
>
>
> On Wed, Sep 23, 2015 at 3:42 PM, Chris Barker
> wrote:
>
>> On Wed, Sep 23, 2015 at 2:21 PM, Travis Oliphant
>> wrote:
>>
>>
>>> As the original author of
23 matches
Mail list logo