Hacker News new | ask | show | jobs
by eudaemon 1094 days ago
Particularly at this point, I'd like to see better communication between the board and wiki members/crats/admins. No news has been the rule with Miraheze except for planned service outages and donation requests. The way I found out about the closure announcement was from a Tweet that rides in with a 503 error message. I know it's early days, but a message about proposing to continue Miraheze would be useful on that platform, yes?
1 comments

No communication is standard operating procedure right now. Volunteers found out this decision at the same time as everyone else, which meant no one had time to prepare.

We need to better communicate our plans and goals, and of course about downtime. But we also don’t want to flood average wiki users with sitenotices either. What kinds of communication would you like to see more of?

I will put out a sitenotice soon, but I need the outgoing board to buy-in first. Which I’m hoping will happen in the next few hours.

Sitenotice is up. Thank you.

RE:communications I'd like to see more of.

1. The shutdown notice would have been one; important news, instead of only posting on Twitter and other social media. After a few tweets like "30,000 wikis!" (not all active, ahem), this just turns into noise.

2. Decisions made by the board. A summary will do.

3. Current or ongoing technical issues. Or do we have to go through the whole of outstanding Phabricator tasks?

This communication can be accomplished by subscription. I would then like to see a notification/bell made with a capsule of what's being shared and its location within the Miraheze maze.

On other business, check out Lithuania as a possible location. It's a very tech-oriented country, and I've worked on a MediaWiki-based wiki based there. I don't know the specific server farm or company.