"Feature maintainers" groups to collaboratively manage IS

[rishabhshuklax]

Similar to the one discussed in publiclab/plots2#6501 we should have maintainers groups in IS to collaboratively manage different features of IS this would help in maintaining the library more efficiently, Features around which we can develop a team around includes:

• core-maintainers:
  GOALS: Stability and optimization of the core library.
  CURRENT PRIORITIES: Fix deprecated libraries. eg: readPixels and savePixels are actually not maintained and in fact, do not work at all for GIFs.

• module-maintainers:
  GOALS: Increasing the number of modules, stability/optimization of existing modules. Ensuring that creating new modules remains easy and accessible and well documented. Developing and maintaining compelling use-cases for IS, as in database/gallery of important/cool sequences #1480.
  CURRENT PRIORITIES: Increasing module GIF support and fixing bugs.

• ui-maintainers
  GOALS: Stability and performance.
  CURRENT PRIORITIES: Fixing UI bugs and perhaps refactoring some of the old, unmanageable code.

• tests-maintainers:
  GOALS: Increasing test coverage.
  CURRENT PRIORITIES: Increasing UI test coverage. Module and GIF tests are messy and decoupled, this needs to change as these tests are breaking unexpectedly.

• cli-maintainers:
  GOALS: maintain existing features and expand test suite.
  CURRENT PRIORITIES: completing initial CLI test suite and covering all basic usages

What do you guys think?

@publiclab/is-reviewers @publiclab/support @publiclab/mentors

cc: @jywarren

[harshkhandeparkar]

This is an awesome idea.

[jywarren]

Agreed!

[harshkhandeparkar]

@jywarren there are many cooked bug fix PRs which have not been merged. And you are very busy I see. Can I get temporary merge permissions to continue with the bug fix event?

[jywarren]

Hi @harshkhandeparkar it has been really tough to keep up. Do we have a prioriy or urgent label you can highlight them to me on? And, you can always bump them up to me in https://gitter.im/publiclab/publiclab -- thank you so much! Hope everyone is safe and doing well. ❤️

[harshkhandeparkar]

I think almost all PRs are outdated and inactive at this point 😅.

[jywarren]

Hi @harshkhandeparkar after #1668 perhaps we can get ahead of this again now! It dramatically simplifies the review process. Thank you and hope you're well!

[jywarren]

though, noting #1681 as well...

Update: fixed!! 🎉

[harshkhandeparkar]

It works really well!

[jywarren]

Thanks for all the reviews and issue cleanup!

[jywarren]

Ah, thought of a new one -- cli-maintainers -- pending the CLI tests in #1694

[jywarren]

Can folks volunteer for a specific one and we can start creating the CODEOWNERS listing? Thank you all!!!

[rishabhshuklax]

I could help out in maintaining modules and core functionalities, while working on #1564 I had to go through a lot of code related to these