Roman Kyrylych wrote:
1) Unclarity about what our committment is to packages in various repos. We need some clear way for the dev team to commit to maintaining a package in the long term, and some way to easily identify and track packages identified thusly.
2) Gross numbers of orphans everywhere and no clear method to follow to proceed to eliminate them on an ongoing basis. (not saying your proposal doesn't address this.. but you asked for the problem list)
This is OK, but this:
2007/10/17, Paul Mattal <paul@mattal.com>:
Aaron Griffin wrote:
What's the first step? Create [mantle]. Vote packages into it by 50%+ vote of dev team. See what happens and what is left in [extra]. Auction any orphans off to other devs and/or TUs to put in community.
These would be the first few steps.
is absolutely bad as a first step. I don't understand how this can be a good first step to archieve all you wrote above.
These first steps are intended to achieve #1 and #2, by creating a repo in which devs clearly have committed to long-term care of the packages and by eliminating orphans and demonstrating how to keep them eliminated on an ongoing basis. - P