Details on Mainteinance / Help ?

[neonsoftware]

Hi @graeme-hill,

First of all, thank you for the library. Really appreciating.

I would like to ask two questions regarding maintenance:

Time

In issue #52 I read

I still maintain this but not closely.

Would it be possible to have a more precise view on the aspects that define "closely" in the current moment ?

For example, in the scenario where none of us has, of course, the time to do everything that is needed for all subjects, which is aspect that for you is the hardest for allocate time for ?

ex.

• time to read, analyze, and process issues [y/n]
• time to inspect, analyze, review, and test PRs [y/n]
• time to adapt to the advancement of build tools [y/n]
• time to enhance the library [y/n]
• time for strategic decision-making [y/n]

As @jean has mentioned on some issues, there might be some staling PRs work since a while, one of the blocking.

Help

How could the community help the library ?

a) finding co-maintainers that share the whole work
b) finding co-maintainers that will perform some of the tasks above for you, and you will still direct, steer, and approve
c) choosing a drop-in fork, and making it official on the Readme
d) other ?

Thank you in advance, and wishing a great week-end