We're hosting a conversation about standardization and continued
development of front-end libraries in MW core on 6/25, 5:30 PM UTC,
This is driven by a recognized need for teams at WMF to work more
effectively on user-facing features and reduce duplication of efforts
and inconsistencies across extensions. We're willing to take a bit of
a hit on the short term velocity of feature development to build a
more robust, consistent and developer-friendly platform.
Timo Tijhof, Trevor Parscal and Roan Kattouw have proposed a
systematic effort to improve MW core's front-end libraries, building
on existing efforts (see
https://www.mediawiki.org/wiki/UX_standardization for a messy but
reasonably comprehensive overview of some of the inconsistencies and
wheel duplication we need to solve).
This will be done in partnership with other interested front-end
engineers across the org and the community.
We'll try to come up with a clear scope of work, such as:
- having Mobile and VisualEditor depend on the same front-end
libraries in MW core and use them effectively
- eliminating dependencies on jQuery UI from all WMF-deployed code, to
be replaced with a MediaWiki-native look and feel
- creating a proper living style guide and UX standardization pipeline
in partnership with the WMF UX team.
This conversation is just a first step to ensure this effort has
visibility from the start, and major architectural changes will go
through the usual public conversations.
VP of Engineering and Product Development, Wikimedia Foundation
Until two days ago, I was able to modify the background color of a Wikipedia
page with a style sheet containing the following:
background-color: rgb(68, 68, 68) !important;
color: rgb(204, 204, 204) !important;
The line for color still works, but the line for background-color does not.
Does anyone know what changed and what I have to do now to change the
If this is not the right mailing list for this question, could someone
direct me to the right one?
I'm writing to communicate an upcoming major change in MediaWiki-Vagrant.
In the coming week, I'm going to upgrade the base image from Precise
Pangolin to Trusty Tahr, the latest version from Canonical. Trusty
integrates many new open-source software components, many of them
specifically targeting cloud and virtual environments. You can read more
about the release in the release announcement and the release notes:
This change to MediaWiki-Vagrant anticipates a migration of Wikimedia's
application server stack from Precise to Trusty, the groundwork for which
is already well underway. (Wikimedia's TechOps team, substantially assisted
by volunteer contributors, has completed a migration to Puppet 3, and has
made a Trusty image available on Labs).
I hope to keep the migration painless so as to not disrupt the work of
those of you who use this stack as your primary development environment.
The fact that a similar migration process is underway for Wikimedia's
production infrastructure will, I hope, foster increased collaboration
across Wikimedia and the broader developer community.
Micru's Associated namespaces RfC is up for discussion this week.
(We also have room for 1 more RfC to discuss.)
Micru said about
> The intended outcome would be:
> 1) find out if there is any objection against the "Namespace registry and
> association handlers" that Mark proposed
> 2) discuss possible problems with this approach
> 3) see if there would be any hands available to work on it; it is a
> delicate topic that might need someone with a deep understanding of MediaWiki
Micru also noted that we've had a previous suggestion for a namespace
manager https://www.mediawiki.org/wiki/Namespace_manager .
> AFIK, it never materialized because back then there was not such a great
> need as there is now - or at least the current use cases didn't exist back
> I hope this RFC moves forward because it affects important upcoming and
> already deployed projects (Commons migration, templates, Visual editor, WD,
Come to #wikimedia-office at 2100 UTC this Wednesday
or reply/comment with your comments/suggestions.
5pm New York
Senior Technical Writer
We've been talking about the HTML templating RFC since the Architecture
Summit in January. And in the Mobile quarterly review the other day,
they said - see
- that they would love a decision soon. So it seems like we ought to
figure it out so it can get off the RfC docket. :-)
I think this is what's up: Many developers like the work that Matt and
Gabriel have been doing on Knockoff, but we're currently lacking all of
the pieces necessary to make a final call. Some folks were testing it
out and need to report back to the list with their verdicts. In the
meantime, some developers (such as the Mobile and Flow teams) have
short-term needs that can't wait up for Knockoff to become a complete
solution, and so are working out interim standardizations outside of
this mailing list so that they can move forward while Knockoff work
continues. (Not sure what all of them are.)
Is this about right? Should I be saying Knockoff or Knockout? Can I put
the RfC decision meeting on the calendar for next week? :-)
Senior Technical Writer
Hi could we discontinue support for internet explorer 6 and 7 because jquery ui 1.11.0 drops support for internet explorer 6 and 7. Windows xp support internet explorer 8. and so I think we can discontinue support for internet exporer 6 and 7.
Fundraising would like the ability to snapshot or retrieve a CentralNotice
banner exactly as it was rendered at an earlier time, including the old
revisions of templates, which is tricky and AFAICT not supported by
I know this issue has come up before but it looks like development is
external and has died out. The most relevant code seems to be
Extension:BackwardsTimeTravel, which adds some expensive-looking hook
callbacks, and Extension:Memento, which is too far into the future and
amends how HTTP operates.
If ours is an unsupported usage, we'll have to implement a horrible kludge
such as taking a recursive snapshot of all transcluded pages.
Hi we just need to keep the codes for internet explorer 6 for reading and editing with basic function. And remove internet explorer6 from extensions and .js codes. And start notify internet explorer 6 and 7 users to upgrade to internet explorer 8 with a link to where they can download it from.
2014-06-30 13:33 GMT+03:00 Derk-Jan Hartman <d.j.hartman+wmf_ml(a)gmail.com>:
> But basic readability will probably be around for quite some time to
> come. Even text based browsers still mostly work with MW.
Could you please elaborate on that? Do you have any tests that I can
check? If so, are these run regularly? I'm asking because I'm using a
text browser with XBMC on RPI and I'm interested in how that support
will evolve over time.