Greetings All,
Over the last couple of weeks a group of devs from Nitobi have been
putting together an Android Wikipedia App for us. They've been using
the PhoneGap framework to build the app and now it mostly has the same
features as our iOS app. I think it's finally gotten to a good state
for people to start hacking on it.
For those just wanting to get started here are the links
code: https://github.com/nitobi/Wikipedia
bugs: http://bit.ly/q1B9Bj
feature ideas: http://meta.wikimedia.org/wiki/Mobile_Projects/App_Features_&_Roadmap#Featu…
Right now the code is sitting in github but the plan is to move it
into our own git repo, alongside MediaWiki.
How can you help?
* Fork the code and help us with open bug requests
* Critique the code and suggest cleanup
* Port the app to iOS, Symbian, BlackBerry, Windows, WebOS, & Bada —
first get it running, then customize to each platform's look and feel
* Start to hack on new features like image uploads, starting a new
article, offline article saving, openZIM support, etc ...
* Localization for the user interface
* ... and whatever else you can come up with
Don't worry if you don't know Objective C, Java, etc .. All you need
to know is HTML5, CSS3, and JS. It's really simple to write these
apps.
Lots of pretty screen shots and a user flow diagram here :
http://meta.wikimedia.org/wiki/Mobile_Projects/WikipediaAndroidApp
Come join us on #wikimedia-mobile and let us know how it goes.
--tomasz
Hi everyone,
We need your help. We have a number of reports on the various village
pumps, helpdesks, Twitter, and such that IE8 users are experiencing
crashes merely by visiting our site. Here's the bug report:
https://bugzilla.wikimedia.org/show_bug.cgi?id=31424
Given the frequency and diversity of reports, there is almost
certainly something to this, even though we don't yet have a solid
repro case that a developer can actually use to fix this.
Here's what we need. If you are actually seeing crashes, we would
love to know exact browser version (e.g. IE 8.0.7601.17514), exact
operating system version, all plugins installed and their exact
versions, and how much RAM your machine has. Please report your
findings either in the bug report above, or if you're more comfortable
on-wiki, then here:
http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#If_you_….
Thanks!
Rob
Hi all,
as you may know, MediaWiki supports video embedding (from sites such as
YouTube, for example) only via separately installable extensions. Many of
these extensions are parser hooks (such as <youtube>), and as such they are
a bit difficult to use for the average editor and many video embedding
extensions are also very hacky and may even contain cross-site scripting
(XSS) vulnerabilities.
What's the solution? A video extension that supports multiple different
providers, is easy to use and is secure. So far none of the existing
extensions really match all the given criteria. Until now, that is. Earlier
today I committed the Video extension (
http://www.mediawiki.org/wiki/Extension:Video) into the official MediaWiki
Subversion repository at http://svn.wikimedia.org/.
The Video extension was originally written by David Pean, who is best known
for his work on the social tools (http://www.mediawiki.org/wiki/Social_tools),
back in 2007 for ArmchairGM (http://en.wikipedia.org/wiki/Wikia#ArmchairGM)
and it saw limited use outside ArmchairGM, but the code was never finished.
For example, while you could add videos to the wiki, there was no way to
delete a video, which would've been a rather easy way for a vandal to troll
the wiki.
During the past summer, I improved various social extensions (see
http://www.mediawiki.org/wiki/Social_tools/Phase_II), including Video. I
added support for deleting (and partially for undeleting) videos and I wrote
plenty of new provider classes. While the Video extension is in pretty good
shape now, it's not yet ready and it needs *your* help! Like I wrote
earlier, the deletion of videos is possible, but undeletion support is not
as functional, due to the way how Special:Undelete does things.
[[Video:Foo]] links can't yet be tracked via Special:WhatLinksHere. And, of
course, I'm not sure if Video supports your favorite provider yet. :-)
If you are a developer who's interested in video support or you know a
developer who'd be interested in helping out, please see
http://www.mediawiki.org/wiki/Extension:Video and
http://www.mediawiki.org/wiki/Commit_access (if you don't yet have SVN write
access).
Thanks and regards,
--
Jack Phoenix
MediaWiki developer
Fellows,
This is Google's cache of http://en.wikipedia.org/wiki/Devo. It is a
snapshot of the page as it appeared on 28 Sep 2011 09:22:50 GMT. The
current page could have changed in the meantime. Learn more ...
Like why is it so much faster than the real thing? Even when not logged in.
Nope, you may be one of the top ranked websites, but no by speed.
So if you can't beat 'em join 'em. Somehow use Google's caches instead
of your own. Something, anything, for a little more speed.
Because of the interest on [[WP:VPT]] in making deployments of MW on the
cluster go more smoothly, I've forked the discussion to a
sub-page: http://hexm.de/87
Please check it out and contribute!
Mark.
Here's part of the "long tail" of making everything fully compliant with
HTTPS page delivery.
I've noticed that there seem to be mixed-content problems with
HTTPS-loaded Wikipedia pages which display the fundraiser banner. At
least part of the problem seems to be this image:
http://upload.wikimedia.org/wikipedia/foundation/3/3d/CNbasicButtonParts.png
which is apparently loaded by the banner via a URL hard-coded into the
central notice CSS.
Can anyone else verify this?
Is there any simple and efficient way of fixing this in a way that will
"just work" in other similar cases, other than writing custom javascript
for this special case, or using the data: URI scheme?
-- Neil
Hi,
I am hoping that someone here can help me - I realize there is an
xmlwikidumps mailing list but it is pretty low volume and expertise relative
to this one. THere is a lot of conflicting advice on the mirroring wikipedia
page. C I am setting up a local mirror of english Wikipedia
pages-articles...xml and I have been stopped by repeated failures in mySQL
configuration.
I have downloaded the .gz data from the dumped and run it through mwdumper
to create an SQL file without problems, but things keep breaking down on the
way into mysql. I have had a lot of agony with inno_db log files, etc. and
have learned how to make them bigger, but I'm still apaprently missing some
pieces.
my target machine is an AWS instance 32 bit Ubuntu 1.7GB RAM, 1 Core, 200
GB, which is only for this project. I can make it bigger if necessary.
Can someone take a look at this my.cnf file and tell me what I need to
change to get this to work?
this is what my.cnf file looks like:
[mysqladmin]
user=
[mysqld]
basedir=/opt/bitnami/mysql
datadir=/opt/bitnami/mysql/data
port=3306
socket=/opt/bitnami/mysql/tmp/mysql.sock
tmpdir=/opt/bitnami/mysql/tmp
character-set-server=UTF8
collation-server=utf8_general_ci
max_allowed_packet=128M
wait_timeout = 120
long_query_time = 1
log_slow_queries
log_queries_not_using_indexes
query_cache_limit=2M
query_cache_type=1
query_cache_size=128M
innodb_additional_mem_pool_size=8M
innodb_buffer_pool_size=256M
innodb_log_file_size=128M
#tmp_table_size=64M
#max_connections = 2500
#max_user_connections = 2500
innodb_flush_method=O_DIRECT
#key_buffer_size=64M
[mysqld_safe]
mysqld=mysqld.bin
[client]
default-character-set=UTF8
port=3306
socket=/opt/bitnami/mysql/tmp/mysql.sock
[manager]
port=3306
socket=/opt/bitnami/mysql/tmp/mysql.sock
pid-file=/opt/bitnami/mysql/tmp/manager.pid
default-mysqld-path=/opt/bitnami/mysql/bin/mysqld.bin
Just wanted to raise two separate incidents that have been reported to me by
two separate users on meta.wikimedia.org after the 1.18 upgrade:
1) A user was attempting to look at all of the translations for a particular
banner in CentralNotice (a common task carried out with no issue prior to
the upgrade) when he saw this error:
PHP fatal error in
/usr/local/apache/common-local/php-1.18/extensions/CentralAuth/CentralAuth.i18n.php
line 19586:
Allowed memory size of 125829120 bytes exhausted (tried to allocate
7864320 bytes)
2) Another user was attempting to move a page on Meta when she saw this:
PHP fatal error in
/usr/local/apache/common-local/php-1.18/includes/GlobalFunctions.php line
1197:
Object of class AFPData could not be converted to string
--
Arthur Richards
Software Engineer
Fundraising/Features/Offline/Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hi all,
If you write, maintain or are otherwise active in development, and directly
or indirectly make use of MediaWiki, then you should subscribe to:
mediawiki-api-announce(a)lists.wikimedia.org
That is a mailing list that only brings important announcements for
developers that use MediaWiki as an API.
Note that this list is not limited to API as "api.php" but about MediaWiki as
a application programming interface (API) in general.
Subjects that have announcements on that list:
* Important changes in database schema (columns or tables added, removed or
changed in such a way that you should change your queries. Think for example
of the addition of rev_deleted, queries should most likely query for
rev_deleted=0 now).
* Changes in the JavaScript API (methods being deprecated or removed in the
mediawiki.js library etc. as well as upgrades of third-party libraries that
ship with MediaWiki, such as jQuery).
* Major changes to the HTML layout (such as the change for the sidebar id to
#mw-panel)
* Hooks in MediaWiki PHP. Mostly for extension developers. Changes or
deprecation of hooks.
* And last but not least, the api.php itself. All major changes.
===
Although time will learn how the list is used, to readers and writers of this
list:
"All subjects should clearly indicate what needs changing and when!"
For example "Vector skin sidebar html ID changes to '#mw-panel' in 1.17".
Also, whenever Wikimedia has scheduled a deployment of revision(s) or entire
branches that expose any change that was previously announced, a new mail
should be sent here to remind/summarize upcoming changes (since gadgets
should/can't be changed until the new version is deployed but new versions can
be prepared or tested in advance)
Hope to see you soon on mediawiki-api-announce(a)lists.wikimedia.org :)
Please reply-to to wikitech to keep discussions about this central.
--
Krinkle
What: Fundraising bug triage
When: Wendesday, October 5, 2011, 17:00UTC (10:00am PDT)
Where: #wikimedia-dev on irc.freenode.net
Wednesday, October 5, we will be conducting a bug triage for open
engineering issues relating to the Wikimedia Fundraiser. We will be
tackling some low-hanging fruit focussing mostly on some of the fundraiser
metric reporting tools, as well as some non-Mediawiki related tools.
This is a great opportunity for new devs to get involved with MediaWiki
development as well as for veterans to help out with one of the most
critical projects for the Wikimedia Foundation. We also have some CiviCRM
related bugs - so if you're a CiviCRM hacker or interested in exploring
another awesome open source project, this is for you!
Take a look at some of the open bugs we'll be addressing during the triage:
http://bit.ly/qSGKn4
Looking forward to seeing you there!
--
Arthur Richards
Software Engineer
Fundraising/Features/Offline/Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
