Good news:
I went to see the servers this evening, after a trip to Fry's. I
bought a new hard drive (36 Gig U320 SCSI 80-pin) for Pliny's DB and 1
more Gig of RAM for Larousse (that's the best Fry's could do).
Bad news:
Only the RAM got installed. It turns out that the setup in Pliny
(unlike every other server in our cage) uses 68-pin SCSI drives. So,
my purchase was incorrect.
Summary:
Larousse has 2 Gig of RAM (PC133 SDRAM), 1 Gig more than before.
Pliny is the same old machine.
--
"Jason C. Richey" <jasonr(a)bomis.com>
Brion Vibber saith:
>On Fri, 8 Aug 2003, Erik Moeller wrote:
>> I intend to edit relevant documentation and webpages to change the name of
>> the software from "Phase III" to "MediaWiki". This is the name that Mav
>> suggested, and it fits nicely together with "Wikimedia". Google shows that
>> the name is unused. Any objections?
>
>Sounds nice, and less likely to send crowds of confused protesters after
>us than "PediaWiki". ;)
What exactly was the history of PediaWiki? I've seen that name occasionally...
mostly in outdated pages. I understand it was the original name of the
software, but...why was it called that?
And MediaWiki intuitively sounds like software for editable multimedia -
something where people can edit sounds and movies online, etc. Wikimedia
sounds like a corporation (which is OK since it's a foundation) but a MediaWiki
is (to me) a Wiki for multimedia. There's no real "editing" of pictures/sounds -
you can replace old media with new...but that's not really a Wiki: Wikis need
editing abilities, else anonymous FTP to an HTTP-served directory could be
called a Wiki.
Why do we need to _rename_ Phase III? Keep that for the name for Phase IV,
which meta's Main Page used to say was a temporary name (probably still does...)
=====
-Geoffrey Thomas
geoffreyerffoeg(a)yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Hi,
I intend to edit relevant documentation and webpages to change the name of
the software from "Phase III" to "MediaWiki". This is the name that Mav
suggested, and it fits nicely together with "Wikimedia". Google shows that
the name is unused. Any objections?
Regards,
Erik
I have been arguing in the past about the oversized fonts, especially
the headers. Well I found out something:
I am probably one of the few people that sees the English Wikipedia in
such a large font size. I use MSIE, default settings (medium text, which
suits me fine on most sites), but I use font Arial Unicode MS , this is
a huge (50 Mb) unicode font that shows most foreign languages well.
Microsoft only supplies it with its Office Suite. I installed it
specifically to be able to render other Wp's at their best. Now it turns
out that this font uses a larger point size for medium text (about 15%
larger than Arial). So this explains why I was bothered more than
others.
People on unicode Wikipedias are more likely to have deviated from MSIE
default fonts. I think this is yet another argument why it would be nice
to have user defined skins (without CVS or sysop intervention), people
could pick their favourite from a list of uploaded skins, e.g. sorted by
popularity.
Erik Zachte
When I try to run a page that has the <math> function I get this error.
from within function "renderMath". MySQL returned error "1054: Unknown
column 'math_conservative' in 'field list'".
This is mysterious because the current create db asks you to create this:
mysql> show columns from math;
+----------------------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+----------------------------+-------------+------+-----+---------+-------+
| math_inputhash | varchar(16) | | PRI | | |
| math_outputhash | varchar(16) | | | | |
| math_html_conservativeness | tinyint(1) | | | 0 | |
| math_html | text | YES | | NULL | |
| math_mathml | text | YES | | NULL | |
+----------------------------+-------------+------+-----+---------+-------+
Fred
On Thu, Aug 07, 2003 at 06:33:59PM +0200, Lars Aronsson wrote:
> Hi Tomasz,
>
> > <dl><dd><dl><dd><dl><dd> Triple indent
> > Any idea to do it in a saner way ?
>
> Five for every colon.
>
> HTML sucks.
No, it will not work at all.
:Foo bar buzz. Ala ma kota. Siala baba mak, nie wiedziala jak.
With blockquote:
Foo bar buzz. Ala ma kota.
Siala baba mak, nie
wiedziala jak.
With s:
Foo bar buzz. Ala ma kota.
Siala baba mak, nie wiedziala
jak.
Lightning wrote:
>I really wish wikipedia had used the public domain
>as a license.
Public domain is /not/ a license. It is the lack of a
license.
>therefore everything would be able to be used
everywhere.
And then Encarta gets a huge free update by importing
all our work into their encyclopedia and then /not/
allowing us, or anybody else for that matter, to use
their improvements as a basis to further improve the
text. The whole cycle of positive feedback gets sucked
dry by parasites who take our text and enslaves it
under a proprietary license. Copyleft protects the
freedom of the content itself.
Information is already free; with copyleft we are
ensuring that it's presentation will also be free.
-- Daniel Mayer (aka mav)
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
>>>>> "SV" == Steve Vertigo <utilitymuffinresearch(a)yahoo.com> writes:
SV> I still dont see Evans point -- what would be the reason for
SV> breaking from GNU FDL at all?
Umm, here's the deal:
http://www.wikitravel.org/article/Wikitravel:Why_Wikitravel_isn%27t_GFDL
The basics: we want Wikitravel content to be useful as 1-2 page
fliers, printouts, etc. Tourist agencies, hotels could keep stacks on
the counter and pass them out in paper form. Helpful travellers could
keep copies of articles in their backpacks.
The GFDL requires also distributing the 8-10 page content of the GFDL
itself, as well as a changelog, with each article. If you distribute
more than 100 copies -- pretty reasonable, actually -- you also have
to distribute the "transparent" work, i.e. Wiki markup source
code. So if you have a stack of 100 photocopies of a one-page article
-- pretty reasonable -- you have to have 1000 pages of license text
and a stack of 100 floppy disks or CD-ROMs.
With the by-sa CC license, you have a copyright notice and the URL of
the license. Baddabingbaddaboom.
We need a print-it-and-go-license; the GFDL is much more oriented to
publishing bound books, where adding another 10 pages isn't really
that important.
SV> Its not the software that drives wiki -- its the open
SV> principle that drives the softwares development (no to mention
SV> the WP's resonance) -- the FDL is simply a way to codify that
SV> principle. Quote: "Contributors (OK, all 20 so far B-) and
SV> redistributors of Wikitravel"
I'm not sure I followed this part.
~ESP
--
Evan Prodromou <evan(a)wikitravel.org>
Wikitravel - http://www.wikitravel.org/
The free, complete, up-to-date and reliable world-wide travel guide
>>>>> "AE" == Andre Engels <engels(a)uni-koblenz.de> writes:
AE> Yes, the _publisher_ can offer as many licenses as he wants,
AE> but the _copier_ can redistribute it under only one one
AE> license, namely the license that he has accepted.
Ah, yes. And, being as wikitravel.org and every contributor would be
copying, deriving, etc., this is kind of a problem.
I'm really grateful for the Wikipedia software, and I'd like to figure
out a way to make Wikipedia and Wikitravel content miscible. If it was
just _me_ having to put up with the hassle, well, that's fine.
But, y'know, it's not me who'd pay the price. It's all the
contributors (OK, all 20 so far B-) and redistributors of Wikitravel
that would have to pay. I don't think that's really fair.
~ESP
--
Evan Prodromou <evan(a)wikitravel.org>
Wikitravel - http://www.wikitravel.org/
The free, complete, up-to-date and reliable world-wide travel guide
Hi, folks!
I just committed my changes. Default behaviour should be as usual. See
DefaultSettings.php for details.
Added:
+ Whitelist mode for reading and/or writing articles. If either one is
turned on, only logged in users are allowed to read and/or write
articles. It is still possible to view the rest - i.e. SpecialPages,
searches, etc. I admit this is merely a hack. A better way of
implementing this would be the complete block of acccess to the Wiki.
This would require changes to the Skins, though.
+ Whitelist mode for creating new accounts. Admins can define a list of
rights. Users who have a suitable right may create a new account. Rights
include: user (all users - even anonymous), sysop, developer. This, too,
is just a hack. Phase3 still lacks user friendly user management.
Changed:
+ It's possible to create an account for a friend and send her a
password by mail with the push of a button. This is only available for
logged in users who are allowed to create accounts.
+ Option that defines the mail sender for password reminder eMail messages.
Bye!
Matthias