Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • S sysadmin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • tails
  • sysadmin
  • Issues
  • #9174
Closed (moved) (moved)
Open
Issue created Apr 07, 2015 by sajolida@sajolidaReporter

Migrate our blueprints out of tails.git and tails.boum.org

Originally created by @sajolida on #9174 (Redmine)

We want to migrate our blueprints out of our main website and in their own ikiwiki. This will allow us to:

  • Be able to push more documents to our blueprints (images, office documents, etc.) without polluting our main repo.
  • Lock down all web editing on our main website.
  • Allow more people to push changes through Git.
  • Host our website on servers that we don’t trust to push to tails.git; ideally, N>1 servers to better resist DDoS (e.g. Tor’s pool of static webservers)

See https://lists.autistici.org/message/20150327.141615.36482193.en.html

Our main options are:

  • Migrate blueprints to a dedicated ikiwiki instance (blueprints.tails.boum.org)
  • Use GitLab’s wiki (#15878 (closed), https://docs.gitlab.com/ce/user/project/wiki/)

Benefits of using the GitLab wiki:

  • We can link to issues, MRs, commits, etc. using the GitLab link syntax
  • Links to issues and MRs are automatically annotated by GitLab with “(closed)”
  • We can manage access control with the same tools/workflow/policy as our other GitLab stuff
  • Arguably nicer user interface for editing pages
  • More powerful flavor of Markdown
  • Probably closer to what new contributors would expect / are used to

Benefits of using ikiwiki:

  • Historical contributors are used to it (whether they like it or not, is another matter, but at least they don’t have to learn anything new)
  • Content drafted on a blueprint can be seamlessly moved to our design doc (it does not rely on GitLab-specific syntax or features)

Probably obsolete subtasks

These subtasks assume we use a new, dedicated ikiwiki for blueprints. If we decide to instead use a GitLab wiki, they'll need to be adjusted:

  • #9175 (closed)
  • #9176 (closed)
  • #9178 (closed)
  • #9179 (closed)
  • #9180 (closed)
  • #9181 (closed)
  • tails#9182 (closed)

Related issues

  • Related to #15878 (closed)
  • Blocked by #14588 (closed)
Edited Oct 06, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking