Skip to contentSkip to conversation

Upcoming project ownership changes

DISCUSSION Brad Bishop 3 participants 6 messages Feb 14, 2018 – Feb 15, 2018

lore
Share & tools
lore
#0 lore raw

OpenBMC community

During your travels you may have noticed that the OpenBMC brand is somewhat fragmented. There are several BMC firmware ecosystems out there today, of which this project is just one.

For the past year, the leaders of these ecosystems have been hard at work to bring all the projects together and move forward with a single industry-wide OpenBMC.

I'm happy to report that these industry leaders have rallied around your community as the meeting point. Very soon it will get a lot more busy around here.

To this end, IBM will be ceding stewardship of this project to the Linux Foundation in the very near future. You can find the project charter here:

https://docs.google.com/document/d/1uBbi5rDhWqj8Al-eoNLxERZ9OK8KVMZThOu
S08-cYto

In the longer term I'm optimistic all this means change, growth and success for all of us. In the shorter term, I don't anticipate any major changes in the day to day of what we all do, with one exception. Under the new charter, contributors will be required to sign a contributor license agreement. There will be corporate (your company signs once for all future contributions originating from your company) and individual agreements available:

https://docs.google.com/document/d/1veiAjszrhgabA8XrJWjYCs7lyXIhs5rcXWg
aeuW-bT8
https://docs.google.com/document/d/1m61YH8GSzQpYVt5YG95fb2QNy1Gs--1-oLD
3znqPNQw

Please work with your legal team (if using the corporate CLA) or sign the individual CLA now and send them to me to avoid any delays in your development work flow when the transfer occurs.

-brad

#1 lore raw

contributor license agreement (CLA) (was: Upcoming project ownership changes)

Dear Brad,

Am 14.02.2018 um 04:53 schrieb Brad Bishop:

[…]

Quoted 9 lines

I'm happy to report that these industry leaders have rallied around your community as the meeting point. Very soon it will get a lot more busy around here.

To this end, IBM will be ceding stewardship of this project to the Linux Foundation in the very near future. You can find the project charter here:

https://docs.google.com/document/d/1uBbi5rDhWqj8Al-eoNLxERZ9OK8KVMZThOuS08-cYto

(Note, the URL is wrapped in your message.)

Thank you. Cooperating is definitely a good thing. My knowledge of the goals and operation of the Linux Foundation is not good enough to comment on that.

Quoted 11 lines

Under the new charter, contributors will be required to sign a contributor license agreement. There will be corporate (your company signs once for all future contributions originating from your company) and individual agreements available:

https://docs.google.com/document/d/1veiAjszrhgabA8XrJWjYCs7lyXIhs5rcXWgaeuW-bT8
https://docs.google.com/document/d/1m61YH8GSzQpYVt5YG95fb2QNy1Gs--1-oLD3znqPNQw

Please work with your legal team (if using the corporate CLA) or sign the individual CLA now and send them to me to avoid any delays in your development work flow when the transfer occurs.

Could you please elaborate, why CLAs are needed? The Linux Kernel is under the umbrella of the Linux Foundation, and no CLAs are needed there. CLAs are a great burden, as the legal department gets involved, and should be avoided at all costs, as contributors want to advance OpenBMC and not do paperwork.

Kind regards,

Paul

#2 lore raw

Re: contributor license agreement (CLA) (was: Upcoming project ownership changes)

Quoted 14 lines · Paul Menzel

Am 14.02.2018 um 04:53 schrieb Brad Bishop:

Quoted 12 lines

Under the new charter, contributors will be required to sign a contributor license agreement. There will be corporate (your company
signs once for all future contributions originating from your company)
and individual agreements available:

https://docs.google.com/document/d/1veiAjszrhgabA8XrJWjYCs7lyXIhs5r
cXWgaeuW-bT8
https://docs.google.com/document/d/1m61YH8GSzQpYVt5YG95fb2QNy1Gs--1
-oLD3znqPNQw

Quoted 7 lines
Quoted 5 lines

Please work with your legal team (if using the corporate CLA) or sign
the individual CLA now and send them to me to avoid any delays in your
development work flow when the transfer occurs.

Could you please elaborate, why CLAs are needed?

I am not a lawyer but my understanding is that it protects the users of OpenBMC from a contribution to the project by a contributor that did not have the necessary grants to make the submission in the first place. I found this page to provide a good layman's overview of the
benefits: http://oss-watch.ac.uk/resources/cla

Quoted 4 lines

The Linux Kernel is
under the umbrella of the Linux Foundation, and no CLAs are needed there. CLAs are a great burden, as the legal department gets involved,

There are successful Linux Foundation projects that do have CLAs. While I can't argue that signing doesn't add any delays, use of the corporate CLA will minimize this effort to a one-time-only cost and lower the risk associated with using the project for our users.

Quoted 10 lines

and should be avoided at all costs, as contributors want to advance OpenBMC and not do paperwork.

Kind regards,

Paul

#3 lore raw

Re: contributor license agreement (CLA)

Dear Brad,

Thank you for your response.

Quoted 7 lines · Brad Bishop
Quoted 6 lines · Paul Menzel

Am 14.02.2018 um 04:53 schrieb Brad Bishop:

Quoted 4 lines

Under the new charter, contributors will be required to sign a contributor license agreement. There will be corporate (your company signs once for all future contributions originating from your company) and individual agreements available:

https://docs.google.com/document/d/1veiAjszrhgabA8XrJWjYCs7lyXIhs5rcXWgaeuW-bT8 >>>

https://docs.google.com/document/d/1m61YH8GSzQpYVt5YG95fb2QNy1Gs--1-oLD3znqPNQw

Quoted 11 lines
Quoted 5 lines
Quoted 3 lines

Please work with your legal team (if using the corporate CLA) or sign the individual CLA now and send them to me to avoid any delays in your development work flow when the transfer occurs.

Could you please elaborate, why CLAs are needed?

I am not a lawyer but my understanding is that it protects the users of OpenBMC from a contribution to the project by a contributor that did not have the necessary grants to make the submission in the first place. I found this page to provide a good layman's overview of the benefits: http://oss-watch.ac.uk/resources/cla

Thank you for the URL, but, unfortunately, it doesn’t answer the question what the advantage over the Linux kernel [1] procedure is.

Quoted 8 lines
Quoted 3 lines

The Linux Kernel is under the umbrella of the Linux Foundation, and no CLAs are needed there. CLAs are a great burden, as the legal department gets involved,

There are successful Linux Foundation projects that do have CLAs. While I can't argue that signing doesn't add any delays, use of the corporate CLA will minimize this effort to a one-time-only cost and lower the risk associated with using the project for our users.

Quoted 2 lines

and should be avoided at all costs, as contributors want to advance OpenBMC and not do paperwork.

Brad, who decided, that CLA are a requirement? To my knowledge, CLAs are only needed, if you think about changing the license in the future. Besides that, there is *no* advantage, and the Linux Kernel procedure should be used. It just scares off people wanting to contribute small fixes and improvements.

Kind regards,

Paul

[1] https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer-s-certificate-of-origin

#4 lore raw

Re: contributor license agreement (CLA)

Quoted 4 lines · Paul Menzel

Dear Brad,

Thank you for your response.

No problem!

Quoted 10 lines
Quoted 7 lines

I am not a lawyer but my understanding is that it protects the users
of OpenBMC from a contribution to the project by a contributor that did not have the necessary grants to make the submission in the first place. I found this page to provide a good layman's overview of the benefits: http://oss-watch.ac.uk/resources/cla

Thank you for the URL, but, unfortunately, it doesn’t answer the question what the advantage over the Linux kernel [1] procedure is.

From the article:

"The purpose of a CLA is to ensure that the guardian of a project’s outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen license."

Again I am not a lawyer but based on my limited understanding, I don't believe projects that only utilize a DCO (like Linux) can make these assurances to their users. This is the advantage - rather than deferring this risk to the users of the project, we provide software free of these concerns from the very start.

Quoted 7 lines

Brad, who decided, that CLA are a requirement? To my knowledge, CLAs are
only needed, if you think about changing the license in the future. Besides that, there is *no* advantage, and the Linux Kernel procedure
should be used.

I think the evidence suggests otherwise. There are many, many OSS projects out there - many highly successful, that require a CLA. Including Linux Foundation projects. If there were no advantage at all then this would not be the case.

Quoted 2 lines

It just scares off people wanting to contribute small fixes and improvements.

I concede the point, but as with any decision it is about cost/benefit
- the cost being the point you have raised here, the benefit being providing our users with software guaranteed to be free of any legal infringement.

#5 lore raw

Re: contributor license agreement (CLA) (was: Upcoming project ownership changes)

In reply to Paul Menzel
Quoted 30 lines · Paul Menzel

Dear Brad,

Am 14.02.2018 um 04:53 schrieb Brad Bishop:

[…]

Quoted 9 lines

I'm happy to report that these industry leaders have rallied around your community as the meeting point. Very soon it will get a lot more busy around here.

To this end, IBM will be ceding stewardship of this project to the Linux Foundation in the very near future. You can find the project charter here:

https://docs.google.com/document/d/1uBbi5rDhWqj8Al-eoNLxERZ9OK8KVMZThOuS08-cYto

(Note, the URL is wrapped in your message.)

Thank you. Cooperating is definitely a good thing. My knowledge of the goals and operation of the Linux Foundation is not good enough to comment on that.

Quoted 8 lines

Under the new charter, contributors will be required to sign a contributor license agreement. There will be corporate (your company signs once for all future contributions originating from your company) and individual agreements available:

https://docs.google.com/document/d/1veiAjszrhgabA8XrJWjYCs7lyXIhs5rcXWgaeuW-bT8
https://docs.google.com/document/d/1m61YH8GSzQpYVt5YG95fb2QNy1Gs--1-oLD3znqPNQw

Quoted 8 lines
Quoted 3 lines

Please work with your legal team (if using the corporate CLA) or sign the individual CLA now and send them to me to avoid any delays in your development work flow when the transfer occurs.

Could you please elaborate, why CLAs are needed? The Linux Kernel is under the umbrella of the Linux Foundation, and no CLAs are needed there. CLAs are a great burden, as the legal department gets involved, and should be avoided at all costs, as contributors want to advance OpenBMC and not do paperwork.

Interesting that this immediately is flagged as a point of contention. Here is a counterpoint from Bradley Kuhn:

https://sfconservancy.org/blog/2014/jun/09/do-not-need-cla/

For the record, I strongly oppose CLAs. However, I will submit this to our legal team for review.

I don't envy you having to have this same conversation over and over and over and over again over the coming years.

--
Michael