Re reading this now on the ground in Austin, reminds me not to send emails in a hurry from an airplane! So trying again - hopefully more grammatically sound this time!
The Tech Engagement team (which includes Wikimedia Cloud Services) in the Tech department is investing in a developer advocacy team who I hope will (amongst other things) speak on behalf of the communities that are affected by tech debt. All the best, Victoria > On Mar 9, 2019, at 6:39 PM, Victoria Coleman <victo...@gocolemans.com> wrote: > > Also, the Tech team at the Foundation is investing in Technical Engagement > team who I hope will be (amongst other things) become advocates for the tech > debt that affects our communities. > > Best regards, > > Victoria > > Sent from my iPhone > >> On Mar 9, 2019, at 6:28 PM, bawolff <bawolff...@gmail.com> wrote: >> >> Regarding: >>> My proposal is to begin the discussion here: how can we better relay issues >>> that are more important to communities than new features? How can we have a >>> "community whishlist for bugs"? >> >> Well fundamentally it starts with making a list. >> >> This is basically a lobbying discussion right. People think WMF should do >> more of X. Lobbying discussions are more successful the more specific they >> are. Having a list of the top 20 worse bugs is something you could convince >> people to do something about. Even something like /WMF spends too much time >> on new features and not enough time on maintenance/bug fixing/, is >> something you could convince people to change, if you for example knew how >> much time WMF currently spends on bug fixing, and you have an idea of how >> much time you think they should be spending. Even if management doesn't >> agree with your proposal, it would at least be specific enough to debate. >> >> When these discussions start from vague places, like there's too many bugs, >> is when they go nowhere. Even if WMF stopped everything else it was doing, >> and worked solely on bugs, I doubt they would fix every bug in existence. >> (We can't all be TeX!), and attempting to do that would be a bad idea. >> >> Change happens when stuff is measurable, and people can work towards a >> goal. Failing that, change happens when people can be held accountable. >> Objective measures are needed. >> >> -- >> Brian >> >> >>> On Sat, Mar 9, 2019 at 10:31 PM Strainu <strain...@gmail.com> wrote: >>> >>> Dan, >>> >>> Thank you for your response. I appreciate far more someone disagreeing with >>> me than someone ignoring me :) >>> >>> Let me start with a simple question, to put the references to wmf into >>> context. You keep talking below about volunteer developers and how they can >>> take over any project. While that's true, how many fully-volunteer teams >>> are there? How does that number compare to the number of wmf teams? Am I >>> right to assume the ratio is hugely in favor of wmf teams? Note: teams, >>> not developers, since decisions on project management are usually done at >>> team level. >>> >>> Pe sâmbătă, 9 martie 2019, Dan Garry (Deskana) <djgw...@gmail.com> a >>> scris: >>> >>>>> On Sat, 9 Mar 2019 at 11:26, Strainu <strain...@gmail.com> wrote: >>>>> >>>>> How many successful commercial projects leave customer iss > > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
