The ideas are not new. I also had it some month ago ;)
There will be (from my point of view): * a global login system * ReactOS main page * compatibility database * packages manager database * new design * new underlaying system (main page generated html pages; all other pages based on a php script + mysql database) * a CMS (for the section mentioned above) for Devs and Admins to manage/control the ReactOS website * integrate the wiki, bugzilla and phpbb system (global login system and new site design) * maybe a online language translation tool for resource files * maybe skin support and personal start-page (only for registered users)
I will have enough time to code the package manager and the compatibility section. These sections are almost finished (on my local pc). And then if no one else do it, I can code the global login system and/or the html generation script (for the main/content pages).
I will have a lot of free time in july - oct. 2005
I made a alpha page with some features some months ago (the design is NOT the final one!): http://frik85.fr.funpic.de/packmgr/
I hope the UI-Team will finalize the Homepage Design soon, so I can start implement the new Design into my script(-system).
"Rick Langschultz wote:
I was wondering if you all would be interested in doing something like a portal system. I know that a content management system is important, and that will be a feature also, but I think a portal system for users, developers, and administrators can become quite a useful feature. I think another factor in getting ReactOS into mainstream computer useage would be a single-sign-on service much like microsoft's passport service or apple's .mac service, which may or may not be sso based I am not really sure. There should also me an MSDN like library for programmers that are currently unaware of programming protocol. There should also me a software compatibility library.
Just a few suggestions
1 - Utilize a portal system 2 - Supply users and developers with a application/drivercompatibility library
3 - Supply users, and developers with an online applicationfor programming help/collaboration.
4 - Utilize a content management system over the portal systemto allow the portal be updateable.
Those are a few of my suggestions.