[I'm sorry if it's not the place to ask, please forward where it should be.]
Hi all,
There is a long frozen idea: to make a transliterator for Crimean Tatar
Wikipedia. Native speakers of crh use both cyrillic and latin script
depending on the country they used to live in.
One example of similar thing in use is https://kk.wikipedia.org — one can
choose in what script they see the content.
There is an old task on Phabricator and were attempts to write a tool in
php but the effort stopped.
https://phabricator.wikimedia.org/T23582
<https://phabricator.wikimedia.org/T23582>
Maybe someone can/wants to help with this tool or create one from scratch?
Maybe you know where else I can find help?
Thanks!
*--*
*Vira Motorko*
project manager, Wikimedia Ukraine <https://ua.wikimedia.org/> non-profit
organisation
m: +380667740499 | f: vira.motorko <https://www.facebook.com/vira.motorko> |
w: Ата <https://meta.wikimedia.org/wiki/User:Ата>
Are you saving your documents in free formats? ;)
Help save natural resources – please think twice before printing this
e-mail or any attachments.
Hi,
Timeless is a new responsive skin based on the Vector layout,
incorporating in design principles from Winter and other modern sites,
which I originally started in 2015 as an example for a tech talk. I kind
of forgot about it for awhile since, but then we (essentially a bunch of
random people on phabricator), based on Paladox' recommendation, started
working on getting it ready for deployment to Wikimedia projects.
Links:
* Labs wiki specifically for timeless:
https://timeless-skin.wmflabs.org/wiki/Main_Page
* A copy of the Simple English Wikipedia on the Beta Cluster, where
Timeless has already been deployed and you can see what it might look
like in production:
https://simple.wikipedia.beta.wmflabs.org/wiki/Main_Page - you can
create an account, set your skin to timeless, and go through some of the
things you might do here, and maybe get a feel for the skin
* Skin ocumentation: https://www.mediawiki.org/wiki/Skin:Timeless
* Phabricator workboard:
https://phabricator.wikimedia.org/project/board/1912/ (there are bugs -
please file more)
As you can probably tell, it needs a lot of work.
Current status: Timeless is deployed to the Beta Cluster; consensus is
being established on various projects as to whether or not they would
want to test it out specifically. See:
https://phabricator.wikimedia.org/T154371
If anyone else would like to ask projects they're particularly active on
or that they think would be useful, that would also be great.
Because the problem is, while things are moving forward and development
is sort of happening, I can't do all of this alone (which, fortunately,
I'm not), and I certainly can't devote the time and effort this project
deserves as a volunteer (which, unfortunately, I am). To address this,
I've put in a proposal for a grant that would allow me to work full-time
on this project, working on developing Timeless into a product truly
worth deploying, and also doing much needed research on and outreach to
the projects in order to determine and properly document how they use
their skins, what they expect out of skins, and what problems and needs
need to be addressed with the general MediaWiki frontend.
Grant proposal: https://meta.wikimedia.org/wiki/Grants:IdeaLab/Timeless
As MediaWiki developers and whatnot yourselves, I expect many of you
have worked on similar projects, would be affected by this down the
road, and/or may have thoughts, concerns, or advice on this matter, so
please, I would very much appreciate any feedback you can give, either
here, on the grant page, or on the Phabricator project.
Thanks!
-Isarra
Basically: skins style the interface, extensions add new interface.
Compatibility then needs to be added to the skins for the extensions, so
they can style the new interface too, but we don't want to load the
extension-specific styles unless the extensions is actually used. Thus
we use $wgResourceModuleSkinStyles to add the skin styles to the
extension modules.
Simple, right?
The problem arises when you're making a fully-responsive skin with
multiple stylesheets for different view modes (say, a common stylesheet
for desktop and mobile, a mobile stylesheet, a desktop stylesheet with
specifics for smaller screens, and a desktop stylesheet for gigantic
monitors). Each of these is a separate file, with its target screen
sizes specified in the module definition in skin.json. For many
extensions, proper compatibility will also require specific styles for
several of these.
Unfortunately $wgResourceModuleSkinStyles cannot be defined the usual
way in skin.json, and lacks support for @media queries, so the only way
to even do this is to set the @media sizes inside the files themselves.
What I'm wondering:
1. Is there any good way to parametrise the @media sizes so we only have
to define them once, and then just have the main skin styles, and all
the extension ones, inherit those values? Or is setting a series of less
variables and then keeping those up-to-date with the values in skin.json
probably the best approach?
2. What are best practices for organising this when you have many sizes
and many extensions? Should each extension have one file? Even if the
@media sizes are all in-line in the same file, that is still a separate
file for each extension. Where should these files be kept?
3. Who would be the folks to go to about making this less bad?
-I
FYI all: deadline for presentations has been extended to April 10.
---------- Forwarded message ----------
From: phoebe ayers <phoebe.wiki(a)gmail.com>
Date: Sun, Mar 26, 2017 at 9:53 PM
Subject: DEADLINE EXTENDED: Wikimania 2017 call for submissions
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>, "Wikimania
general list (open subscription)" <wikimania-l(a)lists.wikimedia.org>
Dear all,
We have extended the deadline for submitting presentations, panels,
roundtables and workshops to Wikimania until *April 10*. The deadline for
posters and birds-of-a-feather sessions remains *May 15*.
Please see below for the call for submissions for Wikimania, and submit
your ideas! Please also note, for those who have already submitted, there
is now a field in the registration form for "completed" or "in-progress"
submission. When you are ready to have your submission reviewed, please
note that it is "completed". Thank you!
Please contact us with any questions: wikimania-program(a)wikimedia.org
best,
Phoebe
On Tue, Feb 14, 2017 at 10:10 AM, phoebe ayers <phoebe.wiki(a)gmail.com>
wrote:
> All,
> I'm very pleased to send out the Wikimania Montréal Call for Submissions,
> which can be found in French here:
> https://wikimania2017.wikimedia.org/wiki/Submissions/fr
> and in English here:
> https://wikimania2017.wikimedia.org/wiki/Submissions/en
>
> On behalf of the Wikimania programme committee,
> Phoebe Ayers
> -----
>
> Que vous soyez un membre de la communauté de l’un des projets Wikimédia
> (tels que Wikipédia, Wikibooks, Wikidata, Wikisource, Wikinews, Wikimedia
> Commons, Wiktionnaire, MediaWiki ou autres), un créateur de contenu libre
> ou un consommateur, nous recevrons avec plaisir votre proposition pour une
> session lors de Wikimania 2017.
>
> *dates importantes*
>
> Appel aux propositions ouvert : 2 février 2017
> Date limite de soumission des présentations (conférence, panneau, table
> ronde et atelier) : *15 avril 2017*
> Date limite de soumission des brefs exposés, affiches et réunions
> d’oiseaux de la même plume : 15 mai 2017.
> Notification d’acceptation des présentations : 20 avril 2017
> Notification d’acceptation des brefs exposés, affiches et réunions
> d’oiseaux de la même plume : 10 juin 2017
>
> *Types de soumissions & Comment soumettre: *https://wikimania2017.wikimedi
> a.org/wiki/Submissions/fr
>
> *Des questions ?* Merci de contacter le Comité du programme par
> wikimania-program(à)wikimedia.org.
>
> ----
>
> Whether you are a community member of one of the Wikimedia projects (such
> as Wikipedia, Wikibooks, Wikidata, Wikisource, Wikinews, Wikimedia Commons,
> Wiktionary, MediaWiki or others), or a fellow open content creator or
> consumer, we welcome your proposal for a session at Wikimania 2017.
>
> *Important dates*
>
> Call for proposals opens: February 2, 2017
> Deadline for submitting presentation (lecture, panel, roundtable and
> workshop) submissions: *April 10, 2017*
> Deadline for submitting lightning talks, poster, and birds of a feather
> submissions: May 15, 2017
> Notification of acceptance for presentations: April 20, 2017
> Notification of acceptance for lightning talks, poster and birds of a
> feather submissions: June 10, 2017
>
> *Submission types & how to submit:* https://wikimania2017.wikimedia.org/wiki/Submissions/en
>
>
> *Any questions?* Please contact the Programme Committee at
> wikimania-program at wikimedia.org
>
--
* I use this address for lists; send personal messages to phoebe.ayers <at>
gmail.com *
Hi All.
while browsing the list of possible projects and i stepped on the project
titled [1] Editor-focused dashboard gadget. I was requested by the
co-mentor of the project to look for someone who may likely opt to act as
primary mentor for the project. So please if you are willing to help me as
the mentor of this project it will be highly appreciated.
Thanks.
[1] https://phabricator.wikimedia.org/T91655
Hi Everyone,
This is an usual use case.
I am an admin on the VM that hosts our Mediawiki. Our wiki used to
allows ZIP uploads from the web but its not functioning at the moment.
As an alternate procedure I would like to scp a ZIP file to my home
directory, and then manually cp it into wiki. I'm not clear on the
directory structure:
# find images/ -name '*.zip'
images/3/3a/GCM-AEAD-Test.zip
images/3/3a/Cryptest-sh.zip
images/7/7c/Oids.zip
images/7/75/Twofish-CBC-Filter.zip
images/7/77/SEC1.zip
images/7/77/Blowfish-CTR-Filter.zip
images/7/74/IDEA-CTR-Filter.zip
images/0/07/Mersenne.zip
images/0/09/AES_RNG.zip
...
My questions are, (1) what is the directory structure I should use
when performing the manual copy (how do I determine the intermediate
directories)? Or, (2) what is the procedure to perform a manual copy
(if I don't need to worry about the directory structure)?
The use case is unusual because we could not find a Mediawiki security
and hardening guide. We got a little overzealous and broke uploads
during our effort to harden Apache, PHP and Mediawiki. At this point I
know its more than ModSecurity because disabling it does not resolve
the issue. Its no big deal to me since I can scp and cp files as
needed.
(And please don't get distracted about broken uploads from the web
interface. I don't care about that problem, and it probably provides
us a better security posture. I am happy to live with it).
Thanks in advance.
Jeff
Hello,
I am Sonali Gupta, an undergrad student of Computer Science and Engineering
from India. I am interested in applying for Outreachy round 14 and have
prepared a draft of my application.
Project: https://phabricator.wikimedia.org/T115158Proposal:https://phabricator.wikimedia.org/T161191
Looking forward to hearing some reviews and suggestions on it.
Thank you.
*Sonali Gupta*
*Vice Chairperson- Computer Society of India, Student Chapter*
*member, The Literary Committee*
*Undergraduate- Computer Science*
The LNM Institute of Information Technology, Jaipur
contact- +91-9462900363
= 2017-03-22=
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Call outs ==
* CodeMirror extension (for syntax highlighting) needs security review
https://phabricator.wikimedia.org/T108687
== Product ==
=== Reading ===
====Android====
* Last week:
** Many miscellaneous UI enhancements for better offline support
** New saved page cache implementation still in progress T156917
* Next week (https://phabricator.wikimedia.org/project/view/2352/ ):
** Continue improving the offline experience
** Continue 2.5.x release
https://phabricator.wikimedia.org/project/board/2667/
==== iOS ====
* Last Week
** 5.4 https://phabricator.wikimedia.org/project/view/2326/
*** Removed places from 5.4 so that updates can be made in response to user
feedback
*** Shipped release candidate for 5.4
* This week
** Release 5.4
*** Login enhancements
*** Two factor auth
*** Bug fixes
** 5.4.1 https://phabricator.wikimedia.org/project/view/2600/
*** Any fixes for 5.4 required after release
*** JS consolidation
** 5.5 https://phabricator.wikimedia.org/project/view/2602/
*** Places updates in response to user feedback
====Reading Infrastructure====
* TemplateStyles:
** CSS sanitizer library
https://gerrit.wikimedia.org/r/#/q/project:css-sanitizer
** RfC closed, discussing implementation plans for deduplicating <style>
tags in https://phabricator.wikimedia.org/T160563
* PageViewInfo: in production
** https://en.wikipedia.org/w/index.php?title=Main_Page&action=info
**
https://en.wikipedia.org/w/api.php?action=query&format=json&prop=pageviews&…
**
https://en.wikipedia.org/w/api.php?action=query&format=json&formatversion=2…
|extracts|pageterms|pageimages|pageprops|revisions&explaintext=&exchars=512&wbptterms=description&piprop=thumbnail&pithumbsize=320
* ORES:
** https://gerrit.wikimedia.org/r/#/c/336963/ (hooks + data attributes for
change list items) *waiting for +2*
* Mobile Content Service:
** deployed a couple of bug fixes for mobile-sections endpoint
** adding more languages to TFA (Today's Featured Article) in aggregated
feed
==== Multimedia ====
* No blocking/blockers
* Deployment work for Extension:3d stalled on deployment work for 3d2png.
We're working through that now, and hopefully it won't take too long.
* Obviously we're in a different section this week. Team is moving. More to
come.
==== Web ====
* Sprint: https://phabricator.wikimedia.org/tag/reading-web-sprint-94/
* Last week:
** Page Previews tech debt clean-up and bug fixes
** Print styles
* This week:
** Reading Web off-site
=== Community Tech ===
* LoginNotify high-priority, aiming for an early April release
https://phabricator.wikimedia.org/T11838https://phabricator.wikimedia.org/T160094
* XTools going very well, "Articleinfo" and "Top Edits" working
https://tools.wmflabs.org/xtools-dev/
** Now working on the edit counter https://phabricator.wikimedia.org/T160481
* Cookie blocks all merged and on next week's deploy train, Tuesday we will
test on Testwiki https://phabricator.wikimedia.org/T158129
* Popular pages bot now includes pageviews of all redirects to each page in
the WikiProject https://phabricator.wikimedia.org/T160201
* Editing team graciously tested a solution to have CodeMirror (syntax
highlighting) work in new wikitext editor, seems promising so we will test
further https://phabricator.wikimedia.org/T161052
** Blocker: Ready to move forward with adding it to old wikitext editor,
but needs security review https://phabricator.wikimedia.org/T108687
=== Editing ===
==== UI Standardization ====
* This week
** Style guide work on components. Both technical and content-wise
https://phabricator.wikimedia.org/tag/wikimediaui_style_guide/
** Wikimedia UI/OOjs UI icon fundamentals:
https://phabricator.wikimedia.org/T135081,
https://phabricator.wikimedia.org/T141801andhttps://phabricator.wikimedia.org/T139351
* Updates
** OOjs UI:
*** Release of v0.20.0 (postponed from last week, due to Jenkins trouble)
**** Huge improvement on/resolving almost entirely `em` sizing based
interface issues across browsers
**** Also including 11 UI touching patches (icon deprecations, removed icon
flags, color amendments, vertical rhythm)
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
==== Language ====
* OOjs migration for ContentTranslation continue.
* Team will ask Services help in https://phabricator.wikimedia.org/T107914 (if
needed)
==== Collaboration ====
* Blocked
* Blocking
* Updates
** RC Filters deployed to test.wikipedia.org and test2.wikipedia.org.
Going to Portuguese and Polish on Tuesday.
*** RC Filters GuidedTour
*** Add ORES filters to new RCFilters
*** Allow the ORES extension features to be 'on' by default
*** RCFilters UI: Add a 'what's this?' link to filter groups
*** More RC Filters UI improvements. E.g.
**** Rework conflicts to be objects in filter or group context
**** Create tooltips for filter states
==== Parsing ====
* Linter now deployed on small wikis; Bugs being fixed based on feedback /
testing; Likely deployed to medium wikis this week
* Planning rollout of ParserMigration extension to let editors compare Tidy
output with its replacement (RemexHTML).
* Based on visual diff testing of a language variants patch in core (
https://gerrit.wikimedia.org/r/#/c/333997/ ), we have identified some pages
(primarily chemical element pages like enwiki:Isavuconazole and others on
multiple wikis that use language variant markup that is being affected by
this patch. We are thinking of updating the markup on these pages to nowiki
the "-{" and "-}" that might be encountered there. Doing a dump grep to
find these
== Technology ==
=== Analytics ===
* finished productionizing edit reconstruction jobs, Data Lake tables in
Hive now have a "snapshot" partition column and will be updated regularly
* not urgent but blocked on people to review mediawiki-config and
mediawiki-extensions changes: https://gerrit.wikimedia.org/r/#/c/344007/,
https://gerrit.wikimedia.org/r/#/c/342913/,
https://gerrit.wikimedia.org/r/#/c/336446/. Especially 342913, which
solves errors in production on every edit. Some people seem to review
these in their own time, but it would be nice to have organizational
support, or should we get +2 rights on our team and do it?
** MF: Deployers have +2 for mediawiki-config. You may want to request at
least one person on your team to become a deployer, for this and other
reasons (e.g. running scripts and mwrepl in production).
* ongoing: legacy pagecount metrics being added to AQS, will be queryable
via the API soon
* ongoing: wikistats 2.0 prototype with Vue, in a little over a week we are
very comfortable with the framework, so great learning curve as advertised
=== Security ===
* Reviews:
* 2FA login on iOS App
* MediaWiki 1.28.1/1.27.2/1.23.16 nearly ready for release
=== Technical Operations ===
* Blocked
* Blocking
* Updates
** Special:Allpages outage incident report
https://wikitech.wikimedia.org/wiki/Incident_documentation/20170320-Special…
** Labs: nfs-exportd not setting correct permissions on exports (resolved
with patch) https://phabricator.wikimedia.org/T160818
** Adjusting Prometheus retention caused missing data
https://phabricator.wikimedia.org/T160677
** Mark on parental leave
=== Services ===
* Blockers: none
* Updates:
** Node.js kafka driver upgraded for all services using kafka
(Change-Prop, Trending, EventStreams)
** Cassandra client encryption enabled in RESTBase Cassandra cluster:
https://phabricator.wikimedia.org/T111113
** Thanks to discovery maps updated to node 6 and the node migration is
now complete
=== Discovery ===
* No blockers
* All searches now served from ElastitcSearch 5.1.2. eqiad cluster upgrade
soon.
* Completion suggester temporarily disabled to accommodate a bugfilx for
title length, will be reeenabled soon (probably today).
* Second A/B test for displaying sister wiki results in search launched (
https://lists.wikimedia.org/pipermail/wikitech-l/2017-March/087800.html)
* Working on adding search to Special:Undelete (
https://phabricator.wikimedia.org/T109561)
* Working on Wikidata search
* Various updates to portal code & stats, see weekly for detals (
https://www.mediawiki.org/wiki/Discovery/Status_updates/2017-03-13)
=== Fundraising Tech ===
* No external blockers
* Blocking: DonationInterface vendor lib double-inclusion
https://phabricator.wikimedia.org/T159099
** Sounds like Reedy doesn't consider it high priority, mostly just
annoying for IDEs to have two versions of classes
* DonationInterface
** More tech debt work https://phabricator.wikimedia.org/T160385
* CentralNotice
** Banner Sequencing https://phabricator.wikimedia.org/T144453
** Reducing cache purges for https://phabricator.wikimedia.org/T154954
* CiviCRM
** Finishing up the address fixes https://phabricator.wikimedia.org/T158268
** Investigating importing 3rd party bulkmailer data
* Opsy
** https://phabricator.wikimedia.org/T159289
** Trying to get our last (and most complicated) Precise box migrated to
Jessie
** Writing some wrapper scripts to run jobs using cron instead of via
Jenkins
*** Thanks for the interest and comments from releng!