As wikipedia is slow at the busy time, I propose to get some new servers for our cluster.
- Some new web servers(3 or 4), P4 2,8Ghz with 2Go of RAM
- A server which could be a backup for nfs server, zwinger, with bigger disk, 80Go is very low, maybe 200 or 250Go
- Upgrading disk of zwinger to 200 or 250Go (or add a new one)
- A db server in 64 bits mode with 4Go of RAM (if we cant make working geoffrin), like this one :
With raid 10 disk system, 4 or 6 drives in raid and 1 stand-by. I prefer 15000rpm disk, but I can understand that they are more expensive
- Maybe another squid server
What do you think of that ?
In de: we have a lot of articles on graph theory missing example images. Graphs
are also useful in other articles to visualize information. Editing images of
graphs with your favorite program and format is a consumption of time and nobody
can easily alter my images. We do have <math> and <hiero>-section. I'd like
editable graphs with <graph>...</graph>.
We could easily use the DOT-syntax and
to create PNG-images or SVG. It's damn powerful and not that complicated!
I'm sorry a lot of these have been held up for a while; we've been
mainly working on stabilizing the wikis under the new server setup and
preparing to put out a new release of the MediaWiki software with all
the latest fixes and features -- for which of course we'll want the
latest language files included.
My old todo list page has gotten rather unwieldy and out of date, I'm
afraid, and it's hard to tell what's been done, what hasn't, etc. It
would be a big help if people could put the relevant information onto
these new wiki pages (currently empty):
All the suggestions for native language names that have been posted
Please link to the exact wiki page that contains the updated file, or
attach an update and send it to this list and say which was sent.
If possible, please compare against the version of the file in CVS:
ensure that anything that got updated separately in CVS is also in your
Any other bugs or problems that are specific to one of the
languages/wikis: missing or corrupted messages, logo updates, sysops,
Hopefully we can get these things cleared up in the next few days...
-- brion vibber (brion @ pobox.com)
I hacked a little C++ utility (hereby under GPL, source files attached)
that converts HTML to wiki markup. A few points:
* It should compile on any Windows/*nix system (you might have to turn
off warnings, though)
* Pipe the HMTL in, and get wiki markup out
* Shouldn't touch existing wiki markup
* Keeps HTML if there's no wiki markup defined for it
* Other wiki markup (for other wikis) can be added with only a few lines
* Internally uses a new string class with 32-bit-chars (potential for
unicode there, also it should work with unicode "as is")
* Doesn't check HTML/wiki markup validity (broken HTML will become
broken wiki markup, which might be less bad though)
* Ignores <nowiki> (though I don't think that matters)
Idea: Have a checkbox on the edit page (or maybe on preferences instead)
"Convert HTML to wiki markup on preview"
Conversion *should* only take place prior to preview, so a human can
make certain nothing's broken.
There's been some progress with the monobook skin recently, new things
are basic rtl support and user styles.
You can tweak styles in the monobook skin by adding a page called
'monobook.css' as a subpage of your user page. My test css is at
http://test.wikipedia.org/wiki/User:Gwicke/monobook.css for example.
Similar with js, the it's called monobook.js in that case.
Other skins don't have the links in the header currently, but those are
easy to add.
The css and js pages are editable only to the user and developers, they
appear protected to anybody else.
The wiki src is retrived with a new method to get the raw wiki text:
application/x-zope-edit. Any of these return the plain wiki src, just
the content header differs. A charset option is optional, e.g.
Brion and me have added an RTL stylesheet to monobook, it seems to work
fine in Opera 7.23, Mozilla/Firefox, IE5.5 and mostly IE6. Screenshots
There've been some changes to the hardware: new disks on zwinger and
suda. If someone's got details, and any knowledge of browne's
situation, an announcement would be welcome.
Currently we're having lots of trouble with the squids.
-- brion vibber (brion @ pobox.com)
Several weeks ago, I reported what I thought to be
some sort of bug. At that time, it involved the
Wikipedia:Orphaned articles page becoming
"duplicated", meaning that the text of the page
appeared two and a fraction times.
I heard talk of this sort of thing happening
elsewhere, and now it has happened on Village pump.
In both cases (Orphaned articles and Village pump),
there were three very quick edits by one user --
apparently repeated clicking of the submit button?
Please take a look at the three edits to Village Pump
by User:Calmypal at 19:35, 29 Apr 2004.
It appears that the first one happened normally. The
second one replaced the page with a partial copy of
the page. The third one seemed to have a partial page
followed by a full page.
Note also that the first and third edit summaries
include the "M" for a minor edit, and a header in the
summary. The middle one had no "M" and no summary.
So, the user pressed submit, which worked but the user
didn't see the results. The user pressed submit a
second time, and then a third time sometime in the
middle of the second's processing, interrupting the
second and appending the third. Does that somehow make
Is it somehow possible that the edit conflict
resolution gets confused when it has a conflict
between the same user (if you know what I mean)?
I know that all the information is preserved in the
history, but fixing it, especially on a heavy use page
like Village pump, is a real pain in the butt.
Just out of curiosity, if I have two open edit
sessions of the same page, and press submit on both in
very short succession, what happens?
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs