Where is my LART...
> This doesn't sound like the correct mailing list for that.
This list is correct for any wikimedia operational tech issues. Hence the name, wiki tech.
Domas
hello.
we currently have some problems with identifying current issues on the site, and
knowing what needs to be done, and so on. i've decided it would be a good idea
to spend some time on 'management' stuff like this, so i'm trying to come up
with a suitable procedure to make sure things work smoothly.
as such, i'd like to propose a new way to manage issues:
the primary point of contact for site issues will be the existing NOC ticket
system, noc(a)wikimedia.org. users should mail this address with any technical
issues *relating to the Wikimedia sites* (i.e., it does not replace bugzilla for
MediaWiki). confirmed issues will be moved to the new "issues" queue by the
"issues manager" (well, you know everyone needs a title). this will also apply
to requests from developers; for example, things that need to be done by the
on-site developer (previously Chad), and other developers (paid developers in
particular).
the issues manager can then formulate a list of tasks required to resolve each
issue, and place them on a wiki page somewhere (probably split by particular
people, and tasks for all developers). there's then a central place to look to
know what needs to be done. further, this can be used to produce a list of
open and resolved problems on the site, and what was done to fix them, to keep
users and the board better informed of what's going on. (for example, a weekly
'issues summary' mail to the list).
this can also be used as central point of contact for communications with
outside partners, such as Kennisnet and Lost Oasis (although purely for
technical matters, not negotiations).
unless anyone has strenuous objections to this, i'd like to try it immediately;
we can see how well it works, or whether anything needs to be changed. as i'm
not doing much actual developer work recently, i'll probably take on the role of
issues manager...
any comments appreciated.
regards,
kate.
"Kate" <keturner(a)livejournal.com> wrote in message
news:20050810074904.E780BDFD84@rose.local...
> i've set up a mail->news gateway for the mailing lists at
> news.wikimedia.org. it only allows reading, not posting to the lists. as
> well as carrying (and archiving) all lists, it may be useful when Gmane is
> down or having issues.
Just picked this message up after my holiday, and the server doesn't seem to
respond.
Has it been rescinded?
--
Phil
[[en:User:Phil Boswell]]
"Edward Z. Yang" <edwardzyang(a)thewritingpot.com> wrote in message
news:42FD1FA9.4030901@thewritingpot.com...
> There are certain pages in Wikipedia where vandalism makes history pages
> very ugly.
[snippety-snip]
I like your ideas, and I have a further suggestion: why not copy a trick
from "Enhanced RecentChanges" and add collapsible sections?
You could collapse multiple edits by a single user into one line, with a
clickable arrow to reveal the details. You could do something similar with
your "rollback=>hide" idea: only display the rollback line with an arrow
which can reveal the edits which were rolled back.
Am I making sense?
--
Phil
[[en:User:Phil Boswell]]
Hola,
Tim Starling used to be "official" earlier, but now he's the most performance/scalability oriented (...and performing) guy here :)
And yes, this list usually contains us all. Or #wikimedia-tech on Freenode, where we usually lurk and respond.
Domas
----------------snip snip
> (Also, is there an official contact for this sort of thing? That is:
> who knows / gets to make the final decision of whether wikipedia can
> handle more load?)
The "official contacts" would be Brion Vibber <brion(a)pobox.com> and Domas Mituzas <domas.mituzas(a)gmail.com>.
http://meta.wikimedia.org/wiki/Chief_Technical_Officerhttp://meta.wikimedia.org/wiki/Hardware_Officer
But, asking on this mailing list may be better since others on the development/sys admin team may have opinions on the matter.
Angela.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
[people on wikien-l wanting the article rating feature switched on]
Magnus Manske (magnus.manske(a)web.de) [050907 00:40]:
> I know, Brion is busy with the XML export/import and a zillion other
> things, but if you find a few minutes, maybe you could give it a quick
> check and turn it on? If it drags the servers down, it can always be
> turned off again...
I understand he didn't like it pulling in all revisions (that being the
aspect which would bring the DB to a grinding halt). Perhaps pull in
just the last ten, and let people page back through earlier revs ten at a
time? And if rating articles is HUGELY popular, change that to five revs at
a time ;-)
http://mail.wikimedia.org/pipermail/wikitech-l/2005-June/030325.html
- the second and third problems there can be worked around by requiring
steward or wikisysop-level access to mess with stuff; changing rating
categories would presumably be a fantastically rare action.
- d.
Due to popular demand (and my general dislike of interaction between
image changes and caching, plus a rash of vandalism of a certain type)
I've added two new permission keys to limit uploads that overwrite
existing images.
Disabling the 'reupload' right will prevent any upload of a file which
already is present, either locally or on the shared repository (Commons).
Disabling the 'reupload-shared' right will prevent overwrites of images
which are present on the shared repository but _not_ on the local wiki.
(A pre-existing local image overrides the Commons image.)
For fun I've set the default message to display a thumbnail of the
conflicting image on the error page like so:
http://upload.wikimedia.org/wikipedia/meta/3/3f/Upload_restrictions.png
Currently, reupload-shared is set to off for regular users on all
Wikimedia wikis, but the general reupload right is left on so local
images can be overwritten (and images on Commons can still be
overwritten there).
The message can be customized/localized at
[[MediaWiki:Fileexists-forbidden]] (for local images) and
[[MediaWiki:Fileexists-shared-forbidden]] (for Commons images)
-- brion vibber (brion @ pobox.com)
Well I'm a newbie coder/skinner :) I will try your method.
-----Original Message-----
From: wikitech-l-bounces(a)wikimedia.org
[mailto:wikitech-l-bounces@wikimedia.org] On Behalf Of Thomas Koll
Sent: Tuesday, September 06, 2005 3:14 PM
To: Wikimedia developers
Subject: Re: [Wikitech-l] Skinning A wiki
Am 06.09.2005 um 22:00 schrieb Bass, Joshua L:
> To get a header, I inserted a table at the top of the center table
> cell
> and gave it dimensions required for my header (i.e. height="150").
> There
> I put my site menu and logo.
That's so 90ies.
Better solution (untested):
give #logo position: absolute; left: 0; top: 0; width: 100%
use background-image in #logo to display your image.
for the three menus, put them into the sidebar where the should be and
use position: absolute; right: 0; top: 0; to position them. make sure
that #column-content and #column-one have a fitting margin-top
(found a nice hint for the margin: and padding: values : TRouBLe ;-)
ciao, tom
--
http://de.wikipedia.org/wiki/Benutzer:TomK32http://www.tomk32.de
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/wikitech-l
I was in the same boat as you are currently only a few weeks ago. The
wiki skins are based entirely on stylesheets, which is something I knew
very little about. This means, that objects on the page are located
based on the .css file where the class and id's are called out, rather
than where they are positioned within the skin.php (monobook.php) file
(to an extent). You can however develop a skin from the ground up as
long as you take into account the required fields.
I started with the monobook skin and add a header. This can be done
several ways. I chose to add a table around the entire skin, adding a
left table cell, center table cell, and right table cell. The left and
right table cells are used to "frame" the wiki. The center table cell
houses the contents of the wiki.
To get a header, I inserted a table at the top of the center table cell
and gave it dimensions required for my header (i.e. height="150"). There
I put my site menu and logo.
I had to change the css for the tabs (labled p-cactions in the monobook
skin) in order to located them below the header.
There are still a few bugs, but the skin is 99% complete. See it in
action here:
http://www.350z-tech.com/wiki
-----Original Message-----
From: wikitech-l-bounces(a)wikimedia.org
[mailto:wikitech-l-bounces@wikimedia.org] On Behalf Of Thomas Koll
Sent: Tuesday, September 06, 2005 2:48 PM
To: mattmozer(a)gmail.com; Wikimedia developers
Subject: Re: [Wikitech-l] Skinning A wiki
Am 06.09.2005 um 21:42 schrieb Matt Mozer:
> I was wondering if anyone here has any experience or has any
> information on
> skinning wiki's.
> I am looking for perhaps some white papers and or a tutorial. I am
> surprised
> not to find more on the web on it since it is no easy task for
> those not
> already tempered with the daunting task.
http://meta.wikimedia.org/wiki/Skins and
http://meta.wikimedia.org/wiki/Gallery_of_user_styles
ciao, tom
--
http://de.wikipedia.org/wiki/Benutzer:TomK32http://www.tomk32.de
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)wikimedia.org
http://mail.wikipedia.org/mailman/listinfo/wikitech-l
