Page MenuHomePhabricator

CentralNotice backend improvements
Open, MediumPublic


We need to decide on the CentralNotice backend improvements RfC.

Event Timeline

Qgil raised the priority of this task from to High.
Qgil updated the task description. (Show Details)
Qgil added a project: Architecture.
Qgil changed Security from none to None.
Qgil moved this task from Inbox to Ready to Go on the Architecture board.
Qgil subscribed.

This RfC will be discussed in the next rfC meeting on Wednesday 24 at 21:00 UTC:

Qgil lowered the priority of this task from High to Medium.Sep 25 2014, 12:20 PM

Meeting logs.

Spage subscribed.

@K4-713 what's up, is anyone on your team working on this? If so could you comment here, and on the #mw-rfcs workboard move it to "under discussion"

@Nemo_bis suggested this RfC for our meeting on Wednesday (E66). He says this is "the most interesting right now if the maintainers are available, as there is momentum right now: a refactor was just deployed successfully and no big fundraising centralnotice campaigns are planned for September."

I'm a bit skeptical that this one is the best choice, but let's take that discussion over to E66.

kchapman subscribed.

Not cross cutting so doesn't need RFC

@K4-713: Resetting the assignee of this task because there has not been progress lately (please correct me if I am wrong!).
Resetting the assignee avoids the impression that somebody is already working on this task. It also allows others to potentially work towards fixing this task.
Please claim this task again when you plan to work on it (via Add Action...Assign / Claim in the dropdown menu) - thanks!

Krinkle renamed this task from RfC: CentralNotice backend improvements to CentralNotice backend improvements.Apr 3 2020, 9:32 PM