[Wikitech-l] 2016-11-02 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-11-02

=2016-11-02=
==Product==
===Reading===
Android
* Current sprint (https://phabricator.wikimedia.org/project/view/2319/ ):
* Wikipedia Zero system notifications are in (T135450)
* Continuing Q2 goals for Wikidata descriptions. Check out the alpha (
https://android-builds.wmflabs.org/, UI only)!
* Beta coming this week or so (includes Zero system notification
changes but not Wikidata descriptions)
* Unit screenshot regression tests are finally enabled in CI (
https://integration.wikimedia.org/ci/job/apps-android-wikipedia-periodic-test/953/artifact/app/screenshots-ref/).
Thanks to hashar, legoktm, dzahn, thcipriani and probably some other folks
from releng for their help and support
* Heavy networking code refactoring (and tests!)
* 226 tests in CI and counting
* Miscellaneous crash fixes
* Next sprint (https://phabricator.wikimedia.org/project/view/2331/ ):
* More Q2 goals for Wikidata descriptions

Web
* Current sprint: https://phabricator.wikimedia.org/project/view/2314/

   - * Continuing work from the last week


   - * Decided to re-write Hovercards.


   - * 2 team members (Sam and Jeff) will work on it with occasional
   reviews from other team members.


   - * A requirements document has been created. The next step is to create
   phabricator tasks.


   - * The rest of the team will continue working on the other extensions

* Next sprint: https://phabricator.wikimedia.org/project/board/2336/

   - * Hovercards and non-hovercards work


   - * Hovercards work depends on the tasks we create during the current
   sprint


   - * Non-hovercards work includes bug fixes, trending service, and page
   images.


 iOS native app 
Current Board - 5.3 (in beta):
https://phabricator.wikimedia.org/project/view/2220/
Since we last met:

   - * Accessibility Volunteer Day - fixed bugs with VoiceOver
   compatibility in the app:
   https://phabricator.wikimedia.org/project/board/1882/


   - * Fixed crashes & other regressions based on Beta feedback


   - * Released app version for UX research - also reinstating nightly
   Alpha builds

Before we meet again:

   - * Converge toward release of 5.3


   - * Continue work on Accessibility sprint - Fix voice over issues found
   in the accessibility audit and add dynamic Text Size (app font size changes
   with system font setting)


   - * Next board - 5.3.1
   https://phabricator.wikimedia.org/project/view/2281/

No blockers

 Reading Infrastructure 
* Not blocking/blocked, no changes since last week

 Mobile Content Service 
* Fixed issue where noprint elements where stripped out unnecessarily
* Got a repo for Trending Edits service

=== Community Tech ===
* Not blocking/blocked
* Investigating adding IP range support in Special:Contributions
https://phabricator.wikimedia.org/T147664
* Some fixes for PageTriage: https://phabricator.wikimedia.org/T149538 Noindex
template on new articles only
* Rest same as last week

=== UI Standardization ===
Working on
* Align Minerva (Mobile Frontend) to overhauled color palette (T146799)
* Replace MultimediaViewer colors (T149769)
* Review and integrate messages, alerts, warnings as WikimediaUI component
(T127405, continued)
* Accessibility sprint, foremost OOjs UI
https://phabricator.wikimedia.org/project/board/697/query/.o5Hlts6Hi1e/
Finished
* Make Echo follow improved color palette (T147365)
* Replace Flow colors with ones from WCAG 2.0 level AA compliant color
palette https://phabricator.wikimedia.org/M82 (T149768)
Blocked
* Do an icon inventory: Keep, move, delete? (T141801) – missing feedback
about products where icons are in use.

=== Discovery ===
* No blockers
* Working on multiwiki indexes
* FIle properties search should be enabled on several wikis, commons
reindexed but not enabled, needs mapping update
** Enabled by temp fix for https://phabricator.wikimedia.org/T147957, still
would like DBA attention to make it permanent
* Second BM25 test enabled



=== Wikidata / WMDE ===
* Wikidata 4th birthday (see all the presents:
https://www.wikidata.org/wiki/Wikidata:Fourth_Birthday/Presents
** new charts visualizaitons in the query service and other improvements
** new #statements parser function (T142940)
** Wikibase documentation (PHP and JS)
* ElectronPDF - security review done, planning deployment to beta + test
wikis, depends on service going into production (T142226)
* RevisionSlider out of beta soon for German Wikipedia

=== Editing ===
 Language 
* No blocker/blocking.
* Updates:
** CX template support in review.
** Vagrant role for contenttranslation needs more eyes:
https://gerrit.wikimedia.org/r/#/c/263523/ (whom to ping?)

 Collaboration 
* No change to blocked/blocking.
* Updates:
** Started work on Special:RecentChanges Beta Feature changes.
** Edit Review Improvements work (including feed) continues.
** Working on a maintenance script to clean up existing Flow 

[Wikitech-l] 2016-10-26 Scrum of Scrums meeting notes

[Grace Gellerman]

https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-10-26

=2016-10-26=

== Product ==
=== Reading ===


 iOS native app 
Current Board (5.3 is in Beta):
https://phabricator.wikimedia.org/project/view/2220/
Since we last met:

   - * Notifications released to beta today (10/25)


   - * Alternate Table of Contents style for UX research complete (T147214)


   - * Analyzed and fixed crashes & other regressions based on Beta feedback

Before we meet again:

   - * Converge toward release of 5.3


   - * Release specialized Alpha app version for UX research


   - * Start work on Accessibility sprint - Dynamic Text Size (app font
   size changes with system font setting)

No blockers

 Android native app 
* Current sprint (https://phabricator.wikimedia.org/project/view/2319/):
* Wikipedia Zero system notifications almost ready (T135450)
* Continuing Q2 goals for Wikidata descriptions
* Beta coming next week or so
* CI screenshot regression testing, lots of new tests written and old
tests revised, lots of tech debt chores
* Lots of volunteer contributions
* Minimum Android API level increased to Android v4.1 (T147010)
* Improved Chinese variant detection
* Next sprint:
* More Q2 goals for Wikidata descriptions

 Mobile Content Service (MCS) 
* Improving blacklisting of page titles from the most-read endpoint

 Reading Web 
* Current sprint:
https://phabricator.wikimedia.org/tag/reading-web-sprint-84-zero-minutes-left/
  * A few tasks related to the New Readers initiative;
  * MobileFrontend tech debt;
  * Setting up a Trending-edits git repo;
  * Getting rid of Flash of Unstyled Content from section collapsing in MF;
  * Hovercards instrumentation related tasks.
* Next sprint:
* Mostly Hovercards

 Reading Infrastructure 
* Blocked on WMDE reviewing a WatchedItemQueryService patch -
https://gerrit.wikimedia.org/r/#/c/315521/
* Not blocking
* Waiting on reviews for ORES API integration:
https://gerrit.wikimedia.org/r/#/q/status:open+topic:ores-api
* Brad is starting to look at https://phabricator.wikimedia.org/T47843:
i18n for API warnings and errors. Use that task for discussion.
* Working on pageviews API - https://phabricator.wikimedia.org/T144865


=== Community Tech ===
* No blockers
* Not blocked
* Several new wikis switched to numeric collation this week: bswiki, hrwiki
and ukwiki
* CopyPatrol nearly ready to be used by more languages:
https://phabricator.wikimedia.org/T145436
* Patch for sending a cookie with each block to prevent vandalism is nearly
done: https://gerrit.wikimedia.org/r/#/c/48029/ (could use some reviews)
* Working on some new features for Programs Dashboard:
https://phabricator.wikimedia.org/T148796
* Starting to work on throttling account creation per browser:
https://phabricator.wikimedia.org/T106930
* Script for backfilling data in CA tables needs a review:
https://gerrit.wikimedia.org/r/#/c/316375/
* Pageviews tool undergoing a UI overhaul:
https://tools.wmflabs.org/pageviews-test

=== Discovery ===
* No blockers
* Working on multiwiki indexes
* Bm25 is being reindexed for top languages
* BM25 test for ja, zh and th coming up
* FIle properties search should be enabled on most wikis except commons,
still waiting to reindex commons, should be done this week
** Enabled by temp fix for https://phabricator.wikimedia.org/T147957, still
would like DBA attention to make it permanent

 Maps 
* Enabled static maps at test - https://test.wikipedia.org/wiki/Mapframe
* Tabular enabled on labs cluster -
https://commons.wikimedia.beta.wmflabs.org/wiki/Data:Sample.tab
* RFC: link & fullscreen caption text in :
https://phabricator.wikimedia.org/T148706

=== Editing ===
 Collaboration 

 Language 
* Not blocking.
* Not blocked.
* Updates:
** ContentTranslation will (most probably this week) get template support
soon.
** Last week was team offsite.

 Parsing 
* Team was away at two back to back offsites in Seattle.
* Linter extension work ongoing (Kunal & Arlo) to expose Parsoid linter
"errors" to editors to fix up pages (see wikitech-l thread).
* Arlo working with releng to fix some edge case issues in scap deploys of
Parsoid code.

== Technology ==
=== Analytics ===
No blockers
* Edit history reconstruction/wikistats, working on performance of
reconstructing history for enwiki
* Public event streams ongoing will use server side events rather than
socket io
* We soon be able to count pageviews for all wikis, like outreach

* iOs pageviews dropping, going forward iOS needs to own changes to user
agent: https://phabricator.wikimedia.org/T148663

* Pivot is available http://pivot.wikimedia.org  to look at pageview data,
devops straightening up usage of LDAP groups.
* Please read https://office.wikimedia.org/wiki/Data_access_guidelines

=== Architecture / ArchCom ===
* ArchCom-RFC Meeting (https://phabricator.wikimedia.org/E325)
  * Topic: SVG Validation using the Sanitizer <

Re: [Wikitech-l] CREDIT in 35 minutes (was: CREDIT Showcase in two days - 2-Nov-2016 - call for demos)

[Adam Baso]

In case you missed it, here's the video.

https://www.youtube.com/watch?v=NmfqtP3pr2Y=47

Today presenters covered Wikipedia offline (including a Progressive Web App
 version) prototypes,
IFTTT  automated testing, file
property searches, and Wikidata visualizations you can copy and paste into
articles. More details on the Etherpad
.

-Adam







On Wed, Nov 2, 2016 at 12:26 PM, Adam Baso  wrote:

> Reminder, CREDIT will be starting in about 35 minutes.
>
> On Mon, Oct 31, 2016 at 10:55 AM, Adam Baso  wrote:
>
>> Hi!
>>
>> The next CREDIT showcase is in two days - Wednesday, 2-November-2016 at
>> 1800 UTC (1100 San Francisco).
>>
>> https://www.mediawiki.org/wiki/CREDIT_showcase
>>
>> Got a demo? Add it here:
>>
>> https://etherpad.wikimedia.org/p/CREDIT
>>
>> Last month (WebM
>> ,
>> YouTube
>> ) we
>> saw great demos of a Raspberry Pi based network conditioner, Wikidata
>> credits for maps, extended OCR support for Indic Wikisource projects, an
>> intro to EventBus and ChangePropagation, data visualizations on maps, and
>> an alternative table of contents approach.
>>
>> We're excited to see what's next! Whether you've just launched a new
>> feature or are just getting started with an idea, we welcome demos from
>> Wikimedia community members and staff alike.
>>
>> See you soon. And if you would like to invite anyone to CREDIT, feel
>> free to use this template.
>>
>> *Hi *
>>
>> *I hope all is well with you! I wanted to let you know about CREDIT, a
>> monthly demo series that we’re running to showcase open source tech
>> projects from Wikimedia Community, Reading, Editing, Discovery,
>> Infrastructure and Technology.*
>>
>> *CREDIT is open to the public, and we welcome questions and discussion.
>> The next CREDIT will be held on November 2nd at 11am PT / 2pm ET / 18:00
>> UTC. *
>>
>> *Here’s a link to the YouTube live stream
>> , which will be available
>> shortly before the event starts. There’s more info on MediaWiki.org
>> , and on Etherpad
>> , which is where we take notes and
>> ask questions. You can also ask questions on IRC in the Freenode chatroom
>> #wikimedia-office (web-based access here
>> ). *
>>
>> *Please feel free to pass this information along to any interested folks.
>> Our projects tend to focus on areas that might be of interest to folks
>> working across the open source tech community: language detection,
>> numerical sort, large data visualizations, maps, and all sorts of other
>> things.*
>>
>> *Thanks, and I hope to see you at CREDIT.*
>>
>>
>>-
>>
>>*YOURNAME*
>>
>>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] CREDIT in 35 minutes (was: CREDIT Showcase in two days - 2-Nov-2016 - call for demos)

[Adam Baso]

Reminder, CREDIT will be starting in about 35 minutes.

On Mon, Oct 31, 2016 at 10:55 AM, Adam Baso  wrote:

> Hi!
>
> The next CREDIT showcase is in two days - Wednesday, 2-November-2016 at
> 1800 UTC (1100 San Francisco).
>
> https://www.mediawiki.org/wiki/CREDIT_showcase
>
> Got a demo? Add it here:
>
> https://etherpad.wikimedia.org/p/CREDIT
>
> Last month (WebM
> ,
> YouTube )
> we saw great demos of a Raspberry Pi based network conditioner, Wikidata
> credits for maps, extended OCR support for Indic Wikisource projects, an
> intro to EventBus and ChangePropagation, data visualizations on maps, and
> an alternative table of contents approach.
>
> We're excited to see what's next! Whether you've just launched a new
> feature or are just getting started with an idea, we welcome demos from
> Wikimedia community members and staff alike.
>
> See you soon. And if you would like to invite anyone to CREDIT, feel free
> to use this template.
>
> *Hi *
>
> *I hope all is well with you! I wanted to let you know about CREDIT, a
> monthly demo series that we’re running to showcase open source tech
> projects from Wikimedia Community, Reading, Editing, Discovery,
> Infrastructure and Technology.*
>
> *CREDIT is open to the public, and we welcome questions and discussion.
> The next CREDIT will be held on November 2nd at 11am PT / 2pm ET / 18:00
> UTC. *
>
> *Here’s a link to the YouTube live stream
> , which will be available
> shortly before the event starts. There’s more info on MediaWiki.org
> , and on Etherpad
> , which is where we take notes and
> ask questions. You can also ask questions on IRC in the Freenode chatroom
> #wikimedia-office (web-based access here
> ). *
>
> *Please feel free to pass this information along to any interested folks.
> Our projects tend to focus on areas that might be of interest to folks
> working across the open source tech community: language detection,
> numerical sort, large data visualizations, maps, and all sorts of other
> things.*
>
> *Thanks, and I hope to see you at CREDIT.*
>
>
>-
>
>*YOURNAME*
>
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia-l] Introducing Victoria Coleman, WMF Chief Technology Officer

[Pine W]

Forwarding.

Pine


-- Forwarded message --
From: Katherine Maher 
Date: Wed, Nov 2, 2016 at 11:22 AM
Subject: [Wikimedia-l] Introducing Victoria Coleman, WMF Chief Technology
Officer
To: Wikimedia Mailing List ,
wikimediaannounc...@lists.wikimedia.org
Cc: Victoria Coleman 


Hi everyone,

I’m excited today to introduce the Wikimedia Foundation's new Chief
Technology Officer, Victoria Coleman. Victoria’s first day is November 7,
and she will be based in the Foundation's office in San Francisco.

Victoria comes to us with more than 20 years of experience in consumer and
enterprise technology. And as you’ll learn quickly when you start getting
to know her, she is deeply passionate about the importance of education,
and how the Wikimedia mission advances education and equity around the
world.

When we started looking for a CTO for the Foundation, projects, and
communities, we knew we were looking for a unique person - someone with the
experience to lead confidently, and the confidence to embrace open
collaboration in leadership. We were looking for someone with a track
record of success leading strategy and execution for technology platforms
at scale, someone will be an effective mentor and leader for our Technology
department, and a strong partner to Product teams. We needed someone who
would thrive in our culture and be an inclusive collaborator with staff and
community. We agreed that Victoria met these requirements and then some.

Victoria has deep experience across consumer and enterprise technology
fields and is a longtime advocate for innovation in education and the
public sector. She has seen and done many things in her career, from
mobility platforms to connected devices to cyber security to web services
at scale. She brings operational excellence in strategic long-term
planning, execution, delivery, and running large distributed teams.

Most recently, Victoria served as Senior Vice President and Chief
Technology Officer for the Connected Home Division of Technicolor, where
she was responsible for innovation strategy, product management, technology
roadmaps, and technical due diligence for acquisitions and partnerships.
Previously, as Senior Vice President of Research and Development at Harman,
she led the core technology platforms of the Infotainment Division
including systems and software, media, tuner, navigation, connectivity, and
advanced driver assist systems. Before this, she served as Vice President,
Emerging Technologies at Nokia, Vice President, Software Engineering of
Hewlett-Packard’s webOS global business unit, and Vice President of
Samsung's Advanced Institute of Technology.

Victoria also has deep familiarity with open source software development,
having witnessed the rise of the Unix movement first as a student and later
as an instructor. She has been actively involved in the development of the
Linux-based LiMo (renamed Tizen). She passionately believes in the power of
open source and is familiar with how a commitment to open source
strengthens platforms and products at an integral level.

Victoria received her B.Sc and M.Sc in Electronic Computer Systems and
Computer
Aided Logic Design respectively from the University of Salford, UK and her
Ph.D. in Computer Science from the University of Manchester, UK. She is the
author of over 60 articles and books (!). She has worked with teams around
the world, including in Belgium, Brazil, China, France, Finland, Germany,
India, Israel, Korea, Russia, the United Kingdom, and the United States.

One thing that struck many of us throughout our conversations was
Victoria's commitment to volunteering her knowledge and expertise outside
of her daily professional activities, serving on advisory councils in
higher education and the public sector. She is on the advisory Board of the
Santa Clara University Department of Computer Engineering, and she is also
a Senior Advisor to the Director of the  University of California
Berkeley’s Center for Information Technology Research in the Interest of
Society. She serves as a volunteer advisor on both Lockheed Martin’s
Technology Advisory Group and on the United States Department of Defense’s
Defense Science Board where she offers advice and recommendations on
science, technology, manufacturing, and acquisition processes.

As a native of Greece, Victoria is interested in becoming a contributor on
Greek Wikipedia, and getting to know our colleagues and communities over
the coming months.

As many of you know, the CTO search has been an intensive process and our
highest recruiting priority in recent months. Dozens of people from across
the organization contributed to this effort, most notably the CTO hiring
committee, which included directors and senior staff from the Technology
department. Representatives from the C-level, Technology, and Product teams
also participated in interviews, panels, and lunches. In total, 

Re: [Wikitech-l] Fwd: [Wikimedia-l] Introducing Victoria Coleman, WMF Chief Technology Officer

[Katherine Maher]

Thanks Pine, good catch. My mistake to leave wikitech-l off the original
distribution!

On Wed, Nov 2, 2016 at 11:49 AM, Pine W  wrote:

> Forwarding.
>
> Pine
>
>
> -- Forwarded message --
> From: Katherine Maher 
> Date: Wed, Nov 2, 2016 at 11:22 AM
> Subject: [Wikimedia-l] Introducing Victoria Coleman, WMF Chief Technology
> Officer
> To: Wikimedia Mailing List ,
> wikimediaannounc...@lists.wikimedia.org
> Cc: Victoria Coleman 
>
>
> Hi everyone,
>
> I’m excited today to introduce the Wikimedia Foundation's new Chief
> Technology Officer, Victoria Coleman. Victoria’s first day is November 7,
> and she will be based in the Foundation's office in San Francisco.
>
> Victoria comes to us with more than 20 years of experience in consumer and
> enterprise technology. And as you’ll learn quickly when you start getting
> to know her, she is deeply passionate about the importance of education,
> and how the Wikimedia mission advances education and equity around the
> world.
>
> When we started looking for a CTO for the Foundation, projects, and
> communities, we knew we were looking for a unique person - someone with the
> experience to lead confidently, and the confidence to embrace open
> collaboration in leadership. We were looking for someone with a track
> record of success leading strategy and execution for technology platforms
> at scale, someone will be an effective mentor and leader for our Technology
> department, and a strong partner to Product teams. We needed someone who
> would thrive in our culture and be an inclusive collaborator with staff and
> community. We agreed that Victoria met these requirements and then some.
>
> Victoria has deep experience across consumer and enterprise technology
> fields and is a longtime advocate for innovation in education and the
> public sector. She has seen and done many things in her career, from
> mobility platforms to connected devices to cyber security to web services
> at scale. She brings operational excellence in strategic long-term
> planning, execution, delivery, and running large distributed teams.
>
> Most recently, Victoria served as Senior Vice President and Chief
> Technology Officer for the Connected Home Division of Technicolor, where
> she was responsible for innovation strategy, product management, technology
> roadmaps, and technical due diligence for acquisitions and partnerships.
> Previously, as Senior Vice President of Research and Development at Harman,
> she led the core technology platforms of the Infotainment Division
> including systems and software, media, tuner, navigation, connectivity, and
> advanced driver assist systems. Before this, she served as Vice President,
> Emerging Technologies at Nokia, Vice President, Software Engineering of
> Hewlett-Packard’s webOS global business unit, and Vice President of
> Samsung's Advanced Institute of Technology.
>
> Victoria also has deep familiarity with open source software development,
> having witnessed the rise of the Unix movement first as a student and later
> as an instructor. She has been actively involved in the development of the
> Linux-based LiMo (renamed Tizen). She passionately believes in the power of
> open source and is familiar with how a commitment to open source
> strengthens platforms and products at an integral level.
>
> Victoria received her B.Sc and M.Sc in Electronic Computer Systems and
> Computer
> Aided Logic Design respectively from the University of Salford, UK and her
> Ph.D. in Computer Science from the University of Manchester, UK. She is the
> author of over 60 articles and books (!). She has worked with teams around
> the world, including in Belgium, Brazil, China, France, Finland, Germany,
> India, Israel, Korea, Russia, the United Kingdom, and the United States.
>
> One thing that struck many of us throughout our conversations was
> Victoria's commitment to volunteering her knowledge and expertise outside
> of her daily professional activities, serving on advisory councils in
> higher education and the public sector. She is on the advisory Board of the
> Santa Clara University Department of Computer Engineering, and she is also
> a Senior Advisor to the Director of the  University of California
> Berkeley’s Center for Information Technology Research in the Interest of
> Society. She serves as a volunteer advisor on both Lockheed Martin’s
> Technology Advisory Group and on the United States Department of Defense’s
> Defense Science Board where she offers advice and recommendations on
> science, technology, manufacturing, and acquisition processes.
>
> As a native of Greece, Victoria is interested in becoming a contributor on
> Greek Wikipedia, and getting to know our colleagues and communities over
> the coming months.
>
> As many of you know, the CTO search has been an intensive process and our
> highest recruiting priority in recent 

[Wikitech-l] Engaging student devs with another outreach event like GSoC, GCI

[Tony Thomas]

Hello all,

I hit across this idea in the recent GSoC Mentors summit, and in the
discussion with Srishti and Sumit on the reducing usability and scope of
GSoC/Outreachy projects[1] among the years.

*The problem*
Students show up one or two weeks before GSoC or Outreachy, and propose a
solution to existing ideas, and often end up completing it and leaving the
project. Due to this, there is a decline in student-proposed ideas as well,
given 1-2 weeks is not enough to understand Wikimedia from any direction.

*How to solve *
Its tricky, and I came across this program codeheat[2] by FOSSASIA which is
kind of like a Google Code In without any age limit. Its open for everyone
(with majority being Univeristy students), and of course - if this runs
before GSoC, these students who shine in this program gets an advantage
while applying for GSoC. Like they would better know the community, and
might be even able to propose a much-needed project.

The timing of the event is pretty important, like if we need students to
stick to their project once they complete one among the outreach programs
(GSoC/Outreachy), they need to be *engaged*. I think a pattern like this
would help.

   1. A Wikimedia specific code challenge running from say Jan 15 to Mar
   1st with grand prize winners given goodies and maybe a conference ticket
   (if funds exists)
   2. Student with Google Summer of Code/ Outreachy from Mar 20 - September
   6th [3] and later mentoring.
   3. Google Code In Mentors from mid November to January 30

The students can then be mentors for the rest of the programs, and thus
feel warm with the community.

What can the* new event cost*
While talking with FOSSASIA, it seems like they just have a registration
app running at [2], and they assign issues via Github to applicants. Since
we have phab, this might be even simple. Since its a challenge, it can get
enough publicity, and specially in Universities which have future
GSoC/Outreach students and mentors.

We might need someone happy enough to run the program too (

Do comment what you think about the idea of retaining GSoC students with
such an event. Feedbacks and comments welcome.

[1] https://www.mediawiki.org/wiki/User:MaxSem/GSoC_analysis
[2] http://codeheat.org/
[3] https://developers.google.com/open-source/gsoc/timeline

Thanks,
Tony Thomas 
Home  | Blog  |
ThinkFOSS 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] No ArchCom IRC meeting this week

[Brion Vibber]

ArchCom IRC meeting was canceled for this week; sorry for the lack of
announcement!

-- brion
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] First release candidate for 1.28 (1.28.0-rc.0)

[Tyler Cipriani]

Hi all!

I am pleased to announce that the first release candidate for MediaWiki 1.28 is
now available.

Full release notes:
* 
https://phabricator.wikimedia.org/diffusion/MW/browse/REL1_28/RELEASE-NOTES-1.28
* https://www.mediawiki.org/wiki/Release_notes/1.28

Known issues and final release blockers can be found in Phabricator:
https://phabricator.wikimedia.org/project/board/1982/

-- Tyler

**
Download:
https://releases.wikimedia.org/mediawiki/1.28/mediawiki-1.28.0-rc.0.tar.gz

GPG signatures:
https://releases.wikimedia.org/mediawiki/1.28/mediawiki-core-1.28.0-rc.0.tar.gz.sig
https://releases.wikimedia.org/mediawiki/1.28/mediawiki-1.28.0-rc.0.tar.gz.sig

Public keys:
https://www.mediawiki.org/keys/keys.html


signature.asc
Description: PGP signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Need example code in Javascript to login API

[Shrinivasan T]

Gergo Tisza,

Recently, we added more then 2000 books to Tamil WikiSource using
Google OCR with OCR4WikiSource
https://github.com/tshrinivasan/OCR4wikisource

Most of the books have 30-40% spell errors. To fix them, editing the
pages manually is not easy.

I am thinking of a browser plugin with the following workflow.

1. user logins to tamil wikisource
2. reads a wiki page for any book
3. Finds a word with spelling error
4. double clicks it
5. Inline textbox opens there
6. Writes correct word and click ok button
7. The change is saved automatically in background
8. The old word and new word are sent to remote server and stored
9. Mass find and replace for the stored wrong,correct words are
executed periodically

With this design plan, hope users can easily contribute to fix the spell errors.

Hope there may be even better solutions. Share your thoughts on this.


Now, I am in point 1.
Cant find any javascript code login to wikipedia without getting
 No 'Access-Control-Allow-Origin' header is present
error.

The CORS link is not useful for beginner.

Example code in javascript to login to wikipedia will be much helpful.




Moriel Schottlender,

Your solution is fine.
Please share the code so that I can extend from there.

Thanks.

-- 
Regards,
T.Shrinivasan


My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com

Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Need example code in Javascript to login API

[Sam Wilson]

This sounds like a great idea (something akin to PGDP's WordCheck tool
?) But I wonder if implementing it as a
Gadget would be easier? That way, the user is already logged in, and can
access all the normal APIs etc.

The word lists (both good and bad?) could be saved as subpages of the Index
page. Could probably make sense to have site-wide word lists too, for all
the really common ones.

Do you have an idea of the interface for correcting words (the right-click
drop down list)?

This could be really useful for all language Wikisources I think!

—Sam


On 3 November 2016 at 06:11, Shrinivasan T  wrote:

> Gergo Tisza,
>
> Recently, we added more then 2000 books to Tamil WikiSource using
> Google OCR with OCR4WikiSource
> https://github.com/tshrinivasan/OCR4wikisource
>
> Most of the books have 30-40% spell errors. To fix them, editing the
> pages manually is not easy.
>
> I am thinking of a browser plugin with the following workflow.
>
> 1. user logins to tamil wikisource
> 2. reads a wiki page for any book
> 3. Finds a word with spelling error
> 4. double clicks it
> 5. Inline textbox opens there
> 6. Writes correct word and click ok button
> 7. The change is saved automatically in background
> 8. The old word and new word are sent to remote server and stored
> 9. Mass find and replace for the stored wrong,correct words are
> executed periodically
>
> With this design plan, hope users can easily contribute to fix the spell
> errors.
>
> Hope there may be even better solutions. Share your thoughts on this.
>
>
> Now, I am in point 1.
> Cant find any javascript code login to wikipedia without getting
>  No 'Access-Control-Allow-Origin' header is present
> error.
>
> The CORS link is not useful for beginner.
>
> Example code in javascript to login to wikipedia will be much helpful.
>
>
>
>
> Moriel Schottlender,
>
> Your solution is fine.
> Please share the code so that I can extend from there.
>
> Thanks.
>
> --
> Regards,
> T.Shrinivasan
>
>
> My Life with GNU/Linux : http://goinggnu.wordpress.com
> Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
>
> Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
> http://FreeTamilEbooks.com
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
User:SWilson (WMF) 
Community Tech
Fremantle, Western Australia
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Engaging student devs with another outreach event like GSoC, GCI

[Dinu Kumarasiri]

Hi Tony and all,

I would like to add information about another program which matches the
Tony's description to a certain extent. It is Season of KDE by KDE [1].
Similar to GSoC and FOSS OPW they add a set of projects but very smaller in
scope. The competition is held typically around December to February. If
you successfully finish the project they give you a certificate and a
T-shirt. After completing the project, the students can remain contributing
and eventually end up in a GSoC.

Based on that and Tony's suggestion, when deciding the type of the
challenge for Wikimedia, I think we have two options.

1. A GCI kind of a challenge where we add specific tasks and students can
claim and do them repeatedly.
2. We add small projects and select a student who will do the project (like
a mini GSoC).

I support Tony's idea because this gives students more time to fomarly
interact with the community and according to my idea, the longer the
student interacts with the community, higher the chance that, he/she is
going to remain.

[1]
https://dot.kde.org/2016/10/06/kde-student-programs-announces-season-kde-2016-2017

Best regards,
Dinu Kumarasiri


On Thu, Nov 3, 2016 at 12:59 AM, Tony Thomas <01tonytho...@gmail.com> wrote:

> Hello all,
>
> I hit across this idea in the recent GSoC Mentors summit, and in the
> discussion with Srishti and Sumit on the reducing usability and scope of
> GSoC/Outreachy projects[1] among the years.
>
> *The problem*
> Students show up one or two weeks before GSoC or Outreachy, and propose a
> solution to existing ideas, and often end up completing it and leaving the
> project. Due to this, there is a decline in student-proposed ideas as well,
> given 1-2 weeks is not enough to understand Wikimedia from any direction.
>
> *How to solve *
> Its tricky, and I came across this program codeheat[2] by FOSSASIA which is
> kind of like a Google Code In without any age limit. Its open for everyone
> (with majority being Univeristy students), and of course - if this runs
> before GSoC, these students who shine in this program gets an advantage
> while applying for GSoC. Like they would better know the community, and
> might be even able to propose a much-needed project.
>
> The timing of the event is pretty important, like if we need students to
> stick to their project once they complete one among the outreach programs
> (GSoC/Outreachy), they need to be *engaged*. I think a pattern like this
> would help.
>
>1. A Wikimedia specific code challenge running from say Jan 15 to Mar
>1st with grand prize winners given goodies and maybe a conference ticket
>(if funds exists)
>2. Student with Google Summer of Code/ Outreachy from Mar 20 - September
>6th [3] and later mentoring.
>3. Google Code In Mentors from mid November to January 30
>
> The students can then be mentors for the rest of the programs, and thus
> feel warm with the community.
>
> What can the* new event cost*
> While talking with FOSSASIA, it seems like they just have a registration
> app running at [2], and they assign issues via Github to applicants. Since
> we have phab, this might be even simple. Since its a challenge, it can get
> enough publicity, and specially in Universities which have future
> GSoC/Outreach students and mentors.
>
> We might need someone happy enough to run the program too (
>
> Do comment what you think about the idea of retaining GSoC students with
> such an event. Feedbacks and comments welcome.
>
> [1] https://www.mediawiki.org/wiki/User:MaxSem/GSoC_analysis
> [2] http://codeheat.org/
> [3] https://developers.google.com/open-source/gsoc/timeline
>
> Thanks,
> Tony Thomas 
> Home  | Blog 
> |
> ThinkFOSS 
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Dinu Kumarasiri
*,*

*Software Engineer,*

*Sri Lanka*
http://sinceeverybodyhasablog.wordpress.com/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] [MediaWiki-announce] OAuth security update

[Gergő Tisza]

Hi all,

a minor security bug [1] has been fixed in the OAuth extension:
* a connected application could use the /identify endpoint to learn the
username of a user even if the application has been disabled.
* a connected application could use the /identify endpoint to learn the
username of a user even if the user was locked or blocked from login (this
could be problematic when OAuth is used for authentication, such as with
the OAuthAuthentication [2] extension).
The fix has been backported to all supported versions (those for MediaWiki
1.23, 1.26 and 1.27).


Gergő
https://www.mediawiki.org/wiki/User:Tgr_(WMF)


[1] https://phabricator.wikimedia.org/T148600
[2] https://www.mediawiki.org/wiki/Extension:OAuthAuthentication
___
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] [MediaWiki-announce] OAuth security update #2

[Gergo Tisza]

The recent OAuth security fix [1] had a bug [2] which caused some
legitimate OAuth requests to be rejected. The affected versions have been
updated to work properly. Apologies for the disruption.

Gergő
https://www.mediawiki.org/wiki/User:Tgr_(WMF)


[1]
https://lists.wikimedia.org/pipermail/mediawiki-announce/2016-October/000197.html
[2] https://phabricator.wikimedia.org/T149194
___
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] [MediaWiki-announce] Parsoid Security Update and Release

[Subramanya Sastry]

The parsing team has fixed a security bug in Parsoid [1].

* Users could send invalid prefixes, formats, or domains and run
  javascript code on the error page that Parsoid displayed.

* This fix has been applied to the Wikimedia cluster [2] and also merged
  into Parsoid master [1].

* We have also released a 0.5.3 deb version with this patch applied. [3]

* We have also released a 0.5.3 npm version of Parsoid. [4]

* Parsoid is a stateless service and doesn't retain any state between
  requests. In private wikis, VisualEditor can be configured to
  forward the user cookie to Parsoid to pass along to the MediaWiki API
  to parse a page, but this exploit is not exposed through VE.

  In addition, Parsoid doesn't receive any user credentials on
  public wikis.

* However, if a wiki's Parsoid service is publicly accessible on the
  internet *and* is accessible through the wiki's domain, then, this
  exploit can be used to leak user cookies for that wiki. For all wikis
  that use Parsoid in this fashion, we recommend they patch their
  Parsoid installation immediately.

* On the Wikimedia cluster, Parsoid is proxied behind RESTBase and is
  not public accessible and as such, this exploit wasn't available for
  an exploit to steal user sessions.

Thanks to the reporter of this exploit, Darian Patrick from the
Security Team, Arlo Breault from the Parsing Team, Daniel Zahn and
others from Ops for their assistance handling this bug and preparing
this release.

Subramanya Sastry,
Technical Lead and Manager,
Parsing Team,
Wikimedia Foundation.


[1] https://gerrit.wikimedia.org/r/#/c/319115
[2] 
https://www.mediawiki.org/wiki/Parsoid/Deployments#Monday.2C_October_31.2C_2016_around_1:15_PT:_Y.C2.A0Deployed_e503e801

[3] https://releases.wikimedia.org/debian/pool/main/p/parsoid/
[4] https://www.npmjs.com/package/parsoid


___
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] [MediaWiki-announce] CentralAuth security update

[Gergo Tisza]

A security bug [1] has been fixed in CentralAuth; the bug caused logouts to
silently fail if the local account on the central login wiki was
unattached. That does not happen under normal circumstances, so the
vulnerability can only be exposed if some other error causes attaching
accounts to fail; nevertheless you are advised to update your
installations. The fix has been backported to all supported versions (those
for MediaWiki 1.23, 1.26 and 1.27).

Gergő
https://www.mediawiki.org/wiki/User:Tgr_(WMF)


[1] https://phabricator.wikimedia.org/T137551
___
MediaWiki announcements mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Engineering] CI maintenance on Thursday 3rd Nov 16:00 UTC

[Greg Grossmeier]

REMINDER: This is happening tomorrow from 16:00 to 18:00 UTC.


> The Wikimedia continuous integration system will be unavailable while some
> scheduled maintenance is done.
> 
> When: Thursday 3rd 2016 for two hours between 16:00 UTC to 18:00 UTC.
> 
> Impact: During that time, you will still be able to send patches to Gerrit but
> no CI jobs will be run nor will patches be automatically merged when someone
> votes "Code-Review +2". All patches sent during the operations will be sent to
> the CI system for you as a convenience.
> 
> Why: The maintenance will move the core of the CI system (Jenkins and Zuul)
> from an aged server to a fresh new machine.
> 
> More info: It will be done by Antoine Musso, Tyler Cipriani and Daniel Zahn.
> You will be able to watch progress on IRC in the #wikimedia-operations 
> channel.
> See also: https://phabricator.wikimedia.org/T95757
> 
> ___
> Engineering mailing list
> engineer...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/engineering

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l