EE

ee@lists.wikimedia.org

502 discussions

Flow scrum notes, Wed Oct 22
by Danny Horn 22 Oct '14

22 Oct '14

*Erik*: Topic moderation patches finished. Looking at LQT script -- found a few bugs, but it's working -- did a whole page of topics. Danny asks: can we see this on ee-flow? Today - LQT and whatever bugs we find for tomorrow's deploy. *Shahyar*: OOJS is merged! Moving out of code review. A few patches will be +2 and merged. Matt asks about collapsing patch, J-2e -- is that part of Shahyar's patch? SG will check it out. *Matt*: Figured out with Shahyar Merged LQT API patch Code review Put up code hygiene patch for our storage API Today: Work on ToC stuff in Trello *Matthias*: Manually tested OOJS patch, it works Tomorrow: Address some code review feedback, then search.

1 0

Flow scrum notes, Tues Oct 21
by Danny Horn 21 Oct '14

21 Oct '14

*Matt*: Yesterday, reviewing and testing LQT conversion script. Reviewed main patch, which Andrew updated. Both patches are vrery close to being ready. Also: meeting about Phabricator & talked with Shahyar about ToC. Finished css Janus change for RTL Wikipedia support. S says that if we feel good about Andrew's patch, we can backport it today in the deployment window and then use it to test out the conversion. Matt will check it out and make sure it's okay to deploy on production. Then, if there's time: J-2b and J-2f -- opening the ToC and API for listing topic titles. *Matthias*: A couple issues that Scrutinizer reported, removed some dead code. Then code review. Tomorrow -- working on the presentation for next week's Wikimania Holland talk. *Shahyar*: Put up an update to OOJS patch. Matt did an in-depth review of the code, Shahyar responded to all of it. We need to get this reviewed and merged by the end of the day. J-2a (ToC header bar) still needs a little work -- putting it in the In Development column -- so he can focus on finishing up OOJS. *Erik*: I-1 (hide topic) and J-1 (hide comments) are both done, in code review. Currently not passing in Jenkins, need to rebase for OOJS patch. *Bug review*: 72280: Low priority 72277: Fatal error, broken functionality 72233: Notifications for new topics don't have a clickable link -- Danny will make this a card for the next sprint. 72225: Shows links in special pages -- not hard to fix that with a filter. 72194: S says we should have a metric to make sure we're paying attention to our performance.

1 0

Flow scrum notes, Mon Oct 20
by Danny Horn 21 Oct '14

21 Oct '14

*Erik*: Worked on add UserMerge support for Flow (for Dan G and Kunal). Today -- Test UserMerge on beta, finish that today. Then work on Hide comments. *Matt*: Full review of OOJS and LQT patches. Next: Testing on LQT Also: Finish the css Janus to fix the Hebrew bugs Matt & Shahyar will talk later today about splitting up the ToC. *Matthias*: Rebased patch for OOJS - editing long topic title bug. Today: working on scrutinizer (what is this? S hasn't heard of it before) *Shahyar*: Danny & S say: OOJS is the most important thing to do -- this needs to be passing qunit tests and finished as soon as possible. Working on J-2a (table of contents header bar). Should have that done today. Out for a dentist appt for a few hours today.

2 1

Flow scrum notes, Fri Oct 17
by Danny Horn 17 Oct '14

17 Oct '14

Top priority is finishing the OOJS handling -- this has to be done and cleared as soon as we can, to remove blocks for other work. Also, Dan G asked for us to help with UserMerge support for Flow -- it's required for SUL, and Dan & Kunal need our help. There's a card at the top of the Sprint J column. Sorry for adding something else to the sprint, but if we can pick it up, it'll help them out. *Erik*: Found a bug in one of Matthias' patches required a change to core parsing for wikilinks. Worked on placement of anon warning in preview (bug 71283), in code review. Text of new topic form remains after submitting (bug 71776). Need to finish a couple things in I-1 (hide topic updates), the no-JS hide and undo. *Matt*: Figuring out how to get the OOJS tests passing. Almost done fully reviewing the OOJS patch. S suggests: focus on the stuff that's actually blocking other patches from working. Removed history entry file, other fixes. Today, after OOJS -- review LQT script, and CSSJanus patch. *Shahyar*: Has an update to the OOJS patch to go up, that will make the qunit tests pass. J2-a (Header bar with ToC header) -- hacky way to get titles, but this is proof of concept patch. Not blocked by J-2f's API work. Put in a spinner for J-2d (clicking on a title beyond the next set) -- you'll see it in the load more "infinite scroll" area as well.

2 1

Editor interaction data sets and visualizations
by Pine W 17 Oct '14

17 Oct '14

Dear colleagues, As you may have heard, https://meta.wikimedia.org/wiki/Grants:IEG/Editor_Interaction_Data_Extracti… is an individual engagement grant proposal. I am working on this proposal with volunteer assistance and advice from Aaron Halfaker (WMF), Haitham Shammaa (WMF), and Fabian Flöck (Karlsruhe Institute of Technology <https://en.wikipedia.org/wiki/Karlsruhe_Institute_of_Technology>). We are still developing this proposal, and plan to have it finalized in the next few days. We would greatly appreciate your comments on whether you support or oppose the general concept of this project, and any suggestions about how to refine the proposal. Additionally, we would like to hear from you about which sets of editor interaction data, and what visualizations of editor interaction data, would be most relevant to your interests. We intend to prioritize our outputs with your comments in mind. Please comment on the proposal talk page. Questions and feedback, both positive and critical, are helpful to us as the proposers, and also help the Individual Engagement Grants Committee [1] to assess the proposal. Regards, Pine [1] I am a member of the Individual Engagement Grants Committee. I am recusing from reviewing proposals in this funding round.

1 0

Re: [EE] [Wikitech-l] Tech Talk: Design Research in Product Development: Oct 22
by Pine W 17 Oct '14

17 Oct '14

Thanks Rachel. I'm forwarding this invite to other lists. Pine On Wed, Oct 8, 2014 at 9:17 AM, Rachel Farrand <rfarrand(a)wikimedia.org> wrote: > Hi Pine, > > The streaming youtube link is public. Feel free to distribute it however > you like. People can also ask questions on the google+ page during the talk > if they don't have access to IRC. I will not be monitoring it quite as > closely, but I still will check it during the talk. > > As you probably already know, the youtube video will also be public after > the talk so anyone can watch or rewatch the talk at any point after it is > over as well. > > I hope this answers your question, > > Rachel > > > > On Tue, Oct 7, 2014 at 11:08 PM, Pine W <wiki.pine(a)gmail.com> wrote: > >> Hi Rachel, >> >> Would it be appropriate to invite people who are outside of the Wikimedia >> universe to watch on Youtube and participate on IRC? This talk in >> particular may interest outsiders who are designers, PMs, researchers, or >> coders. >> >> Pine >> On Oct 7, 2014 3:40 PM, "Rachel Farrand" <rfarrand(a)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+Desig… >>> > >>> 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/caiiagf75bvddr09… >>> >, >>> 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(a)lists.wikimedia.org >>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l >> >> >

1 0

Flow scrum notes, Thurs Oct 16
by Danny Horn 16 Oct '14

16 Oct '14

*Matt*: Reviewed and merged Erik's patch for UUID issue (bug 72086). It's in the branch so it should go out to Mediawiki today. Changed to OOJS patch to drop the new directory, some more work this morning. Did some review yesterday, need to do more later today. Today: Finish reviewing OOJS, then Andrew's LQT work in progress. Also need to work on cssJanus to fix RTL bug. If there's time today, he'll look at J-2 (ToC) cards. *Matthias*: Had to generate csv dumps from article feedback data. (Finishing up a six-month old project from Fabrice?) Tomorrow: Work on J-4 (watchlist topic title link) -- questions have been answered. *Erik*: Action=purge is up. Tested patches on beta. Put up some bug fix patches related to that. One is related to remove duplicate item from watchlist. A WiP patch for Hide comments (J-1) is up, needs to be put onto Shahyar's OOJS meeting. Going to look at bug 71776: Text in New Topic form remains after submitting. S looked at the LQT--> Flow conversion script. There are a lot of items in the checklist that haven't been done yet. Danny is getting a lot of urgent requests to see a test running. Shahyar missed the meeting.

1 0

Flow scrum notes, Wed Oct 15
by Danny Horn 15 Oct '14

15 Oct '14

Right now, the most important project is to get Shahyar's OOJS changes complete, so that we don't have to do extra work rebasing patches. This should get done as soon as possible, to avoid a front-end rewrite style quicksand situation. *Matt*: Worked on taking out collapse code (J-2e). Unfortunately, Shahyar also worked on that without taking the card in Trello. Today: Change OOJS patch to drop the new directory. Code review on OOJS & LQT. When that's done, pick up the next ToC item. *Erik*: Working on hidden comments (J-1) -- still need to figure out how to make it work on contribs. Code review of Shahyar's OOJS patch -- minor issues, but it looks pretty good. Today - replying to Matthias' questions *Shahyar*: Put up patches for H-8. Worked on J-2e, not realizing that Matt had the card -- there's a patch up. Did code review -- ran into a few issues rebasing to fit OOJS code, working on that. *Matthias*: Merged a lot of patches from Erik. Tomorrow: Review OOJS patch.

1 0

Happy Ada Lovelace Day
by Pine W 15 Oct '14

15 Oct '14

Ada Lovelace Day is celebrated on October 14 this year. Augusta Ada King, Countess of Lovelace (born in the year 1815) was a mathematician and computer programmer who worked on Charles Babbage's Analytical Engine. She foresaw how computers could evolve into devices that perform tasks more sophisticated than simple calculations. She is controversially credited with authoring the world's first computer program, and certainly worked extensively with Babbage. [1] Ada Lovelace Day celebrates women's contributions to science, technology, engineering, and mathematics. Wikimedia Commons, English Wikipedia, and Persian Wikipedia have designated a watercolor portrait of Lovelace as a featured picture. [2] Happy Ada Lovelace Day, Pine [1] https://en.wikipedia.org/wiki/Ada_Lovelace [2] https://commons.m.wikimedia.org/wiki/File:Ada_Lovelace_portrait.jpg

1 0

Clarify Flow RecentChanges
by Matthew Flaschen 14 Oct '14

14 Oct '14

I'd like to think about how we can clarify the Flow recent changes text. Right now, the following Flow actions all appear the same: 1. Creating a new topic 2. Initial post to that topic 3. Another post to that topic. 4. An modification to an existing post. 5. Reply to an existing post In wikitext, 1 is usually easy to distinguish, since people mostly use the "New section" link on talk, which creates a summary like: (→<topic title>?: new section) where <topic title> is user-provided. 3/4 can be distinguished from 1 with wikitext (1 and 2 are combined with wikitext normally), since 3/4 do *not* have "new section". To distinguish 3 vs. 4 vs. 5 with wikitext (when writing the post), people sometimes use simple edit summaries (though other times, they don't bother to add a custom summary). E.g.: (→<topic/section title>: reply where this is a section edit, and "reply" is user-provided There is no software support for distinguishing 3 vs. 4 vs. 5. with wikitext. Flow can distinguish all of these actions (which is a *BIG* win over wikitext), but I believe it does not allow custom edit summaries for any of them. That means you don't have the option of adding a custom summary of "reply" or "reply to Dan"; probably such custom summaries are not needed if Flow provides robust auto-summaries. But currently, it also does not include automatic summaries or text identifying the action. So e.g. the following shows examples of 1, 2, 4, and 3 (in that order. (From https://en.wikipedia.org/w/index.php?namespace=2600&tagfilter=&title=Specia…): We're talking about potentially merging 1 and 2 in the various feeds. So I propose (extending https://en.wikipedia.org/wiki/Wikipedia:Automatic_edit_summaries): (diff | hist) Test post on Wikipedia talk:Flow/Developer test page; 21:09 . . (+9)‎ . . Mattflaschen (WMF) (talk | contribs) (←Created new topic with "Truncated body of initial post...") (diff | hist) Test post on Wikipedia talk:Flow/Developer test page; 21:09 . . (+8)‎ . . Mattflaschen (WMF) (talk | contribs) (←Edited a post) (diff | hist) Test post on Wikipedia talk:Flow/Developer test page; 21:23 . . (+22)‎ . . Mattflaschen (WMF) (talk | contribs) (←Added a new post to the topic) Whether to include content (i.e. "Truncated body of initial post...") is something to consider. There could also be: (diff | hist) Test post on Wikipedia talk:Flow/Developer test page; 21:23 . . (+22)‎ . . Mattflaschen (WMF) (talk | contribs) (←Replied) It could potentially say who you replied to. There are other actions (e.g. editing board header, summarizing, etc. which I haven't tested, but should also clarify what happened). Matt Flaschen

2 2

← Newer
1
...
14
15
16
17
18
19
20
...
51
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

EE