I'm interested in helping out in the development of mediawiki. I
think it's very good, but one that seems missing is a good system for
metadata and cross indexing information.
That might not be the best way to put it. As I see it, an article
would include more than just the text of the article. It would have a
summary (possible present on the page), and also metadata (like the
classification for an organism). e.g., on an article for a family of
turtles, say Chelydridae, you might want to list all of the genuses.
Instead of searching and hoping you have them all, then copy/pasting
or making your own summaries, you could just do something like
[[wikipedia searchForArticlesWithTags:genus,family=Testudinidae]
listData:scientificname,commonname,conservationstatus]
This would then automatically get all of those genuses, with the
information specified, and would update if anything changed or new
ones were added. You could also automatically grab summaries, which
are quite common [someArticle getSummary].
Something like this could also keep data in sync. I've seen several
instances of conflicting information between an article, and a small
summary in another article.
Is there something like this in progress? I'd like to help, but I'd
like to avoid duplicating effort on something someone is already
working on. I know how to program, and know a small amount of PHP.
Hi all.
Finally, the first upload of images created with WikiXRay is available:
http://en.wikipedia.org/wiki/Wikipedia:WikiXRay
For next updates I'll try to use Commonist for faster upload of lots of files.
Any comments about the graphics are welcomed.
Saludos.
Felipe Ortega.
---------------------------------
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.
http://es.voice.yahoo.com
Here's an idea. Have a "maintenance mode" preference for editors that
highlights errors in Wikipedia articles so they're easy to spot and
fix. For example:
- Links that go to disambiguation pages
- Links that go to redirects (not necessarily errors, but worth checking)
- Broken syntax - make it big and red and ugly rather than gracefully degrading.
- Spelling errors, possibly?
- Stuff that goes against MoS (for example, level 1 headings, links in
headings...)
There are already tools to do this, but they rely on a user making the
(pretty significant effort) to get AWB and decide that they're going
to do maintenance. Integrating highlighting like this into normal
Wikipedians' daily routine would be a lot more effective. And certain
problems like links going to disambig pages are really hard to pick up
unless you're specifically looking for them.
Any takers?
Steve
Hi All,
How do people feel about allowing the addition of type hinting to MediaWiki's internal function declarations?
E.g. from this:
function UploadForm( &$request ) {
to:
function UploadForm( WebRequest $request ) {
From:
public function parse( $text, &$title, $options, $linestart = true, $clearState = true, $revid = null ) {
to:
public function parse( $text, Title $title, array $options, $linestart = true, $clearState = true, $revid = null ) {
From:
function addLinkObj( &$nt ) {
to:
function addLinkObj( Title $nt ) {
Pros:
* Code is a bit more readable and self-documenting, and it's easier to see what's going on at a glance.
* Redundant object pass-by-refs in function declarations can more easily be identified and removed (i.e. in PHP5 only scalar types
where we modify the input need the pass-by-ref ampersands).
* Types are enforced.
Cons:
* Requires PHP >= 5.1.0 for array type hinting.
* Requires PHP >= 5.1.0 for allowing NULL as a default value for objects.
* For some things like the SpecialPage base class, it may not make sense to add this, so as to make for easier backwards
compatibility for extension writers who use "class MyExtension extends SpecialPage".
I.e. Is it reasonable to require PHP >= 5.1.0 for MediaWiki 1.10, which will be released around mid-April 2007? PHP 5.1.0 was
released on 24-Nov-2005. If so, are there any other reasons to do or not to do this?
All the best,
Nick.
We now have squid logs again, after a long absence. We're using the UDP
logging patch I describe here:
http://www.squid-cache.org/mail-archive/squid-dev/200701/0042.html
The log collection program is running on henbane. The log format is our
own custom format described here:
https://wikitech.leuksman.com/view/Squid_log_format
Only a sampled log will be stored, the full log will only be available as
a real-time stream.
I'd like to invite submissions at this stage for log analysis programs,
which can process either the full stream or a sampled stream, aggregate
the data and present statistics on the web. There are lots of log analysis
packages already available, but I haven't found one yet that is designed
to work at such a high request rate.
Currently we only have a raw log, which contains duplicates due to
requests forwarded between squids. These should probably be filtered out
by the collection daemon before the log is handed out to the analysers.
-- Tim Starling
It seems like the permissions control on rollbacks is a bit flawed. If
a wiki is set up to allow regular user's to rollback pages, they can
rollback protected pages, although they can't edit them, which can be
almost as disruptive as vandalism.
Was this functionality intentional? I would have assumed that if a
user didn't have the rights to edit a page, they wouldn't be able to
roll it back.
Travis
Hi everyone, sorry, newbie question, i think.
I have PHP 5.0 installed, acording to http://se.php.net/gd, GD is bundled
into the PHP install. When i'm running the Mediawiki install, though, under
Checking invironments it says "Couldn't find GD library or ImageMagick; image
thumbnailing disabled." Is there a certain version of GD required, or maybe
i havn't gotten PHP installed properly (?)
Thanks.
Hello everyone
Back in the summer I did a small demo
http://217.147.83.36:9000/history::171=170 that allowed tracking
contributions. It was quite slow and UTF-8 incompatible.
So I'm pleased to announce that after some optimization and rewriting
it in C I've managed to implement UTF-8 support and substantially
increase performance. At the moment it is several times faster than
current wikidiff2 extension (C++ version) and has peak throughput of
around 3 mb/s.
You can take a look at live demo.
Sample blamemap:
http://217.147.83.36:9001/wiki/Freebsd?trackchanges=blamemap&oldid=1524
Can track even a single character change:
http://217.147.83.36:9001/wiki/Freebsd?trackchanges=diff1&oldid=1516
Handles text swap:
http://217.147.83.36:9001/wiki/Freebsd?trackchanges=diff2&oldid=1513
I've plugged it into mediawiki code so at the moment every article and
talk page is having credits section and corresponding blamemap. At the
moment in order to use this you'll have to have root access to the
server and some changes to the mainline code and database will be
needed. If you're interested in testing this extension drop me a line.
Best regards
Roman
An automated run of parserTests.php showed the following failures:
This is MediaWiki version 1.10alpha (r19566).
Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...
18 still FAILING test(s) :(
* URL-encoding in URL functions (single parameter)
* URL-encoding in URL functions (multiple parameters)
* TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)
* TODO: Link containing double-single-quotes '' (bug 4598)
* TODO: message transform: <noinclude> in transcluded template (bug 4926)
* TODO: message transform: <onlyinclude> in transcluded template (bug 4926)
* BUG 1887, part 2: A <math> with a thumbnail- math enabled
* TODO: HTML bullet list, unclosed tags (bug 5497)
* TODO: HTML ordered list, unclosed tags (bug 5497)
* TODO: HTML nested bullet list, open tags (bug 5497)
* TODO: HTML nested ordered list, open tags (bug 5497)
* TODO: Inline HTML vs wiki block nesting
* TODO: Mixing markup for italics and bold
* TODO: 5 quotes, code coverage +1 line
* TODO: dt/dd/dl test
* TODO: Images with the "|" character in the comment
* TODO: Parents of subpages, two levels up, without trailing slash or name.
* TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.
Passed 489 of 507 tests (96.45%)... 18 tests failed!
January 20, 2007
Hello wikitech friends:
I have discovered that the following templates will provide the
following information.
1. Current Day (Sunday to Saturday)
{{CURRENTDAYNAME}}
2. Current Month (January to December)
{{CURRENTMONTHNAME}}
3. Current Day (1 to 31)
{{CURRENTDAY}}
4. Current Year (2007)
{{CURRENTYEAR}}
5. Number of articles on your wiki
{{NUMBEROFARTICLES}}
QUESTION
--------------
On Wikipedia.org, the number of page views can be found here:
http://en.wikipedia.org/wiki/Special:Statistics
What is the template one would use to indicate the number of page views
for a wiki?
Thanks.
David Spencer
in Canada