Yeah, that one's noted for the post-mortem.
Philippe
On Aug 8, 2009, at 12:47 AM, Gregory Maxwell wrote:
> On Sat, Aug 8, 2009 at 2:38 AM, Gerard
> Meijssen wrote:
>> Hoi,
>> This is a huge improvement over the last election where not all
>> projects
>> were targeted for this type of mail. As
On Sat, Aug 8, 2009 at 2:38 AM, Gerard
Meijssen wrote:
> Hoi,
> This is a huge improvement over the last election where not all projects
> were targeted for this type of mail. As a result there is less bias in the
> system. So you can opt out if you do not want to receive an e-mail for the
> next e
Hoi,
This is a huge improvement over the last election where not all projects
were targeted for this type of mail. As a result there is less bias in the
system. So you can opt out if you do not want to receive an e-mail for the
next election.
Iit is a huge improvement to have an e-mail by the orga
Mark Williamson wrote:
> My point is that this situation has arisen many times in the past and
> the response is very frequently a simple "We can't help you, it's a
> local issue". Of course it should be dealt with at a local level but I
> think that the foundation should be a little less hands-off
Birgitte SB wrote:
> I don't know that it is useful to make a general policy for exceptions. I
> think it is better just to watch out for such problems to pop up and try to
> direct attention to them when they are noticed.
>
> I think it is a better use of time and energy to wait and react to
I already voted when I got my email, and I didn't think it was spam. I
smiled at the fact that Wikimedia is making sure everyone who can vote has
the opportunity.
Steven
On Fri, Aug 7, 2009 at 10:05 PM, wrote:
> Thomas,
>
> I'm sorry you got an email that bothered you. Trust me, we try to make
Thomas,
I'm sorry you got an email that bothered you. Trust me, we try to make sure no
one is bothered by them. Sometimes people fall through the cracks, and I'm
sorry that was the case here and in a few other cases.
We try - hard - to make sure that everyone who is entitled to vote knows it.
On Sat, Aug 8, 2009 at 12:40 AM, Thomas Dalton wrote:
> I have just received an email telling me I am eligible to vote in the
> board elections when I have already voted. Please don't send
> untargetted mass emails - they are spam.
"telling me I am eligible" and "untargetted mass e-mails" don't re
On Sat, Aug 8, 2009 at 7:40 AM, Thomas Dalton wrote:
> I have just received an email telling me I am eligible to vote in the
> board elections when I have already voted. Please don't send
> untargetted mass emails - they are spam.
>
> ___
> foundation-l
I have just received an email telling me I am eligible to vote in the
board elections when I have already voted. Please don't send
untargetted mass emails - they are spam.
___
foundation-l mailing list
foundation-l@lists.wikimedia.org
Unsubscribe: https:
2009/8/8 Stevertjgo :
> On Fri, Aug 7, 2009, Thomas Dalton said:
>
>> Perhaps we do need a dispute resolution mailing list for resolving
>> disputes that involve the mailing lists. It would be better than
>> having the lists themselves filled with complaints.
>
> I'm always open to similarly creat
On Fri, Aug 7, 2009, Thomas Dalton said:
> Perhaps we do need a dispute resolution mailing list for resolving
> disputes that involve the mailing lists. It would be better than
> having the lists themselves filled with complaints.
I'm always open to similarly creative suggestions, and I apprecia
Perhaps we do need a dispute resolution mailing list for resolving
disputes that involve the mailing lists. It would be better than
having the lists themselves filled with complaints.
___
foundation-l mailing list
foundation-l@lists.wikimedia.org
Unsubsc
Mark W. wrote:
> It looks to me like Austin did exactly what he should've so I'm not
> sure why you're implying he made an incorrect decision. Exactly what
> did he do wrong in your opinion?
Austin may have done exactly right, but his lack of responsiveness - just
as with Arbcom - just as with Car
On Fri, Aug 7, 2009 at 3:42 PM, Brion Vibber wrote:
> On 8/7/09 3:39 PM, James Forrester wrote:
>> 2009/8/7 Brion Vibber:
>>> On 8/7/09 3:06 PM, Thomas Dalton wrote:
It's not just about resumes, it's also about being taken seriously
when communicating with others. A "Head Software Archite
My point is that this situation has arisen many times in the past and
the response is very frequently a simple "We can't help you, it's a
local issue". Of course it should be dealt with at a local level but I
think that the foundation should be a little less hands-off than it
has often been when it
I don't know that it is useful to make a general policy for exceptions. I
think it is better just to watch out for such problems to pop up and try to
direct attention to them when they are noticed.
I think it is a better use of time and energy to wait and react to the sorts of
extreme situat
On 8/7/09 3:39 PM, James Forrester wrote:
> 2009/8/7 Brion Vibber:
>> On 8/7/09 3:06 PM, Thomas Dalton wrote:
>>> It's not just about resumes, it's also about being taken seriously
>>> when communicating with others. A "Head Software Architect" will
>>> probably be taken more seriously than a "Seni
On 8/7/09 2:35 PM, Gregory Maxwell wrote:
> By containing the magic words "senior" and "architect" the proposed
> "Senior Software Architect" is, in my experience, not inconsistent
> with industry naming practice for the most important tech guru who
> isn't primarily a manager.
>
> It's not a bad t
2009/8/7 Brion Vibber :
> On 8/7/09 3:06 PM, Thomas Dalton wrote:
>> It's not just about resumes, it's also about being taken seriously
>> when communicating with others. A "Head Software Architect" will
>> probably be taken more seriously than a "Senior Software Architect",
>> since the former sho
On 8/7/09 3:06 PM, Thomas Dalton wrote:
> It's not just about resumes, it's also about being taken seriously
> when communicating with others. A "Head Software Architect" will
> probably be taken more seriously than a "Senior Software Architect",
> since the former shows you are the boss, that latt
2009/8/7 Aryeh Gregor :
> Well, we can still informally call him the lead developer.
We can informally call him "Brion". It's worked up until now!
___
foundation-l mailing list
foundation-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/ma
2009/8/7 David Gerard :
> 2009/8/7 Gregory Maxwell :
>
>> It's not bad to have an internal pattern, but I think it's more
>> important to match the practices in industry.
>> By containing the magic words "senior" and "architect" the proposed
>> "Senior Software Architect" is, in my experience, not
It's great to hear this. We've really been lacking in senior
developer time for the last year or two, and I hope we can put an end
to that!
On Fri, Aug 7, 2009 at 5:58 PM, Robert Rohde wrote:
> I would like to note that it isn't just internal naming schemes and/or
> industry conventions that matt
On Fri, Aug 7, 2009 at 2:35 PM, Gregory Maxwell wrote:
> On Fri, Aug 7, 2009 at 5:19 PM, Erik Moeller wrote:
>> Our approach to job titles actually has an emerging basic pattern. :-)
>> It's not 100% consistent because we sometimes have stuck with commonly
>> used titles like "Office Manager" and "
2009/8/7 Gregory Maxwell :
> It's not bad to have an internal pattern, but I think it's more
> important to match the practices in industry.
> By containing the magic words "senior" and "architect" the proposed
> "Senior Software Architect" is, in my experience, not inconsistent
> with industry na
On Fri, Aug 7, 2009 at 5:19 PM, Erik Moeller wrote:
> Our approach to job titles actually has an emerging basic pattern. :-)
> It's not 100% consistent because we sometimes have stuck with commonly
> used titles like "Office Manager" and "General Counsel", but generally
> one we try to follow:
[sni
"Dark concepts"? Really? As encyclopedists, it is rarely our job to
judge, rather we are here to document from a neutral point of view.
Please remember that "darkness" is subjective, I'm sure there are
practices you consider "dark" that I do not and probably vice-versa.
Anyhow, David Goodman said
2009/8/7 Thomas Dalton :
> It's not really title inflation to give someone that is in charge of
> something a title which says that.
Our approach to job titles actually has an emerging basic pattern. :-)
It's not 100% consistent because we sometimes have stuck with commonly
used titles like "Offic
2009/8/7 Michael Snow :
> So you're suggesting we should join in the rampant title inflation of
> corporate America, where everyone is a Sr. Executive Vice-President of
> something? Anyway, your assessment of Brion's ongoing significance to
> our operations is perceptive, and I hope everyone else m
Robert Rohde wrote:
> On Fri, Aug 7, 2009 at 11:12 AM, Thomas Dalton wrote:
>
>> I think this is a fantastic idea. I think the biggest problem the tech
>> side of the WMF has had over the last year or two has been
>> prioritisation and splitting the job like this should help that no
>> end.
>>
>
I'm talking about more general policy, not ja.wp in particular.
On 8/7/09, Birgitte SB wrote:
> There are always extreme situations that merit exceptional treatment.
> ja.WP, however, has a great deal more than 3 active users.
>
> Birgitte SB
>
> --- On Thu, 8/6/09, Mark Williamson wrote:
>
>> F
On Fri, Aug 7, 2009 at 11:12 AM, Thomas Dalton wrote:
> I think this is a fantastic idea. I think the biggest problem the tech
> side of the WMF has had over the last year or two has been
> prioritisation and splitting the job like this should help that no
> end.
>
> I'm curious - would the Senior
On 8/7/09 11:12 AM, Thomas Dalton wrote:
> I think this is a fantastic idea. I think the biggest problem the tech
> side of the WMF has had over the last year or two has been
> prioritisation and splitting the job like this should help that no
> end.
>
> I'm curious - would the Senior Software Arch
On Mon, Aug 3, 2009 at 3:24 PM, David Goodman wrote:
> I'm pleased to accept the epithet. Pro-freedom dogmatist describes me
> nicely with respect to many areas of life, including both sexuality
> and access to information. I think it comes close to describing most
> of the people at Wikipedia i
**
____ _ __ _
/ / /\ \ (_) | _(_)___(_)_ __ ___
\ \/ \/ / | |/ / |_ / | '_ \ / _ \
\ /\ /| | <| |/ /| | | | | __/
\/ \/ |_|_|\_\_/___|_|_| |_|\___|
.org
Year: 2009 Week: 32 Number: 1
I think this is a fantastic idea. I think the biggest problem the tech
side of the WMF has had over the last year or two has been
prioritisation and splitting the job like this should help that no
end.
I'm curious - would the Senior Software Architect report to the CTO?
If so, that means Brion has
Thank you for the update, Brion. You've been effectively wearing every
hat there is to wear for a person with technical skills in the
Wikimedia Foundation. That's an enormously challenging set of
responsibilities, and you've managed them very well, both in good
times and in emergency-crisis-mode-ti
On 8/7/09 12:25 AM, private musings wrote:
> actually - might a WMF 'code of conduct' for projects be a good idea? (as in
> something perhaps a dollop more pragmatic than 'comply with our mission
> statement'!) - sounds like an idea for the strategy wiki... :-)
I'd say yes, but that a "code of con
I'm very excited to announce some new upcoming hiring for tech... I've
also posted this on our tech blog which is mirrored on Planet Wikimedia:
http://techblog.wikimedia.org/2009/08/cto-position-split/
--
Back in 2005, Wikimedia brought me on as the Foundation's first paid
employee after two ye
private musings wrote:
> Well yeah Milos - but we probably won't - will we! - Seems a bit silly.
>
> I was hoping we could have a thread about the principle of discussing /
> evaluating some of the various voluntary codes of conduct out there -
> perhaps someone is aware of a US standard (is that w
private musings wrote:
> Just wondering what folk think about the WMF heading towards
> compliance with things like this;
> http://www.gsmeurope.org/documents/eu_codes/fsm_code_en.pdf
Are you saying that WMF is already heading in that direction (that
would be news to me), and now you want our
There are always extreme situations that merit exceptional treatment. ja.WP,
however, has a great deal more than 3 active users.
Birgitte SB
--- On Thu, 8/6/09, Mark Williamson wrote:
> From: Mark Williamson
> Subject: Re: [Foundation-l] Wikipedia Policy Interlingual Coordinationn -
> WP:NO
Hoi,
I think this is relevant and of interest to us all...
Thanks,
GerardM
Report and related press release of interest...
The Minority Rights Group International (MRG) in collaboration with UNICEF
has recently released their "State of the World's Minorities and Indigenous
Peoples 2
Hoi,
What I like about Google is that they have the guts to try things out. I
like Google because they allow their staff to things that intrigue them.
This has brought me gmail among other things. With Google things may fail.
What you express is the expectation that Knol would fail and I am with y
2009/8/7 Milos Rancic :
> More than a year ago Google lunched Knol. It was a sensation then
> (BTW, it was a sensation for more time than Wolfram Alpha was). Today
> I just may say that I don't remember when I heard for the Knol last
> time.
Well, Wolfram Alpha is occasionally actually useful :-
Hoi,
You morals are fine. They are not mine and I am glad that we have to live to
the best of our abilities with what we can achieve. The problem that I have
with your morals is that you want to impose them onto others with a
multitude of justifications. You have been given to understand that there
On Fri, Aug 7, 2009 at 9:21 AM, Gregory Maxwell wrote:
> We don't have to follow the internet norm that making your web page
> text BLINKING YELLOW ON BLUE is something you don't do… and yet we do.
>
> Don't think of this has "obeying laws", think of it that there are
> some things we don't have to
private musings wrote:
> Well yeah Milos - but we probably won't - will we! - Seems a bit silly.
>
> I was hoping we could have a thread about the principle of discussing /
> evaluating some of the various voluntary codes of conduct out there -
> perhaps someone is aware of a US standard (is that w
actually - might a WMF 'code of conduct' for projects be a good idea? (as in
something perhaps a dollop more pragmatic than 'comply with our mission
statement'!) - sounds like an idea for the strategy wiki... :-)
(which just in case folk haven't seen is here -->
http://strategy.wikimedia.org/wiki/
On Fri, Aug 7, 2009 at 3:08 AM, Milos Rancic wrote:
> On Fri, Aug 7, 2009 at 8:41 AM, private musings wrote:
>> Well yeah Milos - but we probably won't - will we! - Seems a bit silly.
>>
>> I was hoping we could have a thread about the principle of discussing /
>> evaluating some of the various vol
On Fri, Aug 7, 2009 at 9:15 AM, private musings wrote:
> I quite agree (the analogy of paying taxes comes to mind!) - however I don't
> see any tension between that position and also feeling that it's a good idea
> to take a look at the principles involved in such codes of conduct etc. and
> to see
I quite agree (the analogy of paying taxes comes to mind!) - however I don't
see any tension between that position and also feeling that it's a good idea
to take a look at the principles involved in such codes of conduct etc. and
to see where 'we' (the broad WMF family, I guess) fit in
http://
On Fri, Aug 7, 2009 at 8:41 AM, private musings wrote:
> Well yeah Milos - but we probably won't - will we! - Seems a bit silly.
>
> I was hoping we could have a thread about the principle of discussing /
> evaluating some of the various voluntary codes of conduct out there -
> perhaps someone is a
54 matches
Mail list logo
