- User Since
- Feb 7 2018, 3:41 PM (267 w, 6 d)
- LDAP User
- Kate Chapman
- MediaWiki User
- KChapman (WMF) [ Global Accounts ]
Nov 2 2022
Aug 10 2022
Jul 27 2022
Jul 25 2022
Hi all, after reviewing I'm going to approve this for restricted. @thcipriani is back tomorrow and can approve for deployment is that is what is needed.
May 25 2022
Mar 2 2022
Feb 28 2022
Feb 22 2022
Feb 14 2022
Jan 10 2022
Sep 13 2021
I think this is an excellent addition. As teams attempt to reduce Work in Progress (WIP) it would be great to have a status that allows them to see what is currently being worked on.
Aug 11 2021
@Pchelolo currently we are simply framing the problem, not the solution. In your statement are you saying you don't think there is an issue in not having a standard schema for clients to consume knowledge?
Jun 30 2021
Yes that is right @Aklapper that is accurate.
Apr 7 2021
@daniel I don't see why the Tech Decision process needs to be used for this.
Jan 8 2021
Could I be added to the Project-Admins group? I need to create components for the Architecture Team and the Technical Decision Making Process
Aug 6 2020
tagging Platform Engineering, I believe this also is an issue in Whats App
Jul 8 2020
I approve this :)
Jun 1 2020
May 22 2020
I don't have a proposed name, but I would suggest not binding this to MW.
May 13 2020
TechCom is placing this on Last Call ending on 27th of May.
Apr 13 2020
So the plan to move forward with this is for @JoeWalsh to collect stakeholder needs so the RFC becomes a specific implementation proposal. It is understood that performance and security are two key aspects of this and need to be considered in whatever is proposed.
Apr 10 2020
TechCom is hosting a meeting to discuss this on April 15th at 21:00 UTC in #wikimedia-office IRC channel
Mar 18 2020
TechCom approves this RFC with the understanding that a component library needs to be developed so use of Vue.js happens in a coordinated and reusable way. A migration path from OOUI needs to be included in this planning.
Mar 11 2020
Is there still a current specific product use case for this? That would help us evaluate if something generic vs. a specific implementation makes more sense.
Feb 19 2020
Adding CPT for visibility
Feb 12 2020
@Demian we don't believe this is a RFC so untagging TechCom
@jcrespo do you still want us to do the compression in T106386? Are the storage constraints still relevant?
Feb 3 2020
Jan 24 2020
Jan 9 2020
@egardner are you okay with this going on last call after the TechCom meeting next week?
Jan 8 2020
TechCom approved this RFC on 18 Dec 2019
Dec 20 2019
Nov 19 2019
Nov 13 2019
@daniel how big a project is re-architecting this? I moved to future initiative
@daniel would you be able to look at this at some point?
tagging Performance for @aaron to provide input into the proposal.
Untagging CPT, TechCom feel free to retag.
@Pchelolo this is also something that the FAWG is talking about as well. @santhosh and @daniel this might be of interest to you.
Believe this isn't a CPT thing doesn't belong in MW core should probably be a separate repo. We think this is a RelEng thing but we are happy to provide feedback if needed.
Nov 6 2019
Oct 30 2019
IRC meeting hosted on this on October 23rd:
TechCom approved this on October 23rd.
Oct 16 2019
I just wanted to mention this is something that the Platform Engineering is working on as part of our decoupling work. Not sure if that helps in finding a session leader. @daniel would be excellent but I don't think has the time.
Oct 9 2019
@osorio-juan-microsoft you are planning to look into the screenreader issue on your side? Thanks!
Oct 7 2019
Oct 1 2019
Sep 30 2019
@aaron are you requesting code review from Core Platform or do you need something else?
Sep 27 2019
Sep 17 2019
TechCom has approved this RFC.