from_name: Angela

body:
Please find the WikiSym 2007 call for papers below.

CALL FOR PAPERS

2007 International Symposium on Wikis (WikiSym 2007)
Wikis at Work in the World:
Open, Organic, Participatory Media for the 21st Century

October 21-23, 2007, Montreal, Canada
Co-located with ACM OOPSLA 2007
In cooperation with ACM SIGWEB

See http://www.wikisym.org/

Archived * Peer Reviewed * ACM Sponsored

OVERVIEW

The 2007 International Symposium on Wikis brings together wiki
researchers, practitioners, and users. The goal of the symposium is to
explore and extend our growing community. The symposium has a
rigorously reviewed research paper track as well as plenty of space
for practitioner reports, demonstrations, and discussions. Anyone who
is involved in using, researching, or developing wikis is invited to
WikiSym 2007!

We recognize the online world is always evolving, and we also welcome
contributions which are about other online media consistent with the
wiki philosophy of being open, organic and participatory.

We are seeking submissions for

* research papers (long and short): due 7 May 2007
* workshops: due 7 May 2007
* panels: due 7 May 2007
* posters: due 9 July 2007
* demonstrations: due 9 July 2007

Given the interdisciplinary nature of wikis, we invite contributions
from researchers and practitioners in a wide range of fields
including:

* business, marketing, law
* communications and media studies
* computer science, human-computer interaction
* history, political science, geography
* information and library science
* linguistics, discourse analysis, language studies
* natural sciences, medicine

Topics of interest to the symposium include, but are not limited to:

* wiki technologies and implementations
* wiki in the workplace; for business use
* wiki as social software for collaboration and work group processes
* wiki user experiences, usability, discourse analysis
* wiki for non-text media (images, video, audio) and spatial systems
* wiki content dynamics and evolution, wiki metrics
* wiki journalism; wiki archiving
* wiki reputation systems, quality assurance processes
* wiki administration, processes, dealing with abuse
* wiki scalability, social and technical
* wiki and the semantic web, knowledge management, tacit-knowledge
* wikis for specific domains (education, genomics, politics, etc.)
* wikis written by and for small audiences (ex: family wikis)
* wiki legal issues (copyright, licensing)
* wiki translation and multilingual wiki content

SUBMISSION DETAILS

Research papers will be reviewed by the Program Committee to meet
rigorous academic standards of publication. Research papers are
expected to advance the state of the art by describing substantiated
new research or novel technical results or by reporting on significant
experience (including case studies) or experimentation. They will be
reviewed both with respect to conceptual quality and clarity of
presentation. Note that authors of accepted papers are expected to attend
the conference and present the paper, otherwise publication will be canceled.

Accepted research papers will be provided as part of the conference
proceedings. They will be put into the ACM Digital Library and can be
referenced as papers that appeared in the "Proceedings of the 2007
International Symposium on Wikis (WikiSym 2007)". We invite full
papers (recommended length of 10 to 15 pages with maximum of 20 pages,
and a 30 minute
presentation time) and short papers (maximum 6 pages, with a 15 minute
presentation time). Papers should use the ACM SIG Proceedings Format,
see: http://www.acm.org/sigs/pubs/proceed/template.html

Workshop and Panels submissions will be reviewed and selected for
their interest to the community. A submission should consist of two
pages describing what you intend to do and how you meet this
criterion. It should include a 100-word abstract and one-paragraph
bios of all people relevant to the submission. Workshops will be
allocated a half-day or a full-day and a room of their own (depending
on your request). Panels will be given a 90 minutes time slot and a
room of their own.

Poster submissions will be reviewed on their merits and may describe
research projects or experience reports. A submission should consist
of two page extended abstract outlining the content of the
poster. Successful applicants will be invited to bring a poster for
display at the symposium. Posters must be flat and within 1mx2m in
size.

Demos will be reviewed based on their relevance to the community. A
submission should be one page in length, with a title, a short
description of the demo, as well as a description of any special
technical needs you may have (ex: wireless connectivity).

Please submit your papers or proposals in PDF format by the respective
deadline through our submission system, which will be available
through the WikiSym website. Questions should be directed respectively
at papers at wikisym.org (research papers and practitioner reports),
workshopsandpanels at wikisym.org (workshops and panels), or
demosandposters at wikisym.org (posters and demos).

SYMPOSIUM LOGISTICS

The 2007 International Symposium on Wikis will be held at the Palais
des Congr?s in Montreal, Canada, October 21-23, 2007. A special hotel
rate has been negotiated at the Hyatt Regency Montreal. WikiSym 2007
will be co-located with the ACM OOPSLA 2007 conference, and
participants may register for the symposium alone, or may jointly
register for WikiSym and OOPSLA 2007. Registration is handled through
the ACM OOPSLA website: http://oopsla.org/

If you have any questions, please contact Alain Desilets through
chair at wikisym.org.

SYMPOSIUM COMMITTEE

Alain D?silet, NRC-CNRC, Canada (Symposium Chair)
Robert Biddle, Carleton University, Canada (Program Chair)

Phoebe Ayers, U. of California Davis, USA (Wikimedia Liaison and Publicity)
Angela Beesley, Wikia / Wikimedia, USA (Posters and Demos Chair)
Mark Bernstein, Eastgate Systems, USA (Panels and Workshops Chair)
Ward Cunningham, Eclipse Foundation, USA (Honorary Chair)
Ted Ernst, Open Space World (Open Space Chair)
Andrea Forte, Georgia Institute of Technology, USA (Publicity Chair)
Dirk Riehle, SAP, USA (Treasurer and Corporate Sponsorships)
Peter Thoeny, TWiki.org and StructuredWikis LLC, USA (Web Master)

PROGRAM COMMITTEE

Ademar Aguiar, Universidade do Porto, Portugal
Phoebe Ayers, University of California Davis, United States
Angela Beesley, Wikimedia / Wikia, United Kingdom
Amy Bruckman, Georgia Institute of Technology, United States
Mark Bernstein, Eastgate Systems, United States
Robert Biddle, Carleton University, Canada
Sally Jo Cunningham, University of Waikato, New Zealand
Alain D?silets, National Research Council, Canada
Mark Gaved, The Open University, United Kingdom
Brian Greenspan, Carleton University, Canada
Beat Doebeli Honegger, UAS Northwestern, Switzerland
Matthias Jugel, Fraunhofer FIRST, Germany
Elizabeth Da Lio, Marche Polytechnic University, Italy
Ann Majchrzak, University of Southern California, United States
Sky Marsen, Victoria University of Wellington, New Zealand
James Noble, Victoria University of Wellington, New Zealand
Michele Notari, University of Applied Sciences Berne, Switzerland
Alejandro Ramirez, Carleton University, Canada
Dirk Riehle, SAP Research, United States
Hugh Robinson, The Open University, United Kingdom
Cristoff Sauer, Hochschule Heilbronn, Germany
Till Schuemmer, FernUniversitaet in Hagen, Germany
Sunir Shah, BibWiki.com, Canada
Robert Tolksdorf, Freie Universitaet Berlin, Germany
Brion Vibber, Wikimedia Foundation, United States
Max V?lkel, FZI Forschungszentrum Informatik Karlsruhe, Germany
Jacob Vo?, Wikimedia Deutschland, Germany
Christian Wagner, City University of Hong Kong, China


list: wikimedia-l

source: pipermail-mbox

subject: [Foundation-l] WikiSym 2007 Call for Papers


list: wikien-l

from_name: T P

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
On 2/25/07, Ray Saintonge <saintonge at telus.net> wrote:
>
> >I should have said there are no good solutions.  This problem requires a
> >working solution, and we do have one.
> >
> And a working solution need not be a panacea.  If it helps to solve some
> problems it becomes a stepping stone to further solutions.

I would never claim our current solution is the final one.  But we do need
to take the criticism of people like Scott McCloud with a grain of salt.

>Pesonally I don't care whether webcomics are included or not.  I think it's
> >a shame that we have no articles on [[Dance in China]] or [[Media of
> >China]], and [[Military of China]] and [[Tourism in China]] are just
> stubs.
> >
> Those people who are doing a good job with webcomics, by whatever
> standard that sub-community sets, do so partly because the subject
> interests them.  If we ban webcomics articles outright they are more
> likely to go away than to start writing scholarly articles about
> China..  Very few of them would know anything about the subject.

No, of course not.  I'm just saying we all have different priorities for
Wikipedia.

Adam


from_name: Andrew Gray

subject: [WikiEN-l] Reliable sources (Guy Chapman aka JzG)

body:
On 25/02/07, Steve Bennett <stevagewp at gmail.com> wrote:

> I would see no problem with an article about a scientist which was
> entirely about his professional contributions, and didn't so much as
> mention a date of birth, middle name or anything vaguely personal. The
> article should be primarily about their work, and that "biographical"
> information is purely incidental.

For many medieval (or earlier) figures known for their work, not their
life, we're in exactly this state - all sorts of significant
characters where we can guess what country they were born in and have
a decent stab at what decade, but unless they attracted someone to
write a short biography of them *and* had that survive, you're not
going to get much more.

--
- Andrew Gray
  andrew.gray at dunelm.org.uk


from_name: Bryan Derksen

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
Ken Arromdee wrote:
> Then policy is broken.  Straub may be the only person who proposed spurious
> deletions as an experiment, but there are plenty of people who propose
> spurious deletions just because they like to propose spurious deletions.
> These people don't play fair any more than Straub did, and the lesson that
> Straub taught us applies to them too.
>
> Just now, we've had
> [[Wikipedia:Articles_for_deletion/El_Goonish_Shive]]
> where I caught the same person trying to delete two webcomics articles using
> the same boilerplate paragraph while obviously not having checked to see if
> the claims made in the paragraph are valid for each specific article.  Please
> don't tell me this person is playing fair.

And now despite the AfD having come down quite strongly on the side of
the webcomic being "notable", I find that there's a great big notability
dispute template at the top of the page.
<http://en.wikipedia.org/w/index.php?title=El_Goonish_Shive&oldid=110456316>
I also note that there don't appear to be any guidelines provided in the
template for how to go about removing it. So for good measure I'm
throwing in a few external links that were raised in the AfD, despite it
being somewhat awkward shoehorning them into the lead paragraph, and
just plain taking it out.

Articles shouldn't have to have a paragraph beginning with "<subject> is
notable because..." just to survive. It's like we're tailoring our
writing style specifically for an AfD audience - I've actually seen an
article recently with a whole _section_ titled "Notability".


list: wikitech-l

from_name: zetawoof

subject: [Wikitech-l] WikiDump Parsing

body:
You'll do much better with a purpose-built lexical analyzer. If
nothing else, this'll work when titles and tags span across buffers -
something which the previous program will choke on on.

Released into the public domain as a trivial example program. Save as
'titleparse.l' and 'make titleparse'.

%option noyywrap

%{
    #include <stdio.h>
%}

%x TITLE

%%

<INITIAL>"<title>" { BEGIN TITLE; }
<TITLE>"</title>" { BEGIN INITIAL; putchar('\n'); }
<TITLE>"<" { putchar('<'); }
<TITLE>">" { putchar('>'); }
<TITLE>"&quote;" { putchar('"'); }
<INITIAL>.|\n /* ignored */

%%

int main(int argc, char *argv[]) {
    yylex();
    exit(0);
}


from_name: brion at pobox.com

subject: [Wikitech-l] MediaWiki automated test run failure 2007-02-26

body:
An automated run of parserTests.php showed the following failures:

This is MediaWiki version 1.10alpha (r20060).

Reading tests from "maintenance/parserTests.txt"...
Reading tests from "extensions/Cite/citeParserTests.txt"...
Reading tests from "extensions/Poem/poemParserTests.txt"...

  18 still FAILING test(s) :(
      * URL-encoding in URL functions (single parameter)  [Has never passed]
      * URL-encoding in URL functions (multiple parameters)  [Has never passed]
      * TODO: Table security: embedded pipes (http://mail.wikipedia.org/pipermail/wikitech-l/2006-April/034637.html)  [Has never passed]
      * TODO: Link containing double-single-quotes '' (bug 4598)  [Has never passed]
      * TODO: message transform: <noinclude> in transcluded template (bug 4926)  [Has never passed]
      * TODO: message transform: <onlyinclude> in transcluded template (bug 4926)  [Has never passed]
      * BUG 1887, part 2: A <math> with a thumbnail- math enabled  [Has never passed]
      * TODO: HTML bullet list, unclosed tags (bug 5497)  [Has never passed]
      * TODO: HTML ordered list, unclosed tags (bug 5497)  [Has never passed]
      * TODO: HTML nested bullet list, open tags (bug 5497)  [Has never passed]
      * TODO: HTML nested ordered list, open tags (bug 5497)  [Has never passed]
      * TODO: Inline HTML vs wiki block nesting  [Has never passed]
      * TODO: Mixing markup for italics and bold  [Has never passed]
      * TODO: 5 quotes, code coverage +1 line  [Has never passed]
      * TODO: dt/dd/dl test  [Has never passed]
      * TODO: Images with the "|" character in the comment  [Has never passed]
      * TODO: Parents of subpages, two levels up, without trailing slash or name.  [Has never passed]
      * TODO: Parents of subpages, two levels up, with lots of extra trailing slashes.  [Has never passed]

Passed 493 of 511 tests (96.48%)... 18 tests failed!


from_name: Jeffrey V. Merkey

subject: [Wikitech-l] MediaWiki 1.9.3 rebuildImages.php Mime errors

body:
running rebuildImage.php --missing produces a large number of warnings
due to undefined and unreferenced PHP variables.    After
running accross a full Wikipedia images directory it misidentifies all
of the .png files as mine type text/plain and tags them as
"possible malicious code".  The files are simple png images download
from commons.

Jeff


list: wikipedia-l

from_name: Walter van Kalken

subject: [Wikipedia-l] nl.wikipedia introduces wikipedia:Wikicity

body:
<sarcastic mode on>

http://nl.wikipedia.org/wiki/Wikipedia:Wikistad

Because of 2nd life's big succes the Dutch wikipedia brings to you
Wikicity. A place where you can buy your wikihouse, designed by
wikiarchitects build with wikimoney, by wikiconstructors, build with
wikisand on the foundations costs.

It is a place ruled by christians as a mosque was immediately
wikistroyed after it was erected before the muezzin could say its
wikiprayers. Also prominent wikidweller Osama Wiki Laden's wikihouse was
immediately evicted by the wikipubers ruling wikicity.

Next they will start laying wikirails for the Wikitrams and Wikitrains
and muliple cities are planned. Also wikivillages and wikivilla's are
planned and wikicanals and wikistreams will be dug.

This will all be done from the real money paid by our real donators who
expect an effort to build a real encyclopedia. Not a place where we try
to copy 2nd life or any other site with as a purpose building a
community. A bit of fun is fine. But this proposal makes fun the aim!

Waerth


subject: [Wikitech-l] Bad UTF-8

body:
Gregory Maxwell wrote:

>One problem I seem to run into over and over again while working with
>data from our projects is invalid UTF-8 sequences that litter our
>output. I could go on about how doing this is a horrible offense
>against man, but my main concern is to simply get around these issues
>in my own code.
>
>Does anyone have a document describing places where we're known to
>emit malformed unicode?
>
>

I have only seen this on some older dumps. Have not seen it for a while.
I parse them out of the dumps.

Jeff

>Tonight I encountered it in the file history output for a query.php request.
>
>http://commons.wikimedia.org/w/query.php?what=categories|templates|links|permissions|langlinks|backlinks|revisions|imageinfo&titles=Image:00022279.jpg&clextended&iihistory&iiurl&format=xml
>
>You can see it on the site proper at:
>http://commons.wikimedia.org/w/index.php?title=Image:00022279.jpg&action=history
>
>Simply striping the bad characters on the serialized output frightens
>me because I worry that eventually I'll strip an adjacent delimiter
>and make the output unparsable.  It would at least be useful to know
>all the places I could expect to find junk like this. :)
>
>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l at lists.wikimedia.org
>http://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>


subject: [Wikitech-l] WikiDump Parsing

body:
You could also just modify this code (released unde GPLv3) and use it to
strip out titles.

Stuff it into a file under linux called "parsetitle.c" and type:

gcc parsetitle.c -o parsetitle

./parsetitle < enwiki<date>.xml > titles.txt

Jeff

#include "platform.h"

#ifdef WINDOWS

#define strncasecmp strnicmp

#include "windows.h"
#include "winioctl.h"
#include "winuser.h"
#include "stdarg.h"
typedef UCHAR BYTE;
typedef USHORT WORD;
#include "stdio.h"
#include "stdlib.h"
#include "ctype.h"
#include "conio.h"

#endif

#ifdef LINUX

#include <unistd.h>
#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <ctype.h>
#include <string.h>
//#include <ncurses.h>
#include <termios.h>
#include <sys/ioctl.h>
#include <sys/stat.h>
#include <pthread.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <net/if.h>
#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <sched.h>
#include <ctype.h>
#include <openssl/md5.h>

#endif

char buffer[0x10000];
char title[4096];

int main(int argc, char *argv[])
{
    register char *s, *p;
    register int intitle = 0, i, f, inpage = 0;
    register int titlefound = 0, revision = 0, inrev = 0;

    while (s = fgets(buffer, 0x10000, stdin))
    {
       while (*s)
       {
          if (!*s || *s == '\n')
          {
             if (*s)
             {
//                putc(*s, stdout);
                s++;
             }
             break;
          }

          if (!memcmp(s, "<page>", 6))
          {
             s += 6;
             inpage++;
             titlefound = 0;
             revision = 0;
             continue;
          }

          if (!memcmp(s, "</page>", 7))
          {
             s += 7;

             if (!titlefound)
                fprintf(stdout, "no article title?\n");

             if (!revision)
                fprintf(stdout, "no revision?\n");

             titlefound = 0;
             revision = 0;
             if (inpage)
                inpage--;
             continue;
          }

          if (!memcmp(s, "</revision>", 11))
          {
             if (inrev)
                inrev--;
             s += 11;
             continue;
          }

          if (!memcmp(s, "<revision>", 10))
          {
             inrev++;
             revision = 1;
             s += 10;
             continue;
          }

          if (!memcmp(s, "<title>", 7))
          {
             intitle++;
             s += 7;

             p = strstr(s, "</title>");
             if (p)
             {
                if (intitle)
                   intitle--;

                if (p - s)
                {
                   strncpy(title, s, p - s);
                   title[p - s] = '\0';
                   s += (p - s);

                   for (f=i=0; i < (p - s); i++)
                   {
                      if (!isspace(*p++))
                         f = 1;
                   }
                   if (f)
                      fprintf(stdout, "[%s] SPACES?\n", title);
                   else
                      fprintf(stdout, "[%s]\n", title);
                }
                else
                   fprintf(stdout, "[%s] NULL?\n", s);

                titlefound = 1;
                continue;
             }

             if (intitle)
             {
                intitle--;
                printf("state error:  title spanned segments [%s]\n", s);
                continue;
             }
          }
//          putc(*s, stdout);
          s++;
       }
    }
    return 0;
}

Matthew Flaschen wrote:

>Brion Vibber wrote:
>
>
>>Harish TM wrote:
>>
>>
>>>I was trying to parse the Wikipedia dumps but unfortunately I find the XML
>>>file that can be downloaded a little hard to parse. I was wondering if there
>>>is a neat way to extract:
>>>                         1. The article title
>>>
>>>
>>/mediawiki/page/title
>>
>>
>>
>>>                         2. The article content ( without links to articles
>>>in other languages, external links and so on )
>>>
>>>
>>The article content *contains* those links, so I guess you mean you want
>>to parse the text and remove certain elements of it?
>>
>>
>>
>>>                         3. The category.
>>>
>>>
>>Again, that's part of article text.
>>
>>
>>
>>>Also I find that there are a large number of tools that allow one to convert
>>>plain text to media wiki text. What if I want to go the other way and
>>>extract information exactly the way it appears on the wikipedia site.
>>>
>>>
>>Run the wiki parser on it.
>>
>>
>
>Or download (http://static.wikipedia.org/downloads/November_2006/en/) it
>parsed.
>
>Matthew Flaschen
>
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l at lists.wikimedia.org
>http://lists.wikimedia.org/mailman/listinfo/wikitech-l
>


subject: [Wikitech-l] WikiDump Parsing

body:
This c program will also run and complete about 50 times faster then
that java and php code previously metioned.

Jeff

Jeffrey V. Merkey wrote:

>
> You could also just modify this code (released unde GPLv3) and use it
> to strip out titles.
>
> Stuff it into a file under linux called "parsetitle.c" and type:
>
> gcc parsetitle.c -o parsetitle
>
> ./parsetitle < enwiki<date>.xml > titles.txt
>
> Jeff
>


from_name: Gregory Maxwell

subject: [Wikitech-l] Bad UTF-8

body:
One problem I seem to run into over and over again while working with
data from our projects is invalid UTF-8 sequences that litter our
output. I could go on about how doing this is a horrible offense
against man, but my main concern is to simply get around these issues
in my own code.

Does anyone have a document describing places where we're known to
emit malformed unicode?

Tonight I encountered it in the file history output for a query.php request.

http://commons.wikimedia.org/w/query.php?what=categories|templates|links|permissions|langlinks|backlinks|revisions|imageinfo&titles=Image:00022279.jpg&clextended&iihistory&iiurl&format=xml

You can see it on the site proper at:
http://commons.wikimedia.org/w/index.php?title=Image:00022279.jpg&action=history

Simply striping the bad characters on the serialized output frightens
me because I worry that eventually I'll strip an adjacent delimiter
and make the output unparsable.  It would at least be useful to know
all the places I could expect to find junk like this. :)


from_name: The Cunctator

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
On 2/24/07, Jake Nelson <duskwave at gmail.com> wrote:
>
> I increasingly think we need to just nuke the whole deletion system.
> Unless there's sensitive content (personal information, etc.) or
> copyright violations that need to be removed from article history,
> just fix, stub, substub, or blank it (in order of decreasing
> preference).

Yes. This has the benefit of simplicity (meaning it has a chance of
working) and of utility.


from_name: Matthew Flaschen

subject: [Wikitech-l] WikiDump Parsing

body:
Brion Vibber wrote:
> Harish TM wrote:
>> I was trying to parse the Wikipedia dumps but unfortunately I find the XML
>> file that can be downloaded a little hard to parse. I was wondering if there
>> is a neat way to extract:
>>                          1. The article title
>
> /mediawiki/page/title
>
>>                          2. The article content ( without links to articles
>> in other languages, external links and so on )
>
> The article content *contains* those links, so I guess you mean you want
> to parse the text and remove certain elements of it?
>
>>                          3. The category.
>
> Again, that's part of article text.
>
>> Also I find that there are a large number of tools that allow one to convert
>> plain text to media wiki text. What if I want to go the other way and
>> extract information exactly the way it appears on the wikipedia site.
>
> Run the wiki parser on it.

Or download (http://static.wikipedia.org/downloads/November_2006/en/) it
parsed.

Matthew Flaschen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
URL: <http://lists.wikimedia.org/pipermail/wikitech-l/attachments/20070226/d28217ed/attachment.pgp>


list: foundation-l

body:
> Note that authors of accepted papers are expected to attend
> > the conference and present the paper, otherwise publication will be canceled.
>
> That seems like a good way to ensure it remains a strictly North
> American affair...

The same rule applied last year when WikiSym was held in what was
possibly the worst place for international travelers to get to (37
hours for me) yet certainly wasn't a Danish-only, or even
European-only, affair. I don't think it's unusual for conferences to
require that people attend the conference if they want to have their
paper published in the proceedings is it?

Angela


subject: [Wikitech-l] WikiDump Parsing

body:
zetawoof wrote:

> You'll do much better with a purpose-built lexical analyzer. If
> nothing else, this'll work when titles and tags span across buffers -

If they span buffers, the xml parsing libs choke as well, just for your
information.  I know, I've seen them do it.
I have a version that does not choke on buffer spanning, it buffers
underneath.  I just posted that as an example.

Jeff

> something which the previous program will choke on on.
>
> Released into the public domain as a trivial example program. Save as
> 'titleparse.l' and 'make titleparse'.
>
> %option noyywrap
>
> %{
>    #include <stdio.h>
> %}
>
> %x TITLE
>
> %%
>
> <INITIAL>"<title>" { BEGIN TITLE; }
> <TITLE>"</title>" { BEGIN INITIAL; putchar('\n'); }
> <TITLE>"<" { putchar('<'); }
> <TITLE>">" { putchar('>'); }
> <TITLE>"&quote;" { putchar('"'); }
> <INITIAL>.|\n /* ignored */
>
> %%
>
> int main(int argc, char *argv[]) {
>    yylex();
>    exit(0);
> }
>


body:
Rob Church wrote:

>On 26/02/07, Jeffrey V. Merkey <jmerkey at wolfmountaingroup.com> wrote:
>
>
>>running rebuildImage.php --missing produces a large number of warnings
>>due to undefined and unreferenced PHP variables.    After
>>running accross a full Wikipedia images directory it misidentifies all
>>of the .png files as mine type text/plain and tags them as
>>"possible malicious code".  The files are simple png images download
>>from commons.
>>
>>
>
>Please post sample output containing these warnings on a full bug
>report at http://bugzilla.wikimedia.org.
>
>

I will do so. It will be tommorrow. Time for some sleep right now ...

Jeff

>
>Thanks,
>
>
>Rob Church
>
>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l at lists.wikimedia.org
>http://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>


subject: [Wikitech-l] License status of MW screenshots.

body:
Jay R. Ashworth wrote:
> On Tue, Jan 23, 2007 at 02:15:02PM -0500, Simetrical wrote:
>> On 1/23/07, Jay R. Ashworth <jra at baylink.com> wrote:
>>> Someone vastly misunderstands the nature of copyright law, I think.
>>>
>>> (Though, admittedly, IANAL, either.  I just play on on the net.)
>>>
>>> If I create a screenshot of a browser page on my computer displaying
>>> wikipedia, there is *one* copyright involved: *mine*.  The image is not
>>> a derivative work of the browser, the OS, or the website.  Therefore,
>>> none of those people's copyrights apply, and therefore by induction, no
>>> licenses are necessary.  I created an image, and I own its copyright.
>>>
>>> The situation is pretty much identical to my *taking a photograph* of
>>> the screen displaying said browser.
>> Well, I can say that that's certainly not how Wikipedia interprets
>> copyright in such works.  Screenshots of copyrighted programs are
>> generally considered fair use, because the layout/coloring/general
>> appearance of the browser is deemed creative.
>
> Fair use of *what*?
>
>>                                                Whether this is the law
>> I don't know, but certainly a photo of a copyrighted work is
>> derivative of it (if even that).
>
> Derivative is a word with a fairly specific definition as a term of art
> in copyright law.  TTBOMK, only two very narrow categories of
> things-you-can-photograph require care on the part of the photographer:
> Fine Art, and architectural renderings (ie: fancy buildings :-)
>
> I'm off to read the article someone linked to now.

IANAL either, but I think this is blatantly wrong.  Photography and
screenshoting are both forms of copying, and all copying (partial or
total) are covered under copyright law.  If the photo includes little
previously copyrighted material, it is probably fair use.  A screenshot
of Wikipedia, however, includes an entire page of copyrighted material,
so it is not likely fair use.

Think about it.  By your logic, I could copy a whole book by taking
pictures page by page.

Matthew Flaschen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
URL: <http://lists.wikimedia.org/pipermail/wikitech-l/attachments/20070226/ea4bb6ca/attachment.pgp>


subject: [Wikitech-l] mwdumper does not work

body:
Rob Church wrote:

>On 26/02/07, Edward Z. Yang <edwardzyang at thewritingpot.com> wrote:
>
>
>>MySQL 5.0.18 is only experimentally supported by MediaWiki, the
>>production sites use MySQL 4.0.
>>
>>
>
>MediaWiki works with MySQL 5.x without problems if you use the latin1
>schema. I don't think this is the actual cause.
>
>Jeff, are you saying that the page histories appear to be blank when
>accessed? If so, this *could* be a caching problem if the page_touched
>columns haven't been updated.
>
>Could you run a quick statement such as UPDATE page SET page_touched =
>20070226080700 and see if that cures the problem? Please also do a
>hard-reload when viewing one of these pages.
>
>If I've interpreted what the problem is wrongly, then please clarify.
>
>
>Thanks,
>
>
>Rob Church
>
>

Rob,

I think you have it. I am running importDump.php across three wikis
tonight, so I'll have to retest tommorrow. I needed to get the
wikis back up, so after it barfed, I just purged out the databases and
started importDump on clean db files. I can also do this one tommorrow and
try out these commands.

Jeff

>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l at lists.wikimedia.org
>http://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>


body:
Jay R. Ashworth wrote:
> And, incidentally, you cannot *copyright* a logo.  You trademark them.
> And the rules for infringement on trademarks are much clearer than
> copyright; they're pretty much bright-line.  Passing off, reverse
> passing off, confusion, or denigration by association (as opposed to
> editorial).

Of course you can.  A logo is a work of art, and is always copyrighted
(unless copyright is specifically rejected which never happens in
practice) and possibly trademarked.

Matthew Flsachen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
URL: <http://lists.wikimedia.org/pipermail/wikitech-l/attachments/20070226/d6160347/attachment.pgp>


from_name: Tim Starling

subject: [Wikitech-l] Another master split

body:
Tim Starling wrote:
> We're planning on doing another master split this weekend.

Looks like I've run out of time. I've repartitioned all the slaves, that
was the main thing that required off-peak traffic conditions. We can do
the master switch itself during the day on Monday UTC, when there are more
sysadmins around.

The master partitions are designated s1, s2 and s3 (s for section),
assigned as follows:

s1: enwiki
s2: bgwiki, bgwiktionary, commonswiki, cswiki, dewiki, enwikiquote,
enwiktionary, eowiki, fiwiki, idwiki, itwiki, nlwiki, nowiki, plwiki,
ptwiki, svwiki, thwiki, trwiki, zhwiki
s3: everything else

There will also be two additional slave partitions -- sets of servers
which only replicate a reduced set of databases:

s2a: dewiki
s3a: frwiki, jawiki

We do this so that holbach and webster, slave servers with only 4GB of
memory, will have something useful to do. Holbach will be doing s2a and
webster will be doing s3a.

The server assignments at present are:

s1: db2, db3, ariel, db4, db6, db7
s2: db8, ixia, lomaria
s2a: holbach
s3: samuel, thistle, db1, db5
s3a: webster

The main potential pitfall I can see in the master switch is the
possibility that a client with an old configuration may write to the stale
copy of the databases in the old master. To avoid this, I'm proposing that
we change masters for both s2 and s3, leaving old clients harmlessly
attempting to write to a read-only slave. I've enabled binlogs on db8 and
thistle so that they can become the new masters. I'm hoping a Dell such as
db8 will be able to cope with the master load, which is typically less
than the full slave load.

It should be fairly straightforward:

* switch wiki to read-only
* change master assignment in MW
* switch master for s2
* switch master for s3
* switch wiki to r/w

It should only take a couple of minutes if we script the master switches.

-- Tim Starling


from_name: Rob Church

body:
On 26/02/07, Jeffrey V. Merkey <jmerkey at wolfmountaingroup.com> wrote:
> running rebuildImage.php --missing produces a large number of warnings
> due to undefined and unreferenced PHP variables.    After
> running accross a full Wikipedia images directory it misidentifies all
> of the .png files as mine type text/plain and tags them as
> "possible malicious code".  The files are simple png images download
> from commons.

Please post sample output containing these warnings on a full bug
report at http://bugzilla.wikimedia.org.

Thanks,

Rob Church


from_name: Pedro Sanchez

subject: [Foundation-l] a new free image!

body:
On 2/26/07, teun spaans <teun.spaans at gmail.com> wrote:
> I still havent read any good argument for allowing fair use, except that the
> english wiki is using it en masse. Which sounds like a very strange
> argument, it is like saying: it is forbidden to spit, but as everyone spits,
> we allow it. If everyone would be indulging in PAs on the english wiki,
> would we allow them too?
>
>
> On 2/26/07, GerardM <gerard.meijssen at gmail.com> wrote:
> >
> > Hoi,
> > There is no room to get NC and ND as an exemption.
> >
> > You can disagree all you like, the basics of the draft are not up for
> > discussion. There is room in the draft within very narrow confines to opt
> > for a different implementation. Fair use is only possible as part of the
> > an
> > EDP. It is up to a project to want to opt for an EDP. This EDP will have
> > to
> > pass the legal requirements mentioned. An EDP will be denied when it does
> > not comply with what is essential in the resolution.
> >
> > I expect that when the resolution or the EDP is not complied with, the
> > Foundation will reserve the right to enforce this requirement that all
> > projects have to comply with.
> >
> > Thanks,
> >     GerardM
> >
> >
> > On 2/26/07, teun spaans <teun.spaans at gmail.com> wrote:
> > >
> > > Hi Gerard,
> > >
> > > the draft says that communities may create excemption rules. Fair use
> > may
> > > be
> > > an excemption. According to Kats statement, ND and NC do not qualify as
> > > such. This is a draft, and drafts may be discussed. Please try to
> > > understand
> > > that some people disagree with this draft.
> > >
> > > i wish you health and happiness,
> > > teun spaans
> > >
> > > On 2/26/07, Gerard Meijssen <gerard.meijssen at gmail.com> wrote:
> > > >
> > > > Hoi,
> > > > The draft in and of itself does not approve Fair use. What it does is
> > to
> > > > allow a community to have an exemption for the strict rules if the law
> > > > of the US and the relevant countries allow for it. This is however
> > very
> > > > much not something that is favoured; this is clear in the restrictions
> > > > that surround exempted material. My statement about NC and ND is
> > really
> > > > simple. Material that is NC and ND will not be allowed. Fair use
> > > > material may be allowed. When material is allowed under the EDP as
> > Fair
> > > > use, it may have a NC or a ND license; this is incidental and actually
> > > > not relevant.
> > > > Thanks,
> > > >     Gerard
> > > >
> > > > PS Great to hear what you do with these collections .. I am glad to
> > hear
> > > > about this :)
> > > >
> > > > teun spaans schreef:
> > > > > I will probably respond to the rest later, as your statement about
> > NC
> > > > and ND
> > > > > raises som questions. As you have understood, I oppose the intended
> > > > draft if
> > > > > it allows fair use but disapproves other notions.
> > > > >
> > > > > But for the moment I'd like to say that I agree 100% with your
> > remark
> > > > about
> > > > > referring to the mention of museums ion the metadata.
> > > > >
> > > > > As you may or may not know, my main pix are in the area of biology,
> > > and
> > > > I
> > > > > got permission of two academic botanical gardens and a nursery to
> > > > photograph
> > > > > their collections on the condition that I mention their location on
> > > > upload.
> > > > > A condition I gladly fullfill, as I am grateful for the chance they
> > > > offer
> > > > > me.
> > > > >
> > > > >
> > > > >
> > > > > On 2/26/07, Gerard Meijssen <gerard.meijssen at gmail.com> wrote:
> > > > >
> > > > >> Hoi,
> > > > >> You read the draft incorrectly; NC and ND are on its own not
> > > permitted
> > > > >> in an EDP. This has been explicitly confirmed by Kat Walsh. So be
> > > clear
> > > > >> about it; only the argument "Fair use" allows something with a NC
> > or
> > > ND
> > > > >> license to be kept in our projects. This is not negotionable.
> > > > >>
> > > > >> I am not a fan of Fair use, I am not a fan of the overly
> > restrictive
> > > > >> ways that we are embarking on either. There is no way in which we
> > can
> > > > >> have a logo of a company without creating a legalistic mess where
> > the
> > > > >> license says that you can change it and the trademark says that you
> > > > >> cannot is horrible to me. The fact that we do not acknowledge
> > museums
> > > > >> for looking after our cultural heritage by referring to them in the
> > > > Meta
> > > > >> data, the fact that we do not do this because it is Public Domain,
> > is
> > > > >> another missed opportunity to do the right thing.
> > > > >>
> > > > >> The notion that with this doctrine we have established how we have
> > to
> > > > >> deal with digital material once and for all is a notion that I do
> > not
> > > > >> subscribe to.
> > > > >>
> > > > >> You want to remind me on how this thread started; in the Dutch
> > > > community
> > > > >> we are working on getting much more pictures of those famous in the
> > > > >> Netherlands by making it a project. This one picture of a former
> > > > >> basketball player is imho an isolated incident. When people have
> > the
> > > > >> time and the inclination, this is something that can be done
> > > elsewhere
> > > > >> as well. I want to remind you in turn that I responded to a remark
> > > made
> > > > >> in this thread. This is what you do in threads.
> > > > >>
> > > > >> When you wonder how much effort was put in getting Free material..
> > we
> > > > >> can use more people in the (Dutch) committee for free material ..
> > > > >>
> > > > >> Thanks,
> > > > >>     GerardM
> > > > >>
> > > > >>
> > > > >> teun spaans schreef:
> > > > >>
> > > > >>> Gerard,
> > > > >>>
> > > > >>> May I kindly remind you how this thread started.
> > > > >>>
> > > > >>> This thread started with a beautiful story of how the lack of a
> > > photo
> > > > >>> prompted a professional photographer to donate photos. Personally
> > I
> > > > >>>
> > > > >> think
> > > > >>
> > > > >>> this would never happened if there had been an image under the
> > fair
> > > > use
> > > > >>> provision. The lack of a picture makes people run, if there is a
> > > > picture
> > > > >>>
> > > > >> no
> > > > >>
> > > > >>> one gets out of his chair to say: He, there is a match tonight,
> > I'm
> > > > >>>
> > > > >> gonna
> > > > >>
> > > > >>> take some pix.
> > > > >>>
> > > > >>> I know many fair use advocates think the opposite. On this list I
> > > read
> > > > >>>
> > > > >> "the
> > > > >>
> > > > >>> availability of a fair use image won't stop
> > > > >>> someone from adding a free alternative" and "We should also recall
> > > > that
> > > > >>>
> > > > >> the
> > > > >>
> > > > >>> readers, would like to see an image until there "
> > > > >>>
> > > > >>> When we spoke with each other in the past you never supported the
> > > > usage
> > > > >>>
> > > > >> of
> > > > >>
> > > > >>> "fair use". Somehow your statements on this list, when I read
> > them,
> > > > even
> > > > >>> where they seem to say the opposite, seem to suggest that you have
> > > > >>>
> > > > >> changed
> > > > >>
> > > > >>> your point of view.
> > > > >>> For example, when Muhammed suggests "the availability of a fair
> > use
> > > > >>>
> > > > >> image
> > > > >>
> > > > >>> won't stop someone from adding a free alternative", I think: he's
> > > > right
> > > > >>>
> > > > >> it
> > > > >>
> > > > >>> is not forbidden to add a free picture. But no longer any one will
> > > > stand
> > > > >>>
> > > > >> up
> > > > >>
> > > > >>> and say: it is a shame that we dont have a photo, There is a mact
> > /
> > > > >>>
> > > > >> concert
> > > > >>
> > > > >>> / interview tonight, I am going there and snap some pix! So
> > > > effectually,
> > > > >>> having a fair use image does hurt the collecting of free content.
> > > Then
> > > > >>>
> > > > >> you
> > > > >>
> > > > >>> come and suggest that there is no need to cripple images for fair
> > > use
> > > > >>>
> > > > >> (an
> > > > >>
> > > > >>> doubtful statement, see below). Even when you add "If anything we
> > > > should
> > > > >>>
> > > > >> not
> > > > >>
> > > > >>> have "Fair use" material.", your previous statement seems to
> > support
> > > > >>> Muhammeds plead for fair use.
> > > > >>>
> > > > >>> You suggest that it is not necessary to crop high quality images
> > for
> > > > >>>
> > > > >> fair
> > > > >>
> > > > >>> use. The assumption that cropping images improves legal chances
> > for
> > > > fair
> > > > >>>
> > > > >> use
> > > > >>
> > > > >>> application is however very widespread. It also was one of the
> > > factors
> > > > >>>
> > > > >> in
> > > > >>
> > > > >>> Kelly v. Arriba-Soft, 03 C.D.O.S. 5888 (9th Cir. 2003).
> > > > >>>
> > > > >>> The defenders of fair use should realize that we talk about a
> > rather
> > > > >>>
> > > > >> vast
> > > > >>
> > > > >>> amount of images.
> > > > >>> Some numbers:
> > > > >>> Template:albumcovers:     >55.000
> > > > >>> Template:film-screenshot: >15.000
> > > > >>> Template:Tv-screenshot:  > 30.000
> > > > >>> Now these images will be hard to replace, but I really wonder how
> > > many
> > > > >>> attempts have been made to make them free.
> > > > >>> Others, such as those of famous people, and many of the 15.000pics
> > > in
> > > > >>> "template:fair use in" fall in this category, could potentially be
> > > > >>>
> > > > >> replaced
> > > > >>
> > > > >>> by free pictures is someone simply steps out of his chair and
> > starts
> > > > >>>
> > > > >> taking
> > > > >>
> > > > >>> pictures.
> > > > >>>
> > > > >>> Gerad, I think you did not understand what I wrote about NC and
> > ND.
> > > > The
> > > > >>> current draft as I read it, places little restrictions on
> > > exemptions.
> > > > >>>
> > > > >> This
> > > > >>
> > > > >>> may lead to all kinds of unintended exemptions.
> > > > >>>
> > > > >>> I know that in your heart, Gerard, you support the creation of
> > free
> > > > >>>
> > > > >> content.
> > > > >>
> > > > >>> I wish you health and happiness,
> > > > >>> teun spaans
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>> On 2/24/07, GerardM < gerard.meijssen at gmail.com > wrote:
> > > > >>>
> > > > >>>
> > > > >>>> Teun.
> > > > >>>> May I kindly remind you that we are discussing on this list how
> > to
> > > > deal
> > > > >>>> with
> > > > >>>> all types of issues. Personally I have never ever uploaded "Fair
> > > use"
> > > > >>>> material. It is however done on some of our projects. When
> > material
> > > > is
> > > > >>>> used
> > > > >>>> with a justification of being "Fair use", there is imho no reason
> > > to
> > > > >>>> cripple
> > > > >>>> such material. This was suggested in the previous post.
> > > > >>>>
> > > > >>>> You were wrong in how you reacted to what I wrote about NC and ND
> > > the
> > > > >>>> other
> > > > >>>> day, you again assume things that are not in line with what I
> > > wrote.
> > > > It
> > > > >>>>
> > > > >> is
> > > > >>
> > > > >>>> good to remember that "Fair use" is permitted to a project under
> > a
> > > > >>>> Exemption
> > > > >>>> Doctrine Policy if they so choose. It is therefore relevant to
> > > > discuss
> > > > >>>>
> > > > >> how
> > > > >>
> > > > >>>> this is to be implemented if at all. This is what I did.
> > > > >>>>
> > > > >>>> Thanks,
> > > > >>>>      GerardM
> > > > >>>>
> > > > >>>>
> > > > >>>> On 2/24/07, teun spaans <teun.spaans at gmail.com> wrote:
> > > > >>>>
> > > > >>>>
> > > > >>>>> Gerard,
> > > > >>>>>
> > > > >>>>> may I kindly remind you that our aim is to make and collect free
> > > > >>>>>
> > > > >>>>>
> > > > >>>> content?
> > > > >>>>
> > > > >>>>
> > > > >>>>> Fair use is not free.
> > > > >>>>>
> > > > >>>>> And your remark about crippling content looks false: i checked a
> > > few
> > > > >>>>>
> > > > >> of
> > > > >>
> > > > >>>>> the
> > > > >>>>> old versions, and these didnt have a photograph. Not even a fair
> > > use
> > > > >>>>>
> > > > >>>>>
> > > > >>>> one.
> > > > >>>>
> > > > >>>>
> > > > >>>>> regards,
> > > > >>>>> teun spaans
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> On 2/24/07, GerardM <gerard.meijssen at gmail.com > wrote:
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>> Hoi,
> > > > >>>>>> When you have a good quality picture that you want to use under
> > > > Fair
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>> use,
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>> you use it as a good quality picture. Why cripple our content
> > > when
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>> there
> > > > >>>>
> > > > >>>>
> > > > >>>>>> is
> > > > >>>>>> no need ? If anything we should not have "Fair use" material.
> > > > >>>>>> Thanks,
> > > > >>>>>>      GerardM
> > > > >>>>>>
> > > > >>>>>> On 2/24/07, Mohamed Magdy <mohamed.m.k at gmail.com> wrote:
> > > > >>>>>>
> > > > >>>>>>
> > > > >>>>>>> <snip>
> > > > >>>>>>> Well, good work!..but as others said, this isn't the proper
> > way
> > > to
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>> get
> > > > >>>>
> > > > >>>>
> > > > >>>>>>> rid of fair use images..the availability of a fair use image
> > > won't
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>> stop
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>>> someone from adding a free alternative, fair use images
> > > shouldn't
> > > > be
> > > > >>>>>>> added in a high resolution..right? so when someone sees the
> > > image
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>> with
> > > > >>>>
> > > > >>>>
> > > > >>>>>>> low quality and s/he has another free one, s/he will replace
> > it
> > > > with
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>> the
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>>> free image, provided that you place a message on free use
> > images
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>> saying
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>>> 'this image isn't free, if you can help.replace it...'...on
> > the
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>> other
> > > > >>>>
> > > > >>>>
> > > > >>>>>>> end, I think with the increasing popularity, people will just
> > > add
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>> their
> > > > >>>>>
> > > > >>>>>
> > > > >>>>>>> images(to say: hey, i took that image you see on [[Cat]]
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>> article!)...
> > > > >>>>
> > > >
> > > >
> > > > _______________________________________________
> > > > foundation-l mailing list
> > > > foundation-l at lists.wikimedia.org
> > > > http://lists.wikimedia.org/mailman/listinfo/foundation-l
> > > >
> > > _______________________________________________
> > > foundation-l mailing list
> > > foundation-l at lists.wikimedia.org
> > > http://lists.wikimedia.org/mailman/listinfo/foundation-l
> > >
> > _______________________________________________
> > foundation-l mailing list
> > foundation-l at lists.wikimedia.org
> > http://lists.wikimedia.org/mailman/listinfo/foundation-l
> >
> _______________________________________________
> foundation-l mailing list
> foundation-l at lists.wikimedia.org
> http://lists.wikimedia.org/mailman/listinfo/foundation-l
>

Which brings us a problem in other wikis.:

$Why can''t I upload such file?
#Well, because it's fair use and commons/local wiki does not allow it
$Why?
#Since such images aren't free and we're building a free encyclopedia.
$BUT THE ENGLISH WIKIPEDIA ALLOWS NONFREE IMAGES!!!!
#.......


subject: [Foundation-l] a new free image!


from_name: William Pietri

subject: [WikiEN-l] Zero information is preferred to misleading or false

body:
lawrence harms wrote:
> In the reference "Old Catholic Church"  there are listings of Old Catholic Churches in the United States.  There is a Old Catholic Church called "The American Catholic Church in the United States"  This Old Catholic Church is not listed with the rest of the listings.  If you wish, you may want to view there website ACCUS.US
>

For those wondering, the relevant background is at

http://en.wikipedia.org/wiki/Old_Catholic
http://en.wikipedia.org/wiki/American_Catholic_Church_in_the_United_States

The ACCUS is listed under the "See Also" section, but their website
indeed does not appear to be in the "External Links" section. I have
added a note to the [[Old Catholic]] talk page mentioning the request of
Rev. Harms.

William

--
William Pietri <william at scissor.com>
http://en.wikipedia.org/wiki/User:William_Pietri


subject: [Wikitech-l] mwdumper does not work

body:
On 26/02/07, Edward Z. Yang <edwardzyang at thewritingpot.com> wrote:
> MySQL 5.0.18 is only experimentally supported by MediaWiki, the
> production sites use MySQL 4.0.

MediaWiki works with MySQL 5.x without problems if you use the latin1
schema. I don't think this is the actual cause.

Jeff, are you saying that the page histories appear to be blank when
accessed? If so, this *could* be a caching problem if the page_touched
columns haven't been updated.

Could you run a quick statement such as UPDATE page SET page_touched =
20070226080700 and see if that cures the problem? Please also do a
hard-reload when viewing one of these pages.

If I've interpreted what the problem is wrongly, then please clarify.

Thanks,

Rob Church


from_name: christoph.huesler at css.ch

subject: [Wikitech-l] Antwort: Re:  WikiDump Parsing

body:
Jeffrey V. Merkey wrote:
>
> This c program will also run and complete about 50 times faster then
> that java and php code previously metioned.
>
> Jeff

Well... what a surprise </sarcasm>


from_name: A

subject: [WikiEN-l] Pacific Western University hostage crisis update

body:
As we move into month 7 of the WP:OFFICE action on the [[Pacific Western
University]] article, I'd like to raise this issue again.

My from-the-trenches suggestions:

1. Impartial admin(s) assigned to each OFFICEd article at the time it is
protected (preferably someone with no edits to the article prior to
WP:OFFICE and no strong POV about the topics it covers).
2. Perhaps they could be randomly chosen from an existing pool of volunteers
with good track records on controversial issues who could confirm no WP:COI
issues for the article in question, kind of like ArbCom.
3. That person would be listed on the talk page as the coordinator and would
check back in each day and respond to proposed changes.

I like to work on controversial topics, but the current setup makes any
attempts at resolution, especially by non-admins, an exercise in futility.
In this case, it's never been clearly explained what the problem is, though
most who have looked at it believe it has to do with distinguishing the
Hawaii corporation from entities in other states. It appears they may also
want something changed based on accreditation information that has yet to
appear in a reliable published source.

At any rate, half a year under lockdown seems to indicate a significant
problem that needs to be addressed. I believe this and the unilateral speedy
deletion of controversial articles by admins are the two most serious
procedural issues Wikipedia faces right now. Both waste a lot of time, cause
a lot of animosity and generally drive away well-intentioned editors trying
to help.

These edgy issues almost always end up shaping policy, so we should address
these problems sooner than later.

Jokestress


subject: [Wikitech-l] Blocking request: domains used for SEO

body:
Tim 'avatar' Bartel wrote:
> Hi,
>
> there is a infamous person in Germany named "Mario Dolzer" (try Google
> if you speak German) who is mostly known for spreading dialers.
>
> He is building a massive SEO network for his activities. And since
> several weeks he uses dynamically grabbed wikipedia content.
>
> He is not only ignoring "official" OTRS-Mails to him but announce to
> sell his "Wikipedia-SEO-Script".
>
> Most probably it will be best to sue him - that is not an easy job.
> Second best option seems to be to cut him off.
>
> The good thing: Most of his domains are located in a small adress space.
>
> 213.131.228.64/28
> 213.203.193.128/26
> 213.131.229.232/29
>

Is someone addressing this?

Matt Flaschen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
URL: <http://lists.wikimedia.org/pipermail/wikitech-l/attachments/20070226/c4fa7e32/attachment.pgp>


from_name: Sabo, Edmond

body:
Dear colleagues,
I am new to this forum. A few days ago I have proposed a new Wiki project and it is my understanding that
as a first step, I  have to announce it, to the forum.
The link to my suggested project is:
http://meta.wikimedia.org/wiki/User_talk:Esabo
I hope I did it the right way.
Your input will be very much appreciated.
Thank you.
Edmond


from_name: WikiDoc

subject: [Wikipedia-l] Check out the Wikipedia Documentary!!

body:
Doc fans!

The makers of "24 hours on craigslist" have a new project: "Truth in
Numbers: The Wikipedia Story", a documentary chronicling  the rise and
controversy behind the world's most popular encyclopedia.

While producer Michael Ferris Gibson ('24 hours on craigslist') and
Oscar-nominated filmmaker Sam Green ('The Weather Underground') helm the
production from San Francisco, you can check out the crew's continuing video
podcasts from the road and other information about the film here:
www.wikidocumentary.org

As Wikipedia is a global phenomenon-- recently becoming one of the top ten
websites in the world-- director Nic Hill ('Piece by Piece') is currently
traveling the planet with the crew of Underdog Productions, interviewing
Wikipedians and experts on free digital knowledge.  If you know any
wikiheads he should interview give him a hollar at
nic at underdogproductions.com

Best of all, the film's website is actually itself a wiki for the production
(currently hosted at Wikia and maintained by the good folks at Object
Adjective); feel free to contribute ideas, interviewee suggestions,
locations, even your own audio and video to the production!  In the spirit
of free information, this is a non-profit project; so take comfort in
knowing that your contributions will go the worthy cause of exploring one of
the most important phenomena of our time!

-WikiDoc


from_name: Steve Bennett

body:
> > Actually I think this is a good litmus test for whether an individual
> > is encyclopaedically notable.  If there are no sources for basic
> > biographical data other than the individual themselves, in other
> > words
> > if there has never been a reputably published biography or profile,
> > then I don't believe we can have an article.

I would see no problem with an article about a scientist which was
entirely about his professional contributions, and didn't so much as
mention a date of birth, middle name or anything vaguely personal. The
article should be primarily about their work, and that "biographical"
information is purely incidental.

I suspect that for very early scientists (eg, 1700s or earlier) we may
be in this situation anyway.

Steve


subject: [WikiEN-l] Parker Peters

body:
On 2/25/07, The Cunctator <cunctator at gmail.com> wrote:
> Speaking as an upper class gadfly, I have to say that Parker Peters
> wasn't that bad and shouldn't have been banned.
>
> People need to learn how to killfile users they don't like, instead of
> appealing to moderators.

He repeatedly turned reasonable threads into trollfests, and started
new ones. The quality of this list went noticeably down whenever he
was participating. Individual killfiles don't help that situation.

Steve (mod)


body:
A wrote:
> As we move into month 7 of the WP:OFFICE action on the [[Pacific Western
> University]] article, I'd like to raise this issue again.
>
> My from-the-trenches suggestions:
>
> 1. Impartial admin(s) assigned to each OFFICEd article at the time it is
> protected (preferably someone with no edits to the article prior to
> WP:OFFICE and no strong POV about the topics it covers).
> 2. Perhaps they could be randomly chosen from an existing pool of volunteers
> with good track records on controversial issues who could confirm no WP:COI
> issues for the article in question, kind of like ArbCom.
> 3. That person would be listed on the talk page as the coordinator and would
> check back in each day and respond to proposed changes.
>
> I like to work on controversial topics, but the current setup makes any
> attempts at resolution, especially by non-admins, an exercise in futility.
>

As one of the people who spent subjective ages trying to sort out the
Gregory Lauder Frost dustup, I'd second both the feeling and the
suggestions.

My working assumption was just that those in the OFFICE were very busy,
too busy to communicate status on the progress they were making. But it
was hard to tell the difference between that and being ignored because
they had bigger fish to fry. Spending a lot of time trying to understand
and pacify agitated partisans was painful but necessary. But I was
disheartened by the amount of time I had to spend tugging on the sleeves
of people who drew enough water to get the attention of the OFFICE.

Having some admin like that directly involved would certainly speed some
things up, and it would entirely prevent the will-sapping suspicion that
one's case has  fallen behind a file cabinet somewhere.

William

--
William Pietri <william at scissor.com>
http://en.wikipedia.org/wiki/User:William_Pietri


from_name: Matthew Brown

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
On 2/26/07, Jeff Raymond <jeff.raymond at internationalhouseofbacon.com> wrote:
> But I remain pessimistic.  Even now, after three weeks of consistent
> abuses from many administrative forces, the only time Jimbo feels the need
> to step in is due to a wheel war.

Have you considered that Jimbo may not want to have to do this - that
he does not wish to micro-manage?

I'm not sure what you mean by 'three weeks of consistent abuses',
either.  I've been reading this mailing list and have not got that
sense of things.

-Matt


from_name: Simon Whydah

subject:
[WikiEN-l] FW: Important notice -- please confirm your unblock-en-l
	subscription

body:
I am studying your problematic system.

Why are you eager to hide all the contents of Unblock-en-l suddenly?

Why "within one week"?

>From: Luna <lunasantin at gmail.com>
>Subject: Important notice -- please confirm your unblock-en-l subscription
>Date: Sun, 25 Feb 2007 23:52:37 -0800
--------
Dear unblock-en-l subscriber,

We've recently decided to establish some membership criteria for this
mailing list, and are in the process of removing subscriptions which do not
meet those criteria. In particular, we need to associate your email address
with a particular Wikipedia account or identity. In order to do that,
please click on this link:
http://en.wikipedia.org/wiki/Special:Emailuser/Prodego

PLEASE use "unblock-en-l identification" as your subject heading, to allow
faster processing of your email.

Do not email the user directly -- you MUST use the Special:Emailuser
feature, or your identity will not be confirmed.

If you have not replied to this message within one week, your subscription
will be cancelled. You can request to re-join the list at any time. We
apologize for this inconvenience, but hope that you understand the need for
privacy and security, given the sensitive personal information that is
sometimes discussed on this mailing list.

Thank you,
-Luna
--------
I don't believe it.
Luna, Prodego, Mindspillage( Kat Walsh ) and/or essjay are abusing
sockpuppets ?

ALL ADMINs MUST make public and clear their identities in the first place.

--Simon Whydah

_________________________________________________________________
???????????????????? 24????????
http://livesushi.jp/


subject:
[Wikipedia-l] FW: Important notice -- please confirm your
	unblock-en-l subscription


from_name: John Lee

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
On 2/25/07, Philip Sandifer <sandifer at english.ufl.edu> wrote:
>
> I just had dinner with [[Scott McCloud]], and, unsurprisingly, the
> conversation turned to webcomics, and, eventually, to Wikipedia's
> treatment of them. (This was partially spurred by the Kristopher
> Straub debacle, about which I will say only that it demonstrates the
> degree to which the bias is overwhelmingly towards deletion across
> many areas of Wikipedia right now)
>
> McCloud is somebody who knows comics. He quite literally wrote the
> book on them. In the course of the conversation it became clear that
> he was pretty well completely fed up with Wikipedia. And it should be
> noted, this comes from someone who has been on the forefront of
> digital technology debates several times. He makes clear his
> admiration for the concept of Wikipedia. He makes clear his
> admiration for how Wikipedia got started. His problem is with how it
> works now.
>
> The problem he has? Notability. Specifically the arbitrary and
> capricious way in which AfD targets things, questions their
> notability, and uses guidelines that make no sense from the outside.
>
> See also Timothy Noah's recent article on Slate for this - it gives a
> good view of how notability guidelines look to the outside. In this
> case, it's how they look to the subject of the article, but I assure
> you - they look similar to people who are familiar with the subject.
> In short, they appear a Kafka-esque absurdity.
>
> This is a new problem - these are major figures who are sympathetic
> to Wikipedia but fed up with its operation. And I can tell you, the
> tone among people I talk to in that real life thing I maintain is
> pretty similar - great respect for Wikipedia as a concept, reasonable
> respect for Wikipedia as a resource, no respect for Wikipedia as
> something anyone would ever want to edit. The actual editorial
> process of Wikipedia is rightly viewed as a nightmare. Hell, I view
> it as a nightmare at this point - I've given up editing it because
> the rules seem to have been written, at this point, with the
> intention of writing a very bad encyclopedia.
>
> Our efforts to ensure reliability have come at the cost of a great
> deal of respect - and respect from people we should have respect
> from. We are losing smart, well-educated people who are sympathetic
> to Wikipedia's basic principles. That is a disaster.
>
> And it's a disaster that can be laid squarely at the feet of the
> grotesque axis of [[WP:RS]] and [[WP:N]] - two pages that are eating
> Wikipedia alive from the inside out. (And I don't mean this in terms
> of community. I mean that they are systematically being used to turn
> good articles into crap, and have yet to demonstrate their actual use
> in turning bad articles into good ones.)
>
> Best,
> Phil Sandifer
> sandifer at english.ufl.edu

Okay, instead of bickering over whether there is a problem with the status
quo, let's assume there is a problem. What should we do to solve this
problem? I haven't seen many ideas about what ought to be done to resolve
the ostensible issues.

I'm not saying there isn't a problem, nor am I saying it's impossible to
solve it. However, I think it's important to recognise that you can't expect
perfection from an innately imperfect project. When you have something on
the scale of Wikipedia, involving so many mortals, the errors multiply by
each other pretty quickly, and add up to some massive problems. We need to
solve them, and the status quo is what we came up with. It's clunky, it
sucks, but it's better than nothing.

The problem, as I see it, is that there's just far too little common sense.
Defining common sense is of course an ordeal I am not about to delve into,
but the point of our policies and guidelines is to enforce a semblance of
common sense on people lacking it. Why do we have a guideline for reliable
sources even though it's impossible to establish in black and white what
constitutes a reliable source? Because a lot of editors don't have the sense
necessary to discern what is a reliable source and what is not. Why do we
have notability guidelines? Because otherwise deletionists and inclusionists
without common sense would simply do whatever they like on AfD, and never be
able to reach agreement by arguing from the same premises.

In short, policy is a substitute for common sense. Phil seems to suggest
that we ought to block people who exhibit a deficit of common sense. The
problem is that an editor who is insane in one area may turn out to be a
very reasonable and sensible chap in other fields. Since selective blocking
is impossible, it's an all-or-nothing proposition.

Another problem you run into is the obvious controversy that would result if
admins had discretion to block people without common sense. The problem is
that one or two admins themselves would lack the sense to identify who has
common sense, and thus block the wrong people. We'd have a huge debate about
whether this discretion is warranted, and thus further distract us from the
point of WP - to write an encyclopaedia.

The clunky status quo sucks, but it tries to strike a balance to minimise
timewasting controversy. It's erratic, it's inconsistent, and it's far from
ideal - but the idea is to have something that works. Just like WP, I
suppose.

Now, if we want to move beyond the status quo, how are we to resolve the
problem of people lacking the sense to know their limits? If people had some
common sense about their limits on things like webcomics or postage stamps
or content management systems, we wouldn't need policy - we probably
wouldn't even need AFD.

Phil's solution is to liberally apply the banstick. I don't know if this is
the right way to go about things, but I would like to see a way to make the
banstick selective. Other ideas, like article and editor ratings, would also
be very good. In the end, this may come down to the software rather than
writing/destroying policy.

Johnleemk


from_name: Marc Riddell

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
on 2/25/07 10:29 PM, John Lee at johnleemk at gmail.com wrote:

> Okay, instead of bickering over whether there is a problem with the status
> quo, let's assume there is a problem. What should we do to solve this
> problem? I haven't seen many ideas about what ought to be done to resolve
> the ostensible issues.
>
> I'm not saying there isn't a problem, nor am I saying it's impossible to
> solve it. However, I think it's important to recognise that you can't expect
> perfection from an innately imperfect project. When you have something on
> the scale of Wikipedia, involving so many mortals, the errors multiply by
> each other pretty quickly, and add up to some massive problems. We need to
> solve them, and the status quo is what we came up with. It's clunky, it
> sucks, but it's better than nothing.
>
> The problem, as I see it, is that there's just far too little common sense.
> Defining common sense is of course an ordeal I am not about to delve into,
> but the point of our policies and guidelines is to enforce a semblance of
> common sense on people lacking it. ??????
>
> Johnleemk

Common sense or common purpose? What common sense needs to be applied to
accomplish this common purpose?

I see a great deal of the problem being many persons with many different
agendas and purposes for being in WP itself. If a degree of common sense is
needed to accomplish the common goal of ?A? then all persons must be trying
to accomplish ?A?. If others are there to accomplish ?B?, their ?common
sense? will be applied and measured differently.

Solutions? That is going to take some creative, collaborative thinking with
all participants working toward the same common goal. But first, there must
be an agreement about what the problem - and its cause - really is.

There seems to be a great deal of resistance to the idea that many of the
problems within WP involve the very culture itself. This speaks to me of a
great deal of denial on the part of the Community Members.

Denial is saying ?anything but that?. To admit that the ?that? is the
problem, might mean having to confront, and possibly get rid of, the ?that?.
If a chemical dependent admits that the chemical is the ?that? that is
killing them, they might have to give up that ?that?.  ?Anything but that!?

Marc Riddell


from_name: habj

subject:
[Wikipedia-l] Translating the Five pillars (Was: Important Issue to
	Hebrew Wikipedia and AdminAbuse)

body:
2007/2/2, Berto 'd Sera <albertoserra at ukr.net>:

> BTW, how many editions did even bother translating those damn pillars??
> How
> many non-english wikipedians EVEN JUST KNOW that they exist?

Should all Wikipedias translate the pillars? Why? Would it necessarily work,
if they did?

Most of the projects probably have lots to learn from enwiki, since it is
the oldest project and with all its flaws still somehow works despite its
size. Most projects have at one stage or another imported policy pages and
similar from enwiki, or from another wiki that took it from enwiki. Today
however, whatever rules that should be imposed on all projects should come
from the WMF, not English Wikipedia.

The five pillars [1] is, to my knowledge, a compilation of basic policy
created on English Wikipedia. There are other enwiki policy compilations as
well, but it seems the pillars is the one most commonly referred to. I once
a board member ,what policy a Wikipedia has to follow, and got the answer
that probably these are only three: that the content should be free (GFDL),
encyclopaedic and neutral. You can compare the pillars with for instance the
foundation issues page at meta [2] which, interestingly, mentions the "wiki
process" - a badly defined concept that may or may not be identical to the
basic consensus based process of a wiki [3] and that is not mentioned in the
Pillars.

The project that I have been most active at has a compilation of "basic
principles" [4] very similar to the pillars with one exception. This wiki
never imported or reinvented "Ignore all rules", which is the fifth of the
enwiki pillars. I don't think there is anything that tries to make them, or
tells them they should, import that concept from English Wikipedia. I
personally believe they might gain from doing so, but that is another issue
- and a process of much larger scope, and much more painful, than simply
translating a page. Personally I believe the concensus process a.k.a. wiki
process is equally important as Ignore all rules, and deserves a central
place in whatever policy compilation you have. Others might disagree, of
course.

/habj

[1] http://en.wikipedia.org/wiki/Wikipedia:Five_pillars
[2] http://meta.wikimedia.org/wiki/Foundation_issues
[3] http://en.wikipedia.org/wiki/Wikipedia:Consensus
[4] http://sv.wikipedia.org/wiki/Wikipedia:Grundprinciperna


from_name: MacGyverMagic/Mgm

body:
What is the relevance of the email subject and why are you talking about
yourself in the third person?

Mgm

On 2/24/07, lawrence harms <harms621 at adelphia.net> wrote:
>
> Dear Mr. Wales,
>
> In the reference "Old Catholic Church"  there are listings of Old Catholic
> Churches in the United States.  There is a Old Catholic Church called "The
> American Catholic Church in the United States"  This Old Catholic Church is
> not listed with the rest of the listings.  If you wish, you may want to view
> there website ACCUS.US
>
> The ACCUS website will direct you to individuals in places of authority
> within ACCUS.
>
> The Presiding Archbishop of ACCUS is Most Reverend Lawrence J. Harms, D.
> D.  His e-mail address is presidingarchbishop at accus.us.
>
> Thank you for your consideration in reading this e-mail.
>
> The Clergy of ACCUS
> _______________________________________________
> WikiEN-l mailing list
> WikiEN-l at lists.wikimedia.org
> To unsubscribe from this mailing list, visit:
> http://lists.wikimedia.org/mailman/listinfo/wikien-l
>


from_name: Jeff Raymond

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
Marc Riddell wrote:

> I see a great deal of the problem being many persons with many different
> agendas and purposes for being in WP itself. If a degree of common sense
> is
> needed to accomplish the common goal of ?A? then all persons must be
> trying
> to accomplish ?A?. If others are there to accomplish ?B?, their ?common
> sense? will be applied and measured differently.
>
> Solutions? That is going to take some creative, collaborative thinking
> with
> all participants working toward the same common goal. But first, there
> must
> be an agreement about what the problem - and its cause - really is.

Well, I think the first step is to stop thinking that common sense is
universal.  Look at what happened over the weekend - common sense
apparently told people that we did and didn't need an article on Daniel
Brandt, and did and didn't need to discuss it.  Some people feel common
sense is to simply do what you think is best (WP:IAR, which should be
destroyed with heat seeking nuclear missiles after the way February has
gone on this project), some people feel common sense is giving people the
due process they crave.

There's obviously no such thing as "common sense" here, so we need to get
out of that frame of mind and come to a conclusion as to what's best - not
what's favored by any specific group of people, not what the people who
show up on a given afternoon believe, but what makes the most logical
sense for the project to continue to succeed as opposed to looking like
morons to outsiders.

>
> There seems to be a great deal of resistance to the idea that many of the
> problems within WP involve the very culture itself. This speaks to me of a
> great deal of denial on the part of the Community Members.

Damn skippy.  You nailed it with this paragraph.

>
> Denial is saying ?anything but that?. To admit that the ?that? is the
> problem, might mean having to confront, and possibly get rid of, the
> ?that?.
> If a chemical dependent admits that the chemical is the ?that? that is
> killing them, they might have to give up that ?that?.  ?Anything but
> that!?

I mean, an easy short term fix has two steps:

1) Stop giving administrators carte blanche to do as they please when they
please based on their version of common sense.

2) Remove the admin bit from the worst offenders, in which there are more
than enough to cause major problems and further destroy a culture that's
been rotting for a long time.

This solves - in the short term - 90% of our problems, and gives us the
opportunity to fix the problems, heal the wounds, put up the necessary
boundaries, and start as fresh as possible.  We're in a good *position* -
Citizendium, the most capable fork to challenge Wikipedia long-term, is
not ready for prime time, or even cable access - but we're very close to
teetering off the edge.  We can unbecome a top 15 website quicker than we
became one, and that can be headed off at the pass by amputating the
diseased aspects - users, administrators, policies, guidelines, and even
articles.

But I remain pessimistic.  Even now, after three weeks of consistent
abuses from many administrative forces, the only time Jimbo feels the need
to step in is due to a wheel war.  It tells me that the perspective on the
top end is lacking regarding the problems this project is facing on the
interior, which, while a legitimate perogative, is unfortunate for those
of us who are/were doing the legwork to keep the articles coming and the
cash flowing.  And the sickness will still remain.

-Jeff


from_name: geni

subject:
[Foundation-l] Clearing up Wikimedia's media licensing policies
	(some important points)

body:
On 2/26/07, teun spaans <teun.spaans at gmail.com> wrote:
> Gregory,
>
> You write: "Under the "fair dealing" (or in the US "fair use") laws of most
> countries we
> can use works even with the explicit disapproval of the copyright holder"
>
> And "the lawmakers or courts of most countries have realized "
>
> I don't believe your conclusion is correct. Fair use exists in the US,
> Canada and probably a bunch of (ex) UK countries. Other countries indeed
> have something related, but usually the rules are much, much stricter than
> what US courts allow.
>

Fair dealing is far stricter than US law. Do not lumb to two together
(fair dealing probably covers around 25% of the planet mind).

--
geni


from_name: Ray Saintonge

subject: [WikiEN-l] Scott McCloud on Wikipedia

body:
Matthew Brown wrote:

>On 2/26/07, Jeff Raymond <jeff.raymond at internationalhouseofbacon.com> wrote:
>
>
>>But I remain pessimistic.  Even now, after three weeks of consistent
>>abuses from many administrative forces, the only time Jimbo feels the need
>>to step in is due to a wheel war.
>>
>>
>Have you considered that Jimbo may not want to have to do this - that
>he does not wish to micro-manage?
>
I concur with this view.  Most of the time when Jimbo involves himself
in these disputes it tends to create more confusion.  We need to learn
to figure it out among ourselves.  The best use of Jimbo's time is not
in mucking about with these disputes, but in broader service to WMF such
as promotion and public speaking.  For him to be able to solve disputes
would also require him to spend more time monitoring these things, and
for a traveller that is not always possible.  As you know many of these
disputes flare up quite suddenly without any forewarning; that alone
makes them better handled by people with a more regular presence.

Ec


from_name: Platonides

subject: [Wikitech-l] Bot edit rates

body:
Titoxd at Wikimedia wrote:
> Ok, no clue why the other email came up empty, so trying again...
It didn't.


from_name: Jeff V. Merkey

subject: [Wikitech-l] rebuildImage.php MIME detection error 1.9.3

body:
Log excerpt attached. rebuildImage.php is detecting all png files as
"text/plain" and updating the wiki database
with this information. This causes the viewer to fail with "possible
malicious code" errors when the system tries
to render the png images.

Command was:

php maintenance/rebuildImages.php --missing >& /wikidump/image.log

Jeff

chrpdb 2007-02-26 22:42:26: crawling /wikidump/chrp/images/0/00
chrpdb 2007-02-26 22:42:26: Empty filename for
/wikidump/chrp/images/0/00/Lyng?r_1984.jpeg
chrpdb 2007-02-26 22:42:26: Empty filename for
/wikidump/chrp/images/0/00/Guetteur_au_poste_de_l'?cluse_26.jpg
chrpdb 2007-02-26 22:42:26: Empty filename for
/wikidump/chrp/images/0/00/Trollh?ttefallen.jpg
chrpdb 2007-02-26 22:42:27: Empty filename for
/wikidump/chrp/images/0/00/Andr?_Marie_Amp?re.jpg
chrpdb 2007-02-26 22:42:27: Empty filename for
/wikidump/chrp/images/0/00/S?o_Francisco_Ensenada.jpg
chrpdb 2007-02-26 22:42:29: crawling /wikidump/chrp/images/0/01
chrpdb 2007-02-26 22:42:29: Empty filename for
/wikidump/chrp/images/0/01/Karl_Von_Linn?.jpg
chrpdb 2007-02-26 22:42:29: Empty filename for
/wikidump/chrp/images/0/01/CemalG?rsel.jpg
chrpdb 2007-02-26 22:42:30: Empty filename for
/wikidump/chrp/images/0/01/Tu?n_Pham.jpeg
chrpdb 2007-02-26 22:42:32: crawling /wikidump/chrp/images/0/02
chrpdb 2007-02-26 22:42:32: Empty filename for
/wikidump/chrp/images/0/02/Fran?ais.JPG
chrpdb 2007-02-26 22:42:33: Empty filename for
/wikidump/chrp/images/0/02/La_Soufri?re-arieal.jpg
chrpdb 2007-02-26 22:42:33: Empty filename for
/wikidump/chrp/images/0/02/Megas_(H?ttuleg_Hlj?msveit_&_Gl?pakvendi?_Stella).jpg
chrpdb 2007-02-26 22:42:33: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:33: Empty filename for
/wikidump/chrp/images/0/02/Map_g?taland.png
chrpdb 2007-02-26 22:42:34: Empty filename for
/wikidump/chrp/images/0/02/Bento_gon?alves_pt.gif
chrpdb 2007-02-26 22:42:37: crawling /wikidump/chrp/images/0/03
chrpdb 2007-02-26 22:42:37: Empty filename for
/wikidump/chrp/images/0/03/Die_gro?e_Kirche_in_Suwalki.jpg
chrpdb 2007-02-26 22:42:38: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:38: Empty filename for
/wikidump/chrp/images/0/03/Carte_France_D?partement_18.png
chrpdb 2007-02-26 22:42:38: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:38: Empty filename for
/wikidump/chrp/images/0/03/Svpmap_v?sterg?tland.png
chrpdb 2007-02-26 22:42:38: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:38: Empty filename for
/wikidump/chrp/images/0/03/Finnish_map_with_Kittil?_highlighted.png
chrpdb 2007-02-26 22:42:38: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:38: Empty filename for
/wikidump/chrp/images/0/03/G?ttingen_in_Germany.png
chrpdb 2007-02-26 22:42:44: crawling /wikidump/chrp/images/0/04
chrpdb 2007-02-26 22:42:44: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:44: Empty filename for
/wikidump/chrp/images/0/04/J?nk?ping_county.png
chrpdb 2007-02-26 22:42:45: Empty filename for
/wikidump/chrp/images/0/04/Package_Diagram_for_168-Pin_PGA_Embedded_IntelDX2?_Processor.JPG
chrpdb 2007-02-26 22:42:45: Empty filename for
/wikidump/chrp/images/0/04/R?os_Montt.JPG
chrpdb 2007-02-26 22:42:45: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:45: Empty filename for
/wikidump/chrp/images/0/04/Carte_France_D?partement_42.png
chrpdb 2007-02-26 22:42:45: Empty filename for
/wikidump/chrp/images/0/04/Autoportrait_?_la_palette.jpg
chrpdb 2007-02-26 22:42:45: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:45: Empty filename for
/wikidump/chrp/images/0/04/?le-de-France_flag.png
chrpdb 2007-02-26 22:42:54: crawling /wikidump/chrp/images/0/05
chrpdb 2007-02-26 22:42:54: Empty filename for
/wikidump/chrp/images/0/05/C_J?rgens.JPG
chrpdb 2007-02-26 22:42:54: Empty filename for
/wikidump/chrp/images/0/05/Nord-Tr?ndelag_coa.gif
chrpdb 2007-02-26 22:42:54: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:54: Empty filename for
/wikidump/chrp/images/0/05/Bjark?y_coa.png
chrpdb 2007-02-26 22:42:55: Empty filename for
/wikidump/chrp/images/0/05/L?_Eithne_(P31).jpg
chrpdb 2007-02-26 22:42:55: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:55: Empty filename for
/wikidump/chrp/images/0/05/Caff?_Nero_(logo).PNG
chrpdb 2007-02-26 22:42:55: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:55: Empty filename for
/wikidump/chrp/images/0/05/AlbaniaTiran?County.png
chrpdb 2007-02-26 22:42:55: Surprising mime type: text/plain
chrpdb 2007-02-26 22:42:55: Empty filename for
/wikidump/chrp/images/0/05/?land.png
chrpdb 2007-02-26 22:42:56: Empty filename for
/wikidump/chrp/images/0/05/Krag-J?rgensen-Speed_Loader_1.jpg
chrpdb 2007-02-26 22:43:01: crawling /wikidump/chrp/images/0/06
chrpdb 2007-02-26 22:43:01: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:01: Empty filename for
/wikidump/chrp/images/0/06/Pok?mon_Emerald_Trainers.png
chrpdb 2007-02-26 22:43:02: Empty filename for
/wikidump/chrp/images/0/06/Hilmi?zk?k.jpg
chrpdb 2007-02-26 22:43:02: Empty filename for
/wikidump/chrp/images/0/06/Mar?a_Elena_Moyano.jpg
chrpdb 2007-02-26 22:43:02: Empty filename for
/wikidump/chrp/images/0/06/Arnaldo_tamayo_m?ndez.jpeg
chrpdb 2007-02-26 22:43:02: Empty filename for
/wikidump/chrp/images/0/06/G?nter_Verheugen.jpg
chrpdb 2007-02-26 22:43:03: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:03: Empty filename for
/wikidump/chrp/images/0/06/AntiquePok?ball.png
chrpdb 2007-02-26 22:43:09: crawling /wikidump/chrp/images/0/07
chrpdb 2007-02-26 22:43:09: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:09: Empty filename for
/wikidump/chrp/images/0/07/Carte_France_D?partement_26.png
chrpdb 2007-02-26 22:43:10: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:10: Empty filename for
/wikidump/chrp/images/0/07/Carte_Localisation_R?gion_France_Midi-Pyr?n?e.png
chrpdb 2007-02-26 22:43:11: Empty filename for
/wikidump/chrp/images/0/07/OrchestreM?tropolitain.jpg
chrpdb 2007-02-26 22:43:11: Empty filename for
/wikidump/chrp/images/0/07/Filzstift.Sion_Switzerland_Notre_Dame_de_Val?re_2002.jpg
chrpdb 2007-02-26 22:43:11: Empty filename for
/wikidump/chrp/images/0/07/WilhelmR?ntgen.JPG
chrpdb 2007-02-26 22:43:11: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:11: Empty filename for
/wikidump/chrp/images/0/07/Br?nn?y_coa.png
chrpdb 2007-02-26 22:43:18: crawling /wikidump/chrp/images/0/08
chrpdb 2007-02-26 22:43:19: Empty filename for
/wikidump/chrp/images/0/08/Portrait_of_Mikl?s_Zrinyi.jpg
chrpdb 2007-02-26 22:43:20: Empty filename for
/wikidump/chrp/images/0/08/?ire.jpg
chrpdb 2007-02-26 22:43:25: crawling /wikidump/chrp/images/0/09
chrpdb 2007-02-26 22:43:26: Empty filename for
/wikidump/chrp/images/0/09/??nekoski_bus_disaster_2004.jpg
chrpdb 2007-02-26 22:43:26: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:26: Empty filename for
/wikidump/chrp/images/0/09/Celes_Ch?re_menu.png
chrpdb 2007-02-26 22:43:26: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:26: Empty filename for
/wikidump/chrp/images/0/09/Carte_France_D?partement_41.png
chrpdb 2007-02-26 22:43:27: Empty filename for
/wikidump/chrp/images/0/09/L?_Bu_and_Diao_Chan_TV_Serial.jpg
chrpdb 2007-02-26 22:43:27: Empty filename for
/wikidump/chrp/images/0/09/Nornorna_spinner_?dets_tr?dar_vid_Yggdrasil.jpg
chrpdb 2007-02-26 22:43:27: Empty filename for
/wikidump/chrp/images/0/09/Drave_at_V?zv?r,_Hungary.JPG
chrpdb 2007-02-26 22:43:33: crawling /wikidump/chrp/images/0/0a
chrpdb 2007-02-26 22:43:33: Empty filename for
/wikidump/chrp/images/0/0a/La_Martini?re_01.jpg
chrpdb 2007-02-26 22:43:33: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:33: Empty filename for
/wikidump/chrp/images/0/0a/C?te_d'Ivoire_map.png
chrpdb 2007-02-26 22:43:33: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:33: Empty filename for
/wikidump/chrp/images/0/0a/Polli_pula_e_Lleshit_n?_ka?ile_t'leshit.ogg
chrpdb 2007-02-26 22:43:33: Empty filename for
/wikidump/chrp/images/0/0a/Edd?.jpg
chrpdb 2007-02-26 22:43:34: Empty filename for
/wikidump/chrp/images/0/0a/Battle_of_Br?valla.JPG
chrpdb 2007-02-26 22:43:34: Surprising mime type: text/plain
chrpdb 2007-02-26 22:43:34: Empty filename for
/wikidump/chrp/images/0/0a/Provincia_Aut?noma_Hebrea.png


subject: [Wikitech-l] MediaWiki 1.9.3 bugs

body:
It's in svn too. $path was introduced on 15623, by greg.
http://svn.wikimedia.org/viewvc/mediawiki/trunk/phase3/includes/templates/NoLocalSettings.php?r1=15609&r2=15623

What is your $_SERVER['SCRIPT_NAME'] ?

See if this change on /includes/templates/NoLocalSettings.php (line 12)
fixes it.
-$path = preg_replace('/index.php/', '', $_SERVER['SCRIPT_NAME']);
+$path = preg_replace('/index.php/', '/', $_SERVER['SCRIPT_NAME']);


from_name: Gerard Meijssen

subject: [Foundation-l] a new free image!

body:
Hoi,
You read the draft incorrectly; NC and ND are on its own not permitted
in an EDP. This has been explicitly confirmed by Kat Walsh. So be clear
about it; only the argument "Fair use" allows something with a NC or ND
license to be kept in our projects. This is not negotionable.

I am not a fan of Fair use, I am not a fan of the overly restrictive
ways that we are embarking on either. There is no way in which we can
have a logo of a company without creating a legalistic mess where the
license says that you can change it and the trademark says that you
cannot is horrible to me. The fact that we do not acknowledge museums
for looking after our cultural heritage by referring to them in the Meta
data, the fact that we do not do this because it is Public Domain, is
another missed opportunity to do the right thing.

The notion that with this doctrine we have established how we have to
deal with digital material once and for all is a notion that I do not
subscribe to.

You want to remind me on how this thread started; in the Dutch community
we are working on getting much more pictures of those famous in the
Netherlands by making it a project. This one picture of a former
basketball player is imho an isolated incident. When people have the
time and the inclination, this is something that can be done elsewhere
as well. I want to remind you in turn that I responded to a remark made
in this thread. This is what you do in threads.

When you wonder how much effort was put in getting Free material.. we
can use more people in the (Dutch) committee for free material ..

Thanks,
    GerardM

teun spaans schreef:
> Gerard,
>
> May I kindly remind you how this thread started.
>
> This thread started with a beautiful story of how the lack of a photo
> prompted a professional photographer to donate photos. Personally I think
> this would never happened if there had been an image under the fair use
> provision. The lack of a picture makes people run, if there is a picture no
> one gets out of his chair to say: He, there is a match tonight, I'm gonna
> take some pix.
>
> I know many fair use advocates think the opposite. On this list I read "the
> availability of a fair use image won't stop
> someone from adding a free alternative" and "We should also recall that the
> readers, would like to see an image until there "
>
> When we spoke with each other in the past you never supported the usage of
> "fair use". Somehow your statements on this list, when I read them, even
> where they seem to say the opposite, seem to suggest that you have changed
> your point of view.
> For example, when Muhammed suggests "the availability of a fair use image
> won't stop someone from adding a free alternative", I think: he's right it
> is not forbidden to add a free picture. But no longer any one will stand up
> and say: it is a shame that we dont have a photo, There is a mact / concert
> / interview tonight, I am going there and snap some pix! So effectually,
> having a fair use image does hurt the collecting of free content. Then you
> come and suggest that there is no need to cripple images for fair use (an
> doubtful statement, see below). Even when you add "If anything we should not
> have "Fair use" material.", your previous statement seems to support
> Muhammeds plead for fair use.
>
> You suggest that it is not necessary to crop high quality images for fair
> use. The assumption that cropping images improves legal chances for fair use
> application is however very widespread. It also was one of the factors in
> Kelly v. Arriba-Soft, 03 C.D.O.S. 5888 (9th Cir. 2003).
>
> The defenders of fair use should realize that we talk about a rather vast
> amount of images.
> Some numbers:
> Template:albumcovers:     >55.000
> Template:film-screenshot: >15.000
> Template:Tv-screenshot:  > 30.000
> Now these images will be hard to replace, but I really wonder how many
> attempts have been made to make them free.
> Others, such as those of famous people, and many of the 15.000 pics in
> "template:fair use in" fall in this category, could potentially be replaced
> by free pictures is someone simply steps out of his chair and starts taking
> pictures.
>
> Gerad, I think you did not understand what I wrote about NC and ND. The
> current draft as I read it, places little restrictions on exemptions. This
> may lead to all kinds of unintended exemptions.
>
> I know that in your heart, Gerard, you support the creation of free content.
>
>
> I wish you health and happiness,
> teun spaans
>
>
>
> On 2/24/07, GerardM < gerard.meijssen at gmail.com > wrote:
>
>> Teun.
>> May I kindly remind you that we are discussing on this list how to deal
>> with
>> all types of issues. Personally I have never ever uploaded "Fair use"
>> material. It is however done on some of our projects. When material is
>> used
>> with a justification of being "Fair use", there is imho no reason to
>> cripple
>> such material. This was suggested in the previous post.
>>
>> You were wrong in how you reacted to what I wrote about NC and ND the
>> other
>> day, you again assume things that are not in line with what I wrote. It is
>>
>> good to remember that "Fair use" is permitted to a project under a
>> Exemption
>> Doctrine Policy if they so choose. It is therefore relevant to discuss how
>> this is to be implemented if at all. This is what I did.
>>
>> Thanks,
>>      GerardM
>>
>>
>> On 2/24/07, teun spaans <teun.spaans at gmail.com> wrote:
>>
>>> Gerard,
>>>
>>> may I kindly remind you that our aim is to make and collect free
>>>
>> content?
>>
>>> Fair use is not free.
>>>
>>> And your remark about crippling content looks false: i checked a few of
>>> the
>>> old versions, and these didnt have a photograph. Not even a fair use
>>>
>> one.
>>
>>> regards,
>>> teun spaans
>>>
>>>
>>>
>>> On 2/24/07, GerardM <gerard.meijssen at gmail.com > wrote:
>>>
>>>> Hoi,
>>>> When you have a good quality picture that you want to use under Fair
>>>>
>>> use,
>>>
>>>> you use it as a good quality picture. Why cripple our content when
>>>>
>> there
>>
>>>> is
>>>> no need ? If anything we should not have "Fair use" material.
>>>> Thanks,
>>>>      GerardM
>>>>
>>>> On 2/24/07, Mohamed Magdy <mohamed.m.k at gmail.com> wrote:
>>>>
>>>>> <snip>
>>>>> Well, good work!..but as others said, this isn't the proper way to
>>>>>
>> get
>>
>>>>> rid of fair use images..the availability of a fair use image won't
>>>>>
>>> stop
>>>
>>>>> someone from adding a free alternative, fair use images shouldn't be
>>>>> added in a high resolution..right? so when someone sees the image
>>>>>
>> with
>>
>>>>> low quality and s/he has another free one, s/he will replace it with
>>>>>
>>> the
>>>
>>>>> free image, provided that you place a message on free use images
>>>>>
>>> saying
>>>
>>>>> 'this image isn't free, if you can help.replace it...'...on the
>>>>>
>> other
>>
>>>>> end, I think with the increasing popularity, people will just add
>>>>>
>>> their
>>>
>>>>> images(to say: hey, i took that image you see on [[Cat]]
>>>>>
>> article!)...


subject: [Foundation-l] a new free image!