What happens when a Camunda(github) project has no more people to keep?

Hi all,
I’m using the Camunda BPM GraphQL, but the project is very out of date. I made 2 pull requests, updating the project, improving the test structure and adding new queries, but the list of pull request have more pull request waiting since 2018.

The current version, in the Maven repository, don’t work with Spring Boot, because the artifact it’s a war file :frowning:

Without people to approve the pull requests can this project be considered dead?

Hi There @Marcelo_Maico

We do actually have some procedures in place for trying to avoid a situation where a community plugin loses it’s maintainer, i’m not sure what’s happening with the GraphQL plugin at the moment maybe @kiran.oliver (our expert on these matters) will have more details.

Hi there @Marcelo_Maico! I would be happy to review and merge your open PRs. I have assigned myself as a reviewer to them. I noticed you haven’t signed the CLA yet. If you would be so kind as to do that, I can review the PRs ASAP, get them merged, and cut a new release with your contributions in it. :slight_smile:

As for your question, currently, this extension is marked as abandoned and is in need of a maintainer. We encourage interested community members to become maintainers of abandoned extensions if they are interested. If that’s not something that appeals to you, but you’d like to get your PRs looked at in the meantime, please feel free to assign me as a reviewer and I will do my best to look them over!

Thank you so much for these great additions to this extension!

1 Like

Hi there @kiran.oliver. Where do I sign the CLA?
I would be happy to keep this project. I want to make it Spring Boot focused and
create the funcionality that exists today in the Rest API for the GraphQL API.

Thank you so much.


Hi @Marcelo_Maico! You can sign the CLA on GitHub.

Change version graphql11 by mmaico · Pull Request #45 · camunda-community-hub/camunda-bpm-graphql · GitHub is the first CLA to sign on issue #45.

Refactory tests and adding historic queries by mmaico · Pull Request #46 · camunda-community-hub/camunda-bpm-graphql · GitHub is the second, on issue #46. I noticed this issue has two GitHub IDs attached to it, which means that one of your commits was signed with a different GitHub ID than the one referenced in #45. You may want to update the commits to reference one GitHub ID, or you can sign with both. Whichever you prefer.

:x: Marcelo Maico
:x: mmaico

Once you’ve sign the CLA, you can click, ‘Recheck’ on the CLA bot comment and it should re-run that test so I can then review and merge your PRs.

It’s fantastic to hear that you’re interested in maintaining this extension and bringing it up to date! :slight_smile: Thank you so much for your dedication and contributions to Camunda and to this GraphQL extension, we truly appreciate it. Once we get these PRs merged I’ll make an OWNERS file that will list you as the project’s new maintainer.

I made the changes. Thanks @kiran.oliver.

1 Like

Fantastic, thanks so much @Marcelo_Maico! I have sent you an invite to join the Camunda Community Hub GitHub Organization. If you could accept it at your earliest convenience, that would be amazing! :slight_smile:

1 Like