> I volunteered ages ago to try & reorganise naming conventions,
> and tie them in with things like presentation conventions, Wiki
> Projects and "basic topic" pages.
> I'm still mulling it over, and I'e got to the point where I'd like
> to start laying out ideas.
> There's no way this can be cleanly refactored overnight, so I'm
> thinking of using the Meta wiki, to first set out a page scheme and
> then start refactoring. That way "normal service" (!) won't be
> disturbed on the wikipedia: namespace.
> Any objections if I discreetly set up in a corner of MetaWikipedia?
That would be a good way to do it; another method that Mav used for
some of the element pages is to create a page ".../Temp", do all of
the editing there, and then delete it (after moving it to its final
spot). This wasn't an anticipated use of the delete feature, but I
think its a good one.
I rather like the way my reorganization of all the policy pages came
out; you might use that as a model for reoganizing naming conventions.
On the page [[Native American]] one of the books in '''Further Reading'''
has an external link which takes you to this page:
http://www.pricescan.com/books/bookDetail.asp?isbn=0838903533
(Only give a header and a blank page now but in the past has had a list of
bookstores and prices.)
When you edit the page you don't see any code that would generate that link.
If I were to put in a link to find a book I would probably do one for an
Addall search or an ABEbooks search since I find those work best.
http://www.addall.com generates income by being an affiliate of bookstores
as pricescan probably does too.
http://dogbert.abebooks.com is a used book listing service.
So what's going on and what do we want to go on?
Fred Bauder
> Before I too jump on the application bandwagon ;) -- what can
> sysops do that mortals can't?
Just a few "dangerous" functions that we don't want to give to
the general public: permanently deleting articles and history from
the database; querying the database in SQL; moving articles to
a new name with history (we'll probably make that one more
available after a bit more testing and debugging); blocking the
IP address of vandals.
Thought you guys might be amused by this bug
report I just received:
From the look of the Wikipedia web site, it seems
that any visitor can edit the content!
That can't be correct!
> I wanted to apply for sysop status and mailed Jimbo Wales, as
> mentioned on the page concerning the topic; he referred me to
> the list, however. Can any of you sysops judge if my "application"
> is valid? And then also fix the page concerning the topic?
I need to do some more work to the software to organize this process,
so we don't really have a formal process at the moment. I remember
your name from several bug reports you've filed (thanks), and you
participate on the list and have a valid email address, so if you'll
confirm for me that you are wiki user "Jheijmans", and I'll fix you
up.
P.S. I also looked at your contributions page, and it's over half
Talk pages. While they're certainly a necessary part of what goes on
here, we also have an informal tradition here (it was stated
somewhere once, maybe I need to put it into the policy pages) that if
you do a lot or "meta" stuff you should at least do a bit of work on
real articles to balance it out--edit some random articles, add a
short bio of someone, etc. Sysops ought to set an example here.
Hi,
I wanted to apply for sysop status and mailed Jimbo Wales, as mentioned on the page concerning the topic; he referred me to the list, however. Can any of you sysops judge if my "application" is valid? And then also fix the page concerning the topic?
Thanks,
Jeroen Heijmans
Hi, everybody. I thought it's about time I joined the list.
Instead of just a lockout button, why not also provide admins with the
ability to:
a) Limit edits to logged-in users, or
b) Limit the frequency of edits to "one edit per minute" for any
given user or any given IP
(You could adjust the time value of one minute in option B above.)
--Ed Poor
> What I do fear is some script kiddy with a couple dozen rotating
> proxies and a ship-load of bots flooding the database with junk and
> overwriting 20 articles a minute. A panic button to lock-down the
> site would then be nice (Sorry, I can't protect pages fast enough).
> Then that would give a sysop the time needed to block all the IPs
> of the vandal. But again, I don't think we are at that point yet.
I actually do already have a "lock the database" button available
to developers; maybe I should make that available to sysops as well
(as long as "unlock" is as well, of course)?
I also need to start thinking about some back-end stuff like the cron
job for making more frequent backups.
Dear all,
This is my latest, and I hope final, mock-up rendition of Cologne Blue
that I intend to offer to replace the existing implementation of
Cologne Blue.
I enclose a mock-up page: this represents the final look intended in
standard-compliant CSS browsers like Mozilla and IE 6, but will probably
not work properly in non-CSS-aware browsers yet. There's still lots to
do, but the only way to find out is not to build a better mock-up, but
to write the working code.
I realise that this design is not perfect, but it is probably
nicer-looking than the existing implementation, and I'm reading the code
for the new software to see how to make the changes in an evolutionary
way will work with cross-browser support.
I'm also considering the idea of doing a version of this with tables
alone for old browsers that ignore or munge CSS.
If I do the CSS right, the CSS version should work OK for browsers like
Lynx.
Can anyone help me with how to go about contributing code, and where and
how to test it? The first thing I'll need to do is just to clone an
existing style, and call it something like "Cologne Beta", prior to
changing it step-wise into real code.
Once I have something up and running, then we can start voting for
features. As all code will of course be GPL, if you dislike it enough,
you'll be able to change it yourself.
Regards,
Neil
Does anyone know the status of photos taken of works in museums/galleries
(in this case, the Museum of Anthropology at UBC, Vancouver)
--
Gareth Owen
"Wikipedia does rock. By the count on the "brilliant prose" page, there
are 14 not-bad articles so far" -- Larry Sanger (12 Jan 2001)