From ArchWiki

markc 00:42, 26 October 2007 (EDT): I'm not confident enough to edit the main page but some of my thoughts are:

• why couldn't all or most of the suggestions made on the article page be implemented into the current codebase while a total redesign is under way ?
• is the current PHP code publically available somewhere ?
• related to above, why couldn't AUR1/2, and other main site code, be available as Arch packages ? (if some users could use the codebase for personal/business needs then maybe there could be more feedback and patches available for AUR1, and AUR2 when it's ready)
• regarding an XML-RPC api, why not use a REST-like interface right now using an extra argument like ?format=text to provide a plain text listing(s) which would be simple to implement. It could lead to ?format=rss|atom with (x)html being the default.
• why couldn't the AUR interface cover ALL packages (core, testing, community etc) ?
• add a section that accepts some form fields and provides an initial new PGKBUILD template ready for tweaking, and/or something like the WC3 HTML and CSS validation interface
• provide a forum, separate from the current ones, for each package (auto created)
• perhaps merge with the PunBB forum code so comments could be more sophisticated and/or package research and information become intergrated with the general forums
• consider making each package belong to a team/group with the initial uploader being the team leader, if others join then they can more easily and readily help maintain a package (helping to prevent orphaned packages)
• in general, perhaps consider that a package "owns" it's team members rather than a dev owning the package (this is moving beyond AUR into general package policy)