Changes since 1.2.4:
* Fixed install problem with blank root password
* Fixed Special:Emailuser/Username links
* Fixed main-page edit links on fuzzy search results
* Fixed wikipedia-interwiki.sql
* Fixed install with apache2filter (ugly URLs)
* IP in 'go' search brings up contributions
* Switch from broken & to ? on top-level wiki URL hack
* Fix for moved pages in enhanced Recentchanges
* Initial main page on new installs links to the online documentation
There are no database format changes.
If you encounter a problem in the installation process, please include
*all* of the output under the 'Checking environment' heading with your
-- brion vibber (brion @ pobox.com)
When I joined Wikipedia more than 2 years ago, I
remember much unhappiness due to lack of information
of some parts of the project. For those who may not
have this memory (omg, I feel old in saying this),
lack of information lead to a fork. Though a fork is
certainly very unlikely these days, I believe the
growing feeling that fair process is not respected, is
bad for general spirit.
I remember that situation improved a lot, partly
because mailing lists were reorganised, partly because
meta became multilingual, and mostly partly because
people made an effort to
1) give information and
2) give it at the right place
3) discuss things before deciding it (or at least gave
people the opportunity to discuss it)
Sorry to say that, but I think we are on the bad slope
again. And I think we should seriously think about it.
Typical signs which I believe show information flow is
broken again ?
-> I hear people complain on irc
-> We start mail crossing again in an attempt to
restructure mailing flow
-> Things are learned again, not by regular channel,
but by personal information network.
Couple of points
* I think that software improvement should follow
needs, not the reverse. It may be either because
there is open and pressing request from users, or
because there was a suggestion and a developer had a
great idea. But it is curious that soft improvements
are made without users knowing (ie, without the
improvement been mentionned elsewhere than on
wikitech). Could soft improvement be mentionned on
wikipedia-l then ?
* When a soft improvement is done to fit legal
requirements, please, could it be discussed on
foundation-l to check if that complies with the legal
* When a hardware update is being done, please, could
it be announced on wikitech, or on meta, so that when
users wonder what is going on, there is something else
to answer than "no idea"
* When a change is made in the purpose of donations,
could it be mentionned on foundation-l (rather than
only on en:) so that all projects could change the
initial purposes given by Jimbo ?
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
"Brion Vibber" <brion(a)pobox.com> schrieb:
> For '' and ''' we produce <em> and <strong> tags rather than <i> and
> <b>. Is this right or wrong?
> Arguments against are presented by one of our own Wikipedians, claiming
> it's an abuse of semantic markup:
> About the only argument in favor is "that's what UseMod did, and Wiki
> before it".
To give another argument: '' is also used for example for book titles.
In that case making it <em> is simply wrong, it should become <cite>
instead. Because the software is unable to see when <em> and when <cite>
is meant, we might as well make it <i>.
Since Wikipedia's contents is available under GFDL, it is OK to start
mirror websites to display the same contents, and many are doing so.
But does any mirror site provide a search function of their own that
is better than Google or Wikipedia's own? Is any innovation taking
place in that area?
Lars Aronsson (lars(a)aronsson.se)
Aronsson Datateknik - http://aronsson.se/
So, I find update.php really useful as a kind of 'make install' for my
local test installation. Is there a way we could leave this
Evan Prodromou <evan(a)wikitravel.org>
Wikitravel - http://www.wikitravel.org/
The free, complete, up-to-date and reliable world-wide travel guide
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)