...
- Short-form chat (IRC) archives: Matrix-Static, irclogger, ASF Wilderness IRC logs.
- Email/forum archives: haxx.se, ASF Pony Mail, the old Tigris lists. (The old Tigris mailing-lists system used to provide a permalink to the archived version at the bottom of each mail delivered.)
- Issue Tracker: the current Jira issues, the old issuezilla.
- Wiki pages: the current Confluence, the old MoinMoin.
Develop An important step is to develop a URL "permalink" scheme to refer to our various resources. These would be technology-ignorant URLs, all under subversion.apache.org, like "/issue/1234".
...
- start documenting a URL-space map for our resources
- ; initially populate one entry, e.g. "/issue/<number> → issue <number>"
- implement some simple automated handling (e.g. redirects) for that
- well, well... we already have this in our .htaccess which covers that exact case along with some aliases:
"RedirectMatch ^/issue[^A-Za-z0-9]?(\d+)$ https://issues.apache.org/jira/browse/SVN-$1"
- start using it: update existing direct links to point here instead; publicize it
Deeper integration: A permalink URL should not merely redirect the user to its technology-specific target URL, but present the target in such a way that other inbound and outbound URLs also use the permalink form. With a big third-party system like Jira or Confluence the feasibility of that is going to depend entirely on whether the system has built-in support for that usage.
Software Distribution
Problem: Subversion packages are outdated or unavailable for many platforms, especially server/cloud environments (e.g. Docker) and mobile (e.g. Android).
...
Small / Personal Servers
(Home NAS, ; Raspberry Pi, etc.; also personal server software platforms like Sandstorm, UBOS, Yunohost, etc.)
Integrations with IDEs etc.
...