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.
* Labs wiki specifically for timeless:
* 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:
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.
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
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?
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>
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
On Tue, Feb 14, 2017 at 10:10 AM, phoebe ayers <phoebe.wiki(a)gmail.com>
> I'm very pleased to send out the Wikimania Montréal Call for Submissions,
> which can be found in French here:
> and in English here:
> 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
> *Des questions ?* Merci de contacter le Comité du programme par
> 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>
while browsing the list of possible projects and i stepped on the project
titled  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.
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
# find images/ -name '*.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
(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.
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.
Looking forward to hearing some reviews and suggestions on it.
*Vice Chairperson- Computer Society of India, Student Chapter*
*member, The Literary Committee*
*Undergraduate- Computer Science*
The LNM Institute of Information Technology, Jaipur
I couldn't think of a better way of notifying the devs for the aforementioned extensions, but if I could have you guys take attention to https://phabricator.wikimedia.org/T160539
I'd be grateful! Thanks,
WMF Volunteer Developer
Sent from my iPhone