Re: [Wikitech-l] FOSS OPW Mentor Contact
Replied. Thanks. On Thu, Oct 16, 2014 at 4:42 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Hello, The MediaWiki Core Team is having an offsite this week. They are mostly spending their time in discussion with closed laptops. I will make sure to pass your message on to Ori as soon as meetings end today. Thanks for your understanding! Rachel On Thu, Oct 16, 2014 at 4:35 PM, Brian Wolff bawo...@gmail.com wrote: On Oct 16, 2014 7:02 PM, E.C Okpo eco...@gmail.com wrote: Hello, I am working on my application for the FOSS Outreach Program, but I am having some trouble getting in contact with the mentor for my chose project - Ori Livneh https://www.mediawiki.org/wiki/User:Ori.livneh. I have idled on IRC for quite a while trying to get in contact, but no luck. Would anyone know of an alternate means of contact? Thanks, Christy https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_9#Wikimedia_Performance_portal ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l Isnt there some giant meeting today and tomorrow of wmf platform people? Maybe try again on monday? Otherwise i would suggest email. You can email him by using Special:emailuser on wiki, or find his email by looking it up in git, gerrit, bugzilla or old mailing list posts. (There is a good chance he may even be reading this) --bawolff ___ 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 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Now you can submit / claim Engineering Community tasks
Wouldn't be better to have nested projects? GsoC might need a project per year with subprojects for each student to manage their task, is project nesting possible on Phabricator? And what about sister projects? Will each one have a project? Thanks Micru On Wed, Oct 22, 2014 at 3:45 AM, Quim Gil q...@wikimedia.org wrote: Following the activity of the Engineering Community team has never been simple, not even for ourselves. Proposing Engineering Community tasks effectively was even more complex. Here is an attempt to change this: https://phabricator.wikimedia.org/tag/engineering-community/ Since the beginning of this month, we are using Phabricator to organize the Engineering Community team work. https://phabricator.wikimedia.org/tag/ect-october-2014/board/ You can watch, comment, and get involved. You can also submit and claim tasks. What should we be working on next month? How can we facilitate more tech community work done by more people? See you there. -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Etiamsi omnes, ego non ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Now you can submit / claim Engineering Community tasks
Hi Micru, On Wed, 2014-10-22 at 11:45 +0200, David Cuenca wrote: Wouldn't be better to have nested projects? GsoC might need a project per year with subprojects for each student to manage their task, is project nesting possible on Phabricator? Subprojects are not (yet) supported in Phabricator. Upstream ticket: https://secure.phabricator.com/T3670 And what about sister projects? Will each one have a project? A task in Phabricator can have between zero and unlimited associated projects. (This is different from Bugzilla where a ticket must have exactly one product and exactly one component.) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Now you can submit / claim Engineering Community tasks
On Wed, Oct 22, 2014 at 4:53 AM, Andre Klapper aklap...@wikimedia.org wrote: Hi Micru, On Wed, 2014-10-22 at 11:45 +0200, David Cuenca wrote: Wouldn't be better to have nested projects? GsoC might need a project per year with subprojects for each student to manage their task, is project nesting possible on Phabricator? What you are proposing is exactly what we plan to do right now with FOSS OPW Round 9 projects (deadline for submissions: today). https://phabricator.wikimedia.org/T564 Subprojects are not (yet) supported in Phabricator. Upstream ticket: https://secure.phabricator.com/T3670 Tagging describes Phabricator projects a lot better than nesting. In Phabricator, projects are tags and tags are projects. This means that even if the subproject concept is officially missing today, you can organize your work in a similar way. And what about sister projects? Will each one have a project? A task in Phabricator can have between zero and unlimited associated projects. (This is different from Bugzilla where a ticket must have exactly one product and exactly one component.) Exactly. If sister projects want to have Phabricator projects, they could have them. But there us hundreds of them, so we better coordinate first. David, thank you for providing a good excuse to create this task: https://phabricator.wikimedia.org/T802 See you there! ;) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Now you can submit / claim Engineering Community tasks
On Wed, Oct 22, 2014 at 3:31 PM, Quim Gil q...@wikimedia.org wrote: Tagging describes Phabricator projects a lot better than nesting. In Phabricator, projects are tags and tags are projects. This means that even if the subproject concept is officially missing today, you can organize your work in a similar way. I partially agree, but just *partially* :) Tagging is just a poor man's version of classing, since it doesn't let you define the relationship between tags. True that you can put any task in several projects/tags, the problem is that the project structure is nevertheless flat: https://phabricator.wikimedia.org/project/query/all/ Which will become cumbersome to navigate for occasional visitors as the number of projects goes up. Exactly. If sister projects want to have Phabricator projects, they could have them. But there us hundreds of them, so we better coordinate first. David, thank you for providing a good excuse to create this task: Hundreds of them? :D Last time I checked there were between 1 and 12 sisters projects, depending on whom you ask. But if you meant to create projects for each language version of each sister project, then I agree that it would be too much. OTOH, with a proper organization it could be innovative to manage far-reaching content projects through phabricator ;) Cheers, Micru ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Introduction for OPW Round 9
Hi everyone! My Name is Neta Livneh and I am a PhD Student in the Hebrew University of Jerusalem, doing my research the field of computational social science. I am applying to the FOSS Outreach Program for Women round 9 to work on the interesting project Wikipedia article translation metrics. I have a background in data analysis, a bit of machine learning skills and a lot of motivation to find some a way to pinpoint translated articles in Wikipedia. If you want to help or guide just interested in hearing more about the project, please contact me. Cheers, Neta ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] OPW 9 Proposal : Pywikibot - Compat to core migration.
Hi! I am Priyanka Jayaswal and I am willing to contribute towards Compat to core migration for FOSS Outreach Program for Women - Round 9. I have selected a mentorship project from Project list https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects named Pywikibot to resolve it's issue on Compat to core Migration. I have been in contact with mentor John Vandenberg and we have proposed a rough proposal based on our discussions and thoughts. Further information about the project has been provided on the Proposal page: https://upload.wikimedia.org/wikipedia/mediawiki/0/01/ProposalPywikibot-CompattoCoreMigration.pdf Link for wiki proposal page may be found in : https://www.mediawiki.org/wiki/User:Prianka . We need community's valuable suggestions to improve the proposal, add possible features, and views on the project so that this project can be success. Thanks ! -- *Priyanka Jayaswal* Third Year Undergraduate Student Department of Mathematics Indian Institute of Technology, Kharagpur ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tech Talk: Design Research in Product Development: Oct 22
This Tech Talk is starting in 15 min! On Tue, Oct 21, 2014 at 3:52 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Reminder that this Tech Talk will be taking place tomorrow. On Tue, Oct 7, 2014 at 3:40 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Please join us for the following tech talk: *Tech Talk**:* Design Research in Product Development *Presenter:* Abbey Ripstra, Design Usability Research Analyst on The UX team at the Wikimedia Foundation *Date:* October 22 *Time:* 1900 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Design+Research+in+Product+Developmentiso=20141022T19p1=1440ah=1 Link to live YouTube stream http://www.youtube.com/watch?v=jYMTzzosUIw *IRC channel for questions:* #wikimedia-office Google+ page https://plus.google.com/u/0/b/103470172168784626509/events/caiiagf75bvddr09nf4jbgccn30, another place for questions Talk description: The value of design research in product development is being recognized more frequently these days. This talk will quickly describe the innovation process, and how, when and why design research fits into the different parts of the innovation process. For most of the talk, Abbey will focus in on the product development part of innovation and describe how, when and why to best utilize the various methodologies of design research toward building intuitive, easy to use products that meet the needs of users. Abbey will also talk about, and want to collaborate on, the best ways to integrate design research, specifically, into product development at Wikimedia Foundation. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Introduction for OPW Round 9
And here you can find more information about me https://www.mediawiki.org/wiki/User:Livnetata and about the project https://www.mediawiki.org/wiki/User:Livnetata/OPWproposal. Cheers, Neta On Wed, Oct 22, 2014 at 8:31 PM, Neta Livneh neta.liv...@gmail.com wrote: Hi everyone! My Name is Neta Livneh and I am a PhD Student in the Hebrew University of Jerusalem, doing my research the field of computational social science. I am applying to the FOSS Outreach Program for Women round 9 to work on the interesting project Wikipedia article translation metrics. I have a background in data analysis, a bit of machine learning skills and a lot of motivation to find some a way to pinpoint translated articles in Wikipedia. If you want to help or guide just interested in hearing more about the project, please contact me. Cheers, Neta ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tech Talk: Design Research in Product Development: Oct 22
Thanks for watching today! If you would like to view the recording of the talk, here is the link: *https://www.youtube.com/watch?v=jYMTzzosUIw https://www.youtube.com/watch?v=jYMTzzosUIw* If you have any questions about today's talk please feel free to get in touch with Abbey Ripstra arips...@wikimedia.org You can check out past tech talk recordings at the MediaWiki YouTube page here: http://www.youtube.com/channel/UCg4wlhlN8RjP6_e_vMC4CTA If you would like to nominate future tech talks or see what we have coming up, you can find out here: https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event/TechTalks - Rachel On Wed, Oct 22, 2014 at 11:46 AM, Rachel Farrand rfarr...@wikimedia.org wrote: This Tech Talk is starting in 15 min! On Tue, Oct 21, 2014 at 3:52 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Reminder that this Tech Talk will be taking place tomorrow. On Tue, Oct 7, 2014 at 3:40 PM, Rachel Farrand rfarr...@wikimedia.org wrote: Please join us for the following tech talk: *Tech Talk**:* Design Research in Product Development *Presenter:* Abbey Ripstra, Design Usability Research Analyst on The UX team at the Wikimedia Foundation *Date:* October 22 *Time:* 1900 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Design+Research+in+Product+Developmentiso=20141022T19p1=1440ah=1 Link to live YouTube stream http://www.youtube.com/watch?v=jYMTzzosUIw *IRC channel for questions:* #wikimedia-office Google+ page https://plus.google.com/u/0/b/103470172168784626509/events/caiiagf75bvddr09nf4jbgccn30, another place for questions Talk description: The value of design research in product development is being recognized more frequently these days. This talk will quickly describe the innovation process, and how, when and why design research fits into the different parts of the innovation process. For most of the talk, Abbey will focus in on the product development part of innovation and describe how, when and why to best utilize the various methodologies of design research toward building intuitive, easy to use products that meet the needs of users. Abbey will also talk about, and want to collaborate on, the best ways to integrate design research, specifically, into product development at Wikimedia Foundation. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] MediaWiki Architecture Committee updates
Hey all -- Announcement time! The MediaWiki Architecture Committee has added two members by provisional internal consensus: * Roan Kattouw, Wikimedia Foundation (visual editor core) * Daniel Kinzler, Wikimedia Deutschland Roan and Daniel are familiar faces with longtime contributions to MediaWiki. They will be helping with relevant RfC reviews and approvals, and giving advice and ideas as we continue to spin up work in the Arch Committee. These are in addition to the original three members: * Mark Bergsma, Wikimedia Foundation (ops) * Tim Starling, Wikimedia Foundation (core) * Brion Vibber, Wikimedia Foundation (mobile) We plan to have a more formal process for maintenance of the committee membership ready for approval at the MediaWiki Dev Summit in January[1], as well as a more fleshed-out roadmap of what we want the committee to accomplish. Other Arch Committee news: * In the meantime we're concentrating on picking up MediaWiki RfCs to make sure they don't go stale. Last week, Brion and Tim picked up the RfC for styling in templates[2] with an eye to do clean scoping of the styles for security and cleanliness purposes. * We've been chatting with Trevor's Front-end Standardization Group about some other RfC topics such as picking an HTML templating engine for ResourceLoader modules[3]. Jon Robson from Mobile Web has started on a changeset[4] integrating some of the interfaces from the Mantle extension, starting with a basic HTML loader and with plans to include JS-side (and later PHP-side) Handlebars-compatible template compilers. This is still a work in progress as I understand. Both of these RfC pages need to be updated for current status. Also I totally understand that using the term template for both MediaWiki markup templates and HTML UI templates is confusing! * This week's RfC checkup meeting happening real soon now -- 21:00 UTC / 2pm Pacific Time -- in #wikimedia-office so come by and say hello! Until next time arch on! [1] http://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015 [2] http://www.mediawiki.org/wiki/Requests_for_comment/Allow_styling_in_templates [3] http://www.mediawiki.org/wiki/Requests_for_comment/HTML_templating_library [4] https://gerrit.wikimedia.org/r/#/c/165952/ and friends -- brion vibber (brion @ pobox.com / bvibber @ wikimedia.org) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wmfall] Meet-up at WMF: Exploratory Testing for Complex Software, Oct 22 2014
This meet-up is taking place tonight and starting in 4 hours. Logistics Date: Oct 22, 2014 Time: 0130 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Cloudfoundry+Meetupiso=20141022T0130ah=1am=30 On Mon, Oct 20, 2014 at 3:25 PM, Arthur Richards aricha...@wikimedia.org wrote: Just a reminder that this is happening this coming Wednesday, and that we are planning to record/broadcast the event for remote participants. On Tue, Sep 23, 2014 at 10:31 AM, Arthur Richards aricha...@wikimedia.org wrote: On Wednesday, October 22, 2014 the Quality Assurance Group and Team Practices Group hope you will join us for a meet-up at the WMF entitled 'Exploratory Testing for Complex Software; Lessons from Cloud Foundry' with special guest speaker Elisabeth Hendrickson [1]. We will be discussing testing in agile iterative software development, and in particular exploratory testing https://en.wikipedia.org/wiki/Exploratory_testing [0]. This will be a lively and enlightening conversation, aimed at everyone concerned about the overall quality of software - even those who do not necessarily contribute code. *When*: Wednesday, October 22, 2014, 6:00pm - 8:30pm (for WMF folks there is a calendar event on the Engineering calendar) *Where*: Wikimedia Foundation 6th Floor, collab space 149 New Montgomery St. San Francisco, CA (Accessible for remote participation via Hangouts on Air; link TBA) *From the meet-up invite http://www.meetup.com/wikimedia-tech/events/207856222/*[2]: In modern software development organizations, the days are gone when separate, independent Quality Assurance departments test software only after it is finished. Iterative development and agile methods mean that software is constantly being created, tested, released, marketed, and used in short, tight cycles. An important testing approach in such an environment is called Exploratory Testing, and the Wikimedia Foundation has made significant investments to support Exploratory Testing for its software development projects. Elisabeth Hendrickson is test obsessed. She was an early adopter and vocal proponent of all aspects of agile software testing. She has been particularly instrumental in encouraging and defining the practice of Exploratory Testing. Elisabeth's 2013 book Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing is the standard reference on the subject. Join us in the Wikimedia Foundation collaboration space to hear Elisabeth discuss her experience doing software testing for complex projects, with particular examples of Exploratory Testing from her current work as Director of Quality Engineering for Cloud Foundry. This talk is for everyone involved in the overall quality of software, and it will be of particular interest to Project Managers, Product Managers, and those working with software development projects who do not necessarily contribute code directly to the projects. [0] https://en.wikipedia.org/wiki/Exploratory_testing [1] Elisabeth Hendrickson is a tester, developer, and Agile enabler. She wrote her first line of code in 1980, and almost immediately found her first bug. In 2010 she won the prestigious Gordon Pask Award from the Agile Alliance. She is best known for her Google Tech Talk on Agile Testing as well as her wildly popular Test Heuristics Cheatsheet. In 2003, she learned how to do Agile for real from Pivotal Labs while working as a tester on one of their projects. In 2012 she decided it was time to take up permanent residence in the Pivotal offices, where she is the Director of Quality Engineering for Cloud Foundry, Pivotal's Open Source Platform as a Service (PaaS). [2] http://www.meetup.com/wikimedia-tech/events/207856222/ -- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 -- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 ___ Wmfall mailing list wmf...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wmfall] Meet-up at WMF: Exploratory Testing for Complex Software, Oct 22 2014
~ Sorry, I did not finish that last email before it was sent. ~ This meet-up is taking place tonight and starting in 4 hours. *Logistics* *Date:* Oct 22, 2014 *Time:* 0130 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Cloudfoundry+Meetupiso=20141022T0130ah=1am=30 *Remote Participation:* http://www.youtube.com/watch?v=ylWjw9iPWg0 *Physical Location:* WMF HQ, San Francisco, 3rd Floor (RSVP http://www.meetup.com/wikimedia-tech/events/207856222/ necessary). Come at 6pm (0100 UTC) for Pizza and drinks. *IRC Channel for questions and discussion:* #wikimedia-office Hope to see you all there! Rachel On Wed, Oct 22, 2014 at 2:27 PM, Rachel Farrand rfarr...@wikimedia.org wrote: This meet-up is taking place tonight and starting in 4 hours. Logistics Date: Oct 22, 2014 Time: 0130 UTC http://www.timeanddate.com/worldclock/fixedtime.html?msg=Cloudfoundry+Meetupiso=20141022T0130ah=1am=30 On Mon, Oct 20, 2014 at 3:25 PM, Arthur Richards aricha...@wikimedia.org wrote: Just a reminder that this is happening this coming Wednesday, and that we are planning to record/broadcast the event for remote participants. On Tue, Sep 23, 2014 at 10:31 AM, Arthur Richards aricha...@wikimedia.org wrote: On Wednesday, October 22, 2014 the Quality Assurance Group and Team Practices Group hope you will join us for a meet-up at the WMF entitled 'Exploratory Testing for Complex Software; Lessons from Cloud Foundry' with special guest speaker Elisabeth Hendrickson [1]. We will be discussing testing in agile iterative software development, and in particular exploratory testing https://en.wikipedia.org/wiki/Exploratory_testing [0]. This will be a lively and enlightening conversation, aimed at everyone concerned about the overall quality of software - even those who do not necessarily contribute code. *When*: Wednesday, October 22, 2014, 6:00pm - 8:30pm (for WMF folks there is a calendar event on the Engineering calendar) *Where*: Wikimedia Foundation 6th Floor, collab space 149 New Montgomery St. San Francisco, CA (Accessible for remote participation via Hangouts on Air; link TBA) *From the meet-up invite http://www.meetup.com/wikimedia-tech/events/207856222/*[2]: In modern software development organizations, the days are gone when separate, independent Quality Assurance departments test software only after it is finished. Iterative development and agile methods mean that software is constantly being created, tested, released, marketed, and used in short, tight cycles. An important testing approach in such an environment is called Exploratory Testing, and the Wikimedia Foundation has made significant investments to support Exploratory Testing for its software development projects. Elisabeth Hendrickson is test obsessed. She was an early adopter and vocal proponent of all aspects of agile software testing. She has been particularly instrumental in encouraging and defining the practice of Exploratory Testing. Elisabeth's 2013 book Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing is the standard reference on the subject. Join us in the Wikimedia Foundation collaboration space to hear Elisabeth discuss her experience doing software testing for complex projects, with particular examples of Exploratory Testing from her current work as Director of Quality Engineering for Cloud Foundry. This talk is for everyone involved in the overall quality of software, and it will be of particular interest to Project Managers, Product Managers, and those working with software development projects who do not necessarily contribute code directly to the projects. [0] https://en.wikipedia.org/wiki/Exploratory_testing [1] Elisabeth Hendrickson is a tester, developer, and Agile enabler. She wrote her first line of code in 1980, and almost immediately found her first bug. In 2010 she won the prestigious Gordon Pask Award from the Agile Alliance. She is best known for her Google Tech Talk on Agile Testing as well as her wildly popular Test Heuristics Cheatsheet. In 2003, she learned how to do Agile for real from Pivotal Labs while working as a tester on one of their projects. In 2012 she decided it was time to take up permanent residence in the Pivotal offices, where she is the Director of Quality Engineering for Cloud Foundry, Pivotal's Open Source Platform as a Service (PaaS). [2] http://www.meetup.com/wikimedia-tech/events/207856222/ -- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 -- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 ___ Wmfall mailing list wmf...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wmfall ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki Architecture Committee updates
On Wed, Oct 22, 2014 at 1:17 PM, Brion Vibber bvib...@wikimedia.org wrote: Hey all -- Announcement time! The MediaWiki Architecture Committee has added two members by provisional internal consensus: * Roan Kattouw, Wikimedia Foundation (visual editor core) * Daniel Kinzler, Wikimedia Deutschland Congrats to both, and really -- congrats to us for having people of that caliber around. I think they're the right people for the job. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki Architecture Committee updates
+1 Roan doesn't architect software, software architects Roan. - Trevor On Wed, Oct 22, 2014 at 2:56 PM, Ori Livneh o...@wikimedia.org wrote: On Wed, Oct 22, 2014 at 1:17 PM, Brion Vibber bvib...@wikimedia.org wrote: Hey all -- Announcement time! The MediaWiki Architecture Committee has added two members by provisional internal consensus: * Roan Kattouw, Wikimedia Foundation (visual editor core) * Daniel Kinzler, Wikimedia Deutschland Congrats to both, and really -- congrats to us for having people of that caliber around. I think they're the right people for the job. ___ 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
Re: [Wikitech-l] MediaWiki Architecture Committee updates
Brion Vibber wrote: The MediaWiki Architecture Committee has added two members by provisional internal consensus: * Roan Kattouw, Wikimedia Foundation (visual editor core) * Daniel Kinzler, Wikimedia Deutschland This is wonderful news. :-) Ori is right that Wikimedia is very fortunate to have the excellent technical talent (people and skills) that it has. MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikimedia-l] Quarterly reviews of high priority WMF initiatives
Minutes and slides from the recent quarterly review meeting of the Foundation's MediaWiki Core team can now be found at https://www.mediawiki.org/wiki/Wikimedia_MediaWiki_Core_Team/Quarterly_review,_October_2014/Notes . On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller e...@wikimedia.org wrote: Hi folks, to increase accountability and create more opportunities for course corrections and resourcing adjustments as necessary, Sue's asked me and Howie Fung to set up a quarterly project evaluation process, starting with our highest priority initiatives. These are, according to Sue's narrowing focus recommendations which were approved by the Board [1]: - Visual Editor - Mobile (mobile contributions + Wikipedia Zero) - Editor Engagement (also known as the E2 and E3 teams) - Funds Dissemination Committe and expanded grant-making capacity I'm proposing the following initial schedule: January: - Editor Engagement Experiments February: - Visual Editor - Mobile (Contribs + Zero) March: - Editor Engagement Features (Echo, Flow projects) - Funds Dissemination Committee We’ll try doing this on the same day or adjacent to the monthly metrics meetings [2], since the team(s) will give a presentation on their recent progress, which will help set some context that would otherwise need to be covered in the quarterly review itself. This will also create open opportunities for feedback and questions. My goal is to do this in a manner where even though the quarterly review meetings themselves are internal, the outcomes are captured as meeting minutes and shared publicly, which is why I'm starting this discussion on a public list as well. I've created a wiki page here which we can use to discuss the concept further: https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_reviews The internal review will, at minimum, include: Sue Gardner myself Howie Fung Team members and relevant director(s) Designated minute-taker So for example, for Visual Editor, the review team would be the Visual Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker. I imagine the structure of the review roughly as follows, with a duration of about 2 1/2 hours divided into 25-30 minute blocks: - Brief team intro and recap of team's activities through the quarter, compared with goals - Drill into goals and targets: Did we achieve what we said we would? - Review of challenges, blockers and successes - Discussion of proposed changes (e.g. resourcing, targets) and other action items - Buffer time, debriefing Once again, the primary purpose of these reviews is to create improved structures for internal accountability, escalation points in cases where serious changes are necessary, and transparency to the world. In addition to these priority initiatives, my recommendation would be to conduct quarterly reviews for any activity that requires more than a set amount of resources (people/dollars). These additional reviews may however be conducted in a more lightweight manner and internally to the departments. We’re slowly getting into that habit in engineering. As we pilot this process, the format of the high priority reviews can help inform and support reviews across the organization. Feedback and questions are appreciated. All best, Erik [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate ___ Wikimedia-l mailing list wikimedi...@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Tilman Bayer Senior Operations Analyst (Movement Communications) Wikimedia Foundation IRC (Freenode): HaeB ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
