DeveloperWiki:Community

From ArchWiki
Revision as of 14:58, 10 November 2008 by Louipc (Talk | contribs) (New page: Future policies for the community repository should be discussed to improve the usefulness of the repository and decrease the number of unused packages. =Ideas= ==Minimum Vote Requiremen...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Future policies for the community repository should be discussed to improve the usefulness of the repository and decrease the number of unused packages.

Ideas

Minimum Vote Requirement

  1. Votes are an indicator of package usage. They aren't an absolute indicator.
  2. There are almost three hundred packages in community with less than two votes.
  3. If a package has any significant usage a package should really have at least three votes.
  4. If users realise that votes do have more of an impact on community they may be encouraged vote.

Plan of Action

=First Stage

  1. Let users know that votes will be counted via mailing list and forum and packages with few votes will be moved to unsupported.
  2. Provide a deadline when packages will be moved so users can anticipate the change and vote if they need to.
  3. Move all packages with zero votes that are not dependencies of other non-zero vote packages.
  4. Move all packages with only one vote...
  5. And so on.

Maintenance

When adding a package a Trusted User should consider the number of votes that a package has. If the package has a low number of votes (less than 3) then it should not be included in community.

Community should be checked periodically to ensure that it does not contain packages with below the minimum number of votes.

Exceptions

Sometimes a package might be required in community because it is a dependency of a more popular package.