Hoi,

Only Pallas Athena arrived fully mature in armour from the head of Zeus. We will never have a complete plan when all we do is based on the existence of budgets, it failed us miserably. The way forward is to own our infra structure including all software and decide its worth, its risc and if we must have a huge budget for "unexpected" and use it to prevent and mitigate the breakage of user stories.

It is not fair to blame only any CEO, it is fair to expect from a CEO to acknowledge that only working from budgets gets us in the mess we face. We are a community with differing needs, so explaining urgency in the form of user stories really helps.

Thanks,

Gerard

On Sun, 2 Jan 2022 at 22:09, Asaf Bartov <asaf.bartov@gmail.com> wrote:

Yes, I did not purport to offer an easy solution. I tried to clarify *what needs to happen* for significant progress on these issues, without suggesting that it is easy to make that happen.

As I mentioned, a new CEO is beginning work this week, and one of the (many) items on her to-do list is to improve and rationalize the Foundation's annual planning process, and cross-departmental planning and decision-making. Let's give her some time and wait for some guidance on this question of venue, i.e. how and where communities may *effectively* express needs and affect priorities.

In the meantime, I repeat my suggestion that adding non-technical concise statements of impact to each issue would be a big help. For example, I (and many of you) know the impact of our slow/broken video conversion and upload workflows, but it would be helpful to add to SJ's "Bulk conversion for video uploads (videoconverter / video2commons are broken)" an impact statement such as "this is deterring video uploads from casual contributors".

Cheers,

A.
(volunteer capacity)

On Sun, Jan 2, 2022 at 10:45 PM Samuel Klein <meta.sj@gmail.com> wrote:
I appreciate all of the comments; still unsure where to more persistently host the conversation, but for now I posted this still-arbitrary list on Commons. (adding other items mentioned in this thread) SJ

~~~~
- File formats: Support high-demand formats – e.g. CSV, CML, + hundreds of other open tickets
- Uploads: Improve bulk, large, and video uploads.
+ Bulk conversion for video uploads (videoconverter / video2commons are broken)
+ Upload Wizard upgrades (timeouts, batch renaming, batch imports)
- Downloads: Fix multi-download (Imker is broken)
+ Make public dumps (stale since 2013)
- Video playback: Debug + roll out the videojs player
- Search: Bring CQS back up. Implement a noauth option for tools
- General: Move to a blazegraph alternative (for wqcs)
+ Images: Update thumbor and librsvg ||  redesign the image table
- Curation: Simpler content assessment workflow, like en:wp's (QI/VP doesn't scale)

_______________________________________________
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/FVA4YJN5OHPRSLACPXYD4XITFG7NNKSL/
To unsubscribe send an email to wikimedia-l-leave@lists.wikimedia.org

--
Asaf Bartov <asaf.bartov@gmail.com>
_______________________________________________
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/5CTLTK3I46B4OOPEBY6RYVKYJMMZ4JZO/
To unsubscribe send an email to wikimedia-l-leave@lists.wikimedia.org