What is the status of scholarships of 2008 Wikimania? Egypt is a touristic
hotspot so people will not be neither able to find hotel rooms nor plane
tickets if this is delayed any more.
Wikimania does not want to be a filthy rich-only club. :P
- White Cat
Hello,
Stewards can now create and edit global groups[1]. Users assigned to
these groups will have the groups' rights on all public Wikimedia
wikis. For example, a user in the 'global rollback' group could use
the 'rollback' feature on all Wikimedia wikis. However, stewards will
not create or assign these groups without community consensus.
I propose the creation of a global rollback group. This would be very
useful for members of the small wiki monitoring team[2] and other
users involved in multiple-wiki countervandalism. We will also need
objective criteria for its assignment; I suggest elected administrator
access on at least one public Wikimedia wiki, and evidence of activity
in multiple-wiki countervandalism (like links to contributions on
multiple wikis).
[1] http://meta.wikimedia.org/wiki/Steward_handbook#Adjusting_global_groups_.26…
[2] http://meta.wikimedia.org/wiki/Small_Wiki_Monitoring_Team
--
Yours cordially,
Jesse Plamondon-Willard (Pathoschild)
Hotels too
----- Original Message ----
From: White Cat <wikipedia.kawaii.neko(a)gmail.com>
To: Wikimedia Foundation Mailing List <foundation-l(a)lists.wikimedia.org>
Sent: Thursday, May 29, 2008 8:06:12 AM
Subject: Re: [Foundation-l] Scholarships for wikimania
I know that but if it is delayed any more plane tickets will skyrocket and
the work of the committee may go to waste. I am fully aware that the
committee is doing their best. I do not expect any less from them. All I am
pointing out something obvious that might have been overlooked in the heat
of all thats going on.
- White Cat
On Thu, May 29, 2008 at 5:09 PM, Mark (Markie) <newsmarkie(a)googlemail.com>
wrote:
> they are being worked through. im guessing at sometime in the next week
> (BUT DO NOT TAKE THAT AS A PROMISE/DEADLINE) schols comm are working their
> way through the literally HUNDREDS of applications. they do not delay the
> decisions just for the shear fun of it.
>
> regards
>
> mark
>
> On Thu, May 22, 2008 at 11:44 AM, White Cat <
> wikipedia.kawaii.neko(a)gmail.com>
> wrote:
>
> > What is the status of scholarships of 2008 Wikimania? Egypt is a
> touristic
> > hotspot so people will not be neither able to find hotel rooms nor plane
> > tickets if this is delayed any more.
> >
> > Wikimania does not want to be a filthy rich-only club. :P
> >
> > - White Cat
> > _______________________________________________
> > foundation-l mailing list
> > foundation-l(a)lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
> >
> _______________________________________________
> foundation-l mailing list
> foundation-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
>
_______________________________________________
foundation-l mailing list
foundation-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l
For a week or so stewards have a new toy which became a very hot
potato. We got it mysteriously (at least for me; while I may guess how
did we get it), some of stewards started with tests, but, generally,
to be honest, we don't have a clue what to do with that. Actually,
some of us have some clue, some of us started with a very lite usage
of that (we need help from SWMT [1] members, so some of us thought
that it would be useful to give global rollback permission to them;
however, the group is removed after two or three days because we don't
have consensus about this).
So, there are global groups and they are documented at Stewards
handbook [2]. As you are *not* able to see [3], there are a lot of
interesting privileges [A1] and we (the community) need to start a
discussion how to use them.
The other fact is that stewards are now sysops at all projects. This
is, of course, very useful, because we don't need to become sysops for
every action and some of stewards are using admin rights at small
wikis at daily basis (usually, blocking spammers). Stewards are, also,
doubtful about having global CheckUser and Oversight rights and there
is no consensus about giving to ourselves such permissions. One group
thinks that we are not allowed to have global CU rights, while other
group think that we are able to have them, but we are not able to use
them at projects which have their own CUs. I agree with both
statements, while I prefer to treat those rights as purely technical,
but we have some technical problems with treating those rights as
technical, too :) So, yes, we are humans and we have our own doubts.
As I said, this is a hot potato which we got mysteriously. No one of
the Board members said anything to us, as well as we didn't get any
input from the WMF staff (except one not so significant Carry's
question). As this is a *huge* change, I am willing to think that they
are reading our emails and looking what should we do next. And I am
sure that the situation is a little bit funny to them; as well as it
is to me :)
The most important part of the implementation of the global groups is,
of course, a possibility to make a fine adjustments of *global*
permissions. At the [A1] you may see that all of the permissions are
equal to the local ones. This means that we are able to make global
admins, global bureaucrats, global checkusers as well as a global mix
of the permissions (or, better, some new global groups which would fit
better for a particular purpose).
I have some ideas how to make this or that, but I think that it is too
early to talk about that. First of all, you should know what is going
on and to discuss about the fact that we (the community) have
something new -- good or bad (I think that this is a good thing) --
which we probably got from some extraterrestrial form of life.
== A1 ==
The list of global permissions are below.
* Use higher limits in API queries
* Edit semi-protected pages
* Have one's own edits automatically marked as patrolled
* Delete pages with large histories
* Block other users from editing
* Block a user from sending email
* Administer elections
* Be treated as an automated process
* Search deleted pages
* Administrate global accounts
* Merge their account
* Check user's IP addresses and other information
* Create new user accounts
* Create pages (which are not discussion pages)
* Create discussion pages
* Delete pages
* View deleted history entries, without their associated text
* Edit pages
* Edit the user interface
* Edit other users' CSS and JS files
* Edit membership to global groups
* Manage global groups
* Review and restore revisions hidden from Sysops
* Import pages from other wikis
* Import pages from a file upload
* Bypass IP blocks, auto-blocks and range blocks
* Grant and revoke bot flags
* Make users into sysops or bureaucrats
* Mark rolled-back edits as bot edits
* Mark edits as minor
* Move pages
* Not have minor edits to discussion pages trigger the new messages prompt
* nuke
* Override the spoofing checks
* View a previously hidden revision
* Mark others' edits as patrolled
* Change protection levels and edit protected pages
* Bypass automatic blocks of proxies
* Purge the site cache for a page without confirmation
* Read pages
* Rename users
* Overwrite an existing file
* Override files on the shared media repository locally
* Quickly rollback the edits of the last user who edited a particular page
* Perform captcha triggering actions without having to go through the captcha
* Not create a redirect from the old name when moving a page
* Override the title blacklist
* Submit a trackback
* Override the username blacklist
* Undelete a page
* View a list of unwatched pages
* Upload files
* Upload a file from a URL address
* Edit all user rights
== Links ==
[1] - Small wiki monitoring team:
http://meta.wikimedia.org/wiki/Small_Wiki_Monitoring_Team
[2] - http://meta.wikimedia.org/wiki/Steward_handbook#Adjusting_global_groups_.26…
[3] - The example is the list of the stewards' permissions:
http://meta.wikimedia.org/wiki/Special:GlobalGroupPermissions/steward
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wikimedia foundation blog, is located at http://blog.wikimedia.org
Information about this blog can be located at
http://meta.wikimedia.org/wiki/Wikimedia_Blog
The blog is currently encouraging suggested post drafts from the
contributers on here at Wikimedia. Please check out the drafting
instructions at
http://meta.wikimedia.org/wiki/Wikimedia_Blog#Drafting_a_post
Send in your material!
An example of a post that could be drafted is the new SUL / Unified
login system. Perhaps a contributer knowledgeable in that area could
write something up. :)
Very Best!
Jon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIPg5E6+ro8Pm1AtURAsG1AKChff/DbcmMDAzg9fNWIjkiqzskGQCgn3QV
C2WE9SD8rPPdWiCX6xisqPA=
=Ik3m
-----END PGP SIGNATURE-----
----- Original Message ----
From: Gerard Meijssen <gerard.meijssen(a)gmail.com>
To: Wikimedia Foundation Mailing List <foundation-l(a)lists.wikimedia.org>
Sent: Monday, April 14, 2008 1:37:38 AM
Subject: Re: [Foundation-l] Ancient Greek Wikipedia
Hoi,
Greek is understood to be understood to have several
branches<http://www.ethnologue.com/show_family.asp?subid=90066>.
Koine is according to Ethnologue part of "Ancient Greek". This is Greek
until 1453 AD according to the ISO standard. Now when the definition of
"Ancient" is wrongly applied, get this addressed at the appropriate places.
This is the right way to approach this. Again, this is most likely to lead
to a new code to acknowledge modern usage.
Thanks,
GerardM
for gerard and pathoschild
for you, is very important the need of a new class of ISO code? for opening a Wikipedia?
1.- Ancient is a neccesary adjective for differenciating with modern greek (native language), a different language (with its own gramar, sintaxis, etc). it needs even if is used in contemporanean context. unless the modern language no longer called "Greek". i guess, it is imposible.
2.- if you read my last post. you realize that even scholars don't differentiate extint languages that are still in use and the ones aren't to (the unique factor considered is the lack native speaker and no more). don't exist a concept for them. it is the perpetual problem of all the social science, the lack of accurate terms. (latin has also a code of extint language)
if ISO base its decision in these concepts. don't you believe that is practically imposible the creation of a new Kind of Code?
inevitably, it has to be used. does not exist another code for identifying ancient greek.
3.- with a sense of fair, if, i think, it has been more o less clear that ancient greek is still in use in many contexts. you would think is a moment to rethink the decission, woun't you think has been excessively restrictived?
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
---------- Forwarded message ----------
From: Desilets, Alain <Alain.Desilets(a)nrc-cnrc.gc.ca>
*************************************************************
2nd CALL FOR PAPERS: 2 weeks left for submissions deadline
*************************************************************
W i k i S y m 2 0 0 8
The International Symposium on Wikis
http://www.wikisym.org/ws2008/
September 8-10, 2008
Porto, Portugal
In-cooperation with ACM SIGWEB * ACM-DL Archived
*************************************************************
After the excellent response in terms of paper submissions, we are
sending now a gentle reminder to inform that the deadline for
submitting posters, demos, WikiFest proposals, and DoctoralSpace
proposals is still open and due in about *2 weeks*.
Please visit our website at http://www.wikisym.org/ws2008/ for more
information or contact the chairs, Ademar Aguiar and Mark Bernstein
through chair(a)wikisym.org.
Best Regards,
Alain Désilets Mark Bernstein Ademar Aguiar
NRC Canada Eastgate Systems University of Porto
Publicity Chair Program Chair Conference Chair
~ ~ ~
IMPORTANT DATES
* June 11th: submissions deadline for posters, demos, and
DoctoralSpace proposals
* June 25th: notifications for research papers, practitioner reports, panels,
tutorials, DoctoralSpace proposals, posters, and demos
* July 19th: final revised pdf's are due
* Sept 8th-10th: WikiSym 2008 days
~ ~ ~
SYMPOSIUM COMMITTEE
Conference: Ademar Aguiar, INESC Porto, University of Porto, Portugal
Program: Mark Bernstein, Eastgate Systems, USA
Honorary: Ward Cunningham, About Us, USA
Workshops & Panels: Andrea Forte, Georgia Institute of Technology, USA
OpenSpace: Ted Ernst, About Us, USA
WikiFest: Stewart Mader, WikiPatterns.org, Atlassian, Australia;
Uri Dekel, Carnegie Mellon University, USA
Tutorials: Marc Laporte, TikiWiki.org, Canada
Posters and Demos: Martin Cleaver, Blended Perspectives, Canada
Treasurer and Sponsorships: Dirk Riehle, SAP Research, SAP Labs LLC, USA
Publicity: Alain Désilets, National Research Council of Canada;
Marissa Hoftiezer, Carleton University, Canada
Web: Nuno Flores, University of Porto, Portugal
PROGRAM COMMITTEE
Mark Bernstein, Eastgate Systems, USA (Chair)
Phoebe Ayers, University of California at Davis, USA
Robert Biddle, Carleton University, Canada
Dan Bricklin, Software Garden, USA
Amy Bruckman, Georgia Institute of Technology, USA
Thomas Burg, Socialware, Austria
Ward Cunningham, About Us, USA
Chris Dent, Peermore, Ltd., United Kingdom
Alain Désilets, National Research Council of Canada
Lilia Efimova, Telematica Instituut, The Netherlands
Ted Ernst, About Us, USA
Andrea Forte, Georgia Institute of Technology, USA
Frank Fuchs-Kittowski, Fraunhofer-Institut für Software und
Systemtechnik, Germany
Susan Herring, Indiana University, Bloomington, USA
Samuel J. Klein, One Laptop Per Child, USA
George Landow, Brown University, USA
Helmut Leitner, WikiService, Austria
Stewart Mader, Atlassian, Australia/USA
Sky Marsen, Victoria University of Wellington, New Zealand
Cathy Marshall, Microsoft Research, USA
J. Nathan Matias, Cambridge University, United Kingdom
Paulo Merson, Software Engineering Institute, USA
Adrian Miles, Royal Melbourne Institute of Technology, Australia
David Millard, University of Southampton, United Kingdom
Stuart Moulthrop, University of Baltimore, USA
James Noble, Victoria University of Wellington, New Zealand
Dirk Riehle, SAP Research, SAP Labs LLC, USA
Scott Rosenberg, cofounder, Salon, USA
Jeremy Ruston, BT, United Kingdom
Christoph Sauer, Hochschule Heilbronn, Germany
Frank Shipman, Texas A&M, USA
(cc'd to Foundation-l because of para 3)
School shootings are extraordinarily high profile events, nearly always
followed by investigations of warnings and foreshadowing events - where
blame is cast in a wide net on anyone who failed to notice what, in
hindsight, was a "clear sign." Often these "clear signs" are only clear at
all in hindsight, because as human beings we interpret what we see based on
what we have seen in the past and few of us have encountered threats from
children that turned out to be very serious.
Wikipedia is in a unique position to suffer from the recriminations
associated with school shootings, and our role is only going to become more
widespread and high profile as time goes on. Threats made on Wikipedia have
the characteristics of being written, indelible, and traceable to a specific
computer (given the right resources). Additionally, threats on Wikipedia are
*seen* - this is key, because few threats of violence on Wikipedia get past
recent change patrollers and watchlists of attentive editors. So, when a
school shooting threat is posting on Wikipedia it is time stamped,
indelible, traceable and seen more or less immediately.
The question, then, is what if any moral imperative does this impose on us?
And if some of us feel compelled to report such instances to the police, and
others do not, what if any should the extent of policy be on this issue?
Personally I can't agree to any Wikipedia policy that mandates or punishes
behavior off-wiki. On the other hand, I do think a policy that encourages
all editors to report specific school threats to AN and (when willing and
possible) to the police is workable and a good idea. Frankly, I'm surprised
and I'm sure many others would be as well to learn that there isn't already
such a Wikipedia policy. At a minimum, we should have a policy of forwarding
all such threats to the Wikimedia Foundation for "official" action if
necessary.
This issue is distinct from the issue of threats of self-harm, suicide or
harm to public figures. While vague threats to celebrities and "I'ma kill
Joe, he's a dickwad" are often reverted and ignored as simple and unserious
vandalism, school threats have a unique nature in public sentiment and
require a unique position in policy. I'm writing this to the two lists
because its an issue that deserves a higher profile discussion than on a
proposed policy page (already nominated for deletion) with a couple editors
who think the policy is trying to force people in calling the cops when they
don't want to.
Nathan