Hacker News new | ask | show | jobs
by prepend 1931 days ago
I had the same problem and tried a bunch of stuff (mediawiki, confluence, GitHub wiki, gitlab wiki, shared drive, Wordpress, SharePoint) and currently just use GitLab pages because the fork/merge flow for markdown was easier than trying to grant access and moderate a wiki.

It’s still easy to solicit edits, but the issue/question flow is helpful, and have some review process seems to help. Lots of people struggle with git mental models, even using the built in browser IDE in GitLab and GitHub. But most engineers seem to be able to handle.
1 comments
pwdisswordfish0 1931 days ago
Conjecture: almost every belief that your wiki needs support for ACLs and needs to be moderated (for any reason other than spam) is a belief that's wrong from the start. (And it should be a criminal offense the way that GitHub and GitLab to have corrupted the word "wiki" to be understood to include PR- and review-based workflows centered around big collections of offline source files—the very practice that the wiki was created in reaction to, as a means to solve the problems inherent to that workflow.)
link
prepend 1931 days ago
GitHub and GitLab have a wiki feature that is a sort of crappy wiki with no merge requests.

The problem is that wikis can’t be globally editable without license events so in order to edit the wiki you need permissions on the project.

The PR flow is for the non-wiki where there’s just files in a repo that only active project users can edit but anyone can fork and PR.

So it’s a lot easier administratively than trying to grant everyone edit permissions on a repo just to edit a wiki.

If there was a decent wiki product I would love to run it and just have every staff member with edit permissions. But that’s the dilemma.

link
pwdisswordfish0 1931 days ago
> The problem is that wikis can’t be globally editable without license events

What does this mean?

> If there was a decent wiki product

Like Mediawiki.

link