Call for maintainers

[mrtazz]

This is the followup to #649. The transfer is now done, but we still have an open call for maintainers. If you are genuinely interested in becoming a maintainer, start contributing now by e.g. commenting on issues, suggesting labels, testing PRs, writing PRs. This will help with becoming a maintainer as it

• Provides a history of contributing to the project.
• Gives you an idea of what is involved to be a maintainer, so you will know if it's something you actually are still interested in.

Then follow the steps in the maintainers doc.

[BlueHatbRit]

Thanks for getting the repo moved @mrtazz and co, I'll begin submitting and reviewing some PR's and issues.

[reconbot]

Hi @mrtazz and @BlueHatbRit Do you have a roadmap? I'd like to work on supporting node 12 and modernizing some of the code but you have many years of PRs to triage and I don't want to trample on any existing efforts.

[BlueHatbRit]

Hi @reconbot, there's no formal roadmap at the moment. I'm working on a bit of both in tandem when I get time. The best thing you could do to help out would be to pull down a few PR's and test them.

By all means submit PR's to help modernise the code as well if you like, if you could do them in small sections rather than huge PR's then that should make it easy to figure out which existing PR's might clash. We can then work to get them merged in orders that seem to make sense when we get to them.

Personally my first approach would be to start splitting up some of the util/helper/config based JS to make it more readable, document it, and split down the functions to make them easier to consume. Once that's done then I think it'd be easier to start biting off chunks of the main server file.

[pataquets]

@mrtazz et all: check out https://adoptoposs.org