Difference between revisions of "Extensions/website-todo"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 1: Line 1:
 
<h1>The "Official" TODO list</h1>
 
<h1>The "Official" TODO list</h1>
 +
The link for the alpha website is: http://www.cusoo.org/extensions/ooo-ext-website/<br />
 
Please note that everything on this page is subject to revision, and may be lacking in many regards.
 
Please note that everything on this page is subject to revision, and may be lacking in many regards.
 
<h3>For Milestone 1: Alpha</h3> Ready for alpha review. All/Most fundamental functions should now be workable, although may be a little hacked and contrived. The user interface in many instances will be incomplete.
 
<h3>For Milestone 1: Alpha</h3> Ready for alpha review. All/Most fundamental functions should now be workable, although may be a little hacked and contrived. The user interface in many instances will be incomplete.

Revision as of 11:48, 9 January 2007

The "Official" TODO list

The link for the alpha website is: http://www.cusoo.org/extensions/ooo-ext-website/
Please note that everything on this page is subject to revision, and may be lacking in many regards.

For Milestone 1: Alpha

Ready for alpha review. All/Most fundamental functions should now be workable, although may be a little hacked and contrived. The user interface in many instances will be incomplete.
  • 100% - Design database layout.
  • 100% - Create dynamic listing of available extensions.
  • 100% - Allow user login <Note - Profiles not included in this entry>
  • 100% - Allow users to upload/delete/modify their extensions <NOTE: Deferring addition/removal of image previews and modification of actual extension package until next milestone>
  • 80% - Graphical administration of site < As much as is going to be done in this milestone is done>
  • 25% - Graphical install/configuration of site < As much as is going to be done in this milestone is done - more is unnecessary for an alpha review - and may never be needed >
  • 0% - Register as a new user - only login/password/email for a first shoot

For Milestone 2: Alpha 2

Fundamental functions should be well and truly established, with acceptable user interfaces. Preliminary support added for more advanced functions such as searching.
  • 0% - Complete the upload backend, and make ready for uploading of multiple previews, categories etc.
  • 0% - Polish and neaten graphical administration.
  • 0% - Preliminary search functions.
  • 25% - Add functional categories.
  • 0% - User Profiles
  • 0% - Add Graphical interface to translations <NOTE: Database already optimised for easy translation>
  • 0% - Review milestone code, adding preliminary commenting, indenting and optimisation.

For Milestone 3-1: Beta 1

First wide feedback - Advanced Features should be fully operable, and configurable. This Milestone is more of a generic review of code for security flaws and optimisations. All submited extensions would have to be preserved for subsequent changes
  • 0% - Organize user feedback.
  • 0% - Web service for extensions integration. (see Extensions update features)
  • 0% - Code Review - Make neat and tidy + streamlined.
  • 0% - Code Review - Ensure there are no security flaws.
  • 0% - Review the site layout and interface, keeping in mind that the current theme was designed only as a prototype.

For Milestone 3-2: Beta 2

corrections, missing forgoten mandatory features

For Milestone 3-3: Beta 3

corrections, missing forgoten mandatory features

Possibly some more beta releases....

For Milestone 4: Release Candidate

If all goes well, there should be no need to change much.
  • 0% - Intensive Bug Testing.
  • 0% - Fix Bugs that emerge during testing.
  • 0% - Integration with OOo Package manager.

For Milestone 5: Code Cleanup and Final Preparation for public consumption

  • 0% - All done

For Milestone 6: Multilingual features

  • 0% - Site translation - refer to native-langs groups
  • 0% - upload different translated fields for an extension
  • 0% - Allow volunteers to translate (if uploader gives permission)

Issues concerning the website which need to be decided by a vote/discussion

Just add your thoughts below, and put your signature after them.

Should the short description be a completely different field then a longer, more comprehensive one?

I vote no, because it will require more work on behalf of the user uploading the extension. I think we should make it as easy as possible for them. Note that such sites as addons.mozilla.org do not do this either. --Computerdork 23:51, 4 January 2007 (CET)

I vote yes.If no short description is given, the X first characters of the long description are taken automatically, but the uploader should have a mean to give a head summarize. --Lgodard 09:30, 7 January 2007 (CET)

Personal tools