Difference between revisions of "Extensions/website/Minutes/2007-06"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Extensions Website Meeting Minutes June)
 
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
There is a weekly [[Extensions/website]] Meeting. Minutes are gathered for one month per Wiki page, latest first.
+
There is a weekly [[Extensions/website]] Meeting. Minutes are gathered for one month per Wiki page, latest first. Please subscribe to website@extensions. openoffice. org to join the effort.
 +
 
 +
= 2007-06-28 =
 +
 
 +
10:00–10:30 CEST
 +
 
 +
== Attendees ==
 +
 
 +
* Bettina Haberer
 +
* <strike>Joachim Lingner</strike>
 +
* <strike>Jürgen Schmidt</strike>
 +
* Kai Sommerfeld
 +
* Martin Damboldt
 +
* Stefan Taxhet
 +
* Thorsten Bosbach
 +
* Nils Fuhrmann
 +
 
 +
''Minute Taker:'' MD next (TBO, BH, JSC,KSO, ST, MD)
 +
 
 +
== Action Items ==
 +
 
 +
* How could an update feed be generated on the extensions.services.opennoffice.org site? (TBO, In progress)
 +
-> The static answer to send "no update available" will be ready today. For the implementation of the answer "yes there is an update" generated from the submitted Extensions, TBO expects about two weeks effort.
 +
* Redesign the extensions.services.openoffice.org site (STS, In progress)
 +
-> Stella has created two drafts which will be announced later today.
 +
* Establish a new virtual host on the same server as our extensions repository to handle the updates of extensions (TBO, In progress)
 +
-> No feedback so far from OSUOSL about this request. As a workaround we can redirect to current server.
 +
* Extend Extension Manager to use default extension update URL contained in version.ini for update pings (JL, Open)
 +
-> Not done yet, still targeting 2.3 release
 +
* Provide extensions update URL that is to put into version.ini of 2.3 (TBO, In progress)
 +
* Provide document describing the benefits of OXT over Non-OXT as target for "Developer Resources" (JSC, open, due 2007-07-05)
 +
* Prepare Mock-ups for Improved Site (STS, In progress)
 +
* Prepare Notification of Extension Owners about Site (ST, Open)
 +
* Prepare Documentation for Users as target for "User Resources" (BH, Open)
 +
-> BH expects to finish this by end of next week.
 +
 
 +
== Topics ==
 +
 
 +
No special topics have been discussed in todays meeting. We just walked thru the status of the action items. Participants will continue to work on their corresponding items.
 +
 
 +
 
 +
= 2007-06-21 =
 +
 
 +
10:00&ndash;12:00 CEST
 +
 
 +
== Attendees ==
 +
 
 +
* Bettina Haberer
 +
* Joachim Lingner
 +
* Jürgen Schmidt
 +
* <strike>Kai Sommerfeld</strike>
 +
* Martin Damboldt
 +
* Stefan Taxhet
 +
* Thorsten Bosbach
 +
 
 +
''Minute Taker:'' ST next (MD, TBO, BH, JSC,KSO, ST)
 +
 
 +
== Action Items ==
 +
 
 +
* How could an update feed be generated on the extensions.services.opennoffice.org site? (TBO, In progress)
 +
* Redesign the extensions.services.openoffice.org site (STS, In progress)
 +
* Establish a new virtual host on the same server as our extensions repository to handle the updates of extensions (TBO, In progress)
 +
* Extend Extension Manager to use default extension update URL contained in version.ini for update pings (JL, new)
 +
* Provide extensions update URL that is to put into version.ini of 2.3 (TBO, In progress)
 +
* Provide document describing the benefits of OXT over Non-OXT as target for "Developer Resources" (JSC, open, due 2007-07-05)
 +
* Prepare Mock-ups for Improved Site (STS)
 +
* Prepare Notification of Extension Owners about Site (ST)
 +
* Prepare Documentation for Users as tagrget for "User Resources" (BH)
 +
* Ensure that string “Download more extensions...” gets changed to “Get more extension...” (JL, done)
 +
* Implement “Type” for repository items (TBO, done)
 +
 
 +
== Topics ==
 +
 
 +
* We would like to push OXT as the preferred format
 +
* Owners of Extensions mentioned on the Wiki Page could be notified about the availability of the extension site
 +
* Comments during quick review of site home page:
 +
: version of extension should be visible in the items listed in overview
 +
: non-published extensions shouldn't be listed
 +
: update feed should promote most recent version only
 +
: OXT extensions will be promoted with oxt icon in overview
 +
 
 +
* Comments during quick walkthrough of the submission of an extension:
 +
: the term “project” will be replaced by “extension”
 +
: a label for the “extension class” is still to be found
 +
: the provider logo is upload only (no link)
 +
: upload of an extension leads to validation of fields; email is mandatory but has been removed from the form
 +
: Stella will provide some draft mock-ups for improved usability and branding of the site.
 +
: Thorsten will focus on the update feed for extensions and work on the results of the branding discussion then.
 +
[[Category:Extensions/Minutes]]

Latest revision as of 11:28, 4 March 2010

There is a weekly Extensions/website Meeting. Minutes are gathered for one month per Wiki page, latest first. Please subscribe to website@extensions. openoffice. org to join the effort.

2007-06-28

10:00–10:30 CEST

Attendees

  • Bettina Haberer
  • Joachim Lingner
  • Jürgen Schmidt
  • Kai Sommerfeld
  • Martin Damboldt
  • Stefan Taxhet
  • Thorsten Bosbach
  • Nils Fuhrmann

Minute Taker: MD next (TBO, BH, JSC,KSO, ST, MD)

Action Items

  • How could an update feed be generated on the extensions.services.opennoffice.org site? (TBO, In progress)

-> The static answer to send "no update available" will be ready today. For the implementation of the answer "yes there is an update" generated from the submitted Extensions, TBO expects about two weeks effort.

  • Redesign the extensions.services.openoffice.org site (STS, In progress)

-> Stella has created two drafts which will be announced later today.

  • Establish a new virtual host on the same server as our extensions repository to handle the updates of extensions (TBO, In progress)

-> No feedback so far from OSUOSL about this request. As a workaround we can redirect to current server.

  • Extend Extension Manager to use default extension update URL contained in version.ini for update pings (JL, Open)

-> Not done yet, still targeting 2.3 release

  • Provide extensions update URL that is to put into version.ini of 2.3 (TBO, In progress)
  • Provide document describing the benefits of OXT over Non-OXT as target for "Developer Resources" (JSC, open, due 2007-07-05)
  • Prepare Mock-ups for Improved Site (STS, In progress)
  • Prepare Notification of Extension Owners about Site (ST, Open)
  • Prepare Documentation for Users as target for "User Resources" (BH, Open)

-> BH expects to finish this by end of next week.

Topics

No special topics have been discussed in todays meeting. We just walked thru the status of the action items. Participants will continue to work on their corresponding items.


2007-06-21

10:00–12:00 CEST

Attendees

  • Bettina Haberer
  • Joachim Lingner
  • Jürgen Schmidt
  • Kai Sommerfeld
  • Martin Damboldt
  • Stefan Taxhet
  • Thorsten Bosbach

Minute Taker: ST next (MD, TBO, BH, JSC,KSO, ST)

Action Items

  • How could an update feed be generated on the extensions.services.opennoffice.org site? (TBO, In progress)
  • Redesign the extensions.services.openoffice.org site (STS, In progress)
  • Establish a new virtual host on the same server as our extensions repository to handle the updates of extensions (TBO, In progress)
  • Extend Extension Manager to use default extension update URL contained in version.ini for update pings (JL, new)
  • Provide extensions update URL that is to put into version.ini of 2.3 (TBO, In progress)
  • Provide document describing the benefits of OXT over Non-OXT as target for "Developer Resources" (JSC, open, due 2007-07-05)
  • Prepare Mock-ups for Improved Site (STS)
  • Prepare Notification of Extension Owners about Site (ST)
  • Prepare Documentation for Users as tagrget for "User Resources" (BH)
  • Ensure that string “Download more extensions...” gets changed to “Get more extension...” (JL, done)
  • Implement “Type” for repository items (TBO, done)

Topics

  • We would like to push OXT as the preferred format
  • Owners of Extensions mentioned on the Wiki Page could be notified about the availability of the extension site
  • Comments during quick review of site home page:
version of extension should be visible in the items listed in overview
non-published extensions shouldn't be listed
update feed should promote most recent version only
OXT extensions will be promoted with oxt icon in overview
  • Comments during quick walkthrough of the submission of an extension:
the term “project” will be replaced by “extension”
a label for the “extension class” is still to be found
the provider logo is upload only (no link)
upload of an extension leads to validation of fields; email is mandatory but has been removed from the form
Stella will provide some draft mock-ups for improved usability and branding of the site.
Thorsten will focus on the update feed for extensions and work on the results of the branding discussion then.
Personal tools