[IPython-dev] IPython "lab meetings" on g+ hangouts on air

[Carl Smith]

There's prose.io, which edits gh files with support for using Markdown. I
have only played with it, so can't recommend it, but it may work well for
this.
On May 19, 2013 9:59 PM, "Aaron Meurer" <asmeurer at gmail.com> wrote:

> On Sun, May 19, 2013 at 2:34 PM, Fernando Perez <fperez.net at gmail.com>
> wrote:
> > Does anyone have any good suggestions on a tool for collaborative
> > note-taking, so that we can leave some public summary/record of these
> > meetings with minimal fuss?
> >
> > A google doc is a bit of a hassle for this, I think, esp. since we
> > want something to produce plaintext.
>
> Just curious, why does it have to be plain text? I've found Google
> Docs features like tables and highlighting are quite useful in
> sometimes.
>
> Maybe you could find a collaborative editing tool that uses Markdown.
> Then you could just post the result on the wiki.
>
> Ace seems pretty good. Maybe one of these
> (http://ace.ajax.org/#nav=production) can do the trick.
>
> Aaron Meurer
>
> >
> > Etherpad is ugly as sin, but it's fairly functional and I know the
> > software carpentry folks use it very effectively.
> >
> > Unless someone knows of a better solution, I guess we could just use
> > etherpad.  I'm not thinking of anything very involved, simply a
> > document for each meeting where everyone can type, and that we can
> > copy/paste to the mailing list at the end as a quick and dirty
> > summary.
> >
> > I know we won't have time for formal minutes, so these docs could end
> > up being little more than a link to the URL for the youtube video.
> > But if there's anything worth summarizing in text, I think it will be
> > useful to have a note-taking app open with everyone involved.
> >
> > Note that this is different from chat: g+ has an open chat channel,
> > but that's a sequence of messages.  What I'm thinking of is a proper
> > *editor* where we can leave a text file at the end; a chat app won't
> > work for this.
> >
> > I want this to be very lightweight and low-friction, so hopefully a
> > simple g+ hangout plus a common text file is all we'll need.
> >
> > I propose we go with the ugly etherpad unless anyone has a better
> > solution (but I'm happy to use something else if there is such a
> > thing).
> >
> > Cheers,
> >
> > f
> >
> > On Sun, May 19, 2013 at 10:15 AM, epi <massimodisasha at gmail.com> wrote:
> >> I love this,
> >> i enjoyed the first hangout
> >> i'll follow you guys :)
> >>
> >> thanks!
> >>
> >> Massimo.
> >>
> >> Il giorno 19/mag/2013, alle ore 11:45, Damián Avila <
> damianavila at gmail.com> ha scritto:
> >>
> >>> El 16/05/13 22:06, Fernando Perez escribió:
> >>>> Hi folks,
> >>>>
> >>>> as Brian just mentioned, we had a google hangout discussion today,
> >>>> that arose impromptu from having a chat room discussion where it was
> >>>> obvious we needed more bandwidth than just typing can provide.
> >>>>
> >>>> Today (perhaps because of all the changes Google made yesterday, who
> >>>> knows), g+ was a bit glitchy, and we were unable to make the hangout
> >>>> on-air, so it ended up not being recorded.  But in general we want all
> >>>> these discussions to be public, for example here's our previous one:
> >>>>
> >>>> http://www.youtube.com/watch?v=Yb35M8cW7o4
> >>>>
> >>>> While I think it's great to jump in on video conversations like this
> >>>> as-needed from the dev room or a github issue/PR discussion, we've
> >>>> also been thinking about having a more regular 'lab meeting' style
> >>>> discussion that is scheduled at a fixed time.
> >>>>
> >>>> This would give a predictable time for everyone to participate, and
> >>>> would play the same role as lab meetings in everyday research, but
> >>>> taking into consideration the fact that we're an open, international
> >>>> collaboration.
> >>>>
> >>>> Those lab meetings would be held with hangouts on-air, and thus open
> >>>> for anyone who wants to watch and join, and kept on-record afterwards.
> >>>>
> >>>> The plan would be to hold them for ~60-90 minutes, to make regular
> >>>> progress on design decisions that impact the project at large.
> >>>> Impromptu hangouts as required by the everyday workflow will continue
> >>>> to happen, and we'll do our best to also record those in public
> >>>> format.
> >>>>
> >>>> If you like the idea, I'd like to propose Thursdays at 10am US Pacific
> >>>> time, i.e. UTC-7 hours right now (PDT).  That's a good time for all
> >>>> the folks here in California while still being reasonable in Europe.
> >>>> I know we can't find a time that will work across all of Earth, but at
> >>>> least that probably covers reasonably well our current core team and
> >>>> lots of others.
> >>>>
> >>>> How does this sound to you all?  Would the time work for a reasonable
> >>>> chunk of our active developers? Note that I am NOT asking only of the
> >>>> 'core' github committers, but of anyone who is putting lots of time
> >>>> into IPython work and is interested in joining these discussions.
> >>>>
> >>>> Cheers,
> >>>>
> >>>> f
> >>>> _______________________________________________
> >>>> IPython-dev mailing list
> >>>> IPython-dev at scipy.org
> >>>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >>>
> >>>
> >>> I think it is a great idea! I will try to participate in the meeting as
> >>> much as I can.
> >>>
> >>> Cheers.
> >>>
> >>> 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
> _______________________________________________
> 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/20130520/f3243b5a/attachment.html>