Consider how to set copyright / ask publisher

kauffj commented

2018-05-16 02:33:39 +02:00

(Migrated from github.com)

Copy link

Some publishers do not wish to retain copyright or wish to publish under creative commons or similar.

If this information is available via YouTube, we should match it.

If not, we should ask but provide a sane default (e.g. it could be on the lbry.io/youtube/token status page).

Steps:

When publishing, fetch status.license from youtube api (https://developers.google.com/youtube/v3/docs/videos#status.license). If license is creativeCommon, publish under the creative commons license (check which one youtube uses and use the same). If its youtube, do whatever we do now.
add a note on the youtube/token page explaining how we'll be setting the license on published content, and tell the user to email us if they want a different treatment for their content. use our support email

Acceptance Criteria

Definition of Done

Tested against acceptance criteria
Tested against the assumptions of the user story
The project builds without errors
Unit tests are written and passing
Tests on devices/browsers listed in the issue have passed
QA performed & issues resolved
Refactoring completed
Any configuration or build changes documented
Documentation updated
Peer Code Review performed

Some publishers do not wish to retain copyright or wish to publish under creative commons or similar. If this information is available via YouTube, we should match it. If not, we should ask but provide a sane default (e.g. it could be on the lbry.io/youtube/token status page). Steps: - [ ] When publishing, fetch `status.license` from youtube api (https://developers.google.com/youtube/v3/docs/videos#status.license). If license is `creativeCommon`, publish under the creative commons license (check which one youtube uses and use the same). If its `youtube`, do whatever we do now. - [ ] add a note on the youtube/token page explaining how we'll be setting the license on published content, and tell the user to email us if they want a different treatment for their content. use our support email ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed

Consider how to set copyright / ask publisher #13

Acceptance Criteria

Definition of Done