Add team-compass page including JupyterLab Council members

[afshin]

I copied @Zsailer's lead in setting up the Jupyter Notebook page. However, there are a few notable differences and I would really appreciate reviews on this:

• I have changed the term "team" in a lot of places to JupyterLab Council to reflect the difference between the broader team and the decision-making body.
• I have updated the steps outlined to becoming a new member of the JupyterLab Council to reflect the private nature of voting on individual members and to allow members to refuse membership. However I don't want to have unilaterally set the course of our decision-making. Please feel free to comment on this section and make suggestions.
• I don't know what I am doing with regard to publishing to RTD. I think I did this correctly but I am not 100% confident of that.
• @damianavila @marthacryan @ellisonbg @jasongrout @ivanov @krassowski @fperez @isabela-pf @jtpio You are all mentioned by name in this PR. Please take a look 👀

[echarles]

@afshin I may miss context. How is the list of contributors related to commit rights?

[afshin]

@echarles I think the file name is legacy from where I copied it, but there isn't a strict relationship between commit rights and membership in the JupyterLab Council. At some point when the Council is fully set up it might be a 1:1 relationship but for the process of ramping up, there will likely be many more people with commit rights than there are members of the JupyterLab Council.

[afshin]

Just to be clearer: that file in this PR is not the list of contributors for JupyterLab by any stretch 😂

[jasongrout]

There are a lot of mentions of "team" in this file that should be changed to "council". Also, it would be great to change the directory of these files from "team" to "council" if these are all about the council.

[afshin]

I think there are a few mentions of "team" that should mean the wider community of people. And there are some places where "team member" should just be "member". But I do think we should retain some usage of the term "team" because this is, after all, the team-compass.

[jasongrout]

But I do think we should retain some usage of the term "team" because this is, after all, the team-compass.

Yes, absolutely!

[jtpio]

@afshin this is looking good, thanks for setting that up!

Do you think this is ready to be merged, so it can be iterated on as new members are added to the council?

[afshin]

@jtpio yeah, I think so. At first, I was hoping that we would synchronize with https://github.com/jupyter/team-compass-template but actually iterating seems better than leaving this open forever.

[jtpio]

Just tried in a clean environment and although it gives a couple of warnings it seems to be building fine 👍

[jtpio]

We could add the following to the .gitignore as well as they are generated at build time:

# docs generated files
_build
docs/team/active.txt
docs/team/inactive.txt

Otherwise it looks good and should be good to go!

[jtpio]

We could add the following to the .gitignore as well as they are generated at build time:

Added in 151e0de.

[jtpio]

Thanks!

Let's get that one in and iterate. Follow-up actions:

• making sure the project exists on ReadTheDocs
• enable the ReadTheDocs preview for pull requests

[jtpio]

The site is now live on ReadTheDocs: https://jupyterlab-team-compass.readthedocs.io/en/latest/