4 ms·

I understand your position. But it hurts me a bit to see all of the hard work we put into replacing the Apache style CLA with the FPCA and our messaging around

I understand your position. But it hurts me a bit to see all of the hard work we put into replacing the Apache style CLA with the FPCA and our messaging around it to make sure we explain it in transparent ways being reduced to "doesn't really matter, it's still just a CLA if you're not an expert" :(

sytse 9y ago
Mmm, I'm sorry to hear that. I agree that between CLA's there can be vast differences in the terms. We did not intent to detail those differences in our blog post. BTW Have you considered changing it to a DCO?
- richardfontana 9y ago
  I've casually suggested this to some people involved in Fedora. FWIW I think it would be a good idea, and I think at this point the retention of the FPCA by Fedora is mostly a matter of inertia. But I share jwildeboer's sentiment, having been directly involved in the drafting of the FPCA to replace the old Fedora CLA. If one looks at the FPCA in historical context, it may be clearer that it is intended as an "un-CLA". One could argue that the DCO is a type of CLA. I know some people who call the DCO a contributor agreement, at least, and if it is a contributor agreement, it is one that refers to licensing of what's being contributed. Anyway, kudos to Gitlab for switching to the DCO!
  - sytse 9y ago
    Thanks! I've tried to make an update to the rationale document https://www.dropbox.com/s/xklo7gqca1k9jcn/Screenshot%202017-11-15%2011.49.49.png?dl=0 https://www.dropbox.com/s/xklo7gqca1k9jcn/Screenshot%202017-...
    - jhurewitz 9y ago
      It has been updated.
jhurewitz 9y ago
I would like to personally apologize. No offense was ever intended. Looking into what the industry was doing was not a determining factor when we decided to move to the DCO. I personally can appreciate the amount of work it takes to make changes to licensing terms. It is a difficult task to try to create terms that will please your users. As I am sure you have experienced, you will never be able to please everyone, there will always be nay-sayers and opponents. However, if you have any interest in moving to DCO, I would be happy to talk to anyone interested in talking about our analysis and process.

sytse 9y ago

Mmm, I'm sorry to hear that. I agree that between CLA's there can be vast differences in the terms. We did not intent to detail those differences in our blog post. BTW Have you considered changing it to a DCO?

richardfontana 9y ago
I've casually suggested this to some people involved in Fedora. FWIW I think it would be a good idea, and I think at this point the retention of the FPCA by Fedora is mostly a matter of inertia. But I share jwildeboer's sentiment, having been directly involved in the drafting of the FPCA to replace the old Fedora CLA. If one looks at the FPCA in historical context, it may be clearer that it is intended as an "un-CLA". One could argue that the DCO is a type of CLA. I know some people who call the DCO a contributor agreement, at least, and if it is a contributor agreement, it is one that refers to licensing of what's being contributed. Anyway, kudos to Gitlab for switching to the DCO!
- sytse 9y ago
  Thanks! I've tried to make an update to the rationale document https://www.dropbox.com/s/xklo7gqca1k9jcn/Screenshot%202017-11-15%2011.49.49.png?dl=0 https://www.dropbox.com/s/xklo7gqca1k9jcn/Screenshot%202017-...
  - jhurewitz 9y ago
    It has been updated.

jhurewitz 9y ago

I would like to personally apologize. No offense was ever intended. Looking into what the industry was doing was not a determining factor when we decided to move to the DCO. I personally can appreciate the amount of work it takes to make changes to licensing terms. It is a difficult task to try to create terms that will please your users. As I am sure you have experienced, you will never be able to please everyone, there will always be nay-sayers and opponents. However, if you have any interest in moving to DCO, I would be happy to talk to anyone interested in talking about our analysis and process.