Hello Jason,

Thank you for the replay!

It definitely would be better if more people could handle incoming CLAs right now. 

I don't think that voting is appropriate in the current situation because too little JanusGraph members are involved right now. So, I believe you can give access to all PMC members without voting.

Also, I have some questions about automation.

Do you know where we should contact to ask to open a JanusGraph group for identity.linuxfoundation.org ?

I don't know the internal responsibility structure of JanusGraph. 

I have seen for some time that you were responsible for new releases of JanusGraph, so I assume that you owned nexus keys for deployment. So, my assumption that you have more rights in JanusGraph.

If so, my thoughts are that JanusGraph is under The Linux Foundation. It means that at least some support is provided. Right now we need to automate CLA signing (which isn't hard I think). I don't think that we will be rejected of using a little bit of The Linux Foundation functionality, but I think that someone responsible need to ask for this functionality from The Linux Foundation responsible party. Can you contact that responsible party? If no then can you share any contact where I can ask for?

Best regards,

Oleksandr

On Wednesday, February 13, 2019 at 9:37:33 PM UTC+2, Jason Plurad wrote:

+1 I agree that the CLA process needs to be improved.

Currently CLAs are submitted to the janusgraph-cla Google Group which is monitored by Misha and me. A representative from the Linux Foundation is also in the group to observe. The group archive provides the historical record of the signed CLA documents.

I have been a bit removed from the JanusGraph community over the past few months for personal issues, but as a community supported project, the absence of any particular members should not prevent the community from moving forward.

Some steps that I propose we take in the short term:
* All PMC members given access to the janusgraph-cla group so that any PMC member can handle incoming CLAs
* Update the Contributing documentation to help eliminate the common follow up questions around ICLA vs CCLA. This mostly consists of ensuring that an individual contributor has verified that their employer/university/organization is aware of the contributions and will not make any claims on the submitted contributions.

Long term, if we can take advantage of some of the Linux Foundation infrastructure to handle or automate this, that would be fantastic. JanusGraph was created as a "lightweight project", so the support the project has received from the LF has been minimal. My understanding is that the marquee projects (like Kubernetes, CNFC, ODPi) have more sponsor money involved, so they have access to nice things.

Thank you Oleksandr and Florian for starting up this thread. If anybody else is interested in helping to push this topic forward, please reply on this thread.

Thanks,
Jason


On Friday, February 8, 2019 at 12:49:52 PM UTC-5, Oleksandr Porunov wrote:

Florian,

I like the automation method you suggested. I would go for it.

Do you know who should we contact to setup it? I assume either Jason Plurad or Misha Brukman should have necessary rights?

On Friday, February 8, 2019 at 4:19:10 PM UTC+2, Florian Hockmann wrote:

Thanks for bringing this up, Oleksandr. I agree that it's important to make this process easier for contributors as each additional loop they have to jump through could prevent them from contributing to JanusGraph in the first place.

Apparently, Kubernetes has automated its CLA workflow. They are hosted within the Cloud Native Computing Foundation (CNCF) but it seems to use only infrastructure from the Linux Foundation and since the CNCF is also a Linux Foundation project, we should be able to use the same system in general.

They also have docs on how to set up the automation for a new repo. At first glance, it looks like we only need a JanusGraph group for identity.linuxfoundation.org.

While we're at it we could also automate the DCO check with a DCO bot. We currently have to check this manually while reviewing a PR which we tend to forget sometimes.

Am Freitag, 8. Februar 2019 08:16:31 UTC+1 schrieb Oleksandr Porunov:

Hello,

I have a concern about current CLA signing workflow. Currently we need to print a CLA agreement then fill it, then scan it then send it via email and then wait for an unknown amount of time while it is checked then wait while the PR with your signing details is merged into https://github.com/JanusGraph/legal.

It causes very huge delays sometimes more than 1 month. I think it is a big disadvantage for accepting new contributions.

I think we would be able to use either Google form for CLA accepting like this one:

https://docs.google.com/forms/d/e/1FAIpQLSeFFPXTvl4QJ0P-RQJQcRC8V-1JNfYUpGuq3WVmOmFkBN5nNA/viewform?formkey=dGNNVUJEMXF2dERTU0FXM3JjNVBQblE6MQ

Or maybe use some tool for CLA automation like this one:

https://github.com/cla-assistant/cla-assistant

There are a lot of CLA automation tools. I think we could use some.

Can we automate this process to digitally sign CLAs or we need real scanned paper copy?

+1 I agree that the CLA process needs to be improved.

Currently CLAs are submitted to the janusgraph-cla Google Group which is monitored by Misha and me. A representative from the Linux Foundation is also in the group to observe. The group archive provides the historical record of the signed CLA documents.

I have been a bit removed from the JanusGraph community over the past few months for personal issues, but as a community supported project, the absence of any particular members should not prevent the community from moving forward.

Some steps that I propose we take in the short term:
* All PMC members given access to the janusgraph-cla group so that any PMC member can handle incoming CLAs
* Update the Contributing documentation to help eliminate the common follow up questions around ICLA vs CCLA. This mostly consists of ensuring that an individual contributor has verified that their employer/university/organization is aware of the contributions and will not make any claims on the submitted contributions.

Long term, if we can take advantage of some of the Linux Foundation infrastructure to handle or automate this, that would be fantastic. JanusGraph was created as a "lightweight project", so the support the project has received from the LF has been minimal. My understanding is that the marquee projects (like Kubernetes, CNFC, ODPi) have more sponsor money involved, so they have access to nice things.

Thank you Oleksandr and Florian for starting up this thread. If anybody else is interested in helping to push this topic forward, please reply on this thread.

Thanks,
Jason


On Friday, February 8, 2019 at 12:49:52 PM UTC-5, Oleksandr Porunov wrote:

Florian,

I like the automation method you suggested. I would go for it.

Do you know who should we contact to setup it? I assume either Jason Plurad or Misha Brukman should have necessary rights?

On Friday, February 8, 2019 at 4:19:10 PM UTC+2, Florian Hockmann wrote:

Thanks for bringing this up, Oleksandr. I agree that it's important to make this process easier for contributors as each additional loop they have to jump through could prevent them from contributing to JanusGraph in the first place.

Apparently, Kubernetes has automated its CLA workflow. They are hosted within the Cloud Native Computing Foundation (CNCF) but it seems to use only infrastructure from the Linux Foundation and since the CNCF is also a Linux Foundation project, we should be able to use the same system in general.

They also have docs on how to set up the automation for a new repo. At first glance, it looks like we only need a JanusGraph group for identity.linuxfoundation.org.

While we're at it we could also automate the DCO check with a DCO bot. We currently have to check this manually while reviewing a PR which we tend to forget sometimes.

Am Freitag, 8. Februar 2019 08:16:31 UTC+1 schrieb Oleksandr Porunov:

Hello,

I have a concern about current CLA signing workflow. Currently we need to print a CLA agreement then fill it, then scan it then send it via email and then wait for an unknown amount of time while it is checked then wait while the PR with your signing details is merged into https://github.com/JanusGraph/legal.

It causes very huge delays sometimes more than 1 month. I think it is a big disadvantage for accepting new contributions.

I think we would be able to use either Google form for CLA accepting like this one:

https://docs.google.com/forms/d/e/1FAIpQLSeFFPXTvl4QJ0P-RQJQcRC8V-1JNfYUpGuq3WVmOmFkBN5nNA/viewform?formkey=dGNNVUJEMXF2dERTU0FXM3JjNVBQblE6MQ

Or maybe use some tool for CLA automation like this one:

https://github.com/cla-assistant/cla-assistant

There are a lot of CLA automation tools. I think we could use some.

Can we automate this process to digitally sign CLAs or we need real scanned paper copy?

Florian,

I like the automation method you suggested. I would go for it.

Do you know who should we contact to setup it? I assume either Jason Plurad or Misha Brukman should have necessary rights?

On Friday, February 8, 2019 at 4:19:10 PM UTC+2, Florian Hockmann wrote:

Thanks for bringing this up, Oleksandr. I agree that it's important to make this process easier for contributors as each additional loop they have to jump through could prevent them from contributing to JanusGraph in the first place.

Apparently, Kubernetes has automated its CLA workflow. They are hosted within the Cloud Native Computing Foundation (CNCF) but it seems to use only infrastructure from the Linux Foundation and since the CNCF is also a Linux Foundation project, we should be able to use the same system in general.

They also have docs on how to set up the automation for a new repo. At first glance, it looks like we only need a JanusGraph group for identity.linuxfoundation.org.

While we're at it we could also automate the DCO check with a DCO bot. We currently have to check this manually while reviewing a PR which we tend to forget sometimes.

Am Freitag, 8. Februar 2019 08:16:31 UTC+1 schrieb Oleksandr Porunov:

Hello,

I have a concern about current CLA signing workflow. Currently we need to print a CLA agreement then fill it, then scan it then send it via email and then wait for an unknown amount of time while it is checked then wait while the PR with your signing details is merged into https://github.com/JanusGraph/legal.

It causes very huge delays sometimes more than 1 month. I think it is a big disadvantage for accepting new contributions.

I think we would be able to use either Google form for CLA accepting like this one:

https://docs.google.com/forms/d/e/1FAIpQLSeFFPXTvl4QJ0P-RQJQcRC8V-1JNfYUpGuq3WVmOmFkBN5nNA/viewform?formkey=dGNNVUJEMXF2dERTU0FXM3JjNVBQblE6MQ

Or maybe use some tool for CLA automation like this one:

https://github.com/cla-assistant/cla-assistant

There are a lot of CLA automation tools. I think we could use some.

Can we automate this process to digitally sign CLAs or we need real scanned paper copy?

Thanks for bringing this up, Oleksandr. I agree that it's important to make this process easier for contributors as each additional loop they have to jump through could prevent them from contributing to JanusGraph in the first place.

Apparently, Kubernetes has automated its CLA workflow. They are hosted within the Cloud Native Computing Foundation (CNCF) but it seems to use only infrastructure from the Linux Foundation and since the CNCF is also a Linux Foundation project, we should be able to use the same system in general.

They also have docs on how to set up the automation for a new repo. At first glance, it looks like we only need a JanusGraph group for identity.linuxfoundation.org.

While we're at it we could also automate the DCO check with a DCO bot. We currently have to check this manually while reviewing a PR which we tend to forget sometimes.

Am Freitag, 8. Februar 2019 08:16:31 UTC+1 schrieb Oleksandr Porunov:

Hello,

I have a concern about current CLA signing workflow. Currently we need to print a CLA agreement then fill it, then scan it then send it via email and then wait for an unknown amount of time while it is checked then wait while the PR with your signing details is merged into https://github.com/JanusGraph/legal.

It causes very huge delays sometimes more than 1 month. I think it is a big disadvantage for accepting new contributions.

I think we would be able to use either Google form for CLA accepting like this one:

https://docs.google.com/forms/d/e/1FAIpQLSeFFPXTvl4QJ0P-RQJQcRC8V-1JNfYUpGuq3WVmOmFkBN5nNA/viewform?formkey=dGNNVUJEMXF2dERTU0FXM3JjNVBQblE6MQ

Or maybe use some tool for CLA automation like this one:

https://github.com/cla-assistant/cla-assistant

There are a lot of CLA automation tools. I think we could use some.

Can we automate this process to digitally sign CLAs or we need real scanned paper copy?

Hello,

I have a concern about current CLA signing workflow. Currently we need to print a CLA agreement then fill it, then scan it then send it via email and then wait for an unknown amount of time while it is checked then wait while the PR with your signing details is merged into https://github.com/JanusGraph/legal.

It causes very huge delays sometimes more than 1 month. I think it is a big disadvantage for accepting new contributions.

I think we would be able to use either Google form for CLA accepting like this one:

https://docs.google.com/forms/d/e/1FAIpQLSeFFPXTvl4QJ0P-RQJQcRC8V-1JNfYUpGuq3WVmOmFkBN5nNA/viewform?formkey=dGNNVUJEMXF2dERTU0FXM3JjNVBQblE6MQ

Or maybe use some tool for CLA automation like this one:

https://github.com/cla-assistant/cla-assistant

There are a lot of CLA automation tools. I think we could use some.

Can we automate this process to digitally sign CLAs or we need real scanned paper copy?