Hello,
When I started looking at mediawiki code, I tried to find a
yacc/lex/bison php tool to generate a php parser given a syntax.
I have looked again at the pear site and found a wiki text parser
that started at the beginning of dec. 2003 (see below for link).
The class is still alpha stuff but it might possibly be used for our
usage ? Instead of trying to develop our own parser, maybe we can start
trow ideas in text_wiki class and maybe have one day an unified wiki
syntax that will be common to all wikis !!
Pear page of the package : http://pear.php.net/package/Text_Wiki
Package website : http://wiki.ciaweb.net/yawiki/index.php?area=Text_Wiki
The text_wiki supports tables, headers, definition lists, interwikis.
Maybe we can work with them ?
--
Ashar Voultoiz
Folks,
In conjunction with the Wizzy Digital Courier internet
access project http://wizzy.org.za/ I am considering
installing wikipedia.
Wizzy Digital Courier is primarily to enable Internet access
for countries / communities that cannot afford daytime
internet access, due to Telcom monopolies and per-minute
local telephone charges.
In two pilot schools, I have installed wikipedia on their
intranet, with great success. After initial skeptism from
teachers, it has become a very useful resource.
I install the wikimedia tarball, and a weekly snapshot.
Due to the time taken to download new snapshots, I only
do these between semesters - it can take a week or so to
download, using UUCP at cheap rates in evenings and weekends.
After feedback from teachers, I have two requests :-
1. Graphics (you knew that was coming !)
To determine feasibility of this, can you give me
an idea of the size of a potential graphics archive ?
An incremental snapshot would almost be mandatory for
this, I think.
2. A daily SQL update for the main page.
This will give it a newsy feel, instead of talking
about Mandarin Chinese for two months :-) I know
that some of the articles it refers to will not be
available, but ... tough.
Thanks again for an invaluable resource that almost replaces
the web at one fell swoop in places that cannot afford the web.
Cheers, Andy!
Erik Moeller wrote:
>Jimmy-
>
>
>>In my opinion, we are going to need another $100,000 of equipment by
>>the end of the year, *and* we can *easily* raise that from donations
>>from the general public.
>>
>>
>Yes. A $100K fundraising drive makes sense, but at least *some* content
>should be up - at least the squids serving pages in offline mode. That's
>because many of our visitors come from Google, and if fundraising is the
>first thing they see - and no content - they will be turned away.
>
>We should also have realtime updates of funds coming in, this can
>dramatically increase participation. This isn't that hard to do as PayPal
>provides an interface for it:
>https://www.paypal.com/en/cgi-bin/webscr?cmd=p/xcl/rec/ipn-intro
>
>Lastly, I think hardware alone is not enough. We need a fulltime
>professional systems administrator with direct access to the machines.
>Within a $100K budget that is certainly viable. If Brion wants a new job,
>I'd say he should be immediately offered this opportunity.
>
Since we haven't decided yet what hardware we need, or studied how much
it will cost, we don't know how accurate the $100,000 figure is.
However, I'm inclined to take Jimbo's estimate as applying to hardware
costs alone, not possible employee salaries. Given the growth in our
traffic, and the fact that our equipment is not yet adequate to handle
crisis situations, I think we have a lot to do just on the hardware front.
I don't mean to dispute that we are close to the point where paid
employees are necessary, and I agree that Brion is one of the first
people we should consider in that regard, if he's interested. (By the
way, Brion, I'm sorry I don't know how to say this in Esperanto, but
thanks for your efforts in getting the site back up, and you've
certainly earned having a day in your honor.)
However, in terms of financial planning, employee salaries are a
separate consideration from hardware, and not something we can address
through periodic fundraising drives. Salaries are an ongoing cost, and
in order to have employees we need to develop a revenue stream that can
support these costs. The revenue can be from general public donations or
some other source (grants?), but it must be reasonably reliable. Right
now, regular donation levels (outside of specific fundraising efforts)
are not even enough to support the cost of having one employee, even a
part-time one. People will be a lot more critical of our financial
management skills if we're asking for money "so we can make payroll".
In many businesses and organizations, employee salaries and benefits are
the single biggest expense, sometimes more than all other costs put
together. That may not ever be the case here, since we have the efforts
of so many fine volunteers. But if we are going to start hiring
employees, we need to have a good idea that we can pay them on a
continuing basis. Ideally, Larry Sanger should be the last person this
project has to lay off for financial reasons.
--Michael Snow
I cannot "prove" my innocence; and it is ridiculous that I am being asked to defend myself against crimes which don't even exist. If I am a sockpuppet (which I am not), so what? Many users have more than one account. What wikipedia page states that sockpuppetry is a bannable offence? Regardless, Im not a sockpuppet!
I should be unbanned, if you have a problem with me -- you can request mediation and then arbitration. The process should not be usurped by you people, simply because some of you have the power to do so.
---------------------------------
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger
It seems to me that EM's concerns are valid, wether or
not people choose to deal with or recognise them. That
is, that there should be a reasonable firewall between
encyclopedic projects and others. A "vanity project"
instigator myself, I can understand how people can
hold a reasonable objection to the idea that Wikimedia
be a haven for any number of conlang projects,
disguised as encyclopedias. The word is out, and most
certainly there will be more requests.
Since both the hapless Esperanto and the hopeless
Interlingua already have an established place, there
is little viable argument against conlangs in general.
The only reasonable option is to limit them to the
very few that promise some utility.
CS
User:KuniShiro on symbolwiki.org / Various ip ranges
on Wikien.
--- Timwi <timwi(a)gmx.net> wrote:
> Erik Moeller wrote:
>
> > Timwi-
> >
> >>Thanks for your support. Many many people, in fact
> a clear majority,
> >>support full rights for the Klingon Wikipedia.
> Unfortunately, it seems
> >>that this has no significance here. Klingon is
> being treated like
> >>cripple-crap simply because a very small, but very
> loud minority has
> >>some sort of quabbles with it. And because one of
> them has been given
> >>(and is apparently allowed to retain) the power to
> have everything their
> >>way, and then intimidate everyone who tries to
> undo it.
> >
> > Interesting. Is this the way you respect a
> compromise which you yourself
> > proposed?
>
> I failed to make it clear enough that I expected the
> limitations imposed
> on tlh to also apply to tokipona. Now everyone
> things I wanted the
> Klingon Wikipedia, when in fact I only wanted equal
> rights.
>
> And the only reason why we still don't have equal
> rights is because
> people like you insisted on opposing tlh, because
> you said conceited and
> respectless things like "If anyone puts it back up,
> I'll go in there and
> suspend it myself!", and because the prejudice
> against the more
> widely-condemned Klingon is being adhered to more
> than the much more
> reasonable opposition against the less widely-known
> Toki Pona.
>
> Timwi
>
> _______________________________________________
> Wikipedia-l mailing list
> Wikipedia-l(a)Wikimedia.org
> http://mail.wikipedia.org/mailman/listinfo/wikipedia-l
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
I also think we are reaching a point where perhaps
someone will need to be hired.
However, I'd like to point out that it seems to me
that more organisation would be a good way to go as
well. No person on a payroll is ever available 24
hours a day, so just paying *one* person to do
technical maintenance will *not* suffice to fix
technical issues such as what happened two days ago.
When WP blew up, Brion was not available, not
reachable. Several developers spent a lot of time
trying to fix things. They tried to contact Brion and
Shaihulud. No one had Shaihulud references. Perhaps
would it be best that more developers are involved,
that they can contact one another more easily, that
they are more up-to-date with infrastructure status
and caracteristics ?
Now, should we start a fundraising campaign ?
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
U.S. Dollar (Primary): $4,330.40 USD
Canadian Dollar: $195.05 CAD
Euro: �1,646.27 EUR
Pound Sterling: �560.10 GBP
Yen: �5,239 JPY
Current Total in U.S. Dollars: $7501.42 USD
Total of of 28 May 2004: $4662.08 USD
Difference: $2839.24 USD
Also, could a developer include a donations link at the end of the 'Database is
read only ...' message? That should increase the donation rate.
-- Daniel Mayer (aka mav)
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
I am not a previous user who was formerly banned. I have not committed any wrongs. I have merely disagreed with User:172 over the content of an article, and now I am being blacklisted and denied even a pretense of fair treatment!
My posts are not accepted at the english mailing list, I am banned from the chatroom, I am personally attacked and insulted by numerous users, and I am currently banned without the support of Jimbo Wales, or the arbitration committee!!!!!!!!
This is not fair. This is not reasonable. This is not acceptable.
---------------------------------
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger