Noah

> I don't think elm-community should grow in scope. If a package is maintained by an individual, that's an indicator of ownership. It can also be an indicator of quality...

Documentation about a recommended repo isn't going to go anywhere. It will end before it starts.

> Recommended packages will change over time as people innovate, which makes me conclude that the elm-community organization can't be a long-term "one-stop shop for recommended packages" - shuffling repositories...

Agree with mgold and av, these are also my thoughts. In my mind, these _also_ include popular packages that need further direction. When I referred to mentoring on the Slack...

@Skinney, fyi, your post has disappeared. I know Github had issues earlier, so

@BrianHicks I deleted your post- Robin may have deleted it intentionally, so let's wait for them to reply before posting it (so as not to mis-represent anything)

FWIW: I've rewritten large chunks of the readme in the past, but there are some sections that are still from the infancy and old days of elm-community. It needs updating...

@prikhi, this explains the role of the assigned maintainer: https://github.com/elm-community/manifesto#the-role-of-a-maintainer Generally, it is up to them to merge PRs. The exception is when they have not replied in several days...

@prikhi Please open a new issue with those thoughts, it is a bit off topic for this issue.

In the case of lazy-list, I think we will update it to be the pure-Elm version that I created, as it's required for elm-test, and it performs better anyway. A...