Control AMIV wiki access

[temparus]

As of now, all groups have to be manually configured for access to the internal AMIV Wiki.
Most groups would need access to the wiki, so this is kind of silly work.

We could add a flag like restricted_access to the groups entity. This is kept very general and can be used by various tools only differentiating between active and passive member.

What do you think about that? @NotSpecial @hermannsblum @cburchert

[NotSpecial]

What again is the reason for not giving all amiv members access to the wiki?

This seems unnecessarily complicated.

[temparus]

Much content within the AMIV Wiki is not meant to be accessible to a broad audience like that, so it is necessary to have some fine-grained control.

We have a group «VSETH IT Strategie» for example. Those users should not have access to our wiki.

Information for all members can be found our website, so it is not required that every member has access to our complete knowledge found in the Wiki.

[NotSpecial]

As far as I understand, this is not an issue related to groups and rather affects members, correct?

As a results, would a has_wiki_access (or similar) key in /users not be more straightforward?

Or, regarding your concerns: The wiki could only allow access for AMIV members. Others can be part of groups like the VSETH IT Strategie, but as they are not AMIV members, they won't be able to access the wiki. So is a flag even needed?

[temparus]

Wiki access is tightly coupled with groups. Only people who need access to the wiki for their work in the association should be granted access.

Therefore it would be the most intuitive way to handle this on group level as they are most likely in a special group for mailing or cloud storage.

As an addition, we can make that only AMIV members can access the wiki as you suggested. But we do not want to give access to all of our members, so there is definitely another flag needed.

[NotSpecial]

I am still not sure why we shouldn't just give all members access to the wiki. Those that are really active in AMIV will use it and the others probably won't even be aware of it's existence.

AFAIK there are no passwords in the wiki anymore, right? And we could clean up the old user pages too, since that's now handled by the Q-Tool.
Aside from passwords (shouldn't be in the wiki) and personal info (doesn't need to be there anymore either), what information do we need to protect from "normal" AMIV members?

I would advocate for the simplest solution (access for all AMIV members) and make it more complicated only if absolutely necessary.

[temparus]

Well, there are surely some life hacks which should not be spread.

But apart from that, MediaWiki is not made for censorship. You surely can edit or delete a page with critical content. There will ever be a version history with that information in the database even from deleted pages.

So we can decide if we want to recreate the wiki database from a clean install or if we want to restrict access to the platform.

As a side note: This decision can not be made by us alone and some board members are strictly against this policy change.

[NotSpecial]

Mh, I see. I was not aware that this is a concrete policy. I always assumed wiki access was just handled this because we couldn't give members access automatically.

Therefore I thought we could use this chance to improve the current situation.

Maybe we should quickly discuss this issue in the next meeting.