2008/1/3, Samuel Wantman <sam(a)wantman.net> wrote off-list and later
gave me permission to reply on-list:
...
> I agree with you that this should not be on a commercial site. It should
> be part of Wikipedia. Anything outside of Wikipedia is a backwater. I ask
> everyone I meet if they've been to Wikipedia. They all say they have. Then
> I ask them if they have ever been to Wikinews, Wiktionary or Wikia. Not a
> single person I have asked has even heard of Wikia. A very large majority
> have never been to any of the other Wikimedia projects. Anything moved from
> Wikipedia is moved into obscurity.
I agree 100%. Like you say, if it's not on Wikipedia, it doesn't exist.
Then again, some people will still want their stuff to be on
Wikipedia, not Extrapedia, but this will at least help avoid
[[WP:BITE]]'ing newcomers who write articles about non-notable topics.
But still, I think this could help.
> I already have a domain (Wikifree.org) and would host such a site, but I
> would rather see this happen as part of Wikipedia.
I, too, would rather it be done under the aegis of the Wikimedia
Foundation. Though I wonder if it'd really be practical to rally
enough support to get it approved.
Cheers,
--
Jason Spiro: corporate trainer, web developer, IT consultant.
I support Linux, UNIX, Windows, and more.
Contact me to discuss your needs and get a free estimate.
+1 (613) 668-6096 / Email: info(a)jspiro.com / MSN: jasonspiro(a)hotmail.com
I understand the recent database indigestion was caused by someone
deleting the sandbox on en:wp to get rid of a virus. It's times like
these I wonder what happened to VoiceOfAll's individual revision
deletion work ... is there any time frame on this? It's easier to
oversight a single bad rev than it is to delete it, but much harder to
undo if in error ...
- d.
(Cross-posting to wikitech-l and foundation-l, I suggest replying on
wikitech-l.)
All known bugs in the new preprocessor have been fixed. So it's now time
to enable it on Wikimedia. Unfortunately, a lot of articles and templates
rely on bugs in the old parser, and ideally they should be fixed before
the switchover.
We'll be aiming to switch to the new preprocessor on the 24th of January.
For technical background information about this project see my first post
on this subject:
http://lists.wikimedia.org/pipermail/wikitech-l/2007-November/035154.html
Over the past few days, Splarka and MZMcBride have been putting in a great
deal of work to beta test the new parser, by checking articles on the
English Wikipedia and several other wikis for any changes. Between the
three of us, we've built up extensive documentation of the commonly-seen
differences between the old and new parsers, and we've identified and
fixed eight distinct bugs in the new parser.
http://meta.wikimedia.org/wiki/Migration_to_the_new_preprocessor
We'd now like to invite the rest of the community to help.
This post is just a brief summary of the wiki page, please go there to
find out more.
The two most common problems with existing articles are comments after
headings, and abuse of bug 5678. Here's a comment after a heading:
== Heading == <!-- that was a heading -->
This will still make a heading in the new preprocessor, but it won't make
a section edit link. In the old parser, it does make a section edit link.
This change was done to resolve various incarnations of bug 4899, i.e.
mismatches between the section edit link and the section you end up editing.
Bug 5678 is a cluster of problems associated with double-parsing of the
results of parser functions. It's often reported and causes a great deal
of distress. But since the standard way to find out how to write wikitext
is to try it and see what works, many people have inadvertently utilised
behaviour arising from this bug to do various things.
A typical example is misuse of {{!}} to separate template parameters, as in:
{{#if:1| {{template{{!}}parameter}} }}
In the new preprocessor, {{!}} can never be used to separate parameters.
The fact that it was possible in the old parser in certain circumstances
was an accident.
Please see [[m:Migration to the new preprocessor]] for information about
how you can find and fix these problems.
I have introduced two cool new parser features to help ease the pain:
{{#tag:}} and {{#iferror:}}. #tag allows you to invoke XML-style tags such
as <ref> with syntax similar to parser functions, with full access to
template parameters. For example:
{{#tag:ref|[{{{url}}} {{{text}}}]}}
This is equivalent to:
<ref>[{{{url}}} {{{text}}}]</ref>
except that it works. You can also use #tag to call <imagemap> and
<gallery>. #tag is a core parser function with a slightly different syntax
to the one used by the TagParser extension. It is intended for use in
meta-templates where the simpler XML-style syntax is not sufficiently
versatile.
#iferror detects error return codes from #time and #expr. It is part of
the ParserFunctions extension.
-- Tim Starling
Hello,
the component "Site requests" in bugzilla had this description:
Requests for new sites (like wikis) go here. The wiki should be approved
on meta (e.g. be listed on
<a href="http://meta.wikimedia.org/wiki/Approved_requests_for_new_languages">
<q>Approved requests for new languages</q></a>) <b>before</b> a request is
filed to create it
but has often been used by request submitters to tag general shell
requests. Due to these frequent misunderstandings, I've changed the
description to reflect the component's use:
Requests for config changes for the sites hosted by the Wikimedia
Foundation.
Best regards,
jens frank
I just got a DB error on trying to log in:
"User::invalidateCache". MySQL returned error "1114: The table 'user'
is full (10.0.0.235)".
Not good...
On Jan 16, 2008 2:43 PM, Andrew Gray <shimgray(a)gmail.com> wrote:
> On 16/01/2008, Elias Friedman <elipongo(a)gmail.com> wrote:
> > I can view articles, and even use the edit window's preview function, but I
> > can't save any changes.
>
> Large page deleted, backend servers snarled up a bit. I think it's at
> the "solved but choking it all down" stage now, but you may not want
> to quote that :-)
>
> --
> - Andrew Gray
> andrew.gray(a)dunelm.org.uk
>
>
> _______________________________________________
> WikiEN-l mailing list
> WikiEN-l(a)lists.wikimedia.org
> To unsubscribe from this mailing list, visit:
> http://lists.wikimedia.org/mailman/listinfo/wikien-l
>
--
-george william herbert
george.herbert(a)gmail.com
Hello friends,
I am Murali from Hyderabad, India. I am a flash game programmer and web developer.
I am very happy to let you know about my new website wikirace.org. As you all might be aware of wikiracing, my website provides an online place for wikiracers to play and compete.
Wikirace.org is the first wikiracing website. It is the free wikipedia racetrack for wikiracers. Players earn points for every race they finish and every record they break. At Wikirace.org players cannot edit articles which will ensure no workarounds. Year links, date links, category pages, list pages and few disambiguation pages are disabled to make races interesting.
Please check the website and send me your feedback.
Thank you
Murali
simetrical(a)svn.wikimedia.org schreef:
> Revision: 29819
> Author: simetrical
> Date: 2008-01-16 00:06:42 +0000 (Wed, 16 Jan 2008)
>
> Log Message:
> -----------
> * Rollback should not work if the wiki is read-only
> * Spacing, 80-char lines, adjust some comments
>
> Modified Paths:
> --------------
> trunk/phase3/includes/Article.php
>
> Modified: trunk/phase3/includes/Article.php
> ===================================================================
> <snip>
> + * FIXME: This is silly, those messages should be possible to output di-
> + * rectly.
> <snip>
>
For some reason, OutputPage has separate methods for these. Dunno why.
Roan Kattouw (Catrope)
hi anybody,
i am searching for an opportunity to visualize some kind of social network
within wiki. this means i want do display connections between peoples and some
information concerning this people. comparable to xing e.g.
are there any appendages to realise such a functionality?
or maybe some kind of application which could be integrated into mediawiki?
greets
demagggus
Hi, I'm an English Wikipedia administrator. I'd like to make a change to
our user interface, but first I need to know whether it has support.
A problem I frequently encounter is that disruptive users create multiple
accounts to avoid scrutiny. These users often are not banned after being
caught. It isn't very nice to make an active user keep a sock puppeteer
template on their user page. Nonetheless, we need to know when a user has
had sock puppets, because this affects how we deal with future disruption.
When assessing a user conduct issue, we need to know the block history of
the user, and also the block history of any sock puppets. Currently, I must
rummage around to find all the necessary information. This process could be
made more efficient with one simple change.
The idea would be to add two links below the boilerplace text at the top of
special:log&type=block&user=USERNAME. The links would point to the two
sockpuppet categories associated with USERNAME. When looking at an editor's
"rap sheet" it will be very helpful to see whether those links are red or
blue, and if blue, to drill down and see the evidence.
For [[User:ECW500]] the links would be:
<small>[[:Category:Suspected Wikipedia sockpuppets of ECW500]] |
[[:Category:Wikipedia sockpuppets of ECW500]]</small>
For me:
<small>[[:Category:Suspected Wikipedia sockpuppets of Jehochman]] |
[[:Category:Wikipedia sockpuppets of Jehochman]]</small>
As you see, this won't take up much screen real estate. The change would
improve website usability and help the community by making all the relevant
information available via links from a single page. What do you think?
--
Jonathan Hochman
Web Marketing * www.jehochman.com
jeh(a)jehochman.com * 860-777-2011