HSNWiki:Migration from Gitwiki

This page describes the status of our migration from Gitwiki to MediaWiki.

Many of the items on this page are based on the MediaWiki discussion group on 30 January 2019. See the e-mail to the list for details.

Use ✓ for "done", ❌ for "not done".

Settings

• ✓ MediaWiki Installation
• ✓ Allow account creation
• ❌ Add a nice WYSIWYG editor for pages
  • The page above votes to install VisualEditor, the same plugin Wikipedia uses; it still needs to be installed
• ❌ Require manual approval for making accounts
• ❌ Allow sending e-mail from wiki
• ❌ Make a privacy policy (see the e-mail of 30 Jan 2019)
• ✓ Add Github etc. links to the sidebar
• ❌ Other extensions we'd like to see
• ❌ Make a Wiki bot that reports changes to IRC (#hsnijmegen or #hsnwiki)

Settings, if possible?

• ❌ How to make some pages public, some pages private?
• ❌ Can we configure specific accounts to require explicit approval for all changes to pages, while others can change any page without needing approval?
  • "to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace)."
• ❌ Can we show edit history of pages only to logged-in accounts?
• ❌ Can we make user information visible only to logged in accounts? (Could be done by making the user pages private.)
• ❌ Make a calendar/agenda containing all events on the wiki
• ❌ Make an auto-generated index of all pages on the home page?

Theming

• ❌ @Joep to find some nice mediawiki themes to base our theme upon.
• ❌ Together with him, @Robert to take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
• ❌ @Sjors will give them access to the current installation to experiment with how it looks.
• ❌ @Michiel to send graphics to @Joep and @Robert.

Backups

• ❌ @Sjors to make local backups on the VM for now.

Page migration

All pages to migrate:

• ✓ README.md (empty page)
• ✓ docs/budgets.md
• ✓ docs/callforparticipation.md
• ✓ docs/statuten.md
• ✓ docs/knittingmachine.md (added into Knitting Machine to laptop)
• ❌ docs/projects/ProjectOne/planning.md
• ❌ docs/projects/ProjectOne/MiniRCHovercrafts.md
• ❌ docs/projects/ProjectOne/proposals.md
• ❌ docs/projects/ProjectOne/index.md
• ❌ docs/projects/lasercutter.md
• ✓ docs/projects/knittingmachine.md
• ❌ docs/projects/anonycaster.md
• ❌ docs/projects/musicplayer.md
• ✓ docs/contact.md
• ✓ docs/minutes/2018-2.md
• ✓ docs/minutes/2018-1.md
• ✓ docs/index.md
• ✓ docs/contributing.md
• ✓ docs/wishlist.md
• ✓ docs/events/ctfnight.md
• ❌ docs/events/workshops/kicad101.md
• ✓ docs/events/workshops/whatdoesitdo.md
• ❌ docs/events/workshops/propertytesting.md
• ❌ docs/events/workshops/signal_intergrity.md
• ❌ docs/events/workshops/3dprintergettingstarted.md
• ❌ docs/events/workshops/pcbmilling.md
• ✓ docs/events/hack42_on_tour.md
• ✓ docs/events/movienight.md
• ✓ docs/events/boardgamenight.md
• ✓ docs/events/christmas_dinner.md
• ✓ docs/events/openday2018.md
• ✓ docs/spaceopening.md
• ✓ docs/about.md
• ✓ docs/openingparty.md
• ✓ docs/naming.md
• ✓ docs/empty.md (empty page)
• ✓ docs/pcbmilling.md

Hostname + SSL

• ✓ Old wiki is down.
• ❌ Link wiki.hackerspacenijmegen.nl to this wiki.
• ❌ Make SSL certificate.

Discussion group e-mail

Hi all,

With thanks to everyone who attended, I would like to give an update on the consensus reached by the Wiki discussion group of today: me, Sjoerd, Robert, Ed, Joep, Michiel and Natalia.

First, a call to everyone: if you want to help migrating data from gitwiki to mediawiki, we are doing that next week Tuesday (5 feb) probably around 21:30 again. We'll be done quickly, but if you'd like to help, come and join in!

The decision for Mediawiki, as a result of the poll, was affirmed again by the group.

We reached consensus on these topics:
- Who will be able to read the wiki?
- Who will be able to change the wiki?
- Default license of wiki contents
- Privacy / personal information protection
- Theme / house style
- Paying for the hosting
- Backups
- Wanted additions, advantages and disadvantages over the gitwiki
- Migrating data
- Version maintenance / security updates

Here it goes:

- Who will be able to read the wiki?
We often have project information that we would like to share with the world.
We also have information that we would like to keep private to the wiki.
@Sjors to investigate how to configure Mediawiki to have some pages public, some pages private.
Private means only visible to created accounts (or only to hackerspace members, could be a difference, that is undecided).

- Who will be able to change the wiki?
We see the advantage of allowing people interested in a project to contribute information sometimes. But, we need to control these changes, because:
* We want to control spam,
* We want to prevent outsiders dumping illegal stuff on our wiki,
* Project owners may not want anyone to contribute to their wiki page.
Wikipedia allows editing by the world, but they have lots of volunteers to monitor this and we don't.
We require an account to the wiki before people can make changes. We can then make it arbitrarily difficult to create an account based on experiences. To begin with, anyone who asks for approval on IRC can get an account to make edits, even outsiders to the hackerspace. To begin with, these account holders can also see private information on the wiki, until someone triggers a case where this is unwanted and then we re-evaluate.
@Sjors to check whether Mediawiki has a filter to detect 'nonparliamentary words' (eg swear words) in edits, to see if this helps finding abuse.

- License
Sjors chose CC BY-SA as a default. There were no objections to this. People can indicate an alternative license on their own project pages.

- Privacy / personal information protection
We want to be GDPR compliant.
We try to minimize our storage of identifiable/user information, so we do not store IP addresses.
People can enter their e-mail address into the system for notifications, but we do not show it.
All other user information is optional, and user is informed that it may be shown during registration.
We make a privacy policy, and when users register for an account, they explicitly say they will live by it too. It contains at least:
- edit history is kept and remains visible,
- arbitrary account holders can read private pages,
- a point of contact for complaints.
We need to be able to "absolutely" rollback changes (e.g. containing private data), without them being visible in edit history.
@Sjors to check whether there is an extension that allows moderators to need to "approve" changes from some accounts (e.g. outsiders of the hackerspace).
@Sjors to check whether it's possible to show edit history only to logged in accounts.
@Sjors to check whether we can make user information visible only to logged in accounts (could be done by making the user pages private).

- Theming
@Joep will find some nice mediawiki themes to base our theme upon.
Together with him, @Robert will take a look at whether we can theme our wiki (based on an existing one) a bit in our house style, including a logo.
@Sjors will give them access to the current installation to experiment with how it looks.
@Michiel to send graphics to @Joep and @Robert.

- Paying for hosting
The current Wiki installation is hosted on a VM donated by SA007, in his atomic bunker, with triple redundant internet and double redundant power. The installation is then inside Docker, made to be easily movable between machines.
We see an advantage in having it hosted at a more neutral location where multiple people have physical access, but there is a price to it.
Currently, Foundation does not pay for anything other than rent and internet.
This is an active discussion within the board.
The Wiki discussion group advises the foundation board to pull "services for everyone", such as the website and domain into this "general budget", meaning monthly prices will go up.
The Wiki discussion group also advises the foundation board to include the Wiki in this "services for everyone" group.
For now, we agree that hosting with Bas is fine, and when the foundation board has made a decision regarding this we will re-evaluate.

- Backups
When we move hosting providers, could be done by the provider then.
For the time the Wiki is hosted with Bas, we perform local Docker backups on the VM only, not offsite. We will rediscuss when we change hosting location.

- Wanted features, advantages/disadvantages of gitwiki
@Sjors will look whether there is a calendar/agenda extension, which could host an .ics file based on event pages that exist on the wiki.
Gitwiki had a nice summary of all pages (manually edited). @Sjors to see if Mediawiki has an extension for that, or otherwise we would try to keep that manually updated.

- Migrating data
We will do it manually, because markup needs to be changed. We will do it sitting physically together because it is convenient to hand out pages then.
Avel, Joep and Sjors to sit together on Tuesday 5 feb, others welcome too.
For now, all content on old and new wiki is public, until we've established how to make a part of it private.
We will swap hostnames when the migration is done.

- Maintenance / security updates
Sjors will be subscribed to Mediawiki security updates and will apply upgrades as necessary.
In the future, we will need two admins to take care of this.
We could have a "service patch policy" and the wiki would be the first thing to implement it.
We will rediscuss when we change hosting locations.

- WVTTK
Joep wants to have more meetings like this.
Michiel wants to plan a movie night!
Ed wants to plan a synthesizer night!

Meeting closed.