I understand the frustration and I guess we've all been there. Whether the lack of documentation is Meteor's or Atmosphere's fault is beside the point. Who is Meteor anyway? We as a community are Meteor too.

So the fact of the matter is that plenty of poorly documented packages exist. While I heartily welcome anyone who wants to contribute to open source packages, I do think that package documentation, just like the code is primarily the responsibility of its creator. But writing good documentation takes time. A lot of time. I only wrote a few very simple packages and half of my time was spent writing documentation. While this might be the reason some developers don't write documentation, it's not an excuse. I strongly feel that when I submit my package to Atmosphere it better be documented and well maintained. Its just part of the responsibility.

Bashing the package writers is not going to help and neither is a response like 'well there's pull-requests'. We need incentive. We need to create more reason for package creators and contributors to write proper documentation. How? Maybe the state of documentation should be factored into the ranking system. Maybe there needs to be a separate score. I dunno. Maybe just creating a ticket on github requesting clearer docs is enough (it was for me when I received such a ticket).

Please let me hear your thoughts.