Think this could be a little difficult, since Atmosphere should be the place for successful packages. In the case of meteor-desktop and redis-oplog, the Meteor Guide would be the place to be. At this point I’ve to agree that people who use such packages (like me) are responsible to extend the guide.
I agree. But here we also need a clear communication on MDG’s side. I don’t want invest time into something if I don’t know if it will still exists tomorrow. The best example is Blaze. About 6 months ago MDG announced that Blaze is still the way to go, just 2 months later it was removed from the core and given to the community. Now some people will say “It’s okay, the community will take control”, but on another view it is also “MDG don’t want invest money into dead things - so it is probably dead”. Then we had the MeteorPad discussion. The owner only said that MDG suddenly stopped paying bills - but we didn’t get any official statement from MDG. Just silence. That’s not the way how a company should handle it’s community. MDG needs to fix the communication issues first to get some trust back.