> I think this is a good idea, even if only to keep me motivated I'll
> start.

Thanks for the update, Jude. It is appreciated.

I'll state from the outset this is entirely a suggestion. I think it may help
get outsiders involved, but the concepts are entirely subjective.


What I was really looking for though something like this:

1. The dev team creates a list of core packages that need to be in place for
Devuan to boot. Core packages need not include anything related to X at this
point, just what is needed to get to a terminal.

2. The dev team then posts a list of things needed to create an acceptable
Devuan build environment.

3. Dev team posts a list of packages that need work.

4. People on the list express interest in taking them on.

5. Once finished they send them back to the dev team for assessment. If they
decide things are good, then the package can be included in Devuan, otherwise
not. If you do enough good work, then perhaps you might be invited as a core
member someday.

6. Repeat step one, eventually with X, etc

The idea that I am trying to endorse here is to extend communication to the
wider community to speed work, without expanding the core dev team beyond
manageable proportions.

It might sound a bit like the core dev team is a bit of a dictatorship, but
personally I'd rather have a meritocracy rather than a democracy at this
point. Devuan needs people willing to actually do the needed work.