[IPython-dev] [jupyter] Experimenting with a modified dev meeting format?

[Wes Turner]

* https://wrdrd.com/docs/consulting/software-development#stand-up-meeting
*
https://wrdrd.com/docs/consulting/software-development#digital-stand-up-meeting

  * etherpad-lite (operational transformation)

* https://wrdrd.com/docs/consulting/team-building#collaboration-engineering
 On Jun 29, 2015 12:21 AM, "Brian Granger" <ellisonbg at gmail.com> wrote:

> >> I think we should limit the person time though - maybe 7 minutes?
> >
> > I proposed 10 min 3 weeks ago.
>
> Yes and it was a good idea! The only problem is that 10 minutes is
> incompatible with a meeting whole goal is to make a lot of technical
> decisions. We found that out pretty quickly.
>
> Upon thinking more, I am thinking that putting a 5 minute max person
> might even be too high.
>
> >
> > I would also really appreciate to not have 3 words like: “Tag”. An entry
> on
> > the hackpad should be self explanatory (unless link to an issues which
> is self explanatory).
> > Like if the person who wrote that is not here we can decide without them.
>
> But I think the main content of Fernando's proposal is that we won't
> ever make decisions in the dev meetings.
>
> >
> > Have 1 person responsible for taking notes, and turn the hangout into a
> written small report,
> > that we (eventually) post on the blog to keep reader in the loop.
>
> I don't think the blog post is appropriate for most of this stuff -
> and I don't think we have anyone that wants to take the time to turn
> the summary in to a weekly blog post yet.
>
>
> >> We will probably have to think and talk further about the best way of
> >> gathering the right sets of people at the right times and propagating
> >> the information out, but this is a good next step.
> >
> > You mean we still don’t know how to open an issue on GitHub ?
>
> Of course not. But as the project grows, people will be working in a
> more focused and specialized manner, unaware of what is going on in
> the rest of the project. Even today, with ~15-20 repos, not all of us
> are subscribed to all of them. We need ways of propagating information
> from all that development activity on all of those repos in a way that
> project leadership is able to guide the whole project in a coherent
> manner. Also, remember, we are hiring a number of non-coders who will
> need to participate in the project.
>
> > Seem pretty obvious, open an issue, people can subscribe or unsubscribe
> > on a per issue bassi and coordinate.
>
> I don't think that is reasonable. We have to start having people
> focusing and specializing and part of that is that more and more
> people will be involved in the project, but not coding. We will soon
> have people focused on design, fundraising, event planning,
> budget/admin, hiring, managing staff, industry relations, etc. We have
> a huge challenge in integrating these efforts into the code-centric
> core of the project, but we have to.
>
> > Even when you have your earplugs you also generate echo.
> > :-)
>
> Yes, that one was super weird - have never seen it before or since.
>
> Cheers,
>
> Brian
>
> >
> > --
> > M
> >
> > --
> > 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/4D2EC1FC-C333-4DCF-B8DE-9D005FE934FE%40gmail.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
> _______________________________________________
> 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/20150629/3517e607/attachment.html>