Re: [Wikitech-l] ArchCom Monutes, News, and Outlook

Hi, On 03/15/2017 03:58 PM, Gabriel Wicke wrote: > Thanks for everyone who participated in the discussion. Unfortunately, we > ran into a technical issue with setting up the youtube stream that we > weren't able to resolve quickly (my apologies to those unable to follow the > stream), but we did

Re: [Wikitech-l] ArchCom Monutes, News, and Outlook

Thanks for everyone who participated in the discussion. Unfortunately, we ran into a technical issue with setting up the youtube stream that we weren't able to resolve quickly (my apologies to those unable to follow the stream), but we did take detailed notes

Re: [Wikitech-l] ArchCom Monutes, News, and Outlook

Reminder: this is about to start in a couple of minutes. - What: High level mobile frontend requirements & plans - Agenda / discussion notes - When: March 15, 2-3pm PDT (San Francisco) -

[Wikitech-l] Please join the movement strategy conversation (now through April 15)

Dear Wikimedians, If you are a representative of an Affiliate, committee, or other organized group in the Wikimedia Movement, please read this email carefully and forward it to your peers. I am writing you today in my role as the Movement Strategy Lead for organized groups (Track A), and would

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

Derk-Jan On Wed, Mar 15, 2017 at 12:29 PM, you wrote: > You mean like here: https://www.mediawiki.org/wiki/Roadmap ? > No, because that page is not a roadmap but a list of pages none of which is a roadmap in the sense I stated. > Where it is already posting it's annual and quarterly plans to

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

A biennial planning process makes a lot of sense, so long as transparency and accountability is not lost. In the planning year, the most resource efficient way of doing this stuff is to make strategy and operations 6 months out of phase, ensuring that the management and executive don't exhaust

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

Derk-Jan On Wed, Mar 15, 2017 at 12:29 PM, you wrote: > You mean like here: https://www.mediawiki.org/wiki/Roadmap ? > No, because that page is not a roadmap but a list of pages none of which is a roadmap in the sense I stated, and I rather think you knew that when you referrd to it. > Where

[Wikitech-l] 2017-03-15 Scrum of Scrums meeting notes

https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-03-15 = 2017-03-15= contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering == Call outs == * QUnit failures with Jenkins (ie https://phabricator.wikimedia.org/T153038 ) is poping up time-to-time. Some more eyes are needed. * DBAs

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

For what it's worth, my understanding is that WMF is considering transitioning portions of its annual planning to biannual planning. Also, I think that it will be easier to develop a long term technical roadmap after WMF completes its strategy update. Pine On Wed, Mar 15, 2017 at 12:19 AM,

[Wikitech-l] Fwd: [Wikimedia-l] Product draft goals posted on mediawiki

Forwarding. Pine -- Forwarded message -- From: Toby Negrin Date: Wed, Mar 15, 2017 at 7:50 AM Subject: [Wikimedia-l] Product draft goals posted on mediawiki To: Wikimedia Mailing List Hi everyone -- I wanted to let you

[Wikitech-l] GSOC'17/Outreachy'14: Mentor needed for software design and code review guidance

There are a few prospective students interested in working on the Single Image Batch Upload project. We've recruited two mentors already @basvb and @capt_swing (on Phabricator), but we still need a mentor who could provide software design guidance and

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

You mean like here: https://www.mediawiki.org/wiki/Roadmap ? Where it is already posting it's annual and quarterly plans to as much detail as anyone is able to predict a roadmap ? No one from community is discussing it (at least other than those already discussing it before). This 'community

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

A good way of avoiding clashes would be to publish the technical roadmap showing where WMF expects to be taking its technical development over the next five years or so, for the community to discuss and comment on I have yet to hear any reason why this can not or should not be done. "Rogol" On