EE

ee@lists.wikimedia.org

502 discussions

Collab team scrum notes, Thurs Feb 12
by Danny Horn 12 Feb '15

12 Feb '15

*Erik*: Yesterday: lots of interviews. Today: writing reviews. After that, code review. *Matt*: Working through code review backlog, including LQT patches. Will finish that stack soon, and then continue on through review. *Matthias*: Patches are in code review for Q4 (Hidden comments link to history) and Q6 (Timestamps misaligned in Chrome). Tried to test Echo on German WP -- got banned. Nick suggests -- put an explanation on the user page?

1 0

standup notes
by Erik Bernhardson 12 Feb '15

12 Feb '15

Will be at SoS today instead of standup. Yesterday: Worked on logging topic imports to Special:Log (now up for review) Re-deployed the echo patches for better signature detection Investigate problems with reference collection and malformed external links (also up for review) Interview w/ candidate The 10 patches for LQT imports should all be ready for review. Tried to keep them fairly simple and localized for easy review. Today: SoS 3x Interview Sprint Q kickoff Not expecting to get much of any programming type things done today.

2 1

Collab team scrum notes, Mon Feb 9
by Danny Horn 11 Feb '15

11 Feb '15

*Matt*: Finished P3 "45 years" bug, patch in code review Code review on SVG Interviews Importing the gadget that updates the template on WP to show Phab bugs *Matthias: * Fixed bug that took down the EN WikiProjects. Fixed anon user IPs Aaron is working on a problem to change checkin sets -- submitted patch to fix it for Flow Worked on P7 - contributions w Flow aren't included in a user's edit count. Working on maintenance script to update the existing. *Erik*: Working on P1 -- LQT problems. Figured out most of them. There was a conflict with the new create-page API. More updates & clean-ups for a patch that's adding more logging, and standardizing exceptions. Today: More interview stuff Planning to wrap up P1 today. Talked about MoodBar -- there's a proposal on EN to re-enable it, and a ticket has been filed to turn it on. https://phabricator.wikimedia.org/T88954 MoodBar's not really being supported; we're asking James for response.

2 1

Collaboration team scrum notes, Tues Feb 10
by Danny Horn 10 Feb '15

10 Feb '15

*Matt*: Fixed blocking problem with Flow & spam blacklist. Merged patch about Flow user rights. Finished gadget for WP to automatically show current status for Phabricator tickets. Talked to Danny about Translate's SMW tickets -- rough estimates. *Erik*: Deployed Echo mentions patch yesterday, and test pings didn't work. Pulled the patch back. We're going to send it back out today and test it some more. We may have more issues to look at with Echo. Running into some more issues with LQT conversion. Added a patch where invalid references get logged, and we continue writing stuff out. Today: Finish up LQT, interview this afternoon. Work on some code review for Matthias. *Matthias*: P7 -- contributions with Flow aren't included in a user's edit count -- code review. Issue Erik reported yesterday with WikiProjects is also popping up in Contributions error logs. Looking into that. Will do more of that tomorrow.

1 0

May I delete browser tests that target test2wiki?
by Chris McMahon 10 Feb '15

10 Feb '15

Hi collaboration people: We've been discussing this for a while, and we would like to delete the browser test jobs in Jenkins that target test2wiki. At one point they served a purpose, but today beta labs is the test environment of record and mediawiki.org is functionally equivalent to test2wiki. If you have any objections to this let me know, otherwise we'll be deleting these builds in Jenkins this week. Thanks, -Chris

1 0

Help find great wiki articles about love
by Fabrice Florin 07 Feb '15

07 Feb '15

Hello everyone, What is your favorite wiki article about love? As millions prepare to celebrate Valentine’s Day around the world, we’d like to know how the topic of love is covered on Wikipedia and its sister projects, for a special blog post at the end of next week. We’re looking for great wiki articles, images, sounds or videos on this topic -- from platonic to fraternal or romantic love. Please add your suggestions on this email thread -- or on one of these pages: On the Blog: http://blog.wikimedia.org/2015/02/06/wiki-articles-about-love/ On Meta: https://meta.wikimedia.org/wiki/Love_on_the_wikis Be sure to include a link, with a sentence or two about why you picked it! We welcome your suggestions until Wednesday, Feb. 11, 2015 at midnight PST. We'll post some of your top picks next Friday on the Wikimedia Blog and social media -- just in time for Valentine’s Day. Thanks for sharing the love :) Fabrice on behalf of the WMF Comms team _______________________________ Fabrice Florin Movement Communications Manager Wikimedia Foundation https://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF)

1 0

Flow scrum notes, Fri Feb 6
by Danny Horn 06 Feb '15

06 Feb '15

*Matt*: Reviewed & merged Matthias' pagination patches. Merged patch to remove our version of lightncandy, so we use core's version instead. Put in a patch to add navbar to the pagination pages. Today: P3 - "Edited 45 years ago" bug. *Erik*: Merged Matthias' patches for fixing Echo mentions. We'll cherry-pick it Monday for release to all wikis. Spent some time on LQT support (P1).

1 0

Collaboration scrum notes, Thurs Feb 5
by Danny Horn 06 Feb '15

06 Feb '15

*Matt*: Hygiene patch for Erik, fixed translation Followed up on GlobalUserPage -- more complete than we thought. Tim S wants to figure out how to batch it. Kunal is helping. Responding to Mitre questions on Wikimedia-L -- is the user contributions API not supporting Flow? Erik and Matt will look into it. Reviewing Matthias' pagination patch, started merging. *Erik*: Yesterday, worked on the LQT conversion problems. Updates started causing errors. We'll suppress RC messages and just make one message. Still figuring out how to format it, Aaron H suggested it would go in Special:Logs. Increasing the verbosity of the LQT code. Wiring up more stuff to output debug messages, start looking into why some don't have content. *Matthias*: Working on tests for Echo mentions and signature extraction Tomorrow -- finish Echo tests, then work on task we brought into sprint yesterday. Also brought in bug -- fix byte counts. When it's merged, we'll have to run a maintenance script.

1 0

Collaboration scrum notes, Wed Feb 4
by Danny Horn 04 Feb '15

04 Feb '15

*Erik*: Interviews with front-end P2. Category support -- works in Jenkins, up for code review Code review on Elastic search, learning more Today: P1 -- Debug problems with importing LQT threads on Translatewiki *Matthias*: Put up patch to remove lightncandy (P5) A couple minor hygiene patches, fixed exceptions Responded to initial feedback on search patches We're kicking ass on this sprint, so we're moving in another ticket -- P7. Contributions with Flow aren't included in a user's edit count. Matt's at scrum of scrums.

1 0

Re: [EE] [Wikimedia-l] Quarterly reviews of high priority WMF initiatives
by Tilman Bayer 04 Feb '15

04 Feb '15

Minutes and slides from last week's quarterly review meeting of the Foundation's Collaboration team (which was formerly called the Core features team and is working on the Flow project) have appeared here: https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarter… On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller <erik(a)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_r… > > 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 > Wikimedia-l(a)lists.wikimedia.org > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
51
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

EE