Topics

New CLA tool for Cloud Foundry


Chris Clark
 
Edited

Hello all,
 
I am very pleased to announce that Cloud Foundry will be adopting a streamlined, more user-friendly system for CLAs. No more PDFs! We'll be adopting the new EasyCLA tool that the Linux Foundation has developed, and deprecating our long-serving, trusty dreddbot.
 
Migration date: Wednesday, October 2nd. We'll be migrating some repositories next week to test things out a bit, but this tool has already been successfully adopted by multiple large open source projects, so this is just an extra precaution. 
 
What does this mean for you: Probably nothing. If you're a contributor who is covered by an existing CLA, you will not have to resign, and you will likely never notice the difference. If you're a maintainer of a project, you should no longer see noticeable delays in pull requests being approved for new contributors. If you're a new contributor, you'll find a newer, streamlined process for signing a CLA and submitting your first pull request.  
 
CCLAs: We're migrating over all of the whitelisted orgs and employees covered by CCLAs, so this migration won't cause anyone to have to re-sign. If you are covered by a CCLA - the tool will ask (once) what company you are covered by.  At this point, click "CFF Migration", and it should confirm that you are in one of the whitelisted groups that we've moved over. 

We will be doing a bit of housecleaning with our CCLAs in the next few weeks to make sure everything is current, so I may be reaching out to various companies regarding this. The EasyCLA tool allows for CCLA signees to manage their designated employees by whitelisting a Github org (as most have already been doing with Cloud Foundry), or, if you prefer, by having a list of designated employees that you can access and change manually.  Once this process is complete, I'll let you all know.  After that
 
Want to learn more about the EasyCLA tool? Here's a short presentation.  Here's the source code, and associated docs.  
 
I would like to thank the LF for building us this seemingly excellent tool, and the dreddbot and its maintainers at the cf-toolsmiths team for years of faithful service.  
 
Please reach out with any concerns or questions you might have about the new tool, or the migration process!
 
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation


Evan Farrar <evanfarrar@...>
 

Woohoo! Good bye, Dredd!

On Fri, Sep 20, 2019 at 12:25 AM Chris Clark <cclark@...> wrote:
Hello all,

I am very pleased to announce that Cloud Foundry will be adopting a streamlined, more user-friendly system for CLAs. No more PDFs! We'll be adopting the new EasyCLA tool that the Linux Foundation has developed, and deprecating our long-serving, trusty dreddbot.

Migration date: Wednesday, October 2nd. We'll be migrating some repositories next week to test things out a bit, but this tool has already been successfully adopted by multiple large open source projects, so this is just an extra precaution. 

What does this mean for you: Probably nothing. If you're a contributor who is covered by an existing CLA, you will not have to resign, and you will likely never notice the difference. If you're a maintainer of a project, you should no longer see noticeable delays in pull requests being approved for new contributors. If you're a new contributor, you'll find a newer, streamlined process for signing a CLA and submitting your first pull request.  

CCLAs: We're migrating over all of the whitelisted orgs and employees covered by CCLAs, so this migration won't cause anyone to have to re-sign. However - we will be doing a bit of housecleaning with our CCLAs in the next few weeks to make sure everything is current, so I may be reaching out to various companies regarding this. The EasyCLA tool allows for CCLA signees to manage their designated employees by whitelisting a Github org (as most have already been doing with Cloud Foundry), or, if you prefer, by having a list of designated employees that you can access and change manually.  

Want to learn more about the EasyCLA tool? Here's a short presentation.  Here's the source code, and associated docs.  

I would like to thank the LF for building us this seemingly excellent tool, and the dreddbot and its maintainers at the cf-toolsmiths team for years of faithful service.  

Please reach out with any concerns or questions you might have about the new tool, or the migration process!

Chris Clark
Technical Operations Manager
Cloud Foundry Foundation


Abby Chau
 

Awesome news. Thank you!


On Fri, Sep 20, 2019 at 12:25 AM Chris Clark <cclark@...> wrote:
Hello all,

I am very pleased to announce that Cloud Foundry will be adopting a streamlined, more user-friendly system for CLAs. No more PDFs! We'll be adopting the new EasyCLA tool that the Linux Foundation has developed, and deprecating our long-serving, trusty dreddbot.

Migration date: Wednesday, October 2nd. We'll be migrating some repositories next week to test things out a bit, but this tool has already been successfully adopted by multiple large open source projects, so this is just an extra precaution. 

What does this mean for you: Probably nothing. If you're a contributor who is covered by an existing CLA, you will not have to resign, and you will likely never notice the difference. If you're a maintainer of a project, you should no longer see noticeable delays in pull requests being approved for new contributors. If you're a new contributor, you'll find a newer, streamlined process for signing a CLA and submitting your first pull request.  

CCLAs: We're migrating over all of the whitelisted orgs and employees covered by CCLAs, so this migration won't cause anyone to have to re-sign. However - we will be doing a bit of housecleaning with our CCLAs in the next few weeks to make sure everything is current, so I may be reaching out to various companies regarding this. The EasyCLA tool allows for CCLA signees to manage their designated employees by whitelisting a Github org (as most have already been doing with Cloud Foundry), or, if you prefer, by having a list of designated employees that you can access and change manually.  

Want to learn more about the EasyCLA tool? Here's a short presentation.  Here's the source code, and associated docs.  

I would like to thank the LF for building us this seemingly excellent tool, and the dreddbot and its maintainers at the cf-toolsmiths team for years of faithful service.  

Please reach out with any concerns or questions you might have about the new tool, or the migration process!

Chris Clark
Technical Operations Manager
Cloud Foundry Foundation


Eric Malm <emalm@...>
 

That's great news, Chris! Congratulations, and thanks for letting all of us know!

Best,
Eric


On Fri, Sep 20, 2019 at 12:25 AM Chris Clark <cclark@...> wrote:
Hello all,

I am very pleased to announce that Cloud Foundry will be adopting a streamlined, more user-friendly system for CLAs. No more PDFs! We'll be adopting the new EasyCLA tool that the Linux Foundation has developed, and deprecating our long-serving, trusty dreddbot.

Migration date: Wednesday, October 2nd. We'll be migrating some repositories next week to test things out a bit, but this tool has already been successfully adopted by multiple large open source projects, so this is just an extra precaution. 

What does this mean for you: Probably nothing. If you're a contributor who is covered by an existing CLA, you will not have to resign, and you will likely never notice the difference. If you're a maintainer of a project, you should no longer see noticeable delays in pull requests being approved for new contributors. If you're a new contributor, you'll find a newer, streamlined process for signing a CLA and submitting your first pull request.  

CCLAs: We're migrating over all of the whitelisted orgs and employees covered by CCLAs, so this migration won't cause anyone to have to re-sign. However - we will be doing a bit of housecleaning with our CCLAs in the next few weeks to make sure everything is current, so I may be reaching out to various companies regarding this. The EasyCLA tool allows for CCLA signees to manage their designated employees by whitelisting a Github org (as most have already been doing with Cloud Foundry), or, if you prefer, by having a list of designated employees that you can access and change manually.  

Want to learn more about the EasyCLA tool? Here's a short presentation.  Here's the source code, and associated docs.  

I would like to thank the LF for building us this seemingly excellent tool, and the dreddbot and its maintainers at the cf-toolsmiths team for years of faithful service.  

Please reach out with any concerns or questions you might have about the new tool, or the migration process!

Chris Clark
Technical Operations Manager
Cloud Foundry Foundation


Chris Clark
 

UPDATE: There will be a slight delay on the full migration - we're working out a couple kinks with the migration process, but should have things sorted out in the next week. We will, of course, keep you all updated when we're going to make the switch. In the meantime... long live Dreddbot!


On Fri, Sep 20, 2019 at 12:24 AM Chris Clark <cclark@...> wrote:
Hello all,

I am very pleased to announce that Cloud Foundry will be adopting a streamlined, more user-friendly system for CLAs. No more PDFs! We'll be adopting the new EasyCLA tool that the Linux Foundation has developed, and deprecating our long-serving, trusty dreddbot.

Migration date: Wednesday, October 2nd. We'll be migrating some repositories next week to test things out a bit, but this tool has already been successfully adopted by multiple large open source projects, so this is just an extra precaution. 

What does this mean for you: Probably nothing. If you're a contributor who is covered by an existing CLA, you will not have to resign, and you will likely never notice the difference. If you're a maintainer of a project, you should no longer see noticeable delays in pull requests being approved for new contributors. If you're a new contributor, you'll find a newer, streamlined process for signing a CLA and submitting your first pull request.  

CCLAs: We're migrating over all of the whitelisted orgs and employees covered by CCLAs, so this migration won't cause anyone to have to re-sign. However - we will be doing a bit of housecleaning with our CCLAs in the next few weeks to make sure everything is current, so I may be reaching out to various companies regarding this. The EasyCLA tool allows for CCLA signees to manage their designated employees by whitelisting a Github org (as most have already been doing with Cloud Foundry), or, if you prefer, by having a list of designated employees that you can access and change manually.  

Want to learn more about the EasyCLA tool? Here's a short presentation.  Here's the source code, and associated docs.  

I would like to thank the LF for building us this seemingly excellent tool, and the dreddbot and its maintainers at the cf-toolsmiths team for years of faithful service.  

Please reach out with any concerns or questions you might have about the new tool, or the migration process!

Chris Clark
Technical Operations Manager
Cloud Foundry Foundation


--
Chris Clark
Technical Operations Manager
Cloud Foundry Foundation


Chris Clark
 

CLA migration is complete, as of several minutes ago. 

EasyCLA is now set up on all public repositories in the cloudfoundry, cloudfoundry-incubator, and openservicebrokerapi orgs.
Dreddbot is disabled, and is scheduled for retirement in coming weeks.  

Please let me know have any questions or run into any issues with pull requests (chrisclark on CF Slack, christopherclark on GH)!
Less urgently, if you have any thoughts on the new CLA workflow goes, or if there's anything that could be more intuitive, I'd love to hear about that as well.




Chris Clark
 

Hi all,

I’ve got a few updates to the EasyCLA migration, now a few months behind us:

 We’ve removed the prompt to click on “CFF Migration” for previously whitelisted contributors. We’ll be deprecating this shortly, as it was intended as a temporary bridge to minimize disruption to contributors and avoid having covered committers and companies re-sign a CLA. At this point we assume the vast majority of active committers has already signed up with EasyCLA (anyone who has a commit since October has, and that's over 500 committers). Going forward, we’ll ask everyone else to sign a new CLA, which should only take a minute or two. 

Previously, the cloudfoundry and cloudfoundry-incubator GitHub orgs had been whitelisted. This should not have been the case. While the majority of these orgs’ members are covered by an existing CCLA or ICLA, membership in those orgs alone should not exempt committers from being covered by a CLA. Going forward, these orgs will not be whitelisted… so, if you’ve authorized EasyCLA with "CFF Migration" and your whitelisting was based on membership in one of these orgs alone, you may need to re-authorize EasyCLA and select your employer's CCLA, or sign an ICLA. Either way, this should just take a couple minutes.

Bots: If you have an issue with a CI (or any other) bot that makes commits (and therefore will trigger the CLA check), please open a ticket with LF IT (the EasyCLA app will prompt this in the GitHubPR), and they should be able to take care of this for you.

Please reach out to me, or LF IT, if you have any questions, issues, or feedback. Thank you again for your patience with all this!