Short-cut answer to the title question: Me.
On 9 December 2015 at 10:26, Brad Jorsch (Anomie) bjorsch@wikimedia.org wrote:
On Sun, Dec 6, 2015 at 7:30 PM, Bartosz Dziewoński matma.rex@gmail.com wrote:
On 2015-12-04 18:59, Adam Baso wrote:
I do wonder though if we've spent much time studying the ease of getting at least some part of oojs-ui split out or making it so that new stuff
going
forward is part of the oojs-ui family but it's not as monolithich?
Not any more than what is written at < https://phabricator.wikimedia.org/T113681#1673158%3E, as far as I know.
OOjs UI doesn't have a dedicated team (or even a dedicated person) supporting it. The changes are mostly driven by whatever the VisualEditor or Design teams need, and what they are willing to implement themselves (and to a lesser extent, Multimedia team and random people like Brad or Florian). This makes it difficult to make any big changes happen.
If OOjs UI is the thing that we're supposed to be using in the future for our UI stuff, it's very concerning that further development is blocked on T113681
"Further development" is not blocked on this task. A few things that some people want to do are. Please do not exaggerate for effect to try to get your way. I'm sorry that we disagree as to whether your patch belongs in the library in its current form.
but no one is planning on working on that task or feels ownership for the thing.
The value-add of doing that accrues to the people currently not using OOUI. The work is, and has always been, a group effort by engineers, designers and product people making our front-end architecture more sane and consistent. Responsibility for change lies with those that want it and can justify the time, mostly. This is the same model as used for most shared things around MediaWiki. The passion, care and effort from volunteer and staff developers that goes into improving the library as people extend its use to more places is great. I'd love for there to be dedicated engineers to support the use of OOUI, but however.
Is someone going to step up to actually own and maintain the thing?
I am, and remain, the product owner responsible since 2012. The plan was to transfer the product/design side of it entirely to Volker, but we've not formally 'handed over the keys' yet. It doesn't appear that there's a particular rush, given the lack of movement to re-do how skins in MediaWiki work, as had been the ambition in 2013.
[Trim the rest.]
J.