I can assist you with non-technical chores On 2026/01/21 09:35:00 [email protected] 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 [email protected]: > > 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: [email protected] > For additional commands, e-mail: [email protected] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
