Please add more maintainers

[fluffy-critter]

There's a lot of pending changes that really should be merged in, and this project is starting to feel abandoned, when a lot of people are very enthusiastic about improving it. It would be really nice, therefore, if some more people could be appointed maintainers/admins of the repository. @ix5 has done some amazing work in reviewing PRs, and as such I'd like to nominate them.

[ix5]

Thank you for your kind words! I'd certainly be up for trimming the bug tracker a bit and merging trivial fixes.
Larger architectural discussions and uploading to pypi is something I'd leave with the current maintainers though.

@jelmer and @blatinier have done a stellar job so far, but it seems they (rightfully so!) value their private lives, which necessitates a few more maintainers.

For the record, these PRs are great in my eyes, some fix urgent pain points and should be almost ready to merge:

• Handle browsers with no navigator.language better (#521) #674 - Minior, but useful
• Feature: add webhook notification capability #724 - Useful addition that does not break anything
• Build JavaScript files during python package build #697 - Pain point: Missing (minified) javascript files, leading to frustrated new users
• Require an edit cookie to be able to view a comment to be edited. #683 - Fixes a potential scraping "leak"
• admin: restore comment content after cancel edit #470 - Fixes an annoyance in the admin interface that could lead people to think there's data loss

These require some type of decision since they break current behaviour but are still important:

• Have client read out shared settings from server #311 - Pain point: client & server out of sync, creating confusion

These are nice efforts but will probably never be merged:

• Notify syscall 180709 #457 - Unclear benefit
• WIP: Users #261 - Outdated, would require massive rebase
• refactorization and SQLAlchemy #108 - ditto

[ix5]

I'd nominate @Guts, @stefangehn who I think have made some important upkeep contributions.
And maybe @BookGin if they want to help automate a bit of the deployment/CI process.

[jelmer]

I'm in favour of adding more maintainers in general.

That said, time is not really the issue that has prevented me from merging PRs. The testing situation for isso isn't great - there are a handful of tests, and mostly for Python. Every PR (and you can find several examples of this happening) risks breaking isso for the majority of users that doesn't use the feature.

[ix5]

The creator of isso, posativ, has added me as a maintainer. We have also been in contact about trying to open up and modernize some of the development practices and opportunities for community engagement.

We'll be looking into using GitHub Discussions for support requests to keep the issue tracker on a manageable level (which we've managed to cut down to ~120 from over 160 open issues).

[fluffy-critter]

That's great news! I think that resolves this issue then. :)