Use P*Nuke to create Product Download and Support Portal

This project is to use one of the popular open source or free CMS systems ( *nukes, *wikis) and adapt it for a Product Download and Support Portal. I am looking for a creative developer ??" use your own experience as software developers to extend the minimum feature requirements listed below. First preference is for LAMP (Linux/Apache/mySQL) based solutions, although you can make a case for a Java CMS or an ASP.NET based CMS also. Basically, our 40+ files (binaries, docs, app notes) organized by Product Groups need to be selectively made available to customers based on products they have purchased. * We should be able to upload files, and assign them to “Product Groups??. * We should be able to assign customers/portal users to Product Groups. A customer may belong to multiple groups * When a customer logs in to the CMS, based on the group permissions, various Product and Documentation modules get populated with only the files the customer has access to. * CMS User Groups/Categories can correspond to “Products Groups??. * Authentication: Authentication must be against stored passwords in the portal DB <!-- --> * * However, the portal must also support the use of an external LDAP server for authentication. We intend to move to LDAP to store customer and authentication data. * We should be able to create new customer accounts on the CMS using a single http GET from an external program. * Login and download usage statistics should be provided. * Users should be able to UPLOAD files (log files, debug logs in private areas) * When we post new releases or files to portal, customers should be notified. The portal should support mailing lists for this purpose. There is a strong desire to include the following modules found in CMS systems. * Web Forums per Product. * A Web Forum per customer viewable only by us and customer. * Live Chat <!-- --> * FAQ module, which will have FAQs per Product. * Search * RSS feeds. Desirable: Bug Tracking that shows bugs (from Bugzilla) CONTINUES BELOW ## Deliverables Just in case it matters to you, this is what we do now: We have a number of products that are distributed electronically along with related documents. Currently, we have an apache-based portal that used http authentication (.htaccess) to control access to files customers are allowed to access. In addition, there are couple of web forms customers can use to request license keys, and open support cases against the products. The site was created in Dreamweaver, and has other links that link this sub-site to our main site. * There are about 10 products, and they are supported on 3 OS platforms (Solaris/Linux, Windows) resulting in about 30 or so binaries. There are a similar number of associated PDF and TXT documents and application and release notes. Previous versions of binaries may also exist. <!-- --> * When customers or evaluators download binaries, in some cases they have to Accept a displayed end user license agreement before proceeding. <!-- --> * We currently create customer accounts by using a CGI script that creates appropriate .htaccess settings using htpasswd and puts people into groups. This script is also called as a “single hit?? from other sales lead generation programs where pre-sales data about customer has been captured. <!-- --> * The support cases are backed by an interface to [login to view URL], which is done simply by posting the form to an appropriate [login to view URL] link when a customer request support. The support then moves to email at the moment) <!-- --> * Apache logs are run every night to create a report of customer login and download activity. This all works, but is not very elegant and getting to be a pain to maintain. A. You will first deliver a set of deliverables that we can mutually agree on. 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Linux/Solaris Apache mySQL PHP/Perl/ASP/JSP/Servlets IE, Netscape