[IPython-dev] PR squashing meeting

Thomas Kluyver takowl at gmail.com
Thu Sep 11 18:07:32 EDT 2014


Let's see how we go with the first one.

On 11 September 2014 14:48, Brian Granger <ellisonbg at gmail.com> wrote:

> On Thu, Sep 11, 2014 at 2:37 PM, Damián Avila <damianavila at gmail.com>
> wrote:
> >> In fact, shall we say that, if there are 3 or more PRs labeled needs
> >> decision, whoever's around at 10am on any working day should get
> together
> >> and try to either decide, or work out whose input is needed?
>
> I very much like that idea - I think it will help ease some of the
> bottlenecks we have - esp if we can keep the meetings short. Maybe we
> should even time limit them to 30 minutes?
>
> Cheers,
>
> Brian
>
> > Sounds good...
> >
> > 2014-09-11 18:32 GMT-03:00 Thomas Kluyver <takowl at gmail.com>:
> >
> >> OK, let's go for tomorrow at the same time.
> >>
> >> In fact, shall we say that, if there are 3 or more PRs labeled needs
> >> decision, whoever's around at 10am on any working day should get
> together
> >> and try to either decide, or work out whose input is needed?
> >>
> >> Thomas
> >>
> >> On 11 September 2014 14:08, Brian Granger <ellisonbg at gmail.com> wrote:
> >>>
> >>> Fernando and I had talked about keeping these meetings short - 2 or 3
> >>> decisions/PRs at most.
> >>>
> >>> With 10 current decisions to make I don't think we should wait for
> >>> Tuesday - by then we may have 15 ;-)
> >>>
> >>> Tomorrow at 10 am for the first 2-3?
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Sep 11, 2014, at 1:02 PM, Damián Avila <damianavila at gmail.com>
> wrote:
> >>>
> >>> It works for me...
> >>>
> >>> 2014-09-11 16:23 GMT-03:00 Thomas Kluyver <takowl at gmail.com>:
> >>>>
> >>>> We said in our dev meeting that we should schedule a time to go
> through
> >>>> PRs, especially those labelled 'needs decision', and work out what we
> want
> >>>> to do.
> >>>>
> >>>> In keeping with our general pattern, does next Tuesday at 1700 UTC
> (10am
> >>>> in California, 7pm in France) work for enough people? We don't need
> everyone
> >>>> to be there.
> >>>>
> >>>> Thanks,
> >>>> Thomas
> >>>>
> >>>> _______________________________________________
> >>>> IPython-dev mailing list
> >>>> IPython-dev at scipy.org
> >>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Damián
> >>>
> >>> _______________________________________________
> >>> IPython-dev mailing list
> >>> IPython-dev at scipy.org
> >>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >>>
> >>>
> >>> _______________________________________________
> >>> IPython-dev mailing list
> >>> IPython-dev at scipy.org
> >>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> IPython-dev mailing list
> >> IPython-dev at scipy.org
> >> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >>
> >
> >
> >
> > --
> > Damián
> >
> > _______________________________________________
> > IPython-dev mailing list
> > IPython-dev at scipy.org
> > http://mail.scipy.org/mailman/listinfo/ipython-dev
> >
>
>
>
> --
> Brian E. Granger
> Cal Poly State University, San Luis Obispo
> @ellisonbg on Twitter and GitHub
> bgranger at calpoly.edu and ellisonbg at gmail.com
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140911/6aa87476/attachment.html>


More information about the IPython-dev mailing list