Just some observations and remarks on this issue.
I think it was not a mistake that every project got the fundraising notice.
I was on an IRC channel when there was a discussion of some project being upset, and therefore blanking the message or not translating it. One person asked if the messages could be turned off for some projects. A few developers expressed that those projects should come up with alternative fundraising plans that cover their portion of expected funding need. Nothing was turned off. There followed a discussion of putting different traffic priorities to different projects. (But I am not sure if they were really serious about this.)
I have to say I was quite disappointed about the lack of mutual trust. I think the developers thought those projects do not care about our financial needs and only be annoyed by the message. I think those projects reacted negatively because the project members thought the placing of the notice was top-down, English-centric practice.
I have to say that both sides might be right, which is even more disappointing than the mutual distrust
I saw Sj talking with the developers, suggesting some sensible solutions, visiting many Wikipedias and talk to others, and after all, things changed rather easily. Developers did understand how things could work out better, and came up with a better technical solution very quick. Some projects did respond to Sjs call and translate the message into their languages. So, after all, we are not so disappointing, I found.
Tomos
_________________________________________________________________ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/
Tomos at Wikipedia wrote:
I think it was not a mistake that every project got the fundraising notice.
It was a mistake, at least in the sense that I asked for the notice to be put up, and _thought_ that I communicated the intention that it be put up in English only. Whether it went up elsewhere because my intention was not sufficiently clear, or because the person who actually put it up made a mistake, I don't know.
But it only made sense because we are in a cycle of Slashdot stories, and Slashdot is an English website.
I was on an IRC channel when there was a discussion of some project being upset, and therefore blanking the message or not translating it. One person asked if the messages could be turned off for some projects. A few developers expressed that those projects should come up with alternative fundraising plans that cover their portion of expected funding need.
I do not know if this was a joke or a serious proposal, but I do not support this in any way shape or form. And if I don't support, more precisely, if the board doesn't support it (and I think I can comfortably say that none of us would), it isn't going to get anywhere at all.
Nothing was turned off. There followed a discussion of putting different traffic priorities to different projects. (But I am not sure if they were really serious about this.)
I don't know the nature of that discussion, so I can't comment. I would say that *if anything*, I would support that we always tend to "look out for the little guy" first, that is to say, to do whatever we need to do to make sure that small and growing wikimedia communities do not become 'ghettos' without proper support.
So after all, we are not so disappointing, I found.
Yes. Everyone, especially everyone who is really active, can be safely assumed to be acting from maximum goodwill. WikiLove and all that. :-)
Please always communicate to everyone in every language that I view Wikimedia as a _global_ movement, and that I am very much opposed to English-centric decisionmaking.
As a matter of practicality, it is not possible to conduct high-level policy discussions in any other language than English. And this is not just because of the board being English, but rather because for reasons that have nothing to do with any of us, English is the most widely spoken intermediate language in our environment.
If a German, a Japanese, an Italian, and a French person all meet to speak, and they wish to successfully communicate, it will be in English in most cases. This is not the fault of anyone at Wikipedia, and it is not an excuse for being English-centric in any way.
--Jimbo
Jimmy (Jimbo) Wales wrote:
As a matter of practicality, it is not possible to conduct high-level policy discussions in any other language than English. And this is not just because of the board being English, ...
Uh ?
:-)
Anthere wrote:
As a matter of practicality, it is not possible to conduct high-level policy discussions in any other language than English. And this is not just because of the board being English, ...
Uh ?
:-)
:-)
I meant, well, again I put my foot in my mouth. I should have written "the most common language spoken by the board is English".
--Jimbo
--- "Jimmy (Jimbo) Wales" jwales@wikia.com wrote:
Anthere wrote:
As a matter of practicality, it is not possible
to conduct high-level
policy discussions in any other language than
English. And this is
not just because of the board being English, ...
Uh ?
:-)
:-)
I meant, well, again I put my foot in my mouth. I should have written "the most common language spoken by the board is English".
--Jimbo
But seriously Jimbo, given my bad english and my horrible accent, I *really* read that as a compliment !
;-)
__________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail
On Sun, 18 Jul 2004 06:37, Tomos at Wikipedia wrote:
Just some observations and remarks on this issue.
I think it was not a mistake that every project got the fundraising notice.
I was on an IRC channel when there was a discussion of some project being upset, and therefore blanking the message or not translating it. One person asked if the messages could be turned off for some projects. A few developers expressed that those projects should come up with alternative fundraising plans that cover their portion of expected funding need. Nothing was turned off. There followed a discussion of putting different traffic priorities to different projects. (But I am not sure if they were really serious about this.)
The idea about different traffic priorities was mine; the quotes are:
<jeronim`> 1. use delay pools in squid to lower service priority for wikis which reject money-asking messsages
and later,
<jeronim`> could have a community-decided choice between no ads, opt-in, or opt-out? <jeronim`> and quality of service somehow determined based on ad revenue?
This was *just brainstorming*. The idea was to increase choice by allowing each wiki to make its own decision about the tradeoff of aesthetics (advertising/donation requests or the lack of them) against speed (coming from ad revenue/donations).
Maybe these are stupid ideas or maybe not, but I'd like to be able to brainstorm on IRC without having to worry about doing damage control on the mailing list as a result.
--Jerome/jeronim
Jerome Jamnicky wrote:
Maybe these are stupid ideas or maybe not, but I'd like to be able to brainstorm on IRC without having to worry about doing damage control on the mailing list as a result.
While I don't agree with the ideas at all, I do very strongly support you on the idea that we should all be able to brainstorm without worring about damage control. A culture which is too quick to chop people's heads off for stating unpopular ideas is a culture where people may tend to self-censor to avoid getting in trouble.
--Jimbo
wikimedia-l@lists.wikimedia.org