Forwarding.
Pine
---------- Forwarded message ----------
From: Melody Kramer <mkramer(a)wikimedia.org>
Date: Mon, Jul 10, 2017 at 2:26 PM
Subject: [Wikimedia-l] [fellowship] Opportunity for people working on "open
projects that support a healthy Internet."
To: wikimedia-l(a)lists.wikimedia.org
Hi all,
I wanted to pass along an opportunity that I saw earlier today via Twitter:
https://medium.com/read-write-participate/work-in-the-open-
with-mozilla-1410be0a83b2
It sets up people working on "open projects that support a healthy
Internet" with a mentor, a cohort of like-minded people from all over the
world, and a trip to Mozfest, which is a London-based open Internet
conference I've attended/presented at in past years and found really
mind-expanding due to the cross-disciplinary conversations that take place.
You can see previous projects here: https://mozilla.github.
io/leadership-training/round-3/projects/ — it looks like there's quite a
broad cross-section and many of the projects across the movement might be
applicable. The post notes participants will learn about "best practices
for project setup and communication, tools for collaboration, community
building, and running events."
Thank you to Leila for suggesting I pass this along to this listserv. Feel
free to share it broadly.
- Mel
--
Melody Kramer <https://www.mediawiki.org/wiki/User:MKramer_(WMF)>
Senior Audience Development Manager
Read a random featured article from Wikipedia!
<https://en.wikipedia.org/wiki/Special:RandomInCategory/Featured_articles>
mkramer(a)wikimedia.org
_______________________________________________
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
wiki/Wikimedia-l
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
On Wed, 5 Jul 2017 16:31:44 +0300, יגאל חיטרון <khitron(a)post.bgu.ac.il> wrote,
> Hi. Any computer language that has parentheses isn't context free. So
> if
> you are not in Assembly, it's enough.
> About context-free - it's tricky question. I wouldn't call it context
> free
> because of some macro expansions, for example, the pipe ([[abc
> (def)|]] ->
> [[abc (def)|abc]]). The problem I don't know if it will really
> disturb you,
> because highlighting should not care about this.
> The first problem of context-free, templates, should not bother you
> either,
> because you do not have template expansion on the page is
> highlighted, only
> in "runtime". Even "subst" mechanism does not work before saving.
> I tried now to find some wikitext syntax constructs that created a
> "really"
> context sensitive problems, as text power (find ww for some w), but
> had not
> found anything.
> Any other oppinions?
>
Thanks for the reply. So from what I could get does it mean that as far
as syntax-highlighting is concerned 'wikitext' could be considered to
be something close to a context-free language. As a result of, syntax
highlighting could be done with a program that works like a PDA.
Correct me if I'm wrong.
--
Kaartic
Hey, the way non-Latin characters are displayed in section has always been
a serious complaint from our communities:
https://phabricator.wikimedia.org/T152540
Community tech has done some work in this area and it's ready to get more
eyeballs:
https://gerrit.wikimedia.org/r/#/c/362326/
A few words about implementation plan:
* There is now a concept of primary vs. fallback IDs. Primary are used for
linking, fallbacks are used so that old links still work.
* To transition to the new system, a wiki should first continue serving
legacy-encoded sections with new encoding as a fallback, then switch the
two after all older parser/HTTP caches have been filled with new HTML.
Legacy encoding should remain enabled as long as there is a noticeable
traffic using it, on WMF sites that probably means years.
* By default, MediaWiki will still behave exactly like before. Changing the
defaults to something more modern will be discussed later, after all the
initial issues are resolved.
* Because it's being used without escaping in so many places outside of
core and because there is now a fine distinction between ID escaping for
different purposes, Sanitizer::escapeId() is deprecated. It will never
output new encoding and should be replaced with one of escapeIdForHtml(),
escapeIdForLink() or escapeIdForExternalInterwiki() AFTER making sure it's
getting properly escaped.
Your help reviewing/testing/discussing this is highly appreciated!
--
Best regards,
Max Semenik ([[User:MaxSem]])
Hey Jan,
I asked Nizar who did the analysis.
He has updated the phab card with the details:
https://phabricator.wikimedia.org/T166698
Yours,
Chris Koerner
Community Liaison
Wikimedia Foundation
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-07-05
*= **2017-07-05** =*
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Callouts ==
* codfw row B switch upgrade on July 12th
https://phabricator.wikimedia.org/T169345
* Beta thumbnail issues persist (pinging people at random on IRC but if you
can help, please do): https://phabricator.wikimedia.org/T169114
* HTML5 sections need your review, also make sure your team is prepared to
them: https://phabricator.wikimedia.org/T152540
* Scoring Platform
** https://phabricator.wikimedia.org/T167910 - We need to know in which
direction to go with our MW preferences pane.
** https://phabricator.wikimedia.org/T169247 - How should we keep our
labs and production boxes up-to-date?
== Audiences ==
=== Readers ===
==== iOS native app ====
* Blocked by: none
* Blocking: none
* Updates: Released 5.5.0, 5.5.1 (minor bug fixes) releasing today (7/5),
Continuing work on 5.6 (on this day, UI themes)
==== Android native app ====
* Blocked by: n/a
* Blocking: n/a
* Updates: (all ongoing)
** reading list syncing UI work is nearly done; on deck: ZIM support
** Stephen working on cross-platform CSS/JS consolidation
** engineer interviews in progress
==== Reading Web ====
* Blocked by:
* Blocking:
* Updates:
==== Reading Infrastructure ====
* Blocked by:
* Blocking:
* Updates:
==== Multimedia ====
* Blocked by: Beta thumbnail issues persist (pinging people at random on
IRC but if you can help, please do):
https://phabricator.wikimedia.org/T169114
* Blocking: N/A
* Updates:
==== Discovery ====
* Blocked by:
* Blocking:
* Updates:
=== Community Tech ===
* Blocked by:
* Blocking:
* Updates:
** Work on HTML5 section IDs ( https://phabricator.wikimedia.org/T152540 )
is close to conclusion - please review/comment
** Plans to roll out CodeMirror to testwiki this Wednesday
=== Contributors ===
==== Editing ====
* Blocked by:
* Blocking: None known.
* Updates:
==== Parsing ====
* Nothing from us this week
==== Collaboration ====
* Blocked by:
* Blocking: Working to support dump refactoring involving Flow
* Updates:
** Various improvements and fixes for RCFilters, mostly user-facing (e.g.
moving legend and UI fixes).
** Initial version of Article Reminder featured merged. This is an
Outreachy feature to allow requesting an Echo reminder about a particular
page. This is in progress and disabled by default behind a feature flag.
** Improved UI for the feature that allows blacklisting Echo notifications
from particular users.
** Minor additional UI fix to Echo
==== Language ====
* Blocked by:
** Security: review of https://gerrit.wikimedia.org/r/#/c/363156/ would be
nice. Context https://phabricator.wikimedia.org/T169295
* Blocking:
** None known
* Updates:
** Working with visual editor people to determine how to integrate it as a
surface for CX2
==== Contributors Design ====
* Blocked by:
* Blocking:
* Updates:
==== UI Standardization ====
* Updates:
** This week: Further aligning OOjs UI with WikimediaUI Base
** No OOjs UI release last two weeks, upcoming week v0.22.3 will take place
from current planning. Changes in v0.22.2:
** WikimediaUI theme: Use icon instead of indicator in
Tag-/CapsuleItemWidget
** WikimediaUI: Strengthen Radio*Widget's `:checked` state
** Rewrite all styling for "outline controls" (Bartosz Dziewoński)
** OOjs UI demos: Allow linking to specific widgets (Bartosz Dziewoński)
== Technology ==
=== Analytics ===
* Blocked by:
* Blocking: Kaldari's team with ACTRIAL data issues in eventbus
* Updates:
* Still working on eventlogging purging of data, troubleshooting issues
with database to be able to run purging in bulk
* FYI, We will be short two people this quarter, paternity leave
* Working with kaldari in fixing some issues with data for ACTRIAL for
autoconfirmed users, both in data lake and eventbus
* Waiting on final vetting of project-family unique devices. That is
unqiue devices on *.wikipedia.org for example, overall deduplicated
* Work for provisioning new kafka cluster on pause due to vacation
* work continues on wikistats 2.0 UI
=== Cloud Services ===
* Blocked by:
* Blocking:
* Updates:
=== Fundraising Tech ===
* Updates:
** Third-party mailer integration with CRM almost ready for prime time
** deploying some big-ish changes to payment notification listener and job
runner
** just about done with the preliminaries for using our card processor's
new API, starting on the real work
=== MediaWiki Platform ===
* Blocked by:
* Blocking:
* Updates:
=== Performance ===
* Blocked by:
* Blocking:
* Updates:
=== Release Engineering ===
* Blocked by:
* Blocking:
* Updates:
=== Research ===
* Blocked by:
* Blocking:
* Updates:
=== Scoring Platform ===
* Blocked by:
** https://phabricator.wikimedia.org/T167910 - We need to know in which
direction to go with our MW preferences pane.
** https://phabricator.wikimedia.org/T169247 - How should we keep our
labs and production boxes up-to-date?
* Blocking:
** Collaboration may want to take over the MW UI pieces of our
extension, but first we need to formally define the features we care about.
* Updates:
** Thank you to Ops, who got our new service boxes set up faster than
we were able to keep track of.
=== Search Platform ===
* Blocked by: none
* Blocking: none
* Updates:
** "Explore similar" A/B test (
https://phabricator.wikimedia.org/T149809)
** Continuing work on ML-assisted search ranking (load tests are ok:
https://phabricator.wikimedia.org/T169002)
** Working on Japanese analyzers (
https://phabricator.wikimedia.org/T166731)
** Wikidata search code merged, proceeding to tuning the profiles
** Working on the fix for phrase search without Cirrus (
https://phabricator.wikimedia.org/T167798) - currently broken but we have
potential fix
=== Security ===
* Blocked by: none
* Blocking: none
* Updates:
** Reviewing redaction on public labs (cloud?) views
https://phabricator.wikimedia.org/T169665 + some other bugs.
** Review of Security review of Ex:JsonConfig/Ex:Kartographer
interaction upcoming https://phabricator.wikimedia.org/T163827
** Some discussion about new captchas
https://phabricator.wikimedia.org/T125132
=== Services ===
* Blocked by: none
* Blocking: none
* Updates:
** working on container based dev env:
https://github.com/wikimedia/mediawiki-containers
=== Technical Operations ===
* Blocked by:
* Blocking:
* Updates:
** partial ganeti outage
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170629-ganeti
** labstore outage after kernel upgrade
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170629-Labstor…
** codfw row B switch upgrade on July 12th
https://phabricator.wikimedia.org/T169345
== Wikidata ==
* No blockers.
* Continuing on the Lexeme extension.
* Almost ready to migrate from Constraints defined via templates (on
property talk pages) to statements (on properties):
https://phabricator.wikimedia.org/T102759
== German Technical Wishlist ==
* No blockers.
* Voting phase is over. Currently collecting devs/PM/community managers
input on the top 10.
* Be aware we are changing the wikidiff2 PHP extension (written in C++) the
Wikimedia cluster is using for all diffing. Moved paragraphs will be shown
as edited (including inline changes) instead of removed and newly added
paragraphs: https://phabricator.wikimedia.org/T146781
Dear all,
Quoting from my previous post,
“Currently the syntax highlighter of the Wikipedia android app seems
to be slow except on high-end devices. It has been proposed to
change the implementation to provide users with a better
(streamlined) experience while editing[1].”
I recently came to know from a reply to that post [2], that wikitext is
not a "regular language"[3]. I wanted to know what kind of language
wikitext is to ensure that the algorithm for syntax highlighting does
the right work. Is wikitext a "Context Free Language" or is it something
else?
Links
-----
[1]: https://phabricator.wikimedia.org/T164936
[2]: https://lists.wikimedia.org/pipermail/mediawiki-l/2017-June/046627.html
[3]: https://en.wikipedia.org/wiki/Regular_language
---
Regards,
Kaartic