Project

General

Profile

Actions

Bug #1289

closed

outdated and don't corresponding with recent version of site Publishing_extensions document

Added by Vasiliy Petrov almost 9 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Tags:
Documentation

Description

I help the developer of OOoFBTools extension https://sourceforge.net/projects/fbtools/ (which works also together with LibreOffice Writer) to admin resources.
It present in OO extensions catalog, so I find it necessary to put it also into LO extensions catalog.

On the page http://extensions.libreoffice.org/ I see links on Howto documents with description of contributing process.
I prefer to use pdf version, but odt seems to be the same:
https://wiki.documentfoundation.org/images/1/14/Publishing_extensions.pdf

The issue begins on the first step: document suggests to search registration form in the place, where it don't (and should not) present.
Maybe it will be right to put in the document a direct url?

OK, I've find the link, not in the top of the page, but in the bottom…
Hosting your Extension(s) http://extensions.libreoffice.org/@@hosting-your-extension

But, after activation of account (which took more than 24 hours, so, probably, user should be noted about expected interval) I've failed to find 'Add extension' form.

Probably, this document should be completely reviewed.

P.S. There is one more possibly related infrastructure-documenting question:
OOoFBTools in AOO Extensions' catalog wasn't updated for many releases, because of lost registrator.
Thatis why I find necessary to provide co-maintainership feature. Allowing to manage extension (upload new releases) not only for me, but at least to primary developer. Allowing him also to add new co-maintainers and mark outdated inactive ones.
Should I report this question as a separate issue?

Actions #1

Updated by Beluga Beluga about 4 years ago

  • Status changed from New to Closed

Vasiliy Petrov wrote:

OOoFBTools in AOO Extensions' catalog wasn't updated for many releases, because of lost registrator.
Thatis why I find necessary to provide co-maintainership feature. Allowing to manage extension (upload new releases) not only for me, but at least to primary developer. Allowing him also to add new co-maintainers and mark outdated inactive ones.
Should I report this question as a separate issue?

A new extensions & templates site is in development. Please report this co-maintainership suggestion separately.

Actions

Also available in: Atom PDF