Dear all, I would like to briefly expose how things work for orgmode.org.
https://orgmode.org/worg/ is populated by .org pages from the Worg repo after each push: https://git.sr.ht/~bzg/worg Worg is maintained by Krupal and Corwin Brust. Anyone is welcome to contribute: https://orgmode.org/worg/worg-about.html https://orgmode.org is populated by .org pages from the orgweb repo after each push: https://git.sr.ht/~bzg/orgweb So far, only Timothy, Nicolas and me do have write access, these pages are not supposed to be updated very often. The Org maintainer needs to update the orgweb/Changes.org page for each release. https://orgmode.org/elpa/ is here for backward compatibility and will be removed before the release of Org 9.6. The https://orgmode.org contents are hosted on my machine. https://updates.orgmode.org is also hosted on my machine. I plan to work on improving Woof! in the next months to make it more stable and (hopefully) usable and useful, but it helps a lot already. https://list.orgmode.org is the public-inbox archive of the mailing list. It's hosted and maintained by Kyle. The mailing list archives are also here: https://lists.gnu.org/archive/html/emacs-orgmode/ https://stats.orgmode.org was used to provide some stats about orgmode.org visitors via a Fathom instance, but it is gone. Here is the interesting bit: there are ~30K visitors by month. AFAIK, this number as been remarkably stable for the last ten years. https://code.orgmode.org is gone: it was nice testing Gogs, which served us well for very long, but was not necessary anymore. Also, using Gogs required some maintainance (spamalot) and led newcomers to believe they had to create an account on it to contribute, whereas we prefer to receive/read/review patches on the mailing list. Relying on https://git.savannah.gnu.org is the way to go. Publishing Worg pages used to involve scripts on the server that we don't need anymore: the HTML page are generated by a SourceHut build and sent to the server. Same for orgweb. Releasing Org also used to require actions on the server: it does not anymore. Releasing Org only requires to update the "Version:" header, which triggers the release of the GNU ELPA package, which is now the preferred way of installing the last stable Org version. This setup makes many things a lot easier! - I'm really glad Kyle maintains list.orgmode.org: it's really cool and useful, searching the list archives is lightening fast. - Migrating the contents served by orgmode.org is just a matter of rsync'ing to another server. - No need to maintain the Gogs instance and the Fathom instance. - Releasing is now a breeze. Enjoy! -- Bastien
