I'm really liking the idea of the triage meetings for VisualEditor. I sat in on the last one and look forward to the next. As a third-party user/admin it's a great way to be involved and provide insight into the decision making process. Are there plans for the other WMF-led projects to do the same? Echo, MobileFrontend, CirrusSearch, Flow, etc?
If not, how could someone outside, such as myself, propose such a thing?
Thanks for the feedback.
I don't know about other teams' plans, but yes, I think that could be a good move. I worry a bit that it'd be over-whelming to have e.g. ten weekly public meetings, though – if I'm a volunteer and interested in a bunch of different things, do I just have to pick the ones I can do? If they're rotating the times at which they're occurring, who gets to go first, etc.?
Echo, MobileFrontend per se (it's complicated) and CirrusSearch aren't active under development currently (just maintenance), but Flow certainly is – for that, you should ask User:DHorn (WMF).
Other user-facing projects underway which might want to do this are:
There's also Wikidata itself, led by User:Lydia Pintscher (WMDE), and several less user-facing projects – the Wikidata Query Service, front-end standardisation work, the continuous integration workstream, the general Platform backlog and several others.
I am always happy to have help with triaging Wikidata bugs :) I currently do not have the time however to do regular triage sessions on IRC myself. If you want to talk more and help please do reach out.
Hello, we stopped with the IRC triage sessions due to a lack of time and audience. Its an ongoing process for us so triages do happen all the time. We'd be happy to hold similar sessions in future (not immediate). Until that time, if there is enough interest we can make it a part of the office hour that happens every month. Thanks for the suggestion.
Ckoerner, thank you for that feedback - we are considering building meetings like this or similar into the product development lifecycle and need to look into ways of making it scalable in terms of the technology used (Webex vs. GHangout vs. Hangout on Air). Certainly, checking with other teams to see where they're at and whether they're able to accommodate these meetings are a great idea - I can imagine it might not always be useful to do so, but there are other mechanisms that can be used to give more insight into the decision making and development process :)
