Scope of elm-community?

The README [currently says](https://github.com/elm-community/Manifesto/blob/745ff071228b98626426f4e766af22f4c2c4983d/README.md) `elm-community` is for two purposes:

1. [Providing a home for widely used packages that are no longer maintained](https://github.com/elm-community/Manifesto/blob/745ff071228b98626426f4e766af22f4c2c4983d/README.md#package-maintenance)

> It sometimes happens that packages which are widely used need a bit of maintenance...Normally, package authors will deal with that themselves, of course, possibly with the help of pull requests from interested community members etc. However, sometimes package authors may not be available, for one reason or another, and other work can be blocked until the maintenance is performed...In those cases, elm-community can provide a home for a fork, and the necessary work to maintain the package.

2. [Community-Driven Documentation](https://github.com/elm-community/Manifesto/blob/745ff071228b98626426f4e766af22f4c2c4983d/README.md#community-driven-documentation)

> Elm has great documentation, but there is always room for more, and room for documentation oriented towards particular audiences...So, this can serve as a central point for that.

There have been discussions about whether the scope of `elm-community` should be different from this, and I'd like to centralize them here.

So:

1. Should the scope of `elm-community` be different from what the manifesto README currently states?
2. If so, what would be the pros and cons of that different scope?