Comment 2 for bug 356323

On Tue, 2009-04-07 at 13:44 +0000, Karl Fogel wrote:
> 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/contributors ?)

We haven't encountered any problems. I just worry that we're
effectively putting someone into a hard position by asking when they've
already written the patch. They've already put the work in, obviously
they'd like it included, and now we're asking them to do something that
they may not want to. So they're forced to make a choice in a more
difficult position than they should need to.

Specifically I was talking about evolution-indicator, but I've talked to
other OS people about how this was an issue in their projects before,
and the point just kinda hit me to say "Launchpad should do this
better."

> 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.

It would be interesting if we could do it someway like what is done for
Ubuntero support. So that a project, any project, could have a
copyright assignment and I could set up my account to assign copyright.
I imagine most of the FSF projects that require copyright assignment
would appreciate that as well. You could then GPG sign it, upload it,
and remove the warning.

  --Ted