Difference between revisions of "Extensions/website-todo"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
(30 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
<h1>The "Official" TODO list</h1>
 
<h1>The "Official" TODO list</h1>
Please note that everything on this page is subject to revision, and may be lacking in many regards.
+
The link for the development site is: http://extensions.services.openoffice.org/<br />
<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.
+
The link for the superseded alpha website is: http://www.cusoo.org/extensions/ooo-ext-website/. PLEASE NOTE: THIS SITE IS NO LONGER UNDER ACTIVE DEVELOPMENT; DROPPED IN FAVOUR OF A DRUPAL BASED SYSTEM.<br />
<ul>
+
For reference only, the database layout for the original system is available here: [[Extensions/website-db]]<br />
<li style='color: #2DAE36'>100% - Design database layout.</li>
+
Everything on this page is subject to revision and interpretation, and refers to the LATEST drupal-based development website, for which the progress meters below have been reset. At this stage, many of the meters below have been antiquated by the shift to drupal. In the coming weeks this will be made to represent the drupal system.
<li style='color: #2DAE36'>100% - Create dynamic listing of available extensions.</li>
+
<li style='color: #2DAE36'>100% - Allow user login &lt;Note - Profiles not included in this entry&gt;</li>
+
<li style='color: #2DAE36'>100% - Allow users to upload/delete/modify their extensions &lt;NOTE: Deferring addition/removal of image previews and modification of actual extension package until next milestone&gt;</li>
+
<li style='color: #2DAE36'>80% - Graphical administration of site &lt; As much as is going to be done in this milestone is done&gt;</li>
+
<li style='color: #2DAE36'>25% - Graphical install/configuration of site &lt; 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 &gt;</li>
+
</ul>
+
  
<h3>For Milestone 2: Beta 1</h3> Ready for beta review. Fundamental functions should be well and truly established, with acceptable user interfaces. Preliminary support added for more advanced functions such as searching.
+
A more detailed list is at http://wiki.services.openoffice.org/wiki/Extensions/website/wishlist
 +
 
 +
<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. This is the starting point with drupal.
 
<ul>
 
<ul>
<li style='color: #D03234'>0% - Complete the upload backend, and make ready for uploading of multiple previews, etc.</li>
+
<li style='color: #2DAE36'>100% - Design database layout. Drupal does the job.</li>
<li style='color: #D03234'>0% - Polish and neaten graphical administration.</li>
+
<li style='color: #2DAE36'>100% - Create dynamic listing of available extensions.</li>
<li style='color: #D03234'>0% - Preliminary search functions.</li>
+
<li style='color: #2DAE36'>100% - Allow user login.</li>
<li style='color: #8314B6'>25% - Add functional categories.</li>
+
<li style='color: #2DAE36'>100% - Allow users to upload/delete/modify their extensions.</li>
<li style='color: #D03234'>0% - User Profiles</li>
+
<li style='color: #2DAE36'>100% - Graphical administration of site.</li>
<li style='color: #D03234'>0% - Add Graphical interface to translations &lt;NOTE: Database already optimised for easy translation&gt;</li>
+
<li style='color: #2DAE36'>100% - Graphical install/configuration of site.</li>
 +
<li style='color: #2DAE36'>100% - Register as a new user - only login/password/email for a first shoot</li>
 +
<li style='color: #C8C800'>80% - Complete the upload backend, and make ready for uploading of multiple previews, categories etc.</li>
 +
<li style='color: #2DAE36'>100% - Search and sorting functions.</li>
 +
<li style='color: #2DAE36'>100% - Add functional categories.</li>
 
<li style='color: #D03234'>0% - Review milestone code, adding preliminary commenting, indenting and optimisation.</li>
 
<li style='color: #D03234'>0% - Review milestone code, adding preliminary commenting, indenting and optimisation.</li>
 
</ul>
 
</ul>
  
<h3>For Milestone 3: Beta 2</h3> Advanced Features should be fully operable, and configurable. This Milestone is more of a generic review of code for security flaws and optimisations.
+
<h3>For Milestone 3-1: Beta 1</h3> 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
 
<ul>
 
<ul>
 +
<li style='color: #C8C800'>50% - Organize user feedback.</li>
 +
<li style='color: #2DAE36'>100% - Web service for extensions integration. (see Extensions update features)(Provide an atom update feed to the extension manager in OOo.)</li>
 
<li style='color: #D03234'>0% - Code Review - Make neat and tidy + streamlined.</li>
 
<li style='color: #D03234'>0% - Code Review - Make neat and tidy + streamlined.</li>
 
<li style='color: #D03234'>0% - Code Review - Ensure there are no security flaws.</li>
 
<li style='color: #D03234'>0% - Code Review - Ensure there are no security flaws.</li>
<li style='color: #D03234'>0% - Review the site layout and interface, keeping in mind that the current theme was designed only as a prototype.</li>
+
<li style='color: #2DAE36'>100% - Theme overhaul</li>
 
</ul>
 
</ul>
 
<h3>Possibly some more beta releases....</h3>
 
  
 
<h3>For Milestone 4: Release Candidate</h3> If all goes well, there should be no need to change much.
 
<h3>For Milestone 4: Release Candidate</h3> If all goes well, there should be no need to change much.
 +
Target is planned for end of august.
 
<ul>
 
<ul>
<li style='color: #D03234'>0% - Intensive Bug Testing.</li>
+
<li style='color: #C8C800'>50% - Intensive Bug Testing.</li>
<li style='color: #D03234'>0% - Fix Bugs that emerge during testing.</li>
+
<li style='color: #C8C800'>50% - Fix Bugs that emerge during testing.</li>
 +
<li style='color: #2DAE36'>100% - Integration with OOo Extension manager. (starting with OOo 2.3 there is a link called "Get more Extensions" within the extension manager dialog of OOo)</li>
 +
<li style='color: #2DAE36'>100% - Hide/remove test entries</li>
 
</ul>
 
</ul>
 +
 
<h3>For Milestone 5: Code Cleanup and Final Preparation for public consumption</h3>
 
<h3>For Milestone 5: Code Cleanup and Final Preparation for public consumption</h3>
 +
First end user release is targeted at least for OOoCon 2007 middle of september.
 
<ul>
 
<ul>
 
<li style='color: #D03234'>0% - All done</li>
 
<li style='color: #D03234'>0% - All done</li>
 +
</ul>
 +
 +
<h3>For Milestone 6: Multilingual features</h3>
 +
<ul>
 +
<li style='color: #C8C800'>50% - Add Graphical interface to translations - No graphical translation planned - export/import via .po/.pot files</li>
 +
<li style='color: #C8C800'>10% - Site translation - refer to native-langs groups</li>
 +
<li style='color: #D03234'>0% - upload different translated fields for an extension</li>
 +
<li style='color: #D03234'>0% - Allow volunteers to translate (if uploader gives permission)</li>
 
</ul>
 
</ul>
  
 
<h1>Issues concerning the website which need to be decided by a vote/discussion</h1>
 
<h1>Issues concerning the website which need to be decided by a vote/discussion</h1>
 
Just add your thoughts below, and put your signature after them.
 
Just add your thoughts below, and put your signature after them.
<h3>Should the short description be a completely different field then a longer, more comprehensive one?</h3>
 
 
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.
 
--[[User:Computerdork|Computerdork]] 23:51, 4 January 2007 (CET)
 
  
I vote '''yes'''. The amount of work is not a good argument. If no short description, the X first characters of the long description are taken.
+
[[Category:To-Do]]
--[[User:Lgodard|Lgodard]] 09:30, 7 January 2007 (CET)
+

Latest revision as of 14:10, 26 November 2007

The "Official" TODO list

The link for the development site is: http://extensions.services.openoffice.org/
The link for the superseded alpha website is: http://www.cusoo.org/extensions/ooo-ext-website/. PLEASE NOTE: THIS SITE IS NO LONGER UNDER ACTIVE DEVELOPMENT; DROPPED IN FAVOUR OF A DRUPAL BASED SYSTEM.
For reference only, the database layout for the original system is available here: Extensions/website-db
Everything on this page is subject to revision and interpretation, and refers to the LATEST drupal-based development website, for which the progress meters below have been reset. At this stage, many of the meters below have been antiquated by the shift to drupal. In the coming weeks this will be made to represent the drupal system.

A more detailed list is at http://wiki.services.openoffice.org/wiki/Extensions/website/wishlist

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. This is the starting point with drupal.
  • 100% - Design database layout. Drupal does the job.
  • 100% - Create dynamic listing of available extensions.
  • 100% - Allow user login.
  • 100% - Allow users to upload/delete/modify their extensions.
  • 100% - Graphical administration of site.
  • 100% - Graphical install/configuration of site.
  • 100% - Register as a new user - only login/password/email for a first shoot
  • 80% - Complete the upload backend, and make ready for uploading of multiple previews, categories etc.
  • 100% - Search and sorting functions.
  • 100% - Add functional categories.
  • 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
  • 50% - Organize user feedback.
  • 100% - Web service for extensions integration. (see Extensions update features)(Provide an atom update feed to the extension manager in OOo.)
  • 0% - Code Review - Make neat and tidy + streamlined.
  • 0% - Code Review - Ensure there are no security flaws.
  • 100% - Theme overhaul

For Milestone 4: Release Candidate

If all goes well, there should be no need to change much.

Target is planned for end of august.

  • 50% - Intensive Bug Testing.
  • 50% - Fix Bugs that emerge during testing.
  • 100% - Integration with OOo Extension manager. (starting with OOo 2.3 there is a link called "Get more Extensions" within the extension manager dialog of OOo)
  • 100% - Hide/remove test entries

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

First end user release is targeted at least for OOoCon 2007 middle of september.

  • 0% - All done

For Milestone 6: Multilingual features

  • 50% - Add Graphical interface to translations - No graphical translation planned - export/import via .po/.pot files
  • 10% - 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.

Personal tools