Add Jupyter as 1Password users.

[Carreau]

Your Project

1Password Teams URL

https://jupyter.1password.com/home

Project Name

Jupyter

Short Description

The Jupyter Project is a project and community whose goal is to
"develop open-source software, open-standards, and services for
interactive computing across dozens of programming languages"

Project Age

7 Years old (created in 2015)

Number Of Core Contributors

Current Steering council is 17 members (as per
https://jupyter.org/about), the definition of core contributors is a bit
more fuzzy and there are likely a few dozen with all the repos we
manage.

Project Website

https://jupyter.org

Repository URL(s)

https://github.com/jupyter
https://github.com/jupyterhub
https://github.com/jupyterlab
https://github.com/ipython/

Latest Release URL(s)

https://pypi.org/project/jupyterlab/
https://pypi.org/project/notebook
https://pypi.org/project/ipython
https://pypi.org/project/ipykernel

License Type

BSD

License URL

https://github.com/jupyterlab/jupyterlab/blob/master/LICENSE

A Bit About Yourself

Name

Matthias Bussonnier

Email

bussonniermatthias@gmail.com

Project Role

Steering Council Member and Founder of the Jupyter Project since before
it's inception (2012), I'm currently trying to push a bit for better
security practices and credential managements.

Profile/Website

You can find some of my rambling on https://matthiasbussonnier.com/,
otherwise most of my activity is on github https://github.com/carreau
and on twitter (https://twitter.com/mbussonn)

Comments

I'm personally not a 1password users, but I heard good things, the
current solution seem to be a bit inadequate as there is a keepassc
credential file shared via dropbox which is super problematic.

My hope is to make it easier to share sensitive credentials to the core
security/admins, that is everything that does not support account
delegation. Currently the main struggle we have are with:

• Hosting providers that do not support delegation.
• Twitter (and indirectly via twitter: medium)
• Some website like readthedocs,
• the original credentials of some shared accounts (like Gmail, where
  folks are delegated but every now and then need access to them).

We'll likely also store there a few rarely access personal credential in
case of a catastrophe.

I hope that the group structure of 1password will help us to manage who
needs access to what (website/social-media/communication), but as stated
above I don't have much one-password experience.

Side personal note, I really appreciate your team putting out technical
blogs out, like the recent 1password for linux using rust.

Thanks,

[oliverdunk]

Thanks for your application, @Carreau! I've gone ahead and applied the promotion to your account. Super excited about this one - I'm already familiar with Jupyter so it was great to see. I also appreciate all of your kind words on 1Password and our blog posts. I'll be sure to share those with Dave and team!

If you haven't done so already, I would definitely recommend implementing a recovery plan for your team in case access for a particular contributor is ever lost: https://support.1password.com/team-recovery-plan/. You are also welcome to add additional core contributors as you see fit.

[Carreau]

Super excited about this one - I'm already familiar with Jupyter so it was great to see

Thanks ! Let us know if there is anything we can make in Jupyter to make your life easier as well.

I'll follow the advices.

Had 1password had ever thought of trying to replicate some of what https://keybase.io/ was doing ? I'm sort of worried since they've been bought by zoom.

Thanks !