I was going through our code contemplating dropping XHTML 1.1 support and
ran into the RDFa support stuff and realized how out of date and limited
it is.
I've put together an RFC for replacing our code that appears to be based
on the RDFa 1.0 from 2008 with RDFa 1.1 and expanding support for RDFa.
https://www.mediawiki.org/wiki/Requests_for_comment/Update_our_code_to_use_…
--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://danielfriesen.name/]
Hello all,
== Preamble ==
Thanks to Robla, We now have a reliable way of creating a wikipage from
the Google Spreadsheet we actually edit.
Because of that, you can now see diffs! Eg: this is the one from today's
meeting:
http://www.mediawiki.org/w/index.php?title=Roadmap&diff=706771&oldid=703648
== Updates ==
=== iOS and Android apps in June ===
* Finish POTD login screen.
* Finish oboarding tutorial.
* Finish category work
=== Ops ===
* SFO Caching center will be doing a limited test rollout in June, with
the plan to do the full rollout in July.
* Ceph to be rolled out in July (rolled back in June due to interferring
bugs, reported upstream and fixes in progress)
* HTCP (Hypertext Caching Protocol) will be rolled out in June.
=== Platform ===
* VipsScaler is now out (in June)
* Moving primary media storage to Ceph in July (pending the above Ops
work)
* RFP for Release Management completion and kickoff in July.
=== Engineering Community ===
* Bugzilla improvements (see recent wikitech-l thread on patch in
Gerrit status)
* Improve capacity of tech-related news/journalism with especially
TechNews.
* Investigating potential partnerships with related upstreams
(especially Free/Open Source projects that we use internally).
/end
Let me know if you have any questions or clarifications to this!
Best,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
On Mon, Jun 3, 2013 at 8:18 PM, Chris Steipp <csteipp(a)wikimedia.org> wrote:
> We are trying to finish the items in scope (SUL rework, OAuth, and a
> review of the OpenID extension) by the end of this month.
>
Speaking of this, there's an OAuth framework attempt here:
https://gerrit.wikimedia.org/r/66286
Am I the only person who thinks it's a bad idea for the AuthPlugin class to
be relying on the ApiBase class for its interface? Especially since the
AuthPlugin framework isn't supposed to handle authorization logic anyway.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2016
Major in Computer Science
www.whizkidztech.com | tylerromeo(a)gmail.com
When looking for resources to answer Tim's question at
<https://www.mediawiki.org/wiki/Architecture_guidelines#Clear_separation_of_…>,
I found a very nice and concise overview of principles to follow for writing
testable (and extendable, and maintainable) code:
"Writing Testable Code" by Miško Hevery
<http://googletesting.blogspot.de/2008/08/by-miko-hevery-so-you-decided-to.h…>.
It's just 10 short and easy points, not some rambling discussion of code philosophy.
As far as I am concerned, these points can be our architecture guidelines.
Beyond that, all we need is some best practices for dealing with legacy code.
MediaWiki violates at least half of these principles in pretty much every class.
I'm not saying we should rewrite MediaWiki to conform. But I'd wish that it was
recommended for all new code to follow these principles, and that (local) "just
in time" refactoring of old code in accordance with these guidelines was encouraged.
-- daniel
Hello and welcome to the latest installment of your friendly deployment
highlights!
The full calendar for next week is available at:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_June_10th
Here are the highlights:
== Overall ==
* The week of June 10th is the first "clean" one-week cycle. Please let
me know if you run into any problems, either as a developer or
an editor.
== Monday ==
* MediaWiki 1.22wmf6 will go out to all non-WP project sites (eg:
Commons, Wikisource, et al).
== Tuesday ==
* The phasing out of WebFonts and Narayam begins in preparation for the
ULS deployment. For all of the detailed details, see:
https://www.mediawiki.org/wiki/UniversalLanguageSelector/Deployment/Planning
== Thursday ==
* MediaWiki
** 1.22wmf6 goes out to all 'pedias.
** 1.22wmf7 begins and goes out to test/test2/mediawiki.org
** Full roadmap:
https://www.mediawiki.org/wiki/MediaWiki_1.22/Roadmap#Schedule_for_the_depl…
Let me know if you have any questions!
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hola!
I noticed something very strange in unit tests for /languages/Language.php
(/tests/phpunit/languages/LanguageTest.php):
Language::sprintfDate() is tested to conform with expected formatted date
strings. In the test file method 'provideSprintfDateSamples' provides a
test case for the format bit 'W' which means "ISO 8601 week number,
zero-padded". Language::sprintfDate() outputs the result for W as
documented. However, one of the test cases for this format contains
expected value "1" (instead of "01"). As I said above, sprintfDate() adds a
zero (printing "01"), but when I run the tests, they just pass!
What is wrong here? Wrong test case + issue in PHPUnit or what?
--
З павагай,
Павел Селіцкас/Pavel Selitskas
Wizardist @ Wikimedia projects
Hi!
Sorry for not answering via normal Reply, it's because I'm getting
messages in digests.
But I want to say thanks for clarification and for position=top advice
- it's OK with position=top.
Thanks :)