Stuff that we want to change for Website Version 2
- === Old stuff ===
- Forums
- Gateway to email
- Can that be done without breaking mail behaviour, i.e. References and Encoding?
Discussion platform -> mailinglists, also reflected through newsgroups with some webinterface Newsportal comes to mind. (DanielDeKok)
- If a Wiki-based website approach is chosen, it should be fairly easy to write a NNTP
extension for MoinMoin with nntplib. (DanielDeKok)
- More active moderators and contributors?
- Problem: People who can help are normally allergic to web forums. At least I am.
- potential candidates:
- phorum
- fudForum
- Gateway to email
- FAQ's should we transition the FAQ's into the wiki to make it easier for more people to get involved?
- FAQ and current HOWTOs in the wiki. Documentation (like the CentOS Docs from PNAELV) should live somewhere else?
- Announcement system that can syndicate the metadata from Updates repositories to always be current
Extract that info from RepoView (if possible)?
- Wasn't there something in yum which was able to export rss?
- Set up RSS for that and "reimport" that RSS into the website (with rawdog or planet)?
- === End Old Stuff ===
Requirements
- Multilingual / International support
- account migration
- ability to migrate all the content from the existing website, including comments and notes
- integrated auth system (single user for site and forums)
- Spam prevention / Security methods (mod_security, selinux for all apps at a minimum)
- Ad capabilities for google and folks purchasing links.
- ???
People Required
- Website Designer, Graphics Guy/Gal ( we may already have access to a design company )
Potential Systems / Frameworks that can be used
- A newer version of Xoops ?
- Typo3 ?
Maybe use the wiki for the complete website? Fedora does it and it seems to work - also MoinMoin powered.
- Mambo or Joomla
Possibly SMF for the forum software. They offer a multitude of migration tools.
- Is seperating the forums into a forums.centos.org an option ? We can still use single signup, and a single db behind it, but moving it to its own domain might mean we dont need to integrate it that much into the website framework
