I think this is a cool idea, but like @efrancis said, there is the problem of ownership.
I see this coming into play perfectly in the veliovgroup maintained version of flow-router, where they chose to implement some of the data layer strategies from iron router. I’d say there would likely be a heated debate if there were multiple maintainers working on that project about including those features, and those debates take time and resources, that may be better spent on a personal fork.
Not to say there couldn’t be multiple, maintained forks of a repo like that, each with different goals. I do think there are at least a dozen or so packages in use by a lot of us that could benefit from more consistent updates, ones that come from different sources to help address different issues.
I’m as much a perpetrator of the developer’s optimism as the next, and would love to see something like this get traction, but I think the value proposition has to be very clear and understandable to get people on board.
