tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Avoid broken link to non-existing wiki pages 

[Imported from Trac: page MoveOffTrac, version 5]
btlogy 2024-07-02 16:39:11 +00:00
parent 9224181d49
commit 5a7241cbb3
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
MoveOffTrac.md

@ -11,17 +11,17 @@ The goal of this page is to cover the phases of a project aiming at moving some
* MUST be better maintained: Trac is dying? max 2 contributors per month - <https://openhub.net/p/trac> * MUST be better maintained: Trac is dying? max 2 contributors per month - <https://openhub.net/p/trac>
* MUST be easier to maintain: Trac is difficult to update (current = v1.0.13/2016-09-11, latest = v1.6.0/2023-09-23)? * MUST be easier to maintain: Trac is difficult to update (current = v1.0.13/2016-09-11, latest = v1.6.0/2023-09-23)?
* MUST allow Self-Registration (Trac requires manual registration via email) * MUST allow Self-Registration (Trac requires manual registration via email)
* COULD support OAuth2 with [GitHub](GitHub)? * COULD support OAuth2 with Github?
* MUST be (F)OSS * MUST be (F)OSS
* MUST be self-hostable * MUST be self-hostable
* note "able": MUST be a story for getting to a self-hosted instance if we want * note "able": MUST be a story for getting to a self-hosted instance if we want
* ..but doesn't have to be self-hosted right away * ..but doesn't have to be self-hosted right away
2. MUST replace the current landing page (StartPage from the Wiki): 2. MUST replace the current landing page (start/home page from the Trac/Wiki):
* preferably with a static blog/page generator updated from a Git repo (e.g.: (Go)Jekyll, [HuGo](HuGo)) * preferably with a static blog/page generator updated from a Git repo (e.g.: (Go)Jekyll, Hugo)
* possibly with a LAMP stack as discussed: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3892> * possibly with a LAMP stack as discussed: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3892>
3. COULD be used to replace: 3. COULD be used to replace:
* [GitHub](GitHub) code hosting and review (pull request), keeping only a mirrored clone * Github code hosting and review (pull request), keeping only a mirrored clone
* [GitHub](GitHub) Actions (to avoid leaving secrets in environment variables) * Github Actions (to avoid leaving secrets in environment variables)
* Circle CI (to avoid giving them too many permissions) * Circle CI (to avoid giving them too many permissions)
### Inclusions ### Inclusions