Hi all, Florian told me about http://test.libreoffice.org/
I've seen http://test.libreoffice.org/download/ and I would like to help to put that page in the best possible shape to minimize maintenance, execution, and usage costs. Why: - The higher the maintenance costs, the more bugs the page and the site are going to accumulate. - The higher the server-side execution cost, the less people will be able to download LibreOffice on indicated dates such as release dates. - The higher the usage cost, the less people will be able to get the actual software. To achieve that particular goals I think we need, at least, these metrics: - For execution cost: A log and a distribution of execution times - For usage cost: - - The download conversion rate (downloads / visits) per each page presentation. - - A log and an aggregation of user agents. Because the page presentation will depend on it. So my first question would be: how could we get some of all of these metrics? Also, I made a JavaScript function for system detection. It could be used for the current version of http://test.libreoffice.org/download/ with minor changes on the latter. It is available at http://vipinnova.com/libreoffice/download/package-negotiation.js and demoed at http://vipinnova.com/libreoffice/download/client-test.html I've seen http://wiki.documentfoundation.org/User:StefanW/Download_Selection ; StefanW please let me know how can I help you to integrate this function into your code, or to solve any other challenge you have with that page both on the client or the server side. I look forward to help the team to specify, design, and implement this page. Please let me know which is the best way to do it. Regards. -- "Make sure that Office documents very well depends on PROPRIETARY IE capabilities." Bill Gates, 1998. -- Unsubscribe instructions: E-mail to [email protected] List archive: http://www.libreoffice.org/lists/website/ *** All posts to this list are publicly archived for eternity ***
