On Fri, Mar 31, 2017 at 12:39 AM, Ralf Gommers
wrote:
>
>
> On Fri, Mar 31, 2017 at 11:59 AM, Sebastian Berg <
> sebast...@sipsolutions.net> wrote:
>
>> On Thu, 2017-03-30 at 22:46 +1300, Ralf Gommers wrote:
>> >
>>
>> >
>> > Agreed, and I would call that productive. Getting even one new
>> > ma
On Fri, Mar 31, 2017 at 11:59 AM, Sebastian Berg wrote:
> On Thu, 2017-03-30 at 22:46 +1300, Ralf Gommers wrote:
> >
>
> >
> > Agreed, and I would call that productive. Getting even one new
> > maintainer involved is worth organizing multiple sprints for.
> >
> > That said, also +1 to a develope
On Thu, 2017-03-30 at 22:46 +1300, Ralf Gommers wrote:
>
>
> Agreed, and I would call that productive. Getting even one new
> maintainer involved is worth organizing multiple sprints for.
>
> That said, also +1 to a developer meeting this year. It'd be good if
> we could combine it with the Num
On Thu, Mar 30, 2017 at 10:55 AM, Stefan van der Walt
wrote:
> On Wed, Mar 29, 2017, at 13:01, Charles R Harris wrote:
>
> On Tue, Mar 28, 2017 at 5:16 PM, Nathaniel Smith wrote:
>
> In case anyone is interested in helping run a NumPy sprint at SciPy this
> year:
>
>
> I haven't found numpy spri
On Wed, Mar 29, 2017, at 13:01, Charles R Harris wrote:
> On Tue, Mar 28, 2017 at 5:16 PM, Nathaniel Smith
> wrote:
>> In case anyone is interested in helping run a NumPy sprint at SciPy
>> this year:
>
> I haven't found numpy sprints to be very productive. However, I think
> it would be useful
On Tue, Mar 28, 2017 at 5:16 PM, Nathaniel Smith wrote:
> In case anyone is interested in helping run a NumPy sprint at SciPy this
> year:
>
I haven't found numpy sprints to be very productive. However, I think it
would be useful if we could have a developers meeting sometime this year.
Chuck
_
