Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relicense docs to CC-BY-SA and code snippets to CC-0 #1468

Closed
7 of 8 tasks
cjtenny opened this issue Apr 2, 2021 · 18 comments
Closed
7 of 8 tasks

Relicense docs to CC-BY-SA and code snippets to CC-0 #1468

cjtenny opened this issue Apr 2, 2021 · 18 comments
Assignees

Comments

@cjtenny
Copy link
Collaborator

cjtenny commented Apr 2, 2021

Hello fellow Temporal champions,

As part of #1449 / the plan to get Temporal docs into MDN, we need to relicense the docs to CC-BY-SA and the code snippets to CC-0. I believe we do not need copyright holders of typos or minor corrections to relicense their contributions; all others will need to agree to this for our docs to move to MDN.

The following people have contributed non-small-correction changes to the documentation. Please reply to this issue confirming that you are okay with relicensing your contributions to the documentation under CC-BY-SA and your contributions to code snippets in the documentation under CC-0.

I'm tracking this here in this issue so that we ave a written record, thanks! I've assigned it to everybody but feel free to remove yourself once you've confirmed. I'll edit the checkboxes as people reply, or feel free to edit my post if you're allowed to edit it.

(I agree to relicense my contributions - cjtenny)

@cjtenny
Copy link
Collaborator Author

cjtenny commented Apr 2, 2021

(Once this issue is complete, I'll add the appropriate licensing to the files / folder and submit the PR)

@ryzokuken
Copy link
Member

Thanks! I explicitly approve this.

@Ms2ger
Copy link
Collaborator

Ms2ger commented Apr 2, 2021

I agree to relicense my contributions.

@Ms2ger Ms2ger removed their assignment Apr 2, 2021
@pipobscure
Copy link
Collaborator

I agree to relicense

@ptomato
Copy link
Collaborator

ptomato commented Apr 2, 2021

I agree to relicense.

@ptomato ptomato removed their assignment Apr 2, 2021
@justingrant
Copy link
Collaborator

I agree to relicense!

@justingrant justingrant removed their assignment Apr 5, 2021
@meyerweb
Copy link

@sffc @jasonwilliams What do you think?

@pipobscure
Copy link
Collaborator

Since @jasonwilliams is doing this for Bloomberg and they are therefore the relevant entity I can speak for him and agree to the relicense on Bloombergs behalf.

@sffc
Copy link
Collaborator

sffc commented Apr 14, 2021

My contributions, and contributions from other Googlers, can be licensed as CC BY-SA but not CC-0.

@cjtenny
Copy link
Collaborator Author

cjtenny commented Apr 14, 2021

I will redo my audit to see if any Googlers wrote code snippets or just doc text, in which case that's fine.

I'll continue digging into the TC39 copyright ownership as well to figure out how we deal with that. Thanks all! I'll update in the champions meeting tomorrow morning.

@meyerweb
Copy link

Is there anything I can do to help with the audit? I’m reluctant to restart the MDN effort until I know which parts have to be re-written and which can just be ported over.

@cjtenny
Copy link
Collaborator Author

cjtenny commented Apr 19, 2021

My audit shows that the only off-limit code snippets or changes to code snippets contributed by Googlers (@sffc , as far as I can tell you are the only Googler to have contributed to documentation here) that are not minor corrections or typo fixes are:

In terms of "can be ported over", assuming I get the go-ahead from someone who knows whether TC39's claim to the copyright of the entire work includes the copyright to documentation contributions or whether that's considered copyright of individual contributions - which we think likely since other TC39 proposals have probably had docs ported to MDN - every other code snippet and bit of documentation should be safe.

@sffc
Copy link
Collaborator

sffc commented Apr 19, 2021

Most of those code snippets were originally authored by @justingrant, but I checked them in as part of migrating them from a Google Doc to Markdown.

@justingrant
Copy link
Collaborator

The latter two files are draft docs-- I don't expect they'd end up in MDN anyways, so I don't think copyright/license applies to them.

For iso-string-ext.md, there isn't any actual code in that file. It's just string examples that happen to be formatted as code. So I'd treat that file as 100% "not code". ;-)

Are we bringing all the cookbook examples into MDN? Regardless, if licensing is a problem then I'd suggest just omitting this one.

Most of those code snippets were originally authored by @justingrant, but I checked them in as part of migrating them from a Google Doc to Markdown.

Yep. Shane and I collaborated on that doc, but I think it's OK to consider me the primary author/copyright-owner on that page's code samples.

@meyerweb
Copy link

I’m not currently planning to move the cookbook over to MDN, except possibly to raid it for a basic example or two to use on a guide page, with a link out to the full cookbook.

@ptomato
Copy link
Collaborator

ptomato commented Apr 19, 2021

FWIW, from a cursory look, I think the changes that Shane made to futureDateForm.mjs consisted of annotating it with partial ISO calendar examples, and then reverting that annotation - I guess those two commits didn't get squashed together.

@justingrant
Copy link
Collaborator

@meyerweb - Do you need anything else from us to proceed? Seems like all the outstanding code samples above now are unblocked.

@meyerweb
Copy link

@justingrant - I don’t think so, thanks! I’ll take the conversion process back up today, or possibly tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants