Sprint Q ended -- Sprint R starts today.
*Erik*:
Finshed patch so pimple is upgraded to 2.x, so Andrew can do his work
Pulled in card to add prev & next to diff pages, up for review
Wrote script that takes multiple class per file and turns it into one class
per file. Also up for review.
Today: something off the new Sprint R!
*Matthias*:
Code review on WikiLove -- Ari put up a patch.
Put up a Flow patch to support WikiLove. Still needs a little more work.
Started working on Enhanced RC.
*Matt*:
Finished VE spike & put up a patch. A lot of the old code still worked, but
there were some breaking changes. Identified some issues to fix, and
improvements to make.
*Erik*:
Code review -- everything's either reviewed or merged
Looked into why the autoexpand isn't working, but couldn't diagnose -- Matt
says it might need to wait until we refactor for VE soon
Looked at upgrading Pimple so we're not blocking Andrew anymore
*Matt*:
working on VE -- he'll have some stuff to work on tomorrow
Small topictitle fix about truncation
Updated maintenance script for Erik's comments
Commented on Erik's base conversion patch some more
*Matthias*:
Worked on logging entries, currently doesn't show suppressed topic title on
board. thought it was small, but apparently we have bad data in the
maintenance table. title & namespace are inconsistently logged. Patches are
up.
Tomorrow: pick up something that's ready for the sprint we're starting.
*Erik*:
Worked on bugs, Matthias merged them or suggested fixes -- interwiki
problem with content link. Cherrypicked.
Looking into new bug with transclusion at WikiProject:Breakfast. Probably a
parsoid bug.
Out of tickets, need to move something into the sprint
*Matt*:
Fixed maintenance script for logging data that we lost for moderation
actions
Fixed a problem with Getting Started
Started working on VE spike, will continue today.
*Matthias*:
Code review
Fixed patch for previewing a post not resolving links
Put in patch for JS breakage we caused last week
Will pick high-priority bugs from backlog for last day of the sprint.
I am very happy to see such strong interest in VE from the education
communitty.
FYI, if we don't hear back about a lesson plan for VE training in the next
few days, either in Hebrew or English, I will contact our colleague Michal
who is the executive director of WMIL to see if she can provide us with at
least a Hebrew version that we can use for inspration.
Pine
On Feb 22, 2015 2:14 PM, "Vojtěch Dostál" <vojtech.dostal(a)wikimedia.cz>
wrote:
> I also wondered if there is a VE-oriented training somewhere. It seems
> there isn't - because VE is in a state of flux.
>
> Because Czech Republic uses VE to train students we are in a great need of
> such a training, and are currently asking for a small contract to write a
> simple wiki-based tutorial, mostly based on Wikipedia:Training module
> <https://en.wikipedia.org/wiki/Wikipedia:Training/For_students> for
> students.
>
> If there is a Hebrew VE training could someone please link it? It would be
> lovely to see it, at least to get some inspiration.
>
> thanks
>
>
> Vojtěch Dostál
>
> místopředseda / vice-chairman
> Wikimedia Česká republika / Wikimedia Czech Republic
> http://www.wikimedia.cz
> Facebook <https://www.facebook.com/Wikimedia.CR> | Twitter
> <https://twitter.com/Wikimedia_CR> | Newsletter <http://eepurl.com/FsHJr>
>
>
> 2015-02-22 14:02 GMT+01:00 Leigh Thelmadatter <osamadre(a)hotmail.com>:
>
>> I still do not use VE in my training (despite having 200+ students
>> working on three campuses) because there are too many things it cannot do.
>> I dont have time to constantly play with it to see if it is now good enough
>> to use. I will likely not use it until it is accepted by the wider
>> community. However, the lack of a viable VE does make scalability very very
>> difficult, especially with older teachers who adjust less to idea of coding
>> in any form.
>>
>> +1 on the frustrations for those with new accounts. I understand the need
>> for protections with new accounts, but why in the heck does the captcha
>> "error" message appear at the top and the captcha itself at the bottom?
>> Students only see the red "error" and I have to tell them to go to the
>> bottom and its only a captcha. In addition, because we use wireless with
>> the same IP address, we get errors when I am having a class move text into
>> sandboxes or copy/paste finished articles into the mainspace. Most students
>> cant use the move function as they dont have enough errors. Even if they
>> did, using it would render the sandbox worthless because of the redirect.
>> Add to this trigger-happy bibliotecarios in es.wiki who erase student work
>> with little or no explanation, the last two times being wrongly done.
>>
>> ------------------------------
>> Date: Sun, 22 Feb 2015 11:55:31 +0000
>> From: charles.r.matthews(a)ntlworld.com
>> To: education(a)lists.wikimedia.org
>> Subject: Re: [Wikimedia Education] Editor training with VisualEditor
>>
>> On 22 February 2015 at 10:33, Filip Maljković <dungodung(a)gmail.com>
>> wrote:
>>
>> It is my impression that the VE should be ideally made in such a way that
>> a tutorial isn't really necessary. But I guess we don't live in an ideal
>> world :)
>>
>> That is the "ideal world according to Silicon Valley", not the world we
>> inhabit as Wikimedians.
>>
>> The projects want useful content, and how people write for Wikipedia
>> matters much more than how they do on Facebook. The world of no manuals, no
>> help pages, no support is not one in which we can easily grow our community
>> of productive Wikimedians.
>>
>> And the way the WMF releases software makes life very hard for trainers.
>>
>> It is literally true that you need to check the night before giving a
>> workshop, with a new account, what the current experience for a newcomer to
>> Wikipedia is (capchas, strange messages, moving buttons and all).
>>
>> I believe the latest WMUK training leaflet takes the VE as a given. I
>> know their older leaflet on images mentions it, in a way found confusing to
>> a newcomer (as I found - she was a Computer Officer).
>>
>> Charles
>>
>>
>> _______________________________________________ Education mailing list
>> Education(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/education
>>
>> _______________________________________________
>> Education mailing list
>> Education(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/education
>>
>>
>
> _______________________________________________
> Education mailing list
> Education(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/education
>
>
Hi Juliana,
The attendees at the Cascadia Wikimedians User Group editing workshop
expressed a strong preference for VisualEditor after learning the
traditional interface with The Wikipedia Adventure.
Hi Amir,
Would you be willing to translate the training into English?
Pine
On Feb 21, 2015 12:00 PM, "domusaurea" <domusaurea(a)gmail.com> wrote:
> Excellent point, Pine. I myself don't even know how to use the
> VisualEditor - seems odd, but old-timers know how it feels, yep? But
> indeed, I'm sure my students would feel less intimidated if they don't need
> to learn any coding, even wiki.
>
> I'd love to hear from colleagues who made this transition in their
> classes. Is switching to VisualEditor as effective as promised?
>
> Juliana
>
> Enviada do meu iPhone
>
> Em 21/02/2015, às 17:24, Pine W <wiki.pine(a)gmail.com> escreveu:
>
> Hi all,
>
> Is there a lesson plan available for an editor training workshop that uses
> VisualEditor? New editors seem to prefer learning VE but all lesson plans
> that I know of use the traditional wikitext interface.
>
> I would like to be able to teach new editors the basics of editing and
> referencing using VE, plus talk pages using wikitext, in a one hour format.
>
> Thanks,
>
> Pine
>
> _______________________________________________
> Education mailing list
> Education(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/education
>
>
> _______________________________________________
> Education mailing list
> Education(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/education
>
>
Hi all,
Is there a lesson plan available for an editor training workshop that uses
VisualEditor? New editors seem to prefer learning VE but all lesson plans
that I know of use the traditional wikitext interface.
I would like to be able to teach new editors the basics of editing and
referencing using VE, plus talk pages using wikitext, in a one hour format.
Thanks,
Pine
*Erik*:
Two tests we have for extracting from Parsoid weren't working correctly,
and weren't running in Jenkins. Wrote a fix.
Fixed problem in templating, a permission mistake that caused exceptions on
history.
Made some changes for the prototypes on Q1: New model for indentation.
Problem with Byte-count in special:contributions. Will figure it out today.
*Matt*:
Working on maintenance script for lost moderation logs.
Helping Nuria with a problem in Analytics.
Interviewed Stephane.
Today: Finish maintenance script, start working on Visual Editor spike.
*Erik*:
Moved patches from code review to dev't, then back to code review.
Today: question about Q1 - new model for indentation - checking out
validation for who you're replying to.
New model for indentation is up on Flow-tests; we're road-testing it.
*Matthias*:
Code review for category support
Tomorrow: Q8 - lines between topics in ToC. (There's an old patch for that,
check out what's up.)
*Matt*:
Fixed bug in Editcount script
Mostly worked on maintenance script for backfilling maintenance logs.
There's one issue with the timestamp, maybe Erik can weigh in.
After that: Q2 -- Spike to determine MVP for Visual Editor.
Erik asks -- can't reproduce T61138 - Flow:byte-count in
special:contributions incorrect?
*Matt*:
A couple small fixes for Thanks title text, one for Flow.
Reviewed & merged two patches for Compact Personal Bar & Echo.
Reviewed core skin patch.
Reviewed & merged last LQT patch in the chain.
Ran the edit count script on Beta (for P7), Nick can review that now.
Figuring out maintenance script to keep our logs updated.
Danny asked: start on Q2 -- define and estimate work for VE. We'll need
that next week, to plan the next sprint.
*Matthias*:
Some code review today, more tomorrow.
Updated documentation about
Worked on ToC spacing for Q9. It leaves a gap, but doesn't trigger load
more.
Erik's at Scrum of Scrums.
*Erik*:
Yesterday was mostly code review, clearing out the backlog. Some patches
are merged, will go through Phabricator column and move finished tickets to
product review. Some of them are Search related, and we may need to poke
Chad & Nik.
There's an immediate problem that needs to get fixed -- flow-tests is
throwing exceptions when you try to post a message, and we've got some user
testing scheduled in the afternoon. Erik will take care of it.
After that -- there's another important fix -- Flow logging is broken.
Matt's out volunteering today, well done.