Extensions/website

From Apache OpenOffice Wiki
< Extensions
Revision as of 07:56, 3 May 2007 by Tbo (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Introduction

This is a summary of the comments to the website repository:
Extension repository based on DRUPAL framework: http://extensions.services.openoffice.org
Hosted and started at OSU OSL: http://oooapps.osuosl.org
Discussion at website@extensions.openoffice.org, irc://irc.freenode.net/ooo-ext

Todo's / Discussion / Comments

UI

  • (JSC) UI, the look and feel and branding, align it a little bit more to the existing OpenOffice.org pages.
    • (mathias.michel) ext website logo may be the standard OOo logo with something more to tell it's about extensions ( the atom structure, "ext" string hovering...) An the other side, the design of the OOo website is so austere, we may carry on some colour or design improvment to be appealing.
    • (JSC) sure the design of the OO.org website can be improved but that is a different topic and we will focus on the extensions repository and should keep it aligned with the current theme of OO.org
    • (mathias.michel) Frustrating but right Marketing team may propose an option to be consistent with design choice (string or icon, or the .oxt icon or anything they think relevant to say we talk about extensions).
    • (MMP) The logo "OO.o ext" is hard to decipher. We decided to use "oxt" as the suffix for extensions. Very techy, indeed.
    • (TBO) The logo should not contain the abbreviations.
    • (MMP) Pleasing color scheme. I like it.
    • (MMP) Good legibility of text

Items / Blocks / Planet link

  • (JSC) The "story" section, what exactly do we expect here? Who the content, it's an important and prominent place on the main site? Does it make more sense to view the latest or highest rated extensions here?
    • (TBO) The storys about new extensions could also be made in a blog and needn't be on the extension site.
  • (JSC) does the link to Planet OpenOffice.org provide any useful information for ens users? is it really of interest for users who simply search for some nice extensions.
    • (mathias.michel) Planet may be replaced by the latest and best rated ext. Story section content may be examples of use of extensions, News about OOo. We may also include description of new extensions to highlight their interest, beside the list.
    • (TBO) There could be a link to the planet, but there is no need to get the headings of it;

Filter / Applications / Categories

  • (JSC) Filter options for extensions
    • (JSC) By Applications -> we should probably include Charts
    • (JSC) By Category -> we should probably find a better set of categories. Does category mean type of extension like Add-ons, Calc Add-ins, Filter, Templates, Macro Libraries, ... or what does it mean.
  • (MMP) I like that you can filter for modules (e.g. extension that are only applicable to a certain module).
    • (MMP) And do not offer a module filter until there are real extension for that module (e.g. where is a real Math extension?)
  • (MMP) Introduce a general OOo icon to look for all extensions, once you are drilled down to a specific module.
  • (MMP) http://extensions.services.openoffice.org/taxonomy_menu/4
    • Can you sort the apps by significance? Start with Writer, Calc, Impress, Draw, Base, remove Math until there is a real Math extension. I expect to have extensions for Chart at some point. And (as mentioned above) a general category for Gallery schemes and templates makes sense.
  • (MMP) Categories. Where shoud I put (eg.) a presenter screen for Impress? http://blogs.sun.com/GullFOSS/entry/adding_a_presenter_view_to This does not fit into the list of existing categories.
  • (TBO) There could be another Category listing: what license does the extension belong to? http://www.opensource.org/licenses/category

Extension submission / Releasing

  • (JSC) Mandatory and optional submission data, e.g. home page, follow-up page, description, version number, update URL, screenshots, ...
    • (mathias.michel) Name, version and description are mandatory. Everything else should be optional. If a not-so-standard user reaches a small goal of achieving an extenstion which fit his needs, and he proposes it tro the community, we should not ask hilm to also set a webpage, a FAQ, etc... But instead we may have a mailing-list or a forum to help those authors and whoever wants it to support end-users of such extensions. It is our interest.
      • (JSC) The mailing lists are already in place dev@exteniosn.openoffice.org and users@extensons.openoffice.org
  • (MMP) User creation went smoothly. However, I do not understand why I should get a user account.
    • (JSC) you will need the user account only if you want to contribute an extension. noprmal end users won't need it.
  • (MMP) Some extensions have special system requirements. Like OOo 2.3 and higher, or Windows only. Would be great if such info is a) provided and b) can be filtered like category or application
  • (MMP) If I submit an extension,... I am asked to enter the locale. Well, what is this? I have an extension with an English AND German user interface.
    • (JSC) should probably be a list of supported locales. Extensions should always have a default locale (ideally English). so if no appropriate locale is availble the English one is used.
  • (MMP) Is it fair that I can rate my own extensions??
  • (MMP) I do not understand the "Releases" feature. Do I have to upload the extension for each release?
    • (JSC) if the binary oxt is hosted in the repository, yes. Otherwise you have to provide the info about the new version and your provided download URL should link to the new version.
  • (MMP) Product screenshot. It would be great to show a thumbnail of the screenshot on the extension page.

Help topics

  • (MMP) Install Guide for Extensions. Starting with OOo 2.2 the file type ".oxt" is registered. This means that you can simply double-click an oxt-extension to install it.

Download of extension

  • (JSC) specify the exact workflow or behaviour for the downloads. For example extension packages hosted in the repository or on an external page (probably commercial extensions)
    • (JSC) i think it is important to allow commercial extensions here as well to provide one and only one entry point for OpenOffice.org extensions. We should be open for all kind of useful stuff. The user can decide if an extensions is worth the money or not. But it makes definitely sense to include them here as well to help OpenOffice users to find the best solution/tools or whatever for their work environment.
      • (mathias.michel) +1
    • (mathias.michel) Hosting downloads ensure us to have at least one copuy of the extension. If the same not-so-stanbdard user hosts the file on his free webspace service, links to it. One year later, he closes his space, and no more package... We may propose to host download without enforcing it. Infrastructure should be there, of course. If not, maybe mirrors of OOo distrib will accept to host extensions repository ?
  • (TBO) Since one main fokus is to download extensions, the download link should be more prominent, e.g. by a big button 'get extension'

User settings

  • (MMP) My profile page should contain a list of extensions that I have contributed (makes it easy for me to update the info for an extension). And a list of extensions that I have downloaded (and I want to see if there is an update available).

Misc

  • (MMP) Do you provide a list of all members?

Issues

Registered user / Anonymous user

  • (JSC) after login the link All on the left side results in a page error
  • (MMP) If I am not logged in, I still have the link to Submit an extension. The page could provide some info like, "In order to submit an extension you have to create a user account first."
  • (MMP) Hey, now I can browse the extensions by application! Do I have to log in to see this part of the site? Why not offer this to all visitors?!
  • (TBO) Mail sender for registration mail is me@localhost.com

Not working link

  • (mathias.michel) Clicking on an extension in the highest rated section leads to a PHP Fatal Error.

Layout

  • (MMP) The extension home for USA Flag Collection (as an example).
    • I have my browser window at a width of 980. The link for "Release Notes" line-breaks. Now it looks like "Download notes" in the column Links, and "Release" stands alone to the right.
  • (MMP) Footer does not fit at 980 pixels width; the OSL logo hangs out. I suggest to design a full width footer.

Links

Categories

  • (MMP) Highest Rated. The list of highest rated extensions is not sorted by the rating yet. It is 4 stars - 3 stars - 1 star - 4 stars
  • (MMP) Please make the entire app icon clickable.

Extension submission / Releasing

General Comments

  • (JSC) that we have a working extension repository in place with hopefully some nice extensions for the OpenOffice.org conference in September.
  • (JSC) the developers who will help to improve it in the future
  • (TBO) I would like to try to improve the site;
  • (TBO) Start using the site just for what it is intended for: hosting of extensions;
  • (TBO) The site should get an end user focus for downloading extensions.
  • (Laurent Godard) compare to the design and functions of https://addons.mozilla.org

Keep in mind / targets

(Corey Shields)

  • provide resources for the development of extensions (issue tracking) -> Already on OOo-issuetracker
  • allow users to easily find extensions of all types in an organized manner
  • let extensions be ranked and commented on by the community
  • provide a layer of moderation by a vetted community (a lesson learned from Mozilla and the constant flow of malware extensions)
  • Add a thumbnail for each extension, set those up to display in the browsing views

(Laurent Godard)

  • extensible metadata
  • keywords and classification
  • advanced search features
  • RSS feed
  • translations
  • thumbnails/screenshots (localized too)
  • generate the xml description for OOo the online update feature
  • a repository hosting the extensions or not (eg. commercial/non-free that rewards partially or totally OOo project)
  • the extension site should have 3-4 access modes:
    • standard: a user that downloads an extensions
    • submitter: an author that submit and manage a pool of extensions
    • translators: a user that is allowed to give translations on any description of an extension.
    • admin/rewiever: validates the extensions
  • the following architecture has already been proposed. The repository is cut in 3 levels (so a metadata for every extension)
    • Wild : by default submission - All explicit disclaimers
    • Reviewed : Tested bty a rewiever regarding basic flaws
    • Recommended : Often used and requested feature. has been widely tested

Comments are from:

JSC - Juergen Schmidt
MMP - Matthias Mueller-Prove
TBO - Thorsten Bosbach
Corey Shields
Laurent Godard
Mathias Michel
Personal tools