In the past, we were often told that a specific proposal even if it gains
enough support will not be implemented because this is too difficult / not
enough resources / whatever. My understanding is that it does not make
sense to suggest such proposals again. On the contrary, if the proposal
gained
I asked on th talk page, but posting here as well:
-- what's the intended interaction b/t proposals from past years and the
current list? Do people need to find and repost older proposals they want
to see included? Is there a mechanism for refactoring sets of related
proposals?
🌍🌏🌎🌑
On Sat., Jan
Hello, I'd like to refer to the original subject of the discussion -
tomorrow is the last day for submitting proposals for the Community
Wishlist Survey 2022.
Apart from that, everyone is welcome to translate, promote, and discuss
proposals:
https://diff.wikimedia.org/2022/01/10/what-improvements-
În mar., 11 ian. 2022 la 08:01, Kunal Mehta a scris:
>
> So I think the status quo can be changed by just about anyone who is
> motivated to do so, not by trying to convince the WMF to change its
> prioritization, but just by doing the work. We should be empowering
> those people rather than conti
Amir
you raise a good point how do things get into the next budget, the simple
answer is first to have people/teams responsible for each of the projects.
Having someone accountable stops the ball being dropped as easily, it means
WMF starts looking at needs on longer timetables. We've seen this wi
(Speaking in my volunteer capacity)
I doubt there is any malicious intent by WMF. I personally think the
underlying problem is time. Let me explain.
Fixing a big issue in software takes time (I wrote a long essay about it in
this thread) so it makes sense WMF annual planning to focus on issues
bef
