I've submitted a PR for the ICLA.

Regarding adding other committers to the CLA Google Group, it doesn't appear that I have authority to do that, only Misha.

I've noticed that I can't see the CLA archive via the Google Group. I do have a record of every email I've received since being added to the group (April 2018), so I have access to only a partial archive.

On Thursday, February 28, 2019 at 4:05:36 AM UTC-5, Oleksandr Porunov wrote:

I agree. If there is no response, we should go with 3rd party CLA bot.

On Thursday, February 28, 2019 at 10:15:28 AM UTC+2, Florian Hockmann wrote:

Also, is there any news from The Linux Foundation?

From my side, no. The Linux Foundation directed me to two members of the Kubernetes community who I contacted, but haven't heard back from them.

@Misha: Were you more successful?

If we don't hear anything from the LF any time soon, then I suggest that we just go ahead with a 3rd party CLA bot like you (Oleksandr) originally suggested in the first post here.

Am Donnerstag, 28. Februar 2019 00:31:28 UTC+1 schrieb Oleksandr Porunov:

I've noticed that it is already about 1 month has gone when `mad` from github send a CLA. Is there any news about including him into janusgraph/legal? Next PRs are stuck because of this:

#1392

#1406

Also, is there any news from The Linux Foundation?

On Thursday, February 14, 2019 at 6:54:02 PM UTC+2, Misha Brukman wrote:

I've reached out to The Linux Foundation folks I've previously spoken to about CLA automation (which wasn't implemented yet, as you can tell, and I haven't heard back from for a while). I believe they already have a GitHub bot we can reuse. I'll let you know what I find out.

On Fri, Feb 8, 2019 at 9:19 AM Florian Hockmann <f...@...> 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?

--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To post to this group, send email to jan...@....
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/d40dbef3-8d4f-474b-9125-e301b37e563b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.