Maintainance of the project

[JohanMabille]

Hi,

I noticed the last release was in January 2024, and the project appears to have reduced activity over the past months. I co-maintain a stack containing projects that depend on json-schema-validator, and I was wondering if any help to keep this project going would be welcome?

[pboettch]

This, indeed, would be highly appreciated ;-).

How would you want to proceed? Which part would be the most important for you?

[JohanMabille]

Awesome!

I think our priorities would be (from highest to lowest):

• fix the CI and keep it "green" (at list for the tests, I'm not familiar with Fedora nightly builds)
• ensure compatibility with nlohmann_json releases
• review PRs fixing bugs and address bug issues

I also added myself as a maintainer of the conda package, it should help me to catch issues with new releases of nlohmann_json.

[pboettch]

Nice. Thanks for your proposal. Iactivated you as a maintainer for this project.

There are two things I'd like you to acknowledge:

1- I think it's common sense already, but I'd like to be sure: all changes have to go by PRs. No direct pushing on the main-branch.

2- I'd like development-decisions to be discussed and approved between at least both of us before being merged (unless it's a no-brainer). I haven't, for example, not yet made my mind up the amalgated-version and its PR #360.

[JohanMabille]

1 - Yes, that's the way I'm used to work on other repos.
2 - I totally agree, that's also how I'm used to work on other repos, although sometimes it might not be that visible because I can have in person discussions with the other maintainers.

We're definitely on the same line here.

[pboettch]

I see you accepted the collaboration invitation. Let's go. Looking forward to working together.