Upgraded phabricator which fixed it.
May 29 2019
May 16 2019
Well, it seems to be working now. Whatever.
Depending on your email host, you can probably configure a filter so that all Miraheze emails are never marked as spam.
Upstream issue with your email host/Phabricator really.
May 15 2019
Dec 2 2018
This will be done with time.
Nov 4 2018
Added a topic in the noticeboard (https://meta.miraheze.org/wiki/Community_noticeboard#Documentation).
I’ve been a heavy critic of putting docs tasks on Phab. Best example is the hundreds of task on WMF (including a 12 year open task for this) and numerous elsewhere.
Oct 7 2018
Normal priority - no need to be low
Needs to be done by a Phabricator admin.
Sep 21 2018
Sep 11 2018
Sep 10 2018
Aug 22 2018
Thank you Reception and Amanda!
This can be done by any Phabricator administrator. And yes, you can freely edit the work board of your project (frankly, I think you can freely edit the work board of any project that you are a member of, but don’t quote me on that, and I’d strongly advise against doing that even if you can).
Jul 6 2018
Jul 5 2018
I'll do it.
May 28 2018
May 27 2018
Can only be done by ops
May 26 2018
Apr 7 2018
Feb 23 2018
Elasticsearch is definitely the best option, but not needed yet imho.
I'm still not convinced about the benefits of this. For new infrastructure there should be an identified benefit and identified user base and I don't think this really has either.
Feb 20 2018
Feb 18 2018
Jan 11 2018
PS: Emailbot is in ACL*Code of Conduct Commission to ensure task can be created. (Emailbot is "task author" when email is from unrecognized address. If known phabricator user sends a mail, unless they are in ACL*Code of Conduct Commission, it will be refused but still sent to CoC because cocc alias. Commission member will need to manually create the task. (No upstream task but phab support to OSS project is weak (if not none), I can assume they will close this as WONTFIX.)
Jan 10 2018
Jan 8 2018
Hi, pull requests are accepted on GitHub. Puppet repo in phab is for redundancy, and having it closing the bugs as appropriate (which... didn't work as intended for now).
Jan 3 2018
Jan 1 2018
ShortWiki account has been disabled.
Dec 31 2017
@Unad321 Do you have a valid reason for why you really need it deleted and not just disabled?
I would personally not want to delete, unless there is a valid reason. Would a disable really not be enough?
Dec 4 2017
Nov 26 2017
Parsoid, Collection and ES are all memory/cpu heavy services. Hosting them all on a small memory server seems a) unwise b) unreliable.
I think the best course of action in this case would be to expand our current parsoid1 server and make it a misc3. We could host Elasticsearch and Collection there.
Oct 30 2017
Oct 27 2017
Oct 23 2017
Now 4 days left, something needs to be done ASAP!
Oct 16 2017
Oct 14 2017
I am guessing that the user permissions set on where the repo's are located are different from the user set in the phab's config.
Oct 13 2017
Same issue resurfaces now.
Oct 12 2017
I believe Phabricator admins can do this so it's not limited to NDK
Oct 8 2017
Sep 14 2017
Sep 11 2017
Aug 27 2017
Aug 25 2017
Aug 23 2017
Nothing upstream on the repo. Re-open when something of value can be mirrored.
Aug 14 2017
Is this resolved?