Hi all,
It's been almost a month since the last post in this 'flagged revisions'
thread (sincere apologies if I've failed to find discussion which has no
doubt been occurring on lists and wikis everywhere!) - I wanted to ask for
an update from the folk at the coalface working on getting flagged revisions
ready for the english wikipedia.
There's a growing perception over at the english wiki that there is
technical programming work still outstanding in order for the flagged
revisions extension to be enabled - this is somewhat at odds with my
previous understanding that in fact, the code was ready. I think it is
becoming rather important for us to be very clear about the status quo.
(for example see jimbo's comments;
http://en.wikipedia.org/w/index.php?title=Wikipedia:Advisory_Council_on_Pro…
ensuing discussion about whether or not more programmers would be
helpful :-)
It would be great from my perspective to answer the following questions;
- Who will 'make the call' to switch flagged revisions on for the english
wikipedia - Brion? another developer? foundation staff?
- Is there any more technical programming outstanding to complete the
extension?
- Does the team / person responsible for completing this work feel
adequetely resourced? - is there any more the community or foundation can do
to expedite?
If foundation staff, and not the technical team, are delaying the activation
of this extention, perhaps for PR reasons to co-incide WIkimania and Flagged
Revisions, then to a degree I understand - I do however feel that the
english community would appreciate this information - in many ways it's a
volatile time amongst the en editors ('ain't it always!), so openess and
transparency become even more important!
best regards,
Peter,
PM.
I am not finished with the analysis (MacGyver) tool, but I thought I would put up what I have so far on the MediaWiki site. I have created a web page in my user space for the Parser Test code coverage analysis -
http://www.mediawiki.org/wiki/User:Dnessett/Parser_Tests/Code_Coverage
I would appreciate it if someone familiar with the parser would at least glance at the per file statistics for a sanity check. Some things that worry me are:
* parserTests seems to visit Special:Nuke. Does this make sense?
* Only about 72% of Parser.php is exercised. Is this reasonable?
* Xdebug is reporting that the Parser only has 2975 lines of executable code. This contrasts to the report by Happy-Mellon that there is 11,000 lines of code in Parser.php. Are there really that many non-executable lines of code in the parser or is Xdebug missing a whole bunch?
Hey all,
I've compiled a list[1] of extensions in Bugzilla that don't have a default
assignee. If you want to be (or should already be) the assignee for any
of these, please let me know. Would like to really cut that list down
so bugs are getting triaged to someone who cares. Right now, they're
all being assigned to wikibugs-l, and we know how many bugs he
resolves :p
-Chad
[1] http://www.mediawiki.org/wiki/User:^demon/Unloved_extensions
One of the great frustrations of Wikinews for me is that it doesn't
have a system for identifying and pointing users toward opportunities
to get out into the offline world and do original reporting. A
fine-grained cross-project opt-in geonotice system could be a
solution.
Here's how I imagine it working: there is a new opt-in geonotice (in
addition to the current one that reaches everyone in the specified
geography). For the opt-in geonotice (which would hopefully be able
to reach across projects, since many causal Wikinewsies visit that
site only rarely) any trusted user could add new items to let nearby
people know about reporting or photography opportunities. For these
opt-in notices, we would not need to lock down the ability to add
items like we do for the current geonotice system (it's a fully
protected page), since people who opt-in will expect a bit a noise.
So, for example, I would set a notice that Senator Chris Dodd is
holding a public discussion about health care reform on such-and-such
date in Hartford, Connecticut. I mark this as a photo opportunity and
a reporting opportunity. The system sets a default radius (or better
yet, users specify the radius they want to be notified within) and
everyone within x kilometers of Hartford who has opted in to the
notice gets a watchlist message pointing to more details. I can
imagine a wide range of tips and events that could be spread to the
right people with such a system.
This would do a couple things: it would draw in new users to Wikinews,
and given enough participation it could provide a resource that is
useful for professional journalists. Journalists are eager to figure
out useful ways to tap the knowledge of amateurs, and a widely used
geography-based tip-line is something that Wikimedia still has a
chance to be the first organization to do well. I think finding a way
to play a major part in the ongoing changes in the journalism world
ought to be a high priority for the Foundation.
-Sage Ross (User:Ragesoss)
Just a quick heads-up:
I spent a little time this week hacking up integration of test data for
the CodeReview extension, and the ability for ParserTests to upload its
invocation data there.
Once configured live, parser tests will be automatically run on all
checkins to MediaWiki trunk and the results will be visible on the list
& detail views at http://www.mediawiki.org/wiki/Special:Code/MediaWiki
This should help in identifying regressions. :)
The system allows for data on multiple test suites to be sent in, so we
can rig up similar tests for the unit test suites (if they get fixed up
to actually work right!) and client-side Selenium-based tests we've been
talking about but have yet to implement.
If we don't have time to set it up today, the parser test integration
should be ready by early next week.
-- brion
---------- Forwarded message ----------
From: Marc Riddell <michaeldavid86(a)comcast.net>
Date: 2009/7/31
Subject: [Foundation-l] Thanks to the WP Tech people
To: Foundation List <foundation-l(a)lists.wikimedia.org>
It's very good to see the English Wikipedia back and running smoothly again;
my withdrawal symptoms were getting hard to handle :-). Seriously, thank you
to all the people who fixed the problem.
Marc Riddell
_______________________________________________
foundation-l mailing list
foundation-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
Hi,
I wanted to integrate piwigo in my mediawiki website, however, the piwigo api does not permit to do it easily and furthermore it as some similar functions to mediawiki.
So, I began setting up my mediawiki to act as piwigo , using some extensions, I have got few questions to finish it :
a) Do you thing it will be better to put a namespace or use of category to setup photo web page ?
b) Is there a way to have a different toolbox setted up, when using specific namespace or category
c) I know how to setup a gallery, but is there a way to setup a primary article displaying only the first image of the gallery ?
Best Regards
S.Ancelot
The deployment branch, originally envisioned on the lists by myself, is
intended to provide users of mediawiki with access to the latest stable
revision - the one being used on Wikipedia, but not trunk. Unfortunately the
deployment branch has been subverted and is now full of WMF specific hacks.
Can we please have a the WMF deployment branch be a branch of an untainted
branch of the particular revision that is considered stable?
Many thanks!
/Brian