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

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

Being able to mark individual tests as flaky is really nice as we don't have to repeat the whole build job any more now! It also makes it easier to spot the flaky tests so we can inspect them to see

Awesome! Thanks Jason and Florian for getting this added.

Thank you Florian for integrating DCO and code analysis!

We now have Codacy activated for all repos in the JanusGraph organization. The dashboard for the main repo can be found here: https://app.codacy.com/project/JanusGraph/janusgraph/dashboard Codacy

Hi I added a feature to mark flaky tests in the commit https://github.com/JanusGraph/janusgraph/commit/adeaa980d736a0837a33ee33628e1eb7b70b50c1. How to mark test as flaky?

We now have the DCO bot activated. This pull request that was submitted today already contains a successful check. So, it looks like we don't have to manually check every commit manually any more to

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?

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

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

Next time I'll start such a VOTE, I will include an end date directly in the opening post, 72h like we do for releases should be enough usually. But yes, I think it's safe to say that the VOTE is

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

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

+1 thanks for taking the initiative on this, Chris. FWIW, I don't think this would require a vote at all. I think the project would encourage anybody, committer or otherwise, to help triage the queue.

I believe you can submit PR anyway. If any members have objections they can ask them here or in the PR.

+1 makes sense to me

Please ask these types of questions in jausgraph-users. If it turns out to be a bug, an issue can be opened. This group is for discussing development direction, not troubleshooting.

I've had to restart the solr 5 test twice today and most weeks I generally have to restart it at least once. we have +1's from 1 TSC member and 3 commiters. Do you all think I'm good to submit a PR

I have a query `g.V().has("USERID","userid","007").properties()`, but the properties and edges of vertex are all stored in table edgestore, so programs need to query edgestore and get every property