Open Stack

I have been notified of another very small patch that is left in a
limbo, with the author not allowed to sign the CLA and the developers
stuck in unknown legal territory. You can read more about it on

https://bugs.launchpad.net/bugs/1308984

>From what I can see, the patch is trivial and shouldn't even be
copyrightable but the person spotting the issue and fixing it is not
comfortable signing the CLAs. Can any other developer copy the patch and
put it into our trunk? Until when is this sort of behaviour safe?

We're getting more of these small blockers and I think it's already a
problem. Having to sign a Corporate CLA and Individual CLA for a trivial
patch, from an operator (whose job is to run clouds, resulting in small
and rare patches, not to develop large features) can conflict with our
effort to get more operators involved in OpenStack.

I'm not sure what solutions are available. If we can't change the CLA
processes easily, what else can we do to get small contributions like these?

thanks,
/stef

-- 
Ask and answer questions on https://ask.openstack.org