Page MenuHomePhabricator

Define default license for PAWS user data
Open, Needs TriagePublic

Description

Currently there is no default license for user generated content in PAWS. It is all public, but nothing is licensed unless the user specifies it in some manner. I propose we change it to have a default open source license and allow for the users to specify different licenses (or lack thereof) in their own spaces.

If we go forward with this we need to adequately present this to the user, the implementation details should be discussed in subtasks.

Event Timeline

@Phaebz and I were wondering about this − agree this should be nice to have :-)

(I like how Quarry is explicitly CC-0 − probably a hard sell for that code though :)

Taking the @bd808 bump on this to help move it forward.

I think the first step is for us to choose a default license and for us to add it for new users in an opt-out basis. Could be as simple as adding a LICENSE file for new users at first that they can edit at will.

So my rough draft would be:

  1. we'd choose one license from open source licenses (as defined by the cloud-services-team)
  2. Add this license for new PAWS users automatically.
  3. Document a rule that all PAWS code must be under an open source license (as defined by the cloud-services-team).
  4. Leave a period (long? maybe 3 to 6 months) for existing users to adopt an approved license.
  5. Add a LICENSE for all users that have not adopted a license by the end of the period with the license chosen in step 1.

Maybe add steps with notifications for all existing users and then for the non compliant ones after step 4? We won't have emails for all PAWS users but most of them usually add it in the wikis. And of course we should announce this in several channels.

Thoughts?

bd808 added a comment.Mar 8 2020, 5:16 AM

The plan in T221548#5951699 sounds reasonable to me. From past conversations with folks who actually are lawyers, it would be nice if there was an affirmative opt-in step that new PAWS users had to take to select their default license. If that is not readily possible in the jupyterhub workflow, then maybe a .skel file with a name that screams "you need to choose a default license" to prompt them when they first see the file browser view?

we'd choose one license from open source licenses (as defined by the cloud-services-team)

https://opensource.org/licenses/ is the list specified by https://wikitech.wikimedia.org/wiki/Wikitech:Cloud_Services_Terms_of_use