Another great job on this one, @azurecurve! These sound like a logical set of rules and I pretty much agree across the board. A few additional thoughts…
#5 Free/Fremium/Premium plugins are all welcome in the ClassicPress Plugin Directory, but must be identified as such by use of the appropriate tag. Software-as-a-Service must be categorised as a Premium plugin.
Even though I want to offer plugins under a model that most would consider freemium, I wouldn’t include it as a category. To avoid inconsistency in interpreting the infinite possibilities of what may constitute freemium, I think the line between free and premium should simply be black and white: if a plugin 100% works without any form of consideration, then it’s free. Otherwise, it’s premium. I believe users will quickly become accustomed to the idea that they can use the free features of a premium plugin without it being called freemium.
#11 Each time code is updated in the repository, the version number must be incremented. Frequent updates are not acceptable and will be seen as an attempt to game the search results; only release ready code should be committed.
The term frequent updates is subjective and needs definition. What constitutes frequent to one plugin shop may be an eternity to another. To prevent gaming, last updated date might be avoided for sorting purposes.
#17 Plugins should not hijack the ClassicPress admin dashboard with constant or overwhelming notifications and alerts; adverts are not permitted outside of the Plugin settings pages.
The phrase constant or overwhelming notifications and alerts is subjective and needs definition. The idea of plugins only printing notices on their own pages is something that seems long overdue. Big +1 on that!