EE September 2014

ee@lists.wikimedia.org

31 participants
49 discussions

Re: [EE] [Wikitech-l] The future of skins
by Matthew Flaschen 04 Sep '14

04 Sep '14

On 08/27/2014 02:59 AM, Niklas Laxström wrote: > At this point about everyone needs templating library as soon as > possible and do not want to get blocked by the RFC. Please, let's all > work together to complete the RFC for the benefit of everyone. > > -Niklas I completely agree. We can't continue just ignoring the RFC and implementing temporary solutions. Nor should we ignore the RFC and implement a permanent solution. Has this RFC been scheduled for one of the weekly RFC chats yet? In addition to that, let me know how I can help. The RFC is definitely relevant to the Growth team as well. Matt Flaschen

1 0

Flow scrum notes, Wed Sept 3
by Danny Horn 03 Sep '14

03 Sep '14

Sprint ends today -- all the big stuff is done, hooray. Sprint H starts tomorrow! Jon is traveling; Shahyar goes back to Canada today. *Erik*: Lots of code review. Working on getting Cirrus search working. Jon found some problems with lightncandy, Erik put up some patches. *Matthias*: Working on Search G-8. Maybe work on Math bug tomorrow? *Benny*: Yesterday -- code review & Bugzilla. Worked on preview for topic summary. Today -- work on bug with unread notifications are in reverse chronology, make sure that G-14 is merged.

1 0

upcoming changes to Flow moderation and undo
by S Page 02 Sep '14

02 Sep '14

Summarizing some recent Flow in-person discussions: * We're going to append "(undo)" to lines in Flow board and topic history pages, but only for edits to board header, topic title, topic summaries, and posts. (When someone creates a new topic or a reply post, it's not a new revision of the Flow board; for these "Undo" doesn't work at a technical level, and the mental model should be different.) < https://trello.com/c/slbmlcfX/675-g-9-add-undo-rollback-links-to-board-hist… > * To deal with spam topics and posts, we're going to append "(hide)" (and delete | suppress for admins) to "created new topic"/"commented" lines on board and topic history pages. These will work the same as hide|delete|suppress actions do on Flow board and topic pages. We'll append (unhide) to "xx hid topic/post" lines in board and topic history. < https://trello.com/c/V8Flrczl/723-add-hide-delete-suppress-in-board-history… > After this is implemented, we could change Flow boards and topics to not show hidden topics and posts. Users would only see them in the history and could unhide from there. (I can't find the card for this) * We're going to rename Close topic to Lock topic. This better matches what it actually does, which is prevent new posts and changes (with lots of bugs currently). To make it more obvious what Lock does, we'll remove the Reply and Edit links from a locked topic, instead of them failing on submit. < https://trello.com/c/oSuO1E3T/692-1-change-text-from-close-and-open-lock-an… > < https://trello.com/c/yftcsYgu/706-2-when-a-topic-is-locked-the-new-close-ta… > Note many use case of "This topic is closed" fit well with the Summarize topic action. People can and should put {{done}}, {{abandoned}}, {{answered}}, etc. templates and markup in a topic's summary. We'll probably begin developing these in the next two-week sprint. Hope this helps. -- =S Page Features engineer

1 0

Flow scrum notes, Tues Sept 2
by Danny Horn 02 Sep '14

02 Sep '14

*Jon*: Code review on Matthias' patches. Worked on i18n GENDER messages -- loads of stuff in code review. Started the timestamps bug -- not sure what it's asking for. In blocked with questions for now, wants an answer. Needs more work for tomorrow. *Matthias*: Worked on a couple i18n bugs. Working on search spikes, will get as much done as he can before going to Chad and Nik with questions. *Erik*: Today - a lot of stuff needs code review. A couple patches in code review that need to be updated. Some discussion of undo/rollback acceptance criteria. *Benny*: Friday -- mostly code review, rebasing patches. Working on script to clean out older notifications. Unread notifications will last for a year, read notifications will last for (probably) 90 days. *Shahyar*: Has a version of modal that works, but there are some edge cases to be worked out. Will send an e-mail about how he expects it to be used, and how the JS will handle it. Also working on mw-ui standardization (G-5 spike). Will talk to Monte today about wikifonts.

2 1

Individual Engagement Grant funding available
by Pine W 02 Sep '14

02 Sep '14

Forwarding from Siko Bouterse: Greetings! The Wikimedia Foundation Individual Engagement Grants program is accepting proposals for funding new experiments from September 1st to 30th. <https://meta.wikimedia.org/wiki/Grants:IEG> Your idea can improve Wikimedia projects by building a new tool or gadget, organizing a better process on your wiki, conducting research on an important issue, or providing other support for community-building. Whether you need $200 or $30,000 USD, Individual Engagement Grants can cover your own project development time in addition to funding for a team to help you. The program has a flexible schedule and reporting structure, and Grantmaking staff are there to support you through all stages of the process. Do you have have a good idea, but you are worried that it isn’t developed enough for a grant? Put it into the IdeaLab, where volunteers and staff can give you advice and guidance on how to bring it to life. < https://meta.wikimedia.org/wiki/Grants:IdeaLab> Also, IEG will be hosting three Hangout Sessions for real-time discussions to help you make your proposal better - the first will happen on September 16th. < https://meta.wikimedia.org/wiki/Grants:IdeaLab/Events#Upcoming_events> For inspiration, you can read more about past projects < https://blog.wikimedia.org/tag/individual-engagement-grants/> that received funding or review open proposals < https://meta.wikimedia.org/wiki/Grants:IEG#ieg-reviewing>. We are excited to see some of the new ways your grant ideas can support our community and make an impact on the future of Wikimedia projects. Submit your proposal in September! < https://meta.wikimedia.org/wiki/Grants:IEG#ieg-apply>

1 0

Wikiprojects an new editors
by Pine W 02 Sep '14

02 Sep '14

Have there been, or are there, efforts to connect new editors with wikiprojects and other editors who have similar interests, writing styles, and publicly disclosed demographics? Thanks, Pine

2 1

Fwd: Re: [Wikitech-l] Is simplicity is the key to success of Echo and Watchlist?
by Jon Robson 02 Sep '14

02 Sep '14

In case you haven't been following the conversation on wikitech.... ---------- Forwarded message ---------- From: "Derk-Jan Hartman" <d.j.hartman+wmf_ml(a)gmail.com> Date: 2 Sep 2014 14:46 Subject: Re: [Wikitech-l] Is simplicity is the key to success of Echo and Watchlist? To: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org> Cc: On Tue, Sep 2, 2014 at 1:55 PM, Marc A. Pelletier <marc(a)uberbox.org> wrote: > On 09/02/2014 07:47 AM, Derk-Jan Hartman wrote: >> When I watch a talk page, that doesn't mean I want to be NOTIFIED of >> everything on every page. > > Wouldn't simply turning off flow notifications do? Or, perhaps more > flexibly, just making the setting more granular? > I know /I/'d like to be notified of direct replies and pings without > having a notification for every update to a thread -- that does seem > more suited for a passive watch list. I want Flow notifications if someone replies to me, or mentions me in a talk post. Or even for everything if that Flow board would happen to be my own talk page for instance. BUT, that is separate from watching a page. Normally, when watching a page, I would not want notifications on every page that I visit, for every reply to every post, new post or retitled post. I want to see what the last major changes were. Mostly, new topics, and the last change to a new topic. Currently, I feel like Echo is forcing me to consume Flow discussion, where rather, I only want to be 'subscribed' to them and then consume the subscription at the moment that I feel comfortable doing that. It is like it is mixing my mailbox with my newspaper... DJ _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

1 0

Failing Echo test - Flow notifications
by Jon Robson 02 Sep '14

02 Sep '14

The tests [1] seems to be failing as for some reason the creation of this Flow board topic [2] is not triggering a notification for User:Selenium_user_firefox It passes for me fine on my local machine but not on beta labs.. any ideas? Did we break something? [1] https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Ech… [2] http://en.m.wikipedia.beta.wmflabs.org/wiki/Topic:S1kc08qr8383q4hs

1 0

Flow scrum notes, Fri Aug 29.
by Danny Horn 02 Sep '14

02 Sep '14

Some people are out for the long weekend/overseas: Erik, Jon, Matthias. *Benny*: Bug in notifications from Echo changes (new users don't get notifications). The patch is merged to the branch but not to master. He'll merge it. Working on script to delete old notifications. Conv about when to delete notifs. S created a bug, Danny will check in. Worked on performance issues -- it should be better at Mediawiki now, if we see it slow now, we should report it. today -- more tests on the old notifs script. What's up with "no formatting defined for notification error"? It's not logged, we can't find it. Benny will try to investigate more. Danny will test out having lots of notifs, see if we can reproduce. *Shahyar*: Working on mw-ui standardization.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

EE September 2014