Commons-l

commons-l@lists.wikimedia.org

2055 discussions

Re: [Commons-l] Policy
by Gerard Meijssen 15 Feb '09

15 Feb '09

Hoi, The notion that you "have to" desysop people when they are inactive is a falacy on several levels. When people are trusted, they can imho be an admin. In many ways it is an old debate but the difference is that you delete people. Thanks, GerardM 2009/2/15 <abigor(a)forgotten-beauty.com> > Hello, > > > > I need some information I can't really fin don Commons. > > > > We have a policy that says you have to do 5 admin actions in 6 months to > keep your adminship, we have sererval users that doesn't have any admin > actions for more than a year, can those user be desysoped on Meta or is > there a other policy? > > > > Best regards, > > Huiv > > _______________________________________________ > Commons-l mailing list > Commons-l(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/commons-l > >

3 5

Policy
by abigor＠forgotten-beauty.com 15 Feb '09

15 Feb '09

Hello, I need some information I can't really fin don Commons. We have a policy that says you have to do 5 admin actions in 6 months to keep your adminship, we have sererval users that doesn't have any admin actions for more than a year, can those user be desysoped on Meta or is there a other policy? Best regards, Huiv

1 0

Re: [Commons-l] CC video game: commoners vs enclosur
by bawolff 14 Feb '09

14 Feb '09

>Message: 1 >Date: Fri, 13 Feb 2009 18:13:42 +0000 >From: David Gerard <dgerard(a)gmail.com> >Subject: [Commons-l] CC video game: commoners vs enclosure >To: Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org> >Message-ID: <fbad4e140902131013q25930cfdhb89067b0a5d93c90(a)mail.gmail.com> >Content-Type: text/plain; charset=UTF-8 > >http://www.onthecommons.org/content.php?id=2243 > >(That Commons, not this Commons, but apposite to this list.) > > -> d. (cough cc-by-'''nc'''-sa).... Still kind of cool though. -bawolff

1 0

FYI: Proposal for rollback
by ChrisiPK 14 Feb '09

14 Feb '09

Hi everyone, as a discussion on the Village Pump made it clear that we want to have the rollback feature enabled for non-admins, I have started a proposal at Commons:Rollback. Feel free to drop your thoughts on the talk page. See http://commons.wikimedia.org/wiki/Commons:Rollback Thanks and best regards, ChrisiPK

1 0

CC video game: commoners vs enclosure
by David Gerard 13 Feb '09

13 Feb '09

http://www.onthecommons.org/content.php?id=2243 (That Commons, not this Commons, but apposite to this list.) - d.

1 0

Rollbacker
by abigor＠forgotten-beauty.com 10 Feb '09

10 Feb '09

Hello, There is a discussion about activation Rollback for non admins here: http://commons.wikimedia.org/wiki/Commons:Village_pump#Rollback Your opinion is much appriciated. Best regards, Huib

1 0

Re: [Commons-l] Commons-l Digest, Vol 45, Issue 5
by wayne 07 Feb '09

07 Feb '09

> >In terms of activist groups potentially contributing to Commons: > >When I was in Hobart recently for Linux Conference Australia 2009 the >"Steve Irwin" (the Flagship of the Sea [[Shepherd]] anti-whaling >group) had just pulled in to port for refueling and supplies. Actually I talk to Mr. Watson a bit and through his brother Stephen Watson (a great nature artist) I have a CD of Sea Shepherd photos but unfortunately he sent me low resolution photos but still interesting to view.. I have permission from Sea Shepherd but they hardly answer their e-mails if Commons needs them to send the permissions. WayneRay

1 0

some new contributors?
by private musings 07 Feb '09

07 Feb '09

This looks interesting! http://forums.whyweprotest.net/15-media/photographers-wikimedia-commons-ima… It seems members of the anti-scientology movement are interested in contributing to commons - I've heard tell of some early en-wiki volunteers being previously active in usenet scientology discussions, so it's interesting to see the next generation plugging in... cheers, Peter, PM.

2 2

default quality for ogg content?
by Michael Dale 06 Feb '09

06 Feb '09

Once we ship the firefogg extension support for the uploading videos; commons should request that users select the highest quality source video footage available ie the HD video their camera captured or DV original edited footage from their local computer and then commons will supply the transcode settings. I think it would be good if we wrote up some documentation to explain this to uploaders... any volunteers to help on that front? Presently for the firefogg upload support I have arbitrarily chosen 400 pixels wide with keep-aspect ratio and 500kbs bitrate. Firefogg could let us request multiple encodes or profiles from the user. Should we plan on supporting multiple "profiles" ie multiple quality settings? Ie one version at around 320 wide 300kbs for low bandwidth / resolution environments, cell phones etc (300kbs should be "acceptable quality" once the new Thusnelda theora encoder lands). We could additionally read the source file resolution that users provide and choose a "maximum quality preservation version" we could probably even ship the Dirac codec with firefogg (Dirac is a high quality at high resolution wavelate codec for more on dirac see your favorite info source ;) If we want to support multiple quality settings for a single "stream" this will require a bit more infrastructure. Specifically I propose we add another namespace for temporal media called Stream: and have it directly map to ROE xml something like: http://tinyurl.com/72x57r more info on ROE http://wiki.xiph.org/index.php/ROE File:my_movie_low_quality.ogg and File:my_movie_high_quality.ogg would soft redirect to Stream:my_movie and all the meta info would be stored there. The Stream namespace also allows us to group other media tracks that share a temporal meaning such as multiple language audio dubbing and multilingual transcripts/ subtitles. The javascript player can then dynamically select audio language and or subtitles based on the user language. Stream namespace could also store "mirrors" or point to "torrents" improving syndication and bandwith cost distribution for high traffic HD content ie (Miro could read the ROE file and grab the torrent rather than hit our servers) and or a Firefox torrent extension could be detected by our javascript player and choose the torrent over hitting our servers for the HD content. Not to say all these things will happen at once ... just pointing out the need for a new namespace to group idential temporal meaning files. --michael

4 4

Request for extension to provide metadata support
by Brianna Laugher 05 Feb '09

05 Feb '09

Hi all, As you are probably aware, enabling reuse is an important part of Wikimedia Commons' mission. We do this for humans by clearly indicating licenses and author information (that's the theory, anyway :)). But we also need to do it for machines, because it is machines that allow reuse of our material on a much larger scale, e.g. by libraries, museums, and other archives. Currently the data we provide for machines in quite poor. Although it is quite easy for a human to look and see that {{GFDL}} is a license template, for machines it is much harder because there is no "standard" that says which templates represent licenses and which represent other things. Figuring out who the author is, for attribution purposes, is also often difficult (is it the uploader? what if someone uploaded a slightly edited version?). As an example, PediaPress would like to use this information, for their printed wiki-books, to put the licenses of the images. At the moment there is literally no way they could do this reliably without having a human do it for every single image. Anyway, it is my strong belief that for Wikimedia Commons to be more successful and more useful, we need a way of encoding this kind of information in a machine-readable format. There are a number of different approaches one could take, but I think it is better if we just ask the developers for any extension/feature which will do this job, and let them figure out which is most appropriate. If you agree, please sign <http://commons.wikimedia.org/wiki/Commons:Village_pump/Request_for_extensio…> and indicate your support for helping Wikimedia Commons material reach a wider audience. ***Community support is a necessary condition to get a feature like this enabled.*** So please speak up if you want to support this idea, by signing the page. <http://commons.wikimedia.org/wiki/Commons:Village_pump/Request_for_extensio…> thanks! Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Commons-l