Task to follow the progress of the Architecture RfC CentralNotice Caching Overhaul - Frontend Proxy.
See also the RFC discussion on IRC on 2014-07-30.
Description
Description
Details
Details
- Reference
- fl532
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | AndyRussG | T347 RfC: CentralNotice Caching Overhaul - Frontend Proxy | |||
| Resolved | bd808 | T350 Get repo renamed from mw/core/vendor to mw/vendor | |||
| Duplicate | None | T348 Timeline needed/expected on the CentralNotice Caching Overhaul RfC | |||
| Resolved | • csteipp | T349 Security update planning re Composer managed libraries for use on WMF cluster | |||
| Resolved | • csteipp | T74193 Have a check for reported security issues in dependencies |
Event Timeline
Comment Actions
qgil wrote on 2014-08-14 13:25:28 (UTC)
I have created the subtasks related to this RfC following the last RfC meeting notes, although I'm not 100% certain of the relation of all these subtasks with this RfC. Please have a look.
Comment Actions
@K4-713 what's up, ArchCom thought maybe @AndyRussG is working on this? If so could you comment here, and on the #mw-rfcs workboard move it to "under discussion" If you agree about merging with T468, do so.
Comment Actions
Hi! Some of the issues in this RfC have changed, but we still have on the table the idea of merging this with T468 as part of a new RfC to get input for a medium/long-term CentralNotice roadmap and scope out more requirements (as was more or less agreed at the end of the last RfC meetng on CentralNotice). Thanks!
Comment Actions
OK. I'm assigning this task to AndyRussG, feel free to assign it to a manager. I merged T348: Timeline needed/expected on the CentralNotice Caching Overhaul RfC since it's only about timing.
Comment Actions
Closing old RFC that is not yet on to our 2020 process and does not appear to have an active owner. Feel free to re-open with our template or file a new one when that changes.