Florian Hockmann <f...@...>
The gRPC project will beta test the bot and then they want to make it accessible to other projects afterwards.
So, it sounds like we can use this automation in a few weeks / months :-)
Am Dienstag, 5. März 2019 14:12:21 UTC+1 schrieb Oleksandr Porunov: Asking to check CLAs for the next contributors:
- VladimirBogomolov - wangzheng90 On Tuesday, March 5, 2019 at 1:57:00 PM UTC+2, Oleksandr Porunov wrote: Thanks for pointing to this problem. I didn't think about CCLAs before. We need to investigate it. On Tuesday, March 5, 2019 at 12:56:53 PM UTC+2, Florian Hockmann wrote: I agree with you that the CLA process takes too long right now and scares away some possible contributors which is really problematic.
The only problem I see with these tools is that they all only seem to handle individual CLAs (ICLA), but not corporate CLAs (CCLA). Since most of our contributors use a CCLA, we also need to find a solution for that.
Out of the 3 tools you listed, I found two that had issues for CCLAs: Am Dienstag, 5. März 2019 10:43:30 UTC+1 schrieb Oleksandr Porunov: Florian, I believe we can move with 3rd party CLA bot now because there is no any news from LF.
There are contributors who would like to contribute, but CLA verification is taking too much time to accept new contributors. It really slows down the process because most of the time new contributors either don't want to go through the process where they need to print then sign then scan then send CLA or even when they do it they are losing interest after 1+ months of verification.
As for me, I think we should move to automate CLA signing ASAP. I think we can discuss a CLA bot for JanusGraph.
Some possible solutions could be either CLA automation tool like these tools:
Or signing with Google form like this one:
It would be nice to move to automate CLA signing on this or the next week.
On Friday, March 1, 2019 at 11:13:01 AM UTC+2, Oleksandr Porunov wrote: Jason, thank you for submitting the PR. Also reporting that wangzheng90 from github sent a CLA. Related PR-1456.
Misha, could you please add necessary permissions to Jason? On Friday, March 1, 2019 at 7:50:45 AM UTC+2, Jason Plurad wrote: 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: #1406Also, 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.
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:
Or maybe use some tool for CLA automation like this one:
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.
|
