Moving towards a more structured team setup

[Fernando Perez]

Hi all,

this is an email that is long overdue... As the project has grown in size and complexity, we have at times struggled with how to effectively coordinate, communicate and work in this larger context.

At the dev meeting we conducted a survey of the folks who were there, looking for a way to slice the project into major areas and to identify who could assume leadership of each of these areas.  As usual, "leadership" here means mostly responsibility, not some vertical, unilateral definition of authority. In every area of the project we maintain an ethos of openness and collaboration, and we want participation to continue increasing.

But the reality is that, at this size and number of moving parts, it's becoming detrimental not to have designated leads who can move things forward, focus and keep an eye on their area, and sometimes make decisions needed to get the ball rolling.  While I'm happy to maintain my role as project's BDFL as long as the community wants me to, that role can't mean that I make final decisions up and down our massive number of repos and project areas.

In summary, this is about delegating for efficiency and improved communication.

I'd like to post here the table of what we have so far.  Thanks to Jamie's dedicated crunching of the info, we have it now broken down by large areas and all active repos are assigned to an area.

This isn't perfect, and in particular what is called tentatively "user engagement" includes a LOT of work on the broad/public-facing aspects of the project that will probably require more refinement.  But I don't want to keep delaying this any further.

Please take a look at the table below, and let's see if we can agree on the roles and rough slicing.  In particular, folks whose name appears in a leadership role should mention whether they are OK with the idea, whether there's any other area they'd prefer to focus on, etc.

I want to clarify that we did our best to digest people's survey responses, but I also did some moving around in an attempt to cover everything we have in the air.  If I moved you around in a way you didn't want, I apologize and just let's figure out a better solution.  I didn't intend to strong-arm anyone.

Cheers,

f

Core
Leader Min? Mostly FT Work Min Ragan-Kelley Mostly PT Work Carol Willing Thomas Kluyver Matthias Bussonnier Jason Grout Steven Silvester	Projects/Functional Areas	Repos
	jupyter_core	jupyter_core
	jupyter client	jupyter_client
	Python 2 Support
	message spec
		testpath
		jupyter_kernel_test
JupyterLab and J. Notebook
Leader Brian Granger Matthias Bussonnier Jason Grout Mostly FT Work Steven Silvester Mostly PT Work Nicholas Bollweg Chris Colbert Afshin Darian Fernando Perez Peter Parente Thomas Kluyver Carol Willing Min Ragan-Kelley Damián Avila	Projects/Functional Areas	Repos
	single user server	jupyter-drive
	classical notebook UI	notebook
	Real Time Collaboration (RTC)
	Dashboarding (incubation)
	Element filtering
	jupyterlab	jupyterlab
		jupyter-js-services
		jupyter-js-utils
		jupyter_logger
Widgets
Leader Sylvain? Mostly FT Work Grant Nestor Mostly PT Work Peter Parente Jason Grout Afshin Darian Steven Silvester Nicholas Bollweg Brian Granger Jonathan Frederic	Projects/Functional Areas	Repos
	ipywidgets	ipywidgets
	traitlets	traitlets
	declarative widgets
		widget-cookiecutter
Parallel
Level of Effort: Low
Leader Min Ragan-Kelley Mostly FT Work None Mostly PT Work Carol Willing	Projects/Functional Areas	Repos
	ipyparallel	ipyparallel
Kernel
Leader Thomas Mostly FT Work Thomas Kluyver Matthias Bussonnier Mostly PT Work Min Ragan-Kelley Steven Silvester	Projects/Functional Areas	Repos
	jupyter_console	jupyter_console
	NB software engineering (Thomas)
	IPython	ipython
		ipykernel
		ipython_genutils
	Shadow_ipython	ipython-sec PRIVATE
Services
Leader Carol? Community? Talk to Min Mostly FT Work Min Ragan-Kelley Mostly PT Work Carol Willing Peter Parente Kyle Kelley Nicholas Bollweg	Projects/Functional Areas	Repos
	tmpnb	tmpnb
		tmpnb-deploy
		tmpnb-redirector
	nbviewer	nbviewer
		nbcache
	kernel_gateway	kernel_gateway
		kernel_gateway_demos
	demohub	try.jupyter.org
	collab. with binder
	etc. -need to specify-
		cdn.jupyter.org
		docker-demo-images
		docker-stacks
		nbshot
		ops-handbook PRIVATE
		enhancement-proposals
		salt-states-nbviewer
		ipython-ansible-jenkins
Documents
Leader Matthias? Thomas? +Fernando? Mostly FT Work Mike Pacer Mostly PT Work Fernando Perez Katie White Nicholas Bollweg Min Ragan-Kelley Jessica Hamrick Damián Avila Matthias Bussonnier Thomas Kluyver Carol Willing Peter Parente	Projects/Functional Areas	Repos
	nbconvert	nbconvert
		nbconvert-examples
	nbformat	nbformat
	nbdime	nbdime
JupyterHub
Leader Min Ragan-Kelley Mostly FT Work Carol Willing Mostly PT Work Jessica Hamrick Kyle Kelley Brian Granger	Projects/Functional Areas	Repos
	jupyterhub	jupyterhub
	deployment	oauthenticator
		jupyterhub-deploy-teaching
		dockerspawner
		jupyterhub-carina
		jupyterhub-tutorial
		configurable-http-proxy
		jupyterhub-deploy-docker
		sudospawner
		ldapauthenticator
Jupyter in Education
Leader Jessica Hamrick Katie White Mostly FT Work None Mostly PT Work Fernando Perez Min Ragan-Kelley Brian Granger	Projects/Functional Areas	Repos
	nbgrader	nbgrader
Events
Leader Ana Ruvalcaba Katie White Mostly FT Work None Mostly PT Work Fernando Perez Steven Silvester Nicholas Bollweg	Projects/Functional Areas	Repos
	JupyterDays	lbnl-jupyterday
	JupyterCon
	Semi-Annual Dev Meetings
Break this out?
? Rename "Community & Governance"?
User_Eng
Leader Katie White Ana Ruvalcaba Mostly FT Work None Mostly PT Work Fernando Perez Steven Silvester Damián Avila Min Ragan-Kelley Brian Granger Matthias Bussonnier Thomas Kluyver Carol Willing	Communications/Marketing
	- Blog	jupyter-blog-theme
	- Websites	jupyter.github.io
		ipython.github.com
		ipython-website
		ipython-doc
	- Newsletter	newsletter
	- Twitter
	- Marketing	marketing
		design (move to communications)
	Technical Communication
	- Docs	jupyter-sphinx-theme
	- Tutorials	jupyter
		ngcm-tutorial
		scipy-2015-advanced-topics
		scipy-advanced-tutorial
		strata-sv-2015-tutorial
		mozfest15-training
		nature-demo
		docker-demo-images
		docker-stacks
		nbcache
		ipython-in-depth
		mozfest2014
		front-to-back
		talks
	- Videos
	- Academic Papers
	User Support
	- Gitter?
	- Stack Overflow (SO)
	- Help	help
	- Mailing List (double listed)
	Community and Governance
	- Community Pipeline	enhancement-proposals
		lbnl-jupyterday
		datasets
		jupyter-overview-paper PRIVATE
		usersurveys
		paper-notebook2013
	- Development Workflow(s)	roadmap
	- Fundraising/sponsorship	sloan-2013-reports
	- User Surveys
	- Governance	governance
	Software Development Process
	- Gitter?
	- GitHub

--

Fernando Perez (@fperez_org; http://fperez.org)
fperez.net-at-gmail: mailing lists only (I ignore this when swamped!)
fernando.perez-at-berkeley: contact me here for any direct mail

[Matthias Bussonnier]

Thanks Fernando and Jamie for making this writeup. 

I'm happy to help lead the nbconvert/document part while I help Mike get up to speed on the codebase. 

I would be really happy to help Jason and Brian coordinate the Notebook/JupyterLab transition as well; 

There is a lot of information to take in there, so I'll re-read and comment further later if needed !

Thanks, 

-- 

Matthias

 

--
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/CAHAreOrgaieFm77%2Bj72g-Rf8kP1MozQywA6fXriptAC0h1gzzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Brian Granger]

I want to emphasize that the content Fernando is sharing ghere is the result of a process that started in April and has involved:

* A survey of core developers about which areas of the project they are interested in and what level of effort they are planning on

* A series of semi-weekly meetings between myself, Jamie and Fernando going through the results of that survey along with the different areas of the project (repos, areas of focus, activities)

* Lots of offline work by Jamie is organizing everything

Cheers,

Brian

On Tue, Aug 16, 2016 at 12:52 AM, Fernando Perez <fpere...@gmail.com> wrote:

--

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/CAHAreOrgaieFm77%2Bj72g-Rf8kP1MozQywA6fXriptAC0h1gzzg%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

[Sylvain Corlay]

Thanks a lot for working on formalizing this.

This slicing looks good to me! I am happy to lead the charge of the widgets track of meeting.

Best,

Sylvain

To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpRuKv5wdijBLu27mhQRM47LFLno7XUaT7QHumxOtng0_A%40mail.gmail.com.

[Thomas Kluyver]

This looks good; I'm happy to lead the work on the kernel+terminal parts, to have some leadership role on documents, and to work as needed on the other bits I'm listed under.

Thomas

To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAK%3DPhk6worM%2B0fQ67EZ0PxAqCEdb%3DirFVj8LGZ01WB%3DZ9C9fNg%40mail.gmail.com.

[Carol Willing]

A great start. I’ve mentioned to Brian and Jamie (though I can’t remember if I shared with Fernando) a bit of concern over the meaning of Full time and Part time as well as a check for overloading of individuals.

I’m currently listed with 1 full time job, 6 part time jobs, and potential co-leadership of operations as well as documentation management. While the concepts are acceptable to me, I’m a bit concerned that I may need to borrow some of Min and Steven’s clones to work with my clones ;-)

Thanks for moving this forward.

Carol

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/CAOvn4qguJmp0o4Fjxc3ZWD8qcpx0ygV4cxnaqSvN-OtibEYNjA%40mail.gmail.com.

[Brian Granger]

Yes, I think a better way of tracking the FT/PT stuff is to list the percentage of each persons time on that team. And then make sure those percentages add up to 100%, except for those who have a clone army working - for them it can be N*100%.

To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAOvn4qguJmp0o4Fjxc3ZWD8qcpx0ygV4cxnaqSvN-OtibEYNjA%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@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/D75739D4-73B6-4904-8886-14158F473E88%40gmail.com.

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

[Damián Avila]

First of all, thank you for this work.

I know this kind of work is very time challenging but I also think it rewards a lot.

The map already presented here makes sense to me.

Also +1 to latest Bryan idea about quoting % of time on each section/subteam.

Cheers.

To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/CAH4pYpR_t9DQyKxoJnQxzFMQn0Fa64p0x6WXW-ndwhztWMz%2Bbg%40mail.gmail.com.

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

--

Damián