So I have to constantly clean up the mess over 750 wikis generate on a daily basis. We can avoid the entire process with little cooperation. - White Cat
On Sun, Apr 20, 2008 at 5:45 AM, Chad innocentkiller@gmail.com wrote:
If anyone would like to comment by the way, I threw up a basic draft over at [[c:Commons:Licensing_templates]]. I think it would be easier to make such a list and keep /it/ updated (and would be a good task for your bot, White_Cat), as opposed to a massive Foundation-wide renaming.
-Chad
On Sat, Apr 19, 2008 at 10:29 PM, Chad innocentkiller@gmail.com wrote:
Has nothing to do with "getting even" with commons. It's about commons doing their own work and the wikis doing theirs. While interoperability is a good idea, mass renaming would be highly disruptive. Not only would you need to agree on a good language-neutral name in and of itself (which is a task, knowing this or any other mailing list, or meta), then comes the job of localizing all of the information (you can't just rename templates. If they're going to be treated as the same, they must have /identical/ verbiage, localized), not to mention making sure every language affected has been notified (and agrees!). Now, I don't think individual wikis would mind helping gather the information for conversion tables (like I suggested), but I do think they would object to arbitrary renaming just to make the job easier for commons.
In light of all of these: no, I don't think running your bot is going to happen.
-Chad
On Sat, Apr 19, 2008 at 5:38 PM, White Cat
wikipedia.kawaii.neko@gmail.com wrote:
On Sat, Apr 19, 2008 at 11:59 PM, Pedro Sanchez pdsanchez@gmail.com
wrote:
On Sat, Apr 19, 2008 at 3:36 PM, White Cat wikipedia.kawaii.neko@gmail.com wrote:
The tone of your response is not in the spirit of what I am
trying to
do
here. I find it a bit repulsive. I would encourage you to tone
it down.
I am not asking for an English naming. "PD" is an abbreviation
like
"UN".
What you say isn't necessarily true. Japanese wikipedia for
example
uses
commons compatible names for their license templates.
http://ja.wikipedia.org/wiki/Category:%E7%94%BB%E5%83%8F%E3%81%AE%E8%91%97%E...
It is obviously more than workable.
I think Thai people can easily read the content of the template
even if
they
completely fail to read the templates name (say "{{GFDL}}") in
the
code.
People who edit wikipedia will figure out what such
abbreviation mean
in a
very short period of time. People who do not edit wikipedia
will never
see
these template names.
- White Cat
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe:
https://lists.wikimedia.org/mailman/listinfo/foundation-l
People incorrectly upload images, not just when uploading from
local
wikis to commons, but even when uploading directly to commons. Tempalte naming won't stop that problem.
Now, what I've understood, is that you want all wikis to make a
change
(and that change isn't being proposed on the wikis) to accomodate commons. You also need to take int oaccount that wikis have local uplaods,
and
thus thir template namings need to reflect the usage and language
for
the wiki users, with a much higher priority than commons needs.
Commosn has always complained when wikipedias demand commons to do something, telling "we're not here to serve wikipedias, we're a project on our own" Same goes reverse, wikipedias are not to serve commons, and you
want
to run a bot (for an unapproved task) to change widely used
templates
in many wikis without first discussing it with the wikis you will
be
affecting
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe:
https://lists.wikimedia.org/mailman/listinfo/foundation-l
So this is merely a getting even with commons huh? Commons isn't the
enemy.
- White Cat
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe:
https://lists.wikimedia.org/mailman/listinfo/foundation-l
foundation-l mailing list foundation-l@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/foundation-l