I'm not trying to add or take away from any of your points, but I'm confused about point #3.

and it's not even possible to advertise it within the structures you've provided

Why not? One of the initiatives was to "unlock" the listings page to the community. You should be able to freely update: docs/DOC-12922

and it should in turn show up on the listings page.

Gotcha, Here is my take on that... The page I linked above is editable, regardless of whether you complete the google form or not. I get that the document implies they want everything there, but like I said the document is editable. As a user, I'd rather have your ZenPacks linked form that page regardless of where they are.

I believe the only thing that "won't happen" without the google form submission is that your GitHub Repo (Which you are not using), wont get linked via their zenpacks submodules. Since there has been 0 updates on how that will benefit the community, I'd consider it to be a "who cares".

Quite honestly, there has been so little activity on any of those documents or processes, my vote would be to link to your packs regardless of their resting place. If Zenoss Inc sees that as a problem, the community can certainly find a place to host a simple table of links

I'm digging the zenpack --fetch. Having all the packs available in a 2.7 egg format is also Handy.

Simon the fact that a 2.7 egg is available for every pack is pretty huge. Is there any reason this has been more promoted throughout the ALPHA testing?

deptzel,

you seem to have found out somehow, wait... did Alan give away our little secret? We'll I suppose it's out now. Again, this shouldn't really be a surprise, since we've anounced this as a "futures" item during the original Github post. Anyway, it would be great if you guys could start to simply checking your ZenPacks into Github, then simply use the Google form to tell us about the checkin location. Thereafter we will add it to the community-submodule directory. Anything that is currently part of the community-submodule directory will be build as soon as any check-in occurs.

Alan,

I hope this is enough for now to rename the post to at least: "ZenPacks on Github might be a pretty cool?" (I am just kidding about the renaming part). We'll be attacking other areas of improvement soon as well.

Possibly tangential to the original issues, but if you had not learned elsewhere, Chet has put together an impressive automated test infrastructure for all  zenpacks to be authored by or blessed by Zenoss, which relies on their being acessible as Git submodules, presumably on GitHub itself.

Here's his G+ post under the Zenoss G+ account:on Improving ZenPack Quality.