Weekly meeting written summary ?

[Matthias Bussonnier]

Hi all,

As you may know we regularly have video meeting to get things moving
forward and catch up with the development as well as requesting
feedback.

While these meetings are recorded and available on Youtube, and that
some notes are taken on jupyter.hackpad.com, I find it relatively
difficult to catch up when I can't attend, or try to get through
archives.

I'm thinking that a shorter, curated version of these notes might be
more useful than watching the video as you can more easily follow the
notes at your own pace; at the right time.

I am working full-time on IPython and Jupyter and it is already hard
to follow development, so I'm wondering even how anyone not full-time
can try to get a hold on what's happening.

Am I the only one who feel this way ? And for who a weekly summary
would be helpful ?

Note that I'm not speaking of something like the newsletter but
something a bit more dev-oriented, where typos are ok, but still use
full sentences links, but is a "Summary" not an exhaustive list.

Thanks !
--
M

[Brian Granger]

Would you post these to the Google Group? I think what you are
proposing is very reasonable. I think having team leaders responsible
for summarizing their meetings like this would also be helpful.

> --
> 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+u...@googlegroups.com.
> To post to this group, send email to jup...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CANJQusVffod924xJMDs5F0yYHh6Vda3mC7%3Dzqg%3Dpc1vxbv_vGQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.



--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
bgra...@calpoly.edu and elli...@gmail.com

[Thomas Kluyver]

I think a summary of the meetings would be useful.

On a related note, I'd like to propose that we organise the Hackpad notes (and consequently the meeting format) around parts of the project, rather than around individuals. I.e. rather than the notes saying 'Thomas Kluyver: foo, bar', I'd like to see 'IPython kernel: baz, qux'. And it's fine to leave components out if there's no particular update on that area. I think this would make the meetings a more useful exchange of information, both for the people in the meeting and anyone looking at the notes later.

--
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@googlegroups.com.

[Matthias Bussonnier]

On Fri, Nov 18, 2016 at 2:49 PM, Brian Granger <elli...@gmail.com> wrote:
> Would you post these to the Google Group?

Possibly, I would _prefer_ to have a better archiving medium where
only this is available, but I don't see any harm in posting that on
the google group. The _advantage_ of building that on a separate
platform is that it can be built progressively and in collaboration
with each other.

> I think having team leaders responsible
> for summarizing their meetings like this would also be helpful.

It would be nice to have leader _involved_, but making them
responsible would be (IMHO) too much strain on them as they can be
unavailable, travelling. I would prefer to have the responsibility
that this get done on the leader but have a regular involvement on a
day-to-day basis from individuals. I even think that having a rough
outline before each meeting would be helpful to shorten the meetings
and make them more useful.

The question remain do we do 2 summaries per week (same days as
meetings) or one ?

On Sat, Nov 19, 2016 at 6:25 AM, Thomas Kluyver <tak...@gmail.com> wrote:
> I think a summary of the meetings would be useful.
>
> On a related note, I'd like to propose that we organise the Hackpad notes
> (and consequently the meeting format) around parts of the project, rather
> than around individuals. I.e. rather than the notes saying 'Thomas Kluyver:
> foo, bar', I'd like to see 'IPython kernel: baz, qux'. And it's fine to
> leave components out if there's no particular update on that area. I think
> this would make the meetings a more useful exchange of information, both for
> the people in the meeting and anyone looking at the notes later.

I think from a _practical_ perspective, as people fill in things
during the meeting it might be hard.
But for the summary, yes definitively.

Also instead of arguing how it should be let's do something like Carol did:

https://github.com/willingc/jhub-week/issues/1

--
M

[Thomas Kluyver]

On 19 November 2016 at 21:13, Matthias Bussonnier <bussonnie...@gmail.com> wrote:

I think from a _practical_ perspective, as people fill in things
during the meeting it might be hard.
But for the summary, yes definitively.

It would require a bit more organisation to put some notes together before the meeting starts. But I think it's worth doing that so we can have a productive conversation.

[Damián Avila]

+1 to weekly summaries (maybe two are OK as well given that jupyterlab has it own meeting/space).

Btw, Thomas proposal worked really well in the last meeting IMHO... so we should continue to do that.... even more, with the new topic-based organization, making a summary would be easier than when you tried to do it from a person-based meeting notes.

--

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@googlegroups.com.
To post to this group, send email to jup...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qiQPWunL3CN2c97-xDZmG6M5qre-%3DkgjH3vJWbt6JS4aQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Damián Avila

[Jessica B. Hamrick]

+1 also to weekly summaries. I also think the topic-based organization works better than that organized individuals.

Cheers,

Jess

To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH%2BmRR29Rfp79bk9G2GqXfdr025gm8hG%2BMjd8XNd-Gxz7vSVDw%40mail.gmail.com.

[Yuvi Panda]

+1

We do this wikimedia-wide.
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-11-16 for an
example of the summary, https://www.mediawiki.org/wiki/Scrum_of_scrums
for more info about it.

>>> email to jupyter+u...@googlegroups.com.

>>> To post to this group, send email to jup...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jupyter/CAOvn4qiQPWunL3CN2c97-xDZmG6M5qre-%3DkgjH3vJWbt6JS4aQ%40mail.gmail.com.
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> --
>> Damián Avila
>>
>> --
>> 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+u...@googlegroups.com.

>> To post to this group, send email to jup...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jupyter/CAH%2BmRR29Rfp79bk9G2GqXfdr025gm8hG%2BMjd8XNd-Gxz7vSVDw%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+u...@googlegroups.com.

> To post to this group, send email to jup...@googlegroups.com.
> To view this discussion on the web visit

> https://groups.google.com/d/msgid/jupyter/CALUXcBxKKX42X6H%3Dksx0siEF%3DBsn3Rp5NWDknN5UtbDkaew0hg%40mail.gmail.com.

>
> For more options, visit https://groups.google.com/d/optout.



--

Yuvi Panda T
http://yuvi.in/blog