We need to decide on the CentralNotice backend improvements RfC.
Description
Related Objects
- Mentioned In
- T313004: Cold cache page view to metawiki times out then fails with OOM in timeout handler
E187: RFC Meeting: triage meeting (2016-05-25, #wikimedia-office)
T125865: Assign RFCs to ArchCom shepherds
E66: ArchCom RFC Meeting Wxx: <topic TBD> (<see "Starts" field>, #wikimedia-office)
T347: RfC: CentralNotice Caching Overhaul - Frontend Proxy - Mentioned Here
- E66: ArchCom RFC Meeting Wxx: <topic TBD> (<see "Starts" field>, #wikimedia-office)
T347: RfC: CentralNotice Caching Overhaul - Frontend Proxy
Event Timeline
This RfC will be discussed in the next rfC meeting on Wednesday 24 at 21:00 UTC: https://lists.wikimedia.org/pipermail/wikitech-l/2014-September/078698.html
- https://www.mediawiki.org/wiki/Requests_for_comment/CentralNotice_backend_improvements (TimStarling, 21:35:37)
- bundle banner dependencies to avoid startup module bloat (TimStarling, 21:44:28)
- let's expand the CN RFCs, possibly merge them, try to get all the requirements pinned down (TimStarling, 21:54:16)
- TimStarling not volunteering to do implementation work (TimStarling, 21:54:30)
- implementation will not commence before January (TimStarling, 21:58:08)
- Krinkle would like to still serve banners as a single blob of HTML (TimStarling, 22:02:35)
- https://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates (TimStarling, 22:08:23)
@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.
@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!