lbryio / lbryio/ytsync

Consider how to set copyright / ask publisher

Open
#8 2 comments 0 reactions 0 assignees View on GitHub
type: discussion
Dominant language
Go
Stars
40
Forks
17
PR merge metrics
No merged PRs in 30d

Description

@kauffj commented on [Tue May 15 2018](https://github.com/lbryio/lbry.go/issues/13)

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

Contributor guide

No contributing guide indexed for this repository

Research direction

Trace the publishing flow that calls the YouTube API and inspect the youtube/token page mentioned in the issue. Verify how status.license values are handled, determine the matching Creative Commons treatment and default behavior, then add tests and update the page so the documented policy matches the implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, documentation
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.