Terms of Service and Code of Conduct for 2i2c Hubs

[rabernat]

Context

LEAP (2i2c customer) will be opening our hubs to a broad community of participants, including students, researchers, and outside affiliates.

Our executive committee is interested in making sure that our hub users all agree to abide by:

• Terms of Service - which specify explicitly that the hub should not be used for any kind of abusive behavior, hacking, crypto-mining etc.
• Code of Conduct - our project's CoC applies to behavior on the hub, interaction with support staff, etc.

ToS and CoC are related but distinct.

Proposal

I propose that we create a universal "Terms of Service" which applies to all 2i2c hubs. This will give customers like LEAP peace of mind that there is a clear framework for what behavior is not permitted on the hub. Presumably this is standard boilerplate.

I also propose that we give hubs the opportunity to link to a community CoC on their landing page (e.g. https://leap.2i2c.cloud/hub/login).

Updates and actions

No response

[damianavila]

@rabernat is there any timeline expected for this request?

[rabernat]

There is no specific deadline if that's what you're asking.

[sgibson91]

@damianavila with your PM hat on, do you agree that this issue should be split into two?

1. Optional link to a community's CoC on the homepage in https://github.com/2i2c-org/default-hub-homepage
2. Create a Terms of Service in https://github.com/2i2c-org/team-compass

The reason I suggest this is because I think that writing ToS will likely involve collaborating with CS&S, like with creating the privacy policy etc., and that should be tracked separately/differently from the CoC link and nearer to, e.g., 2i2c-org/team-compass#388

[choldgraf]

Fair use / Terms of Service / Acceptable use

We actually started an issue around "acceptable use" last year, maybe we can revive that one and publish something after an iteration with CS&S. Here is that issue:

• Acceptable Use Policy for Managed JupyterHubs infrastructure#342 (there is a draft inside in a google doc)

Code of Conduct

For the Code of Conduct - to be clear, you don't need 2i2c to define any kind of COC or enforcement mechanisms, you just need a link that is on the hub's landing page? If that's the case I agree w/ @sgibson91 that should be a dedicated issue.

That said, I would be interested in brainstorming with @rabernat and others what is the "ideal" UX around landing pages. It feels to me like over-riding the "log in" template is a bit hacky, and ideally you'd have something that's a bit more easily extendable/customizable (e.g. a Jupyter Book landing page or something?)

[damianavila]

@damianavila with your PM hat on, do you agree that this issue should be split into two?

Yes

We actually started an issue around "acceptable use" last year, maybe we can revive that one and publish something after an iteration with CS&S.

OK, let's resurrect that one as the ToS piece.

For the Code of Conduct - to be clear, you don't need 2i2c to define any kind of COC or enforcement mechanisms, you just need a link that is on the hub's landing page? If that's the case I agree w/ @sgibson91 that should be a dedicated issue.

And let's use this issue for the CoC "linker" (planning to update the title after I get some +1).

That said, I would be interested in brainstorming with @rabernat and others what is the "ideal" UX around landing pages. It feels to me like over-riding the "log in" template is a bit hacky, and ideally you'd have something that's a bit more easily extendable/customizable (e.g. a Jupyter Book landing page or something?)

IIRC, we can serve docs alongside our Hubs: https://infrastructure.2i2c.org/en/latest/howto/customize/docs-service.html
Maybe we can also serve a CoC?