[IPython-dev] [jupyter] Experimenting with a modified dev meeting format?
Brian Granger
ellisonbg at gmail.com
Tue Jun 30 13:09:53 EDT 2015
We are using bluejeans from another room - seems to be working fine
On Tue, Jun 30, 2015 at 9:21 AM, Jason Grout <jason at jasongrout.org> wrote:
> We could set up an audio conference call if needed. Let us know if we need
> to.
>
> Jason
>
>
> On Tue, Jun 30, 2015, 12:07 Matthias Bussonnier
> <bussonniermatthias at gmail.com> wrote:
>>
>> Last minutes change of plan (Probably) new furniture beeing installed in
>> video-room.
>> So no BlueJeans setup.
>> We will have to fallback on something else most likely.
>>
>> --
>> M
>>
>> > On Jun 29, 2015, at 23:16, Brian Granger <ellisonbg at gmail.com> wrote:
>> >
>> > Sounds good, I have also posted a summary of these changed at the top
>> > of the meeting hackpad. See you tomorrow!
>> >
>> > Cheers,
>> >
>> > Brian
>> >
>> > On Mon, Jun 29, 2015 at 6:25 PM, MinRK <benjaminrk at gmail.com> wrote:
>> >>
>> >>
>> >> On Mon, Jun 29, 2015 at 5:56 PM, Fernando Perez <fperez.net at gmail.com>
>> >> wrote:
>> >>>
>> >>> On Sat, Jun 27, 2015 at 8:07 PM, MinRK <benjaminrk at gmail.com> wrote:
>> >>>>
>> >>>> I think turning Tuesdays into check-ins/reports is a good idea.
>> >>>> Having
>> >>>> just one or two topics for actual in-depth meetings with smaller
>> >>>> groups
>> >>>> should definitely be more effective.
>> >>>
>> >>>
>> >>> OK, here's a wrap-up and my suggested path forward, so we can call
>> >>> this
>> >>> thread done, unless someone objects strenuously to something. As
>> >>> usual, we
>> >>> will fine-tune over time as we learn from experience...
>> >>>
>> >>> - Let's go with a max of 5 minutes per person on reporting of
>> >>> activity.
>> >>>
>> >>>
>> >>> - When reporting, you should try make sure what you say answers the
>> >>> following questions for the others:
>> >>>
>> >>> * What have I been working on?
>> >>> * What do I plan on working on?
>> >>> * What things are preventing me from making progress?
>> >>>
>> >>> This will ensure that everyone leaves knowing what everyone is up to,
>> >>> and
>> >>> that we can effectively help each other, identify where resources are
>> >>> needed, bottlenecks, etc.
>> >>>
>> >>>
>> >>> - We try to take notes as usual collectively on Hackpad, BUT, we
>> >>> designate
>> >>> a person each week who has an explicit responsibility that week to
>> >>> spend a
>> >>> bit of time after the meeting making sure the notes make sense and
>> >>> posting
>> >>> them to the Jupyter list. Hopefully that won't take more than a few
>> >>> minutes,
>> >>> if the collective note-taking was sufficient.
>> >>>
>> >>> This will give us a static record on the list of each week's meeting,
>> >>> which is better than just having a doc on hackpad.
>> >>>
>> >>> I volunteer to be the note-poster for tomorrow.
>> >>>
>> >>>
>> >>> - Let's keep the total meeting time to 1h, hard limit. Tomorrow,
>> >>> we're
>> >>> going to use a trick to enforce that: our nice videoconferencing room
>> >>> at
>> >>> BIDS is booked at 11am every other Tuesday, so we'll get kicked out
>> >>> anyways.
>> >>> We could obviously use another one, but instead we'll use the room
>> >>> with the
>> >>> better audio equipment and be forced to stay on schedule :)
>> >>>
>> >>>
>> >>> Did I miss anything?
>> >>
>> >>
>> >> Sounds like a good plan. See you all tomorrow.
>> >>
>> >> -MinRK
>> >>
>> >>>
>> >>>
>> >>> Cheers,
>> >>>
>> >>> f
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> >>> Groups
>> >>> "Project Jupyter" group.
>> >>> To unsubscribe from this group and stop receiving emails from it, send
>> >>> an
>> >>> email to jupyter+unsubscribe at googlegroups.com.
>> >>> To post to this group, send email to jupyter at googlegroups.com.
>> >>> To view this discussion on the web visit
>> >>>
>> >>> https://groups.google.com/d/msgid/jupyter/CAHAreOpdZ4tryfYk0PKktwJ2iTbhyMttYoGD9JU3c8A4CdM5mA%40mail.gmail.com.
>> >>>
>> >>> For more options, visit https://groups.google.com/d/optout.
>> >>
>> >>
>> >> --
>> >> You received this message because you are subscribed to the Google
>> >> Groups
>> >> "Project Jupyter" group.
>> >> To unsubscribe from this group and stop receiving emails from it, send
>> >> an
>> >> email to jupyter+unsubscribe at googlegroups.com.
>> >> To post to this group, send email to jupyter at googlegroups.com.
>> >> To view this discussion on the web visit
>> >>
>> >> https://groups.google.com/d/msgid/jupyter/CAHNn8BV61o_M8ziSOQnfOJz0Am6Pux14Yk6TVumCBK28LsaMVw%40mail.gmail.com.
>> >>
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> >
>> > --
>> > Brian E. Granger
>> > Cal Poly State University, San Luis Obispo
>> > @ellisonbg on Twitter and GitHub
>> > bgranger at calpoly.edu and ellisonbg at gmail.com
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups "Project Jupyter" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an email to jupyter+unsubscribe at googlegroups.com.
>> > To post to this group, send email to jupyter at googlegroups.com.
>> > To view this discussion on the web visit
>> > https://groups.google.com/d/msgid/jupyter/CAH4pYpSLq5LqHgoX1ULsqw3EwB%3Dn%2BR0qiqYKE%2BrHb2R2JEQSLg%40mail.gmail.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> _______________________________________________
>> 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
>
--
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgranger at calpoly.edu and ellisonbg at gmail.com
More information about the IPython-dev
mailing list