**I'm hoping this post makes its way to someone at Zenoss Inc. who can supply some feedback**

ZenPacks are now on Github for a while, and for the most part I think this has been a postive experience, however there is one part that is concerning me. The new workflow allows someone to create a new public repo under there own account. They are the sole owner of said repo. They then let Zenoss Inc know and they link the submodules to this new repo. This also works pretty well.

However.... If the original owner decides they no longer have interest, time, whatever that repo can't be updated, new egg files can be link in the download section. So I'm sure your immediate answer is "Just Fork It" Sure... but then how do tell Zenoss Inc "This is the new location, and to please update the submodule reference". Your now left with two versions (or more if the forker also loses interest) of the same pack leading to lots of copies of the same exact exact thing.

I'm wondering if it makes sense to create (or leverage an existing) organization. For the sake of the discussion lets call the organization "ZenPackContributors". From there every community provided pack goes here. A "team" is created per repo/zenpack and the original author is added to the team with full access to that repo only (I'm a little unclear on if this is possible, but the github docs on orgs seems to imply it is).

In addition to the author and teams, a set of folks will be owners of this organization (perhaps zenoss and ZCA). This provides ample resources should the original author wish to discontinue contributions, to ensure someone still has access to update etc.

I believe Zenoss Inc. could still use the submodule approach they are using today, but rather than linking to individuals github repos they would link to the ones kept in the "ZenPackContributors" organization.