Copyright assignment requirements should be clear when submitting patches
Bug #356323 reported by
Ted Gould
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When people submit patches on some projects they require copyright assignment. It would be nice if this was more clear and told to them up front. It sucks if they spend time on a patch, and then realize that they no have copyright assignment. Perhaps we could do something in the bug tracker to make it clear that any patches uploaded will require copyright assignment. That way at least they know before uploading, if they didn't know before writing it.
tags: | added: patch-tracking |
Changed in malone: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
Not all projects require copyright assignment, though some do. Can you say which projects you encountered the problem in? (Of particular interest to me: any of the ones listed at http:// www.canonical. com/contributor s ?)
Your idea of having some sort of automated support for reminding people about copyright assignment requirements is interesting. Working out the right place to do that in the UI could be tricky. It'll be easier to think about after we have a better sense of the scope of the problem.
A simple solution that any project can take right now, though, is to mention such a requirement in their hacking guidelines -- the document that one would naturally read before starting a patch anyway.