You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pe...@apache.org on 2026/01/27 12:15:04 UTC

[update] extension and template website

The website download links work again. I am not sure why they did not 
work 2 weeks ago and what caused the fix.

But in order to get a maintainable extension and template website I will 
continue with the plan I have layed out.

We will in future maintain the website in a github repository, where 
changes can be made by Pull Request. Its a bit technical but should be 
okay for maintainers.

The file space we will keep at sf.net. I would like to reorient them by 
category/extension name/ extension file.

historic old files i move to svn. I am still working on the exact update 
process for files.

Currently i am still working at collecting everything together to make 
the transition.


Am 21.01.2026 um 13:25 schrieb Dick Groskamp:
> I can assist you with non-technical chores
>
> On 2026/01/21 09:35:00 Petko@apache.org wrote:
>> While I tried yesterday to check how i can download the files all at
>> once, i stumbled over the current code.
>>
>> I figured that we already had everything converted to html.
>>
>> Maybe it is a simpler / Faster step to change the downloadlink, und
>> simply upload the files again as a quick measure. I am currently on that
>> point.
>>
>> And then i look into the points below.
>>
>> all the best
>>
>> peter
>>
>> Am 13.01.2026 um 11:57 schrieb Petko@apache.org:
>>> Hi all,
>>>
>>> Thanks to ideas from Fernando Cassia on the users list, I have created
>>> a new roadmap for extensions/templates.
>>>
>>> Dick Groskamp suggested an intermediate post on forums or wiki to
>>> inform users about the current situation and possible immediate
>>> workarounds. Perhaps we could include this roadmap there as well?
>>>
>>>
>>>   Proposed Roadmap:
>>>
>>> 1.
>>>
>>>     Reorganize the files on
>>>     https://sourceforge.net/projects/aoo-extensions into a more
>>>     maintainable structure and migrate to an SVN repository on
>>> SourceForge.
>>>
>>> 2.
>>>
>>>     Export the extensions from the Drupal database and create static
>>>     pages from the export.
>>>
>>> 3.
>>>
>>>     Convert the download links to the new paths.
>>>
>>> 4.
>>>
>>>     Set up a repository similar to openoffice.org with the static
>>>     content (containing only website pages, but not extension files).
>>>
>>> 5.
>>>
>>>     Add a search feature for the static website (this could be
>>>     JavaScript-based with static indexing, or a micro service in Docker
>>>     with better search capabilities).
>>>
>>> 6.
>>>
>>>     Add a maintenance page as a micro service to make it easier for
>>>     maintainers to edit their extension pages.
>>>
>>>
>>>   Pros and Cons
>>>
>>> *Benefits of this approach:*
>>>
>>>   * Simple tech stack with fewer security issues
>>>   * Relatively easy transition that should be achievable without too
>>>     much effort
>>>   * Work can be divided into smaller tasks that new volunteers could
>>>     tackle without requiring extensive access or technical expertise
>>>
>>> *Drawbacks:*
>>>
>>>   * Less user-friendly initially. SVN and pure HTML are technical
>>>     approaches, and only with point 6 (which will need its own roadmap)
>>>     will this improve
>>>   * Adding new extensions will be labor-intensive. Creating new pages
>>>     will require manual work, so the site won't be particularly
>>>     attractive or user-friendly for new templates/extensions in the
>>>     short term
>>>
>>>
>>>   Conclusion and Request for Feedback
>>>
>>> I know this has been a critical issue for years, but I never had a
>>> viable solution until now. I think this is the first approach that
>>> could actually work. I am unsure how fast I can complete the list
>>> alone. If someone wants to support then please let me know.
>>>
>>> What are your thoughts? Do you see any blockers or issues? Please
>>> share your feedback.
>>>
>>> All the best
>>>
>>> Peter
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: [update] extension and template website

Posted by Matthias Seidel <ma...@hamburg.de>.
Am 27.01.26 um 18:25 schrieb Petko@apache.org:
>
> Am 27.01.2026 um 18:14 schrieb Marcus:
>> Am 27.01.26 um 13:27 schrieb Matthias Seidel:
>>> Am 27.01.26 um 13:15 schrieb Petko@apache.org:
>>>> The website download links work again. I am not sure why they did 
>>>> not work 2 weeks ago and what caused the fix.
>>>
>>> I cannot confirm this, trying to download the most recent English 
>>> dictionary here:
>>>
>>> https://extensions.openoffice.org/en/project/english-dictionaries- 
>>> apache-openoffice.html
>>>
>>> still leads to an error:
>>>
>>> https://extensions.openoffice.org/en/download/19529
>>
>> I get also an error, maybe the same:
>>
>> German:
>>
>> Fehler: Umleitungsfehler
>> Die aufgerufene Website leitet die Anfrage so um, dass sie nie 
>> beendet werden kann.
>> Dieses Problem kann manchmal auftreten, wenn Cookies deaktiviert oder 
>> abgelehnt werden.
>>
>> English:
>>
>> Error: Redirect error
>> The requested website is redirecting the request in such a way that 
>> it can never be completed.
>> This problem can sometimes occur if cookies are disabled or rejected.
>>
>> Maybe this helps.
>
> This seems to affect this specific dictionary. I have forwarded this 
> to Dave Brondsema for review. He told me that the forwarding should work.
>
> https://extensions.openoffice.org/en/project/us-english-spell-checking-dictionary.html 
> seems to work
>
> (which is the same just for OOo3? Do we want to keep this stuff? or 
> move it maybe?

For whatever reason, this dictionary gets bundled with NL and RU 
versions of AOO:

https://github.com/apache/openoffice/blob/trunk/main/extensions.lst#L77

Regards,

    Matthias

>
>>
>> Thank you for your work. :-)
>>
>>
>> Marcus
>>
>>
>>
>>>> Am 21.01.2026 um 13:25 schrieb Dick Groskamp:
>>>>> I can assist you with non-technical chores
>>>>>
>>>>> On 2026/01/21 09:35:00 Petko@apache.org wrote:
>>>>>> While I tried yesterday to check how i can download the files all at
>>>>>> once, i stumbled over the current code.
>>>>>>
>>>>>> I figured that we already had everything converted to html.
>>>>>>
>>>>>> Maybe it is a simpler / Faster step to change the downloadlink, und
>>>>>> simply upload the files again as a quick measure. I am currently 
>>>>>> on that
>>>>>> point.
>>>>>>
>>>>>> And then i look into the points below.
>>>>>>
>>>>>> all the best
>>>>>>
>>>>>> peter
>>>>>>
>>>>>> Am 13.01.2026 um 11:57 schrieb Petko@apache.org:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Thanks to ideas from Fernando Cassia on the users list, I have 
>>>>>>> created
>>>>>>> a new roadmap for extensions/templates.
>>>>>>>
>>>>>>> Dick Groskamp suggested an intermediate post on forums or wiki to
>>>>>>> inform users about the current situation and possible immediate
>>>>>>> workarounds. Perhaps we could include this roadmap there as well?
>>>>>>>
>>>>>>>
>>>>>>>   Proposed Roadmap:
>>>>>>>
>>>>>>> 1.
>>>>>>>
>>>>>>>     Reorganize the files on
>>>>>>>     https://sourceforge.net/projects/aoo-extensions into a more
>>>>>>>     maintainable structure and migrate to an SVN repository on
>>>>>>> SourceForge.
>>>>>>>
>>>>>>> 2.
>>>>>>>
>>>>>>>     Export the extensions from the Drupal database and create 
>>>>>>> static
>>>>>>>     pages from the export.
>>>>>>>
>>>>>>> 3.
>>>>>>>
>>>>>>>     Convert the download links to the new paths.
>>>>>>>
>>>>>>> 4.
>>>>>>>
>>>>>>>     Set up a repository similar to openoffice.org with the static
>>>>>>>     content (containing only website pages, but not extension 
>>>>>>> files).
>>>>>>>
>>>>>>> 5.
>>>>>>>
>>>>>>>     Add a search feature for the static website (this could be
>>>>>>>     JavaScript-based with static indexing, or a micro service in 
>>>>>>> Docker
>>>>>>>     with better search capabilities).
>>>>>>>
>>>>>>> 6.
>>>>>>>
>>>>>>>     Add a maintenance page as a micro service to make it easier for
>>>>>>>     maintainers to edit their extension pages.
>>>>>>>
>>>>>>>
>>>>>>>   Pros and Cons
>>>>>>>
>>>>>>> *Benefits of this approach:*
>>>>>>>
>>>>>>>   * Simple tech stack with fewer security issues
>>>>>>>   * Relatively easy transition that should be achievable without 
>>>>>>> too
>>>>>>>     much effort
>>>>>>>   * Work can be divided into smaller tasks that new volunteers 
>>>>>>> could
>>>>>>>     tackle without requiring extensive access or technical 
>>>>>>> expertise
>>>>>>>
>>>>>>> *Drawbacks:*
>>>>>>>
>>>>>>>   * Less user-friendly initially. SVN and pure HTML are technical
>>>>>>>     approaches, and only with point 6 (which will need its own 
>>>>>>> roadmap)
>>>>>>>     will this improve
>>>>>>>   * Adding new extensions will be labor-intensive. Creating new 
>>>>>>> pages
>>>>>>>     will require manual work, so the site won't be particularly
>>>>>>>     attractive or user-friendly for new templates/extensions in the
>>>>>>>     short term
>>>>>>>
>>>>>>>
>>>>>>>   Conclusion and Request for Feedback
>>>>>>>
>>>>>>> I know this has been a critical issue for years, but I never had a
>>>>>>> viable solution until now. I think this is the first approach that
>>>>>>> could actually work. I am unsure how fast I can complete the list
>>>>>>> alone. If someone wants to support then please let me know.
>>>>>>>
>>>>>>> What are your thoughts? Do you see any blockers or issues? Please
>>>>>>> share your feedback.
>>>>>>>
>>>>>>> All the best
>>>>>>>
>>>>>>> Peter
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: [update] extension and template website

Posted by Marcus <ma...@wtnet.de>.
Am 27.01.26 um 18:25 schrieb Petko@apache.org:
> Am 27.01.2026 um 18:14 schrieb Marcus:
>> Am 27.01.26 um 13:27 schrieb Matthias Seidel:
>>> Am 27.01.26 um 13:15 schrieb Petko@apache.org:
>>>> The website download links work again. I am not sure why they did 
>>>> not work 2 weeks ago and what caused the fix.
>>>
>>> I cannot confirm this, trying to download the most recent English 
>>> dictionary here:
>>>
>>> https://extensions.openoffice.org/en/project/english-dictionaries- 
>>> apache-openoffice.html
>>>
>>> still leads to an error:
>>>
>>> https://extensions.openoffice.org/en/download/19529
>>
>> I get also an error, maybe the same:
>>
>> German:
>>
>> Fehler: Umleitungsfehler
>> Die aufgerufene Website leitet die Anfrage so um, dass sie nie beendet 
>> werden kann.
>> Dieses Problem kann manchmal auftreten, wenn Cookies deaktiviert oder 
>> abgelehnt werden.
>>
>> English:
>>
>> Error: Redirect error
>> The requested website is redirecting the request in such a way that it 
>> can never be completed.
>> This problem can sometimes occur if cookies are disabled or rejected.
>>
>> Maybe this helps.
> 
> This seems to affect this specific dictionary. I have forwarded this to 
> Dave Brondsema for review. He told me that the forwarding should work.
> 
> https://extensions.openoffice.org/en/project/us-english-spell-checking- 
> dictionary.html seems to work

yes, same for me.

> (which is the same just for OOo3? Do we want to keep this stuff? or move 
> it maybe?

3.4.1 is the last version of the 3.x branch. It's from 2012.
So, I don't think that we still need this.

Marcus



>>>> Am 21.01.2026 um 13:25 schrieb Dick Groskamp:
>>>>> I can assist you with non-technical chores
>>>>>
>>>>> On 2026/01/21 09:35:00 Petko@apache.org wrote:
>>>>>> While I tried yesterday to check how i can download the files all at
>>>>>> once, i stumbled over the current code.
>>>>>>
>>>>>> I figured that we already had everything converted to html.
>>>>>>
>>>>>> Maybe it is a simpler / Faster step to change the downloadlink, und
>>>>>> simply upload the files again as a quick measure. I am currently 
>>>>>> on that
>>>>>> point.
>>>>>>
>>>>>> And then i look into the points below.
>>>>>>
>>>>>> all the best
>>>>>>
>>>>>> peter
>>>>>>
>>>>>> Am 13.01.2026 um 11:57 schrieb Petko@apache.org:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Thanks to ideas from Fernando Cassia on the users list, I have 
>>>>>>> created
>>>>>>> a new roadmap for extensions/templates.
>>>>>>>
>>>>>>> Dick Groskamp suggested an intermediate post on forums or wiki to
>>>>>>> inform users about the current situation and possible immediate
>>>>>>> workarounds. Perhaps we could include this roadmap there as well?
>>>>>>>
>>>>>>>
>>>>>>>   Proposed Roadmap:
>>>>>>>
>>>>>>> 1.
>>>>>>>
>>>>>>>     Reorganize the files on
>>>>>>>     https://sourceforge.net/projects/aoo-extensions into a more
>>>>>>>     maintainable structure and migrate to an SVN repository on
>>>>>>> SourceForge.
>>>>>>>
>>>>>>> 2.
>>>>>>>
>>>>>>>     Export the extensions from the Drupal database and create static
>>>>>>>     pages from the export.
>>>>>>>
>>>>>>> 3.
>>>>>>>
>>>>>>>     Convert the download links to the new paths.
>>>>>>>
>>>>>>> 4.
>>>>>>>
>>>>>>>     Set up a repository similar to openoffice.org with the static
>>>>>>>     content (containing only website pages, but not extension 
>>>>>>> files).
>>>>>>>
>>>>>>> 5.
>>>>>>>
>>>>>>>     Add a search feature for the static website (this could be
>>>>>>>     JavaScript-based with static indexing, or a micro service in 
>>>>>>> Docker
>>>>>>>     with better search capabilities).
>>>>>>>
>>>>>>> 6.
>>>>>>>
>>>>>>>     Add a maintenance page as a micro service to make it easier for
>>>>>>>     maintainers to edit their extension pages.
>>>>>>>
>>>>>>>
>>>>>>>   Pros and Cons
>>>>>>>
>>>>>>> *Benefits of this approach:*
>>>>>>>
>>>>>>>   * Simple tech stack with fewer security issues
>>>>>>>   * Relatively easy transition that should be achievable without too
>>>>>>>     much effort
>>>>>>>   * Work can be divided into smaller tasks that new volunteers could
>>>>>>>     tackle without requiring extensive access or technical expertise
>>>>>>>
>>>>>>> *Drawbacks:*
>>>>>>>
>>>>>>>   * Less user-friendly initially. SVN and pure HTML are technical
>>>>>>>     approaches, and only with point 6 (which will need its own 
>>>>>>> roadmap)
>>>>>>>     will this improve
>>>>>>>   * Adding new extensions will be labor-intensive. Creating new 
>>>>>>> pages
>>>>>>>     will require manual work, so the site won't be particularly
>>>>>>>     attractive or user-friendly for new templates/extensions in the
>>>>>>>     short term
>>>>>>>
>>>>>>>
>>>>>>>   Conclusion and Request for Feedback
>>>>>>>
>>>>>>> I know this has been a critical issue for years, but I never had a
>>>>>>> viable solution until now. I think this is the first approach that
>>>>>>> could actually work. I am unsure how fast I can complete the list
>>>>>>> alone. If someone wants to support then please let me know.
>>>>>>>
>>>>>>> What are your thoughts? Do you see any blockers or issues? Please
>>>>>>> share your feedback.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: [update] extension and template website

Posted by Pe...@apache.org.
Am 27.01.2026 um 18:14 schrieb Marcus:
> Am 27.01.26 um 13:27 schrieb Matthias Seidel:
>> Am 27.01.26 um 13:15 schrieb Petko@apache.org:
>>> The website download links work again. I am not sure why they did 
>>> not work 2 weeks ago and what caused the fix.
>>
>> I cannot confirm this, trying to download the most recent English 
>> dictionary here:
>>
>> https://extensions.openoffice.org/en/project/english-dictionaries- 
>> apache-openoffice.html
>>
>> still leads to an error:
>>
>> https://extensions.openoffice.org/en/download/19529
>
> I get also an error, maybe the same:
>
> German:
>
> Fehler: Umleitungsfehler
> Die aufgerufene Website leitet die Anfrage so um, dass sie nie beendet 
> werden kann.
> Dieses Problem kann manchmal auftreten, wenn Cookies deaktiviert oder 
> abgelehnt werden.
>
> English:
>
> Error: Redirect error
> The requested website is redirecting the request in such a way that it 
> can never be completed.
> This problem can sometimes occur if cookies are disabled or rejected.
>
> Maybe this helps.

This seems to affect this specific dictionary. I have forwarded this to 
Dave Brondsema for review. He told me that the forwarding should work.

https://extensions.openoffice.org/en/project/us-english-spell-checking-dictionary.html 
seems to work

(which is the same just for OOo3? Do we want to keep this stuff? or move 
it maybe?

>
> Thank you for your work. :-)
>
>
> Marcus
>
>
>
>>> Am 21.01.2026 um 13:25 schrieb Dick Groskamp:
>>>> I can assist you with non-technical chores
>>>>
>>>> On 2026/01/21 09:35:00 Petko@apache.org wrote:
>>>>> While I tried yesterday to check how i can download the files all at
>>>>> once, i stumbled over the current code.
>>>>>
>>>>> I figured that we already had everything converted to html.
>>>>>
>>>>> Maybe it is a simpler / Faster step to change the downloadlink, und
>>>>> simply upload the files again as a quick measure. I am currently 
>>>>> on that
>>>>> point.
>>>>>
>>>>> And then i look into the points below.
>>>>>
>>>>> all the best
>>>>>
>>>>> peter
>>>>>
>>>>> Am 13.01.2026 um 11:57 schrieb Petko@apache.org:
>>>>>> Hi all,
>>>>>>
>>>>>> Thanks to ideas from Fernando Cassia on the users list, I have 
>>>>>> created
>>>>>> a new roadmap for extensions/templates.
>>>>>>
>>>>>> Dick Groskamp suggested an intermediate post on forums or wiki to
>>>>>> inform users about the current situation and possible immediate
>>>>>> workarounds. Perhaps we could include this roadmap there as well?
>>>>>>
>>>>>>
>>>>>>   Proposed Roadmap:
>>>>>>
>>>>>> 1.
>>>>>>
>>>>>>     Reorganize the files on
>>>>>>     https://sourceforge.net/projects/aoo-extensions into a more
>>>>>>     maintainable structure and migrate to an SVN repository on
>>>>>> SourceForge.
>>>>>>
>>>>>> 2.
>>>>>>
>>>>>>     Export the extensions from the Drupal database and create static
>>>>>>     pages from the export.
>>>>>>
>>>>>> 3.
>>>>>>
>>>>>>     Convert the download links to the new paths.
>>>>>>
>>>>>> 4.
>>>>>>
>>>>>>     Set up a repository similar to openoffice.org with the static
>>>>>>     content (containing only website pages, but not extension 
>>>>>> files).
>>>>>>
>>>>>> 5.
>>>>>>
>>>>>>     Add a search feature for the static website (this could be
>>>>>>     JavaScript-based with static indexing, or a micro service in 
>>>>>> Docker
>>>>>>     with better search capabilities).
>>>>>>
>>>>>> 6.
>>>>>>
>>>>>>     Add a maintenance page as a micro service to make it easier for
>>>>>>     maintainers to edit their extension pages.
>>>>>>
>>>>>>
>>>>>>   Pros and Cons
>>>>>>
>>>>>> *Benefits of this approach:*
>>>>>>
>>>>>>   * Simple tech stack with fewer security issues
>>>>>>   * Relatively easy transition that should be achievable without too
>>>>>>     much effort
>>>>>>   * Work can be divided into smaller tasks that new volunteers could
>>>>>>     tackle without requiring extensive access or technical expertise
>>>>>>
>>>>>> *Drawbacks:*
>>>>>>
>>>>>>   * Less user-friendly initially. SVN and pure HTML are technical
>>>>>>     approaches, and only with point 6 (which will need its own 
>>>>>> roadmap)
>>>>>>     will this improve
>>>>>>   * Adding new extensions will be labor-intensive. Creating new 
>>>>>> pages
>>>>>>     will require manual work, so the site won't be particularly
>>>>>>     attractive or user-friendly for new templates/extensions in the
>>>>>>     short term
>>>>>>
>>>>>>
>>>>>>   Conclusion and Request for Feedback
>>>>>>
>>>>>> I know this has been a critical issue for years, but I never had a
>>>>>> viable solution until now. I think this is the first approach that
>>>>>> could actually work. I am unsure how fast I can complete the list
>>>>>> alone. If someone wants to support then please let me know.
>>>>>>
>>>>>> What are your thoughts? Do you see any blockers or issues? Please
>>>>>> share your feedback.
>>>>>>
>>>>>> All the best
>>>>>>
>>>>>> Peter
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: [update] extension and template website

Posted by Marcus <ma...@wtnet.de>.
Am 27.01.26 um 13:27 schrieb Matthias Seidel:
> Am 27.01.26 um 13:15 schrieb Petko@apache.org:
>> The website download links work again. I am not sure why they did not 
>> work 2 weeks ago and what caused the fix.
> 
> I cannot confirm this, trying to download the most recent English 
> dictionary here:
> 
> https://extensions.openoffice.org/en/project/english-dictionaries- 
> apache-openoffice.html
> 
> still leads to an error:
> 
> https://extensions.openoffice.org/en/download/19529

I get also an error, maybe the same:

German:

Fehler: Umleitungsfehler
Die aufgerufene Website leitet die Anfrage so um, dass sie nie beendet 
werden kann.
Dieses Problem kann manchmal auftreten, wenn Cookies deaktiviert oder 
abgelehnt werden.

English:

Error: Redirect error
The requested website is redirecting the request in such a way that it 
can never be completed.
This problem can sometimes occur if cookies are disabled or rejected.

Maybe this helps.

Thank you for your work. :-)


Marcus



>> Am 21.01.2026 um 13:25 schrieb Dick Groskamp:
>>> I can assist you with non-technical chores
>>>
>>> On 2026/01/21 09:35:00 Petko@apache.org wrote:
>>>> While I tried yesterday to check how i can download the files all at
>>>> once, i stumbled over the current code.
>>>>
>>>> I figured that we already had everything converted to html.
>>>>
>>>> Maybe it is a simpler / Faster step to change the downloadlink, und
>>>> simply upload the files again as a quick measure. I am currently on 
>>>> that
>>>> point.
>>>>
>>>> And then i look into the points below.
>>>>
>>>> all the best
>>>>
>>>> peter
>>>>
>>>> Am 13.01.2026 um 11:57 schrieb Petko@apache.org:
>>>>> Hi all,
>>>>>
>>>>> Thanks to ideas from Fernando Cassia on the users list, I have created
>>>>> a new roadmap for extensions/templates.
>>>>>
>>>>> Dick Groskamp suggested an intermediate post on forums or wiki to
>>>>> inform users about the current situation and possible immediate
>>>>> workarounds. Perhaps we could include this roadmap there as well?
>>>>>
>>>>>
>>>>>   Proposed Roadmap:
>>>>>
>>>>> 1.
>>>>>
>>>>>     Reorganize the files on
>>>>>     https://sourceforge.net/projects/aoo-extensions into a more
>>>>>     maintainable structure and migrate to an SVN repository on
>>>>> SourceForge.
>>>>>
>>>>> 2.
>>>>>
>>>>>     Export the extensions from the Drupal database and create static
>>>>>     pages from the export.
>>>>>
>>>>> 3.
>>>>>
>>>>>     Convert the download links to the new paths.
>>>>>
>>>>> 4.
>>>>>
>>>>>     Set up a repository similar to openoffice.org with the static
>>>>>     content (containing only website pages, but not extension files).
>>>>>
>>>>> 5.
>>>>>
>>>>>     Add a search feature for the static website (this could be
>>>>>     JavaScript-based with static indexing, or a micro service in 
>>>>> Docker
>>>>>     with better search capabilities).
>>>>>
>>>>> 6.
>>>>>
>>>>>     Add a maintenance page as a micro service to make it easier for
>>>>>     maintainers to edit their extension pages.
>>>>>
>>>>>
>>>>>   Pros and Cons
>>>>>
>>>>> *Benefits of this approach:*
>>>>>
>>>>>   * Simple tech stack with fewer security issues
>>>>>   * Relatively easy transition that should be achievable without too
>>>>>     much effort
>>>>>   * Work can be divided into smaller tasks that new volunteers could
>>>>>     tackle without requiring extensive access or technical expertise
>>>>>
>>>>> *Drawbacks:*
>>>>>
>>>>>   * Less user-friendly initially. SVN and pure HTML are technical
>>>>>     approaches, and only with point 6 (which will need its own 
>>>>> roadmap)
>>>>>     will this improve
>>>>>   * Adding new extensions will be labor-intensive. Creating new pages
>>>>>     will require manual work, so the site won't be particularly
>>>>>     attractive or user-friendly for new templates/extensions in the
>>>>>     short term
>>>>>
>>>>>
>>>>>   Conclusion and Request for Feedback
>>>>>
>>>>> I know this has been a critical issue for years, but I never had a
>>>>> viable solution until now. I think this is the first approach that
>>>>> could actually work. I am unsure how fast I can complete the list
>>>>> alone. If someone wants to support then please let me know.
>>>>>
>>>>> What are your thoughts? Do you see any blockers or issues? Please
>>>>> share your feedback.
>>>>>
>>>>> All the best
>>>>>
>>>>> Peter


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Re: [update] extension and template website

Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Peter, All,

Am 27.01.26 um 13:15 schrieb Petko@apache.org:
> The website download links work again. I am not sure why they did not 
> work 2 weeks ago and what caused the fix.

I cannot confirm this, trying to download the most recent English 
dictionary here:

https://extensions.openoffice.org/en/project/english-dictionaries-apache-openoffice.html

still leads to an error:

https://extensions.openoffice.org/en/download/19529

Regards,

    Matthias

>
> But in order to get a maintainable extension and template website I 
> will continue with the plan I have layed out.
>
> We will in future maintain the website in a github repository, where 
> changes can be made by Pull Request. Its a bit technical but should be 
> okay for maintainers.
>
> The file space we will keep at sf.net. I would like to reorient them 
> by category/extension name/ extension file.
>
> historic old files i move to svn. I am still working on the exact 
> update process for files.
>
> Currently i am still working at collecting everything together to make 
> the transition.
>
>
> Am 21.01.2026 um 13:25 schrieb Dick Groskamp:
>> I can assist you with non-technical chores
>>
>> On 2026/01/21 09:35:00 Petko@apache.org wrote:
>>> While I tried yesterday to check how i can download the files all at
>>> once, i stumbled over the current code.
>>>
>>> I figured that we already had everything converted to html.
>>>
>>> Maybe it is a simpler / Faster step to change the downloadlink, und
>>> simply upload the files again as a quick measure. I am currently on 
>>> that
>>> point.
>>>
>>> And then i look into the points below.
>>>
>>> all the best
>>>
>>> peter
>>>
>>> Am 13.01.2026 um 11:57 schrieb Petko@apache.org:
>>>> Hi all,
>>>>
>>>> Thanks to ideas from Fernando Cassia on the users list, I have created
>>>> a new roadmap for extensions/templates.
>>>>
>>>> Dick Groskamp suggested an intermediate post on forums or wiki to
>>>> inform users about the current situation and possible immediate
>>>> workarounds. Perhaps we could include this roadmap there as well?
>>>>
>>>>
>>>>   Proposed Roadmap:
>>>>
>>>> 1.
>>>>
>>>>     Reorganize the files on
>>>>     https://sourceforge.net/projects/aoo-extensions into a more
>>>>     maintainable structure and migrate to an SVN repository on
>>>> SourceForge.
>>>>
>>>> 2.
>>>>
>>>>     Export the extensions from the Drupal database and create static
>>>>     pages from the export.
>>>>
>>>> 3.
>>>>
>>>>     Convert the download links to the new paths.
>>>>
>>>> 4.
>>>>
>>>>     Set up a repository similar to openoffice.org with the static
>>>>     content (containing only website pages, but not extension files).
>>>>
>>>> 5.
>>>>
>>>>     Add a search feature for the static website (this could be
>>>>     JavaScript-based with static indexing, or a micro service in 
>>>> Docker
>>>>     with better search capabilities).
>>>>
>>>> 6.
>>>>
>>>>     Add a maintenance page as a micro service to make it easier for
>>>>     maintainers to edit their extension pages.
>>>>
>>>>
>>>>   Pros and Cons
>>>>
>>>> *Benefits of this approach:*
>>>>
>>>>   * Simple tech stack with fewer security issues
>>>>   * Relatively easy transition that should be achievable without too
>>>>     much effort
>>>>   * Work can be divided into smaller tasks that new volunteers could
>>>>     tackle without requiring extensive access or technical expertise
>>>>
>>>> *Drawbacks:*
>>>>
>>>>   * Less user-friendly initially. SVN and pure HTML are technical
>>>>     approaches, and only with point 6 (which will need its own 
>>>> roadmap)
>>>>     will this improve
>>>>   * Adding new extensions will be labor-intensive. Creating new pages
>>>>     will require manual work, so the site won't be particularly
>>>>     attractive or user-friendly for new templates/extensions in the
>>>>     short term
>>>>
>>>>
>>>>   Conclusion and Request for Feedback
>>>>
>>>> I know this has been a critical issue for years, but I never had a
>>>> viable solution until now. I think this is the first approach that
>>>> could actually work. I am unsure how fast I can complete the list
>>>> alone. If someone wants to support then please let me know.
>>>>
>>>> What are your thoughts? Do you see any blockers or issues? Please
>>>> share your feedback.
>>>>
>>>> All the best
>>>>
>>>> Peter
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org