There's a pretty hilarious American police procedural TV show in 2015
called "CSI: Cyber", featuring mostly cybercrime. Obviously they have to
dredge up snippets of code from places for screenshots on the show.
Episode 4 happened to include a tidbit from MediaWiki 1.25/wmf3. Supposedly
the code was a hack to make your printer blow up.
Original lulz and screenshots via
http://moviecode.tumblr.com/post/114815574587/this-is-from-csi-cyber-s01e04…
Hi folks,
We have an RfC review meeitng scheduled for 2015-09-16 at 21:00 UTC.
Full details can be found on Phabricator:
https://phabricator.wikimedia.org/E66
The meeting will be on the IRC channel #wikimedia-office on
chat.freenode.net. We haven't worked out the agenda yet, but please
comment on Phabricator if you have a bias and would like to sway the
rest of us. The discussion positive or negative about the RfC itself
should be on the task associated with the RfC. Discussion on E66
should be about the tradeoff between discussing something sooner
rather than later.
Here are the top choices being considered:
* T90914: Provide semantic wiki-configurable styles for media display
* T108255: RfC: Enable MariaDB/MySQL's Strict Mode
* T484: RfC: Scoped language converter
* T468: RfC: CentralNotice backend improvements
* T388: RfC: Graphical configuration interface
Thanks
Rob
I seem to remember that all Wikimedia wikis now share a single search
index, and per-wiki searches are filtered through a tag for the respective
wiki.
If that is indeed the case, is there an API to search all wikis, but
omitting that tag?
lightning talks <https://en.wikipedia.org/wiki/Lightning_talk> on Sep 22!
~ More logistic details/signups found in the email below ~
Please sign up if you would like to do a quick 10 min talk this month.
These talks will continue every month until there is no longer interest.
A youtube stream will be sent out to this list just before the talks start
so you can follow along, you can ask questions on IRC, and the talks will
also be recorded so that you can watch them whenever you like.
---------- Forwarded message ----------
From: Kevin Leduc <kevin(a)wikimedia.org>
Date: Tue, Sep 8, 2015 at 4:33 PM
Subject: [Engineering] September Lightning Talks
To: "Staff (All)" <wmfall(a)lists.wikimedia.org>, Engineering list <
engineering(a)lists.wikimedia.org>
Hello!
September's Lightning Talks are in two weeks and we are looking for more
volunteers to present. Lightning Talks are an opportunity for teams @ WMF &
in the Community to showcase a Quarterly Goal achieved, significant
milestone, release, or anything of significance to the rest of the
foundation and the movement as a whole. These talks will be open to our
communities.
Each presentation will be 10 minutes or less, the formal part should be not
be longer than 5 minutes and the remainder can be used for questions. We
need at least three people to sign-up to be speakers on the wiki page
<https://www.mediawiki.org/wiki/Lightning_Talks> by September 15 or else
the talks will be postponed to the next month.
Too many questions to answer in the allotted time? No worries, your
lightning talk will be a great candidate for a future Tech Talk.
Third Round of Lightning Talks:
When: Tuesday September 22, 1800 UTC
<http://www.timeanddate.com/worldclock/fixedtime.html?msg=Lightning+Talks+-+…>,
11am PDT
Where: 5th Floor
Remotees: On-Air google hangout will be provided just before the meeting
IRC: #wikimedia-tech
Sign up for a 10 minute slot here:
https://www.mediawiki.org/wiki/Lightning_Talks
Thanks!
Kevin Leduc, Rachel Farrand, Megan Neisler
_______________________________________________
Engineering mailing list
Engineering(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/engineering
Apologies for cross-posting from wikidata-l, but this may be of relevance
to readers of this list.
---------- Forwarded message ----------
From: Dan Garry <dgarry(a)wikimedia.org>
Date: 7 September 2015 at 15:29
Subject: Announcing the release of the Wikidata Query Service
To: wikidata-l(a)lists.wikimedia.org
The Discovery Department at the Wikimedia Foundation is pleased to announce
the release of the Wikidata Query Service
<https://www.mediawiki.org/wiki/Wikidata_query_service>! You can find the
interface for the service at https://query.wikidata.org.
The Wikidata Query Service is designed to let users run queries on the data
contained in Wikidata. The service uses SPARQL
<https://en.wikipedia.org/wiki/SPARQL> as the query language. You can see
some example queries in the user manual
<https://www.mediawiki.org/wiki/Wikidata_query_service/User_Manual>.
Right now, the service is still in beta. This means that our goal
<https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals#Wikid…>
is
to monitor of the service usage and collect feedback about what people
think should be next. To do that, we've created the Wikidata Query Service
dashboard <https://searchdata.wmflabs.org/wdqs/> to track usage of the
service, and we're in the process
<https://phabricator.wikimedia.org/T111403> of setting up a feedback
mechanism for users of the service. Once we've got monitored the usage of
the service for a while and got user feedback, we'll decide on what's next
for development of the service.
If you have any feedback, suggestions, or comments, please do send an email
to the Discovery Department's public mailing list,
wikimedia-search(a)lists.wikimedia.org.
Thanks,
Dan
--
Dan Garry
Lead Product Manager, Discovery
Wikimedia Foundation
Hi this is a question but shoulden Wikimedia wikis such as Wikipedia be updated with a user friendly design. Currently vector is coming out of date because now a days you see sites with bruitiful colours not old ones as they were in 2010 when vector came out. We could create another skin to replace vector as we did with monobook or update vector with a new look that has bold colours and goes along with mediawiki code and is also mobile optimised even though we have the mobilefrontend extension some users may not want to install instead hoping the skin is mobile optimised.
Hello,
Jenkins jobs start failing on some repositories release branches because
they are lacking the CI [entry points]. For example if the 'npm' job
has been enabled, the master branch has a 'package.json' but the release
branches do not. That causes CI to reject backports.
I would like us to update our repositories REL1_24 and REL1_25 branches
with package.json and composer.json whenever they are present in master.
The commands being run would need be tweaked but at the very minimal
each branches should check:
* the i18n files using grunt-banana-checker (in package.json)
* php lint (jakub-onderka/php-parallel-lint) (in composer.json)
Repositories that haven't switched yet are not impacted nor are the
branches already having the package.json/composer.json files.
[entry points]
https://www.mediawiki.org/wiki/Continuous_integration/Entry_points
--
Antoine "hashar" Musso