Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Pete Forsyth

On 01/25/2017 09:52 PM, Anna Stillwell wrote:
Got it. (I add color so I can see. I think I need better glasses. Sad!). 

:)

I was just asking whether you thought it was reasonable to give them the
time that they asked for.  It wasn't a governance question, or a discussion
about authority. I was just asking if those who commented, who all seemed
to have legitimate concerns, were willing to have the team get back to them
with any answers that they could fairly, justly, respectfully and legally
provide, but more likely they would talk about the future work.

In my mind I've been clear and consistent: "Hey, do you guys think it is
reasonable to give these guys some time?" But it seems like I've not made
this point clear. Would singing it at karaoke help?

Ha! Maybe.

I haven't said it's unreasonable, and I'm not sure anybody else has, 
either. In fact, I think The DJ explicitly acknowledged some of the 
points in your initial message, and by my reading implicitly 
acknowledged others. I don't think anybody is singling out the "pause in 
explaining the pause" as unreasonable.


I've heard the request, and with all the considerations, sure, it seems 
reasonable enough. What I've tried to do is express what some of the 
costs of further delay are; but asserting costs is not the same thing as 
saying further delay is unreasonable. I read Pine as trying to put it in 
a broader context of problems that may be systemic; but I don't think 
that's the same as saying it's unreasonable, either. So, perhaps we're 
not all as far apart as it might appear?

I'd be happy to chat if you come back to it at the end of Q3, if you'd
like.

Thanks. I'll reach out.

I'll have the karaoke machine ready!

-Pete
[[User:Peteforsyth]]


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Anna Stillwell
On Wed, Jan 25, 2017 at 9:14 PM, Pete Forsyth  wrote:

> Anna,
>
> I've now read what you quoted for a third time, and can confirm I did
> understand, and agree with, what you said. I'm sorry my summary was
> inadequate, and may have made it seem otherwise.
>
> As for planning, I am not making assumptions, but perhaps interpreting
> differently from you. I'm happy to defer to Pine on the details; their
> recent message captures the gist of what I intended.
>
> I can't give a solid estimate of the "half-life," but I do not think the
> enthusiasm I've seen (and the metrics I cited in my initial message on this
> thread) constitute a passing crush. I do think a "pause" that necessitates
> addressing uncertainty when discussing popular features can have a
> significant impact, and therefore should be minimized to whatever degree is
> attainable. I could be wrong, but that's my belief.
>

Got it.  (I add color so I can see. I think I need better glasses. Sad!).

>
> As for the request for more time, I guess I'm just not sure what to make
> of it. I make no demands, and I'm not sure I've heard Pine, James, DJ, or
> anybody in this thread make demands. Is there somebody with standing to
> grant such a request? I've heard it, and it makes sense. It's worthwhile to
> know that the team needs more time, and plans to share more on a scale that
> sounds like days-to-weeks. But if there's something specific being asked of
> me (or others on this list), I'm not clear on what it is.
>

I was just asking whether you thought it was reasonable to give them the
time that they asked for.  It wasn't a governance question, or a discussion
about authority. I was just asking if those who commented, who all seemed
to have legitimate concerns, were willing to have the team get back to them
with any answers that they could fairly, justly, respectfully and legally
provide, but more likely they would talk about the future work.

In my mind I've been clear and consistent: "Hey, do you guys think it is
reasonable to give these guys some time?" But it seems like I've not made
this point clear. Would singing it at karaoke help?

>
> I'd be happy to chat if you come back to it at the end of Q3, if you'd
> like.
>

Thanks. I'll reach out.

>
> -Pete
>
> [[User:Peteforsyth]]
>
>
>
> On 01/25/2017 06:38 PM, Anna Stillwell wrote:
>
>> On Wed, Jan 25, 2017 at 4:53 PM, Pete Forsyth 
>> wrote:
>>
>> Anna,
>>>
>>> Pete,
>>
>> Your points are valid and well taken. If I may summarize what I think I
>>> heard, it's basically: "Getting things right can be hard, and if full
>>> preparations weren't made ahead of time, thorough answers may not be
>>> readily available. Be compassionate/patient." Is that about right?
>>>
>>
>> I appreciate that you are trying to understand what I mean. Thanks.
>>
>> No, I didn’t say getting things right can be hard. I said, “This
>> communication thing is hard, especially when people are involved.
>> Sometimes
>> there are laws that constrain what we say. Sometimes we don’t know whether
>> we are right yet and we need a further unpacking of the facts. The truth
>> is
>> that there can be a whole host of reasons for partial communication that
>> aren’t related to competence or the intent to deceive.”
>>
>> As for the preparations, it seems that a lot of assumptions are being
>> made.
>> As for thorough answers, some might already be known and others known once
>> more planning is completed. However, it could be that the explanations you
>> want are not legal to share. There are many issues where employment law
>> and
>> worker protections are crystal clear, as they should be.
>>
>> As for compassion, I don’t require it. That seems like extra to me. I
>> usually prefer just paying attention, but that’s my personal choice.
>>
>> The team asked for some time. I wondered if that would be a reasonable
>> request to grant them.
>>
>> If so, I agree in principle and in spirit, but I think the point is in
>>
>>> tension with
>>> another one:
>>>
>>> Community and public enthusiasm for software can be a rare and important
>>> thing. The conditions that make it grow, shrink, or sustain are complex,
>>> and largely beyond the influence of a handful of mailing list
>>> participants.
>>> The recent outputs of the Interactive Team have generated enthusiasm in a
>>> number of venues, and many on this list (both volunteers and staff) would
>>> like to see it grow or sustain, and perhaps throw a little weight behind
>>> an
>>> effort to make it grow or sustain.
>>>
>>> Good points. I mean that. Glad to hear of these recent outputs generate
>> excitement. I’m personally also getting quite excited about ORES
>> 
>> and
>>
>> what’s going on with the Community Tech Wish List, Labs, and New Readers.
>> But I also get that you want to be clear: you'd like to see the
>> interactive
>> team’s work grow or sustain. Makes sense.
>>

Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Pete Forsyth

Anna,

I've now read what you quoted for a third time, and can confirm I did 
understand, and agree with, what you said. I'm sorry my summary was 
inadequate, and may have made it seem otherwise.


As for planning, I am not making assumptions, but perhaps interpreting 
differently from you. I'm happy to defer to Pine on the details; their 
recent message captures the gist of what I intended.


I can't give a solid estimate of the "half-life," but I do not think the 
enthusiasm I've seen (and the metrics I cited in my initial message on 
this thread) constitute a passing crush. I do think a "pause" that 
necessitates addressing uncertainty when discussing popular features can 
have a significant impact, and therefore should be minimized to whatever 
degree is attainable. I could be wrong, but that's my belief.


As for the request for more time, I guess I'm just not sure what to make 
of it. I make no demands, and I'm not sure I've heard Pine, James, DJ, 
or anybody in this thread make demands. Is there somebody with standing 
to grant such a request? I've heard it, and it makes sense. It's 
worthwhile to know that the team needs more time, and plans to share 
more on a scale that sounds like days-to-weeks. But if there's something 
specific being asked of me (or others on this list), I'm not clear on 
what it is.


I'd be happy to chat if you come back to it at the end of Q3, if you'd like.

-Pete

[[User:Peteforsyth]]


On 01/25/2017 06:38 PM, Anna Stillwell wrote:

On Wed, Jan 25, 2017 at 4:53 PM, Pete Forsyth  wrote:


Anna,


Pete,


Your points are valid and well taken. If I may summarize what I think I
heard, it's basically: "Getting things right can be hard, and if full
preparations weren't made ahead of time, thorough answers may not be
readily available. Be compassionate/patient." Is that about right?


I appreciate that you are trying to understand what I mean. Thanks.

No, I didn’t say getting things right can be hard. I said, “This
communication thing is hard, especially when people are involved. Sometimes
there are laws that constrain what we say. Sometimes we don’t know whether
we are right yet and we need a further unpacking of the facts. The truth is
that there can be a whole host of reasons for partial communication that
aren’t related to competence or the intent to deceive.”

As for the preparations, it seems that a lot of assumptions are being made.
As for thorough answers, some might already be known and others known once
more planning is completed. However, it could be that the explanations you
want are not legal to share. There are many issues where employment law and
worker protections are crystal clear, as they should be.

As for compassion, I don’t require it. That seems like extra to me. I
usually prefer just paying attention, but that’s my personal choice.

The team asked for some time. I wondered if that would be a reasonable
request to grant them.

If so, I agree in principle and in spirit, but I think the point is in

tension with
another one:

Community and public enthusiasm for software can be a rare and important
thing. The conditions that make it grow, shrink, or sustain are complex,
and largely beyond the influence of a handful of mailing list participants.
The recent outputs of the Interactive Team have generated enthusiasm in a
number of venues, and many on this list (both volunteers and staff) would
like to see it grow or sustain, and perhaps throw a little weight behind an
effort to make it grow or sustain.


Good points. I mean that. Glad to hear of these recent outputs generate
excitement. I’m personally also getting quite excited about ORES
 and
what’s going on with the Community Tech Wish List, Labs, and New Readers.
But I also get that you want to be clear: you'd like to see the interactive
team’s work grow or sustain. Makes sense.

The only thing I heard is that the team said that they needed to pause,
have a bit of time, and get back to everybody. “The team's aim during this
period is to get its work to a stable and maintainable state.”


But that enthusiasm has a half-life. What is possible today may not be
possible next week or next month. The zeitgeist may have evolved or moved
on by then.


I'm not in disagreement with your main point about enthusiasm for software.
I think it's a very good one. Enthusiasm with a half life of a week,
however, sounds more like a passing crush. Nevertheless, your point still
stands.


-Pete
--
[[User:Peteforsyth]]


/a
[[User:Annaproject]]


On Wed, Jan 25, 2017 at 3:53 PM, Anna Stillwell 
wrote:


You make substantive points, Tim. Thank you.

"An employee should not experience their time off as a period where his
[her/they] work load is just temporarily buffered until his [her/they]
return, but where colleagues will step in and take care of business."

I take this point seriously and don't wish you to 

Re: [Wikimedia-l] [discovery] Interactive Team putting work on pause

2017-01-25 Thread Anna Stillwell
Pine,

>
> This email is probably a little harsher than I would like it to sound. I
> admit to being frustrated -- not so much about this particular case, but
> the general situation of the very mixed levels of WMF staff responsiveness
> to requests for information.
>

Heard.

I'll be ready to talk ideas about this at the end of Q3, but not before.
I'm not promising a course of action yet, I'd like to understand a lot more
first. Might I reach out to you at that time and understand your thoughts?
Anyone else willing to let me ring them and ask them questions?

/a

>
> Pine
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>



-- 
"If you have knowledge, let others light their candles in it." - Margaret
Fuller

Anna Stillwell
Director of Culture
Wikimedia Foundation
415.806.1536
*www.wikimediafoundation.org *
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [discovery] Interactive Team putting work on pause

2017-01-25 Thread Anna Stillwell
Hey Kelly,

Nice to hear from you. Glad you've chimed in.

I know a lot of people on this team. They have all seemed reasonable to me
in addition to being well intentioned. They're competent people. My bet is
that they have this handled, but there's a lag in communication time for
some reason and that they are working on that.

And contributors are enthusiastic about software. Claro que si! This is
obviously a good thing and we very much want to listen to what they have to
say and understand their needs.

I just stepped in at the last minute to see if people were willing to give
them a bit of time. The credit belongs elsewhere, but it's nice to hear
your voice and I hope your new role is going well.

Warmly,
/a



On Wed, Jan 25, 2017 at 7:33 PM, Kelly Battles 
wrote:

> Anna thank you so much for handling all of this.
> You do a great job and I am very appreciative of that...
>
> > On Jan 25, 2017, at 3:53 PM, Anna Stillwell 
> wrote:
> >
> > You make substantive points, Tim. Thank you.
> >
> > "An employee should not experience their time off as a period where his
> > [her/they] work load is just temporarily buffered until his [her/they]
> > return, but where colleagues will step in and take care of business."
> >
> > I take this point seriously and don't wish you to think otherwise. In
> > theory, I absolutely agree. In practice, sometimes we all face
> constraints.
> > There are roughly 300 of us (order of magnitude). Every now and then,
> there
> > are not enough of us to go around on everything on a timeline that meets
> > the legitimate need that you present here. We'll continue to work on
> this.
> > But, to clarify, no one ever said it was a "useful practice" nor did
> anyone
> > suggest that it was generalized across the org.
> >
> > What I was wondering about in my previous email and now reiterating in
> this
> > one too, are people willing to grant their request: a bit of time and
> allow
> > for one person to return to work?
> >
> > Does that seem like a way to move forward?
> >
> > Warmly,
> > /a
> >
> > On Wed, Jan 25, 2017 at 2:50 PM, Tim Landscheidt  >
> > wrote:
> >
> >> Anna Stillwell  wrote:
> >>
> >>> […]
> >>
> >>> I also hear that the pause on the interactive work is temporary. I’ve
> >> heard
> >>> them request time. I am comfortable granting that request, but no one
> is
> >>> required to agree with me. They’ve also said that the person with the
> >> most
> >>> information is on vacation. As someone who has seen employees go
> through
> >>> considerable stress in the last years, the entire executive team is
> >> working
> >>> to establish some cultural standards around supporting vacations. We
> want
> >>> people here to feel comfortable taking proper vacations and sometimes
> >> that
> >>> can even need to happen in a crisis. People often plan their vacations
> >> well
> >>> in advance and may not know that something tricky will come up. Just so
> >> you
> >>> understand one bias I bring to this conversation.
> >>
> >>> […]
> >>
> >> I concur with DJ in his initial mail that this is not a use-
> >> ful practice, and I doubt very much that it relieves employ-
> >> ees' stress.  It conveys the organizational expectation that
> >> employees are SPOFs without any backup.  An employee should
> >> not experience their time off as a period where his work
> >> load is just temporarily buffered until his return, but
> >> where colleagues will step in and take care of business.
> >> Especially such a major decision like "pausing" a team
> >> should not depend on the inner thoughts of one employee, but
> >> be backed and explainable by others.
> >>
> >> Tim
> >>
> >>
> >> ___
> >> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> >> wiki/Mailing_lists/Guidelines
> >> New messages to: Wikimedia-l@lists.wikimedia.org
> >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> >> 
> >>
> >
> >
> >
> > --
> > "If you have knowledge, let others light their candles in it." - Margaret
> > Fuller
> >
> > Anna Stillwell
> > Director of Culture
> > Wikimedia Foundation
> > 415.806.1536
> > *www.wikimediafoundation.org *
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
>
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: 

Re: [Wikimedia-l] [discovery] Interactive Team putting work on pause

2017-01-25 Thread Pine W
Thanks for the summary, Chris.

Communications problems with WMF are a sore spot for me, as I've suffered
through a number of them. Despite years of talking about improving
communication, I've seen mixed results to date. I think that the community
liaisons have been valuable, but there is still much room for improvement,
particularly when it comes to how unpredictable WMF staff are in responding
to talk page and email inquiries.

Narrowing focus a little bit to to expand on my earlier point on the value
of having the decision-maker available to answer questions: if the
decision-maker is unavailable for a good reason (and I don't mean a
scheduled vacation, as a decision to pause the work for a team should have
been thoughtfully considered prior to its announcement, and there is every
good reason to budget an hour or two to prepare communications before
announcing decisions like this), I think it's reasonable to expect that
someone else with full access to the facts should be available for Q
That might be a communication person or a technical liaison, or the
person's supervisor. The impression I get is that Dan was making a
good-faith effort to answer questions but did not have access to all of the
facts. I hope that in future cases where the decision-maker is unavailable,
that there will be better planning so that someone who does have access to
all of the facts is available for Q

I'm going to be frank. A scheduled vacation isn't an excuse for poor
planning. I don't mean to say that in a punitive way (I've made planning
errors myself), but rather in the sense that I hope that there will be
thought invested in how to do better planning in the future for
communications surrounding significant decisions when the decision-maker
will be unavailable. Looping back to the beginning of this thread, I agree
with DJ: "2: It shouldn't matter that Katie is on holidays, I'd assume/hope
someone takes over her duties while she is away (Likely Dan himself and/or
Wes Moran). Providing information on topics like this shouldn't have to
wait until someone returns from a (likely well deserved) holiday." I've had
similar frustrations with unresponsiveness from other staff, and I'd like
to see some meaningful effort invested in ensuring that every good-faith
inquiry gets a timely and well-informed answer.

This email is probably a little harsher than I would like it to sound. I
admit to being frustrated -- not so much about this particular case, but
the general situation of the very mixed levels of WMF staff responsiveness
to requests for information.

Pine
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [discovery] Interactive Team putting work on pause

2017-01-25 Thread Kelly Battles
Anna thank you so much for handling all of this.
You do a great job and I am very appreciative of that...

> On Jan 25, 2017, at 3:53 PM, Anna Stillwell  wrote:
> 
> You make substantive points, Tim. Thank you.
> 
> "An employee should not experience their time off as a period where his
> [her/they] work load is just temporarily buffered until his [her/they]
> return, but where colleagues will step in and take care of business."
> 
> I take this point seriously and don't wish you to think otherwise. In
> theory, I absolutely agree. In practice, sometimes we all face constraints.
> There are roughly 300 of us (order of magnitude). Every now and then, there
> are not enough of us to go around on everything on a timeline that meets
> the legitimate need that you present here. We'll continue to work on this.
> But, to clarify, no one ever said it was a "useful practice" nor did anyone
> suggest that it was generalized across the org.
> 
> What I was wondering about in my previous email and now reiterating in this
> one too, are people willing to grant their request: a bit of time and allow
> for one person to return to work?
> 
> Does that seem like a way to move forward?
> 
> Warmly,
> /a
> 
> On Wed, Jan 25, 2017 at 2:50 PM, Tim Landscheidt 
> wrote:
> 
>> Anna Stillwell  wrote:
>> 
>>> […]
>> 
>>> I also hear that the pause on the interactive work is temporary. I’ve
>> heard
>>> them request time. I am comfortable granting that request, but no one is
>>> required to agree with me. They’ve also said that the person with the
>> most
>>> information is on vacation. As someone who has seen employees go through
>>> considerable stress in the last years, the entire executive team is
>> working
>>> to establish some cultural standards around supporting vacations. We want
>>> people here to feel comfortable taking proper vacations and sometimes
>> that
>>> can even need to happen in a crisis. People often plan their vacations
>> well
>>> in advance and may not know that something tricky will come up. Just so
>> you
>>> understand one bias I bring to this conversation.
>> 
>>> […]
>> 
>> I concur with DJ in his initial mail that this is not a use-
>> ful practice, and I doubt very much that it relieves employ-
>> ees' stress.  It conveys the organizational expectation that
>> employees are SPOFs without any backup.  An employee should
>> not experience their time off as a period where his work
>> load is just temporarily buffered until his return, but
>> where colleagues will step in and take care of business.
>> Especially such a major decision like "pausing" a team
>> should not depend on the inner thoughts of one employee, but
>> be backed and explainable by others.
>> 
>> Tim
>> 
>> 
>> ___
>> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
>> wiki/Mailing_lists/Guidelines
>> New messages to: Wikimedia-l@lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> 
>> 
> 
> 
> 
> -- 
> "If you have knowledge, let others light their candles in it." - Margaret
> Fuller
> 
> Anna Stillwell
> Director of Culture
> Wikimedia Foundation
> 415.806.1536
> *www.wikimediafoundation.org *
> ___
> Wikimedia-l mailing list, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
> 


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Anna Stillwell
On Wed, Jan 25, 2017 at 4:53 PM, Pete Forsyth  wrote:

> Anna,
>

Pete,

>
> Your points are valid and well taken. If I may summarize what I think I
> heard, it's basically: "Getting things right can be hard, and if full
> preparations weren't made ahead of time, thorough answers may not be
> readily available. Be compassionate/patient." Is that about right?


I appreciate that you are trying to understand what I mean. Thanks.

No, I didn’t say getting things right can be hard. I said, “This
communication thing is hard, especially when people are involved. Sometimes
there are laws that constrain what we say. Sometimes we don’t know whether
we are right yet and we need a further unpacking of the facts. The truth is
that there can be a whole host of reasons for partial communication that
aren’t related to competence or the intent to deceive.”

As for the preparations, it seems that a lot of assumptions are being made.
As for thorough answers, some might already be known and others known once
more planning is completed. However, it could be that the explanations you
want are not legal to share. There are many issues where employment law and
worker protections are crystal clear, as they should be.

As for compassion, I don’t require it. That seems like extra to me. I
usually prefer just paying attention, but that’s my personal choice.

The team asked for some time. I wondered if that would be a reasonable
request to grant them.

If so, I agree in principle and in spirit, but I think the point is in
> tension with
> another one:
>
> Community and public enthusiasm for software can be a rare and important
> thing. The conditions that make it grow, shrink, or sustain are complex,
> and largely beyond the influence of a handful of mailing list participants.
> The recent outputs of the Interactive Team have generated enthusiasm in a
> number of venues, and many on this list (both volunteers and staff) would
> like to see it grow or sustain, and perhaps throw a little weight behind an
> effort to make it grow or sustain.
>

Good points. I mean that. Glad to hear of these recent outputs generate
excitement. I’m personally also getting quite excited about ORES
 and
what’s going on with the Community Tech Wish List, Labs, and New Readers.
But I also get that you want to be clear: you'd like to see the interactive
team’s work grow or sustain. Makes sense.

The only thing I heard is that the team said that they needed to pause,
have a bit of time, and get back to everybody. “The team's aim during this
period is to get its work to a stable and maintainable state.”

>
> But that enthusiasm has a half-life. What is possible today may not be
> possible next week or next month. The zeitgeist may have evolved or moved
> on by then.
>

I'm not in disagreement with your main point about enthusiasm for software.
I think it's a very good one. Enthusiasm with a half life of a week,
however, sounds more like a passing crush. Nevertheless, your point still
stands.

>
> -Pete
> --
> [[User:Peteforsyth]]
>

/a
[[User:Annaproject]]

>
> On Wed, Jan 25, 2017 at 3:53 PM, Anna Stillwell 
> wrote:
>
> > You make substantive points, Tim. Thank you.
> >
> > "An employee should not experience their time off as a period where his
> > [her/they] work load is just temporarily buffered until his [her/they]
> > return, but where colleagues will step in and take care of business."
> >
> > I take this point seriously and don't wish you to think otherwise. In
> > theory, I absolutely agree. In practice, sometimes we all face
> constraints.
> > There are roughly 300 of us (order of magnitude). Every now and then,
> there
> > are not enough of us to go around on everything on a timeline that meets
> > the legitimate need that you present here. We'll continue to work on
> this.
> > But, to clarify, no one ever said it was a "useful practice" nor did
> anyone
> > suggest that it was generalized across the org.
> >
> > What I was wondering about in my previous email and now reiterating in
> this
> > one too, are people willing to grant their request: a bit of time and
> allow
> > for one person to return to work?
> >
> > Does that seem like a way to move forward?
> >
> > Warmly,
> > /a
> >
> > On Wed, Jan 25, 2017 at 2:50 PM, Tim Landscheidt  >
> > wrote:
> >
> > > Anna Stillwell  wrote:
> > >
> > > > […]
> > >
> > > > I also hear that the pause on the interactive work is temporary. I’ve
> > > heard
> > > > them request time. I am comfortable granting that request, but no one
> > is
> > > > required to agree with me. They’ve also said that the person with the
> > > most
> > > > information is on vacation. As someone who has seen employees go
> > through
> > > > considerable stress in the last years, the entire executive team is
> > > working
> > > > to establish some cultural standards 

Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Chris Koerner
Today marks my 1 year anniversary with the WMF. What a ride it's been!

A little clarification, or a timeline if you will.

Work on Interactive was led by very energetic and talented technical folks
for a good chunk of time with out a lot structure around the work. Then,
about a quarter ago, the team tried to start with more planning - a
roadmap, team roles, checklists for deployment - the usual stuff. It didn't
go well. The structure was too burdensome for some team members and lacking
for others. It caused a bit of stress to all members of the team, myself
included. But, to be good stewards of our resources we need some structure.

Lacking that structure it was decided to put a pause on things, rethink the
approach, and figure out how this all fits into planning and strategy for
the comping months/years. In the middle of this was the holiday, dev summit
and WMF all-hands (a solid week away from the office for the WMF), then
Yuri's departure, and Katie's scheduled (and deserved) vacation. Looking
back at it, a mess of bad timing.

So, Dan posted the message on discovery-l. I can't speak for him, but my
interpretation was, "Hey, just a head's up. We're going to pause things
while we work some stuff out and we'll let you know more in the future". An
honest attempt to do what so many of us ask for - quick communication in
the open. Personal note, I really didn't expect so many people would
care/notice! I'm happy to see that I was wrong.

It's hard to talk about these things. It's a sign of vulnerability to do so
and this information puts you at risk for criticism and embarrassment
(deserved or otherwise!). We're professionals, we never make mistakes,
right? Nope. We do, and it's hard to talk about. It's also hard with
professional and legal reasons when talking about individual staff. Heck,
even writing this reply I'm worried I'm going to say something wrong. :)

Now a few of the folks in Discovery are coming up with a plan, to be
discussed with our director upon their return from vacation. I personally
believe it would be wrong to make a decision without their involvement. I,
like many of you, personally hope we figure out a good way to keep the work
the interactive team has done moving forward. Once we have a plan, we'll
let you all know.

At this point I feel like I'm repeating what others have already said. :) I
don't expect this will put all minds at ease, but I too ask for your
patience and assume good faith.

I’ve always respected Derk-Jan's perspective and thoughts in the community.
I appreciate his concerns and I hope he continues bring them forth.


Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Pete Forsyth
Anna,

Your points are valid and well taken. If I may summarize what I think I
heard, it's basically: "Getting things right can be hard, and if full
preparations weren't made ahead of time, thorough answers may not be
readily available. Be compassionate/patient." Is that about right? If so, I
agree in principle and in spirit, but I think the point is in tension with
another one:

Community and public enthusiasm for software can be a rare and important
thing. The conditions that make it grow, shrink, or sustain are complex,
and largely beyond the influence of a handful of mailing list participants.
The recent outputs of the Interactive Team have generated enthusiasm in a
number of venues, and many on this list (both volunteers and staff) would
like to see it grow or sustain, and perhaps throw a little weight behind an
effort to make it grow or sustain.

But that enthusiasm has a half-life. What is possible today may not be
possible next week or next month. The zeitgeist may have evolved or moved
on by then.

-Pete
--
[[User:Peteforsyth]]

On Wed, Jan 25, 2017 at 3:53 PM, Anna Stillwell 
wrote:

> You make substantive points, Tim. Thank you.
>
> "An employee should not experience their time off as a period where his
> [her/they] work load is just temporarily buffered until his [her/they]
> return, but where colleagues will step in and take care of business."
>
> I take this point seriously and don't wish you to think otherwise. In
> theory, I absolutely agree. In practice, sometimes we all face constraints.
> There are roughly 300 of us (order of magnitude). Every now and then, there
> are not enough of us to go around on everything on a timeline that meets
> the legitimate need that you present here. We'll continue to work on this.
> But, to clarify, no one ever said it was a "useful practice" nor did anyone
> suggest that it was generalized across the org.
>
> What I was wondering about in my previous email and now reiterating in this
> one too, are people willing to grant their request: a bit of time and allow
> for one person to return to work?
>
> Does that seem like a way to move forward?
>
> Warmly,
> /a
>
> On Wed, Jan 25, 2017 at 2:50 PM, Tim Landscheidt 
> wrote:
>
> > Anna Stillwell  wrote:
> >
> > > […]
> >
> > > I also hear that the pause on the interactive work is temporary. I’ve
> > heard
> > > them request time. I am comfortable granting that request, but no one
> is
> > > required to agree with me. They’ve also said that the person with the
> > most
> > > information is on vacation. As someone who has seen employees go
> through
> > > considerable stress in the last years, the entire executive team is
> > working
> > > to establish some cultural standards around supporting vacations. We
> want
> > > people here to feel comfortable taking proper vacations and sometimes
> > that
> > > can even need to happen in a crisis. People often plan their vacations
> > well
> > > in advance and may not know that something tricky will come up. Just so
> > you
> > > understand one bias I bring to this conversation.
> >
> > > […]
> >
> > I concur with DJ in his initial mail that this is not a use-
> > ful practice, and I doubt very much that it relieves employ-
> > ees' stress.  It conveys the organizational expectation that
> > employees are SPOFs without any backup.  An employee should
> > not experience their time off as a period where his work
> > load is just temporarily buffered until his return, but
> > where colleagues will step in and take care of business.
> > Especially such a major decision like "pausing" a team
> > should not depend on the inner thoughts of one employee, but
> > be backed and explainable by others.
> >
> > Tim
> >
> >
> > ___
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines
> > New messages to: Wikimedia-l@lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > 
> >
>
>
>
> --
> "If you have knowledge, let others light their candles in it." - Margaret
> Fuller
>
> Anna Stillwell
> Director of Culture
> Wikimedia Foundation
> 415.806.1536
> *www.wikimediafoundation.org *
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: 

[Wikimedia-l] Research on ways to reduce minority/gender gap in Wikipedia

2017-01-25 Thread Leila Zia
Hi all,

From time to time, we have a chance in WMF Research to start a research
collaboration with researchers in academia/industry. In this case, we may
have an opportunity to form a research collaboration to spend some of our
attention on minority/gender gap issues on Wikipedia [1].

There is a specific proposal [2] that I would like to hear if you and/or
your community are interested to work with us on. As you will see once you
read the proposal, the general idea of the intervention suggested will
require at least one community, likely more depending on the size of the
community, being willing to work with us and give it a try. Individual
contributors, chapters, affiliates, and user groups are all welcome, as I
understand the gender/minority gap is a topic that many of you are
interested in.

Please leave comments on the discussion page of the proposal if you would
like to get more involved or if you have questions/comments.

Thank you! :)

Best,
Leila

[1] The current proposal is for Wikipedia. However, this does not need to
remain a research project on Wikipedia. For example, it would be invaluable
to learn if there are differences in projects in terms of how their
volunteer projects respond to interventions with the aim of reducing gender
gap, for example. So, if your project is not Wikipedia, you're still
welcome to get in touch with me.

[2]
https://meta.wikimedia.org/wiki/Research:Voice_and_exit_in_a_voluntary_work_environment


--
Leila Zia
Senior Research Scientist
Wikimedia Foundation
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread James Heilman
Agree with Tim, one would image that a fair bit of thought would have gone
into a decision such as this. That it would have occurred over multiple
meetings with substantial input from various parts of the organization. I
think it is reasonable to give the WMF some time to comment on this further.

Yuri Astrakhan is still listed as "Interactive Tech Team Lead"
https://www.mediawiki.org/wiki/User:Yurik Further clarification around that
including comments from him would be useful. I know from my meetings with
Yuri over the years he is very dedicated to the work of developing tools
that help Wiki(m)pedia build rich content.

J

On Wed, Jan 25, 2017 at 2:50 PM, Tim Landscheidt 
wrote:

> Anna Stillwell  wrote:
>
> > […]
>
> > I also hear that the pause on the interactive work is temporary. I’ve
> heard
> > them request time. I am comfortable granting that request, but no one is
> > required to agree with me. They’ve also said that the person with the
> most
> > information is on vacation. As someone who has seen employees go through
> > considerable stress in the last years, the entire executive team is
> working
> > to establish some cultural standards around supporting vacations. We want
> > people here to feel comfortable taking proper vacations and sometimes
> that
> > can even need to happen in a crisis. People often plan their vacations
> well
> > in advance and may not know that something tricky will come up. Just so
> you
> > understand one bias I bring to this conversation.
>
> > […]
>
> I concur with DJ in his initial mail that this is not a use-
> ful practice, and I doubt very much that it relieves employ-
> ees' stress.  It conveys the organizational expectation that
> employees are SPOFs without any backup.  An employee should
> not experience their time off as a period where his work
> load is just temporarily buffered until his return, but
> where colleagues will step in and take care of business.
> Especially such a major decision like "pausing" a team
> should not depend on the inner thoughts of one employee, but
> be backed and explainable by others.
>
> Tim
>
>
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>



-- 
James Heilman
MD, CCFP-EM, Wikipedian

The Wikipedia Open Textbook of Medicine
www.opentextbookofmedicine.com
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Anna Stillwell
You make substantive points, Tim. Thank you.

"An employee should not experience their time off as a period where his
[her/they] work load is just temporarily buffered until his [her/they]
return, but where colleagues will step in and take care of business."

I take this point seriously and don't wish you to think otherwise. In
theory, I absolutely agree. In practice, sometimes we all face constraints.
There are roughly 300 of us (order of magnitude). Every now and then, there
are not enough of us to go around on everything on a timeline that meets
the legitimate need that you present here. We'll continue to work on this.
But, to clarify, no one ever said it was a "useful practice" nor did anyone
suggest that it was generalized across the org.

What I was wondering about in my previous email and now reiterating in this
one too, are people willing to grant their request: a bit of time and allow
for one person to return to work?

Does that seem like a way to move forward?

Warmly,
/a

On Wed, Jan 25, 2017 at 2:50 PM, Tim Landscheidt 
wrote:

> Anna Stillwell  wrote:
>
> > […]
>
> > I also hear that the pause on the interactive work is temporary. I’ve
> heard
> > them request time. I am comfortable granting that request, but no one is
> > required to agree with me. They’ve also said that the person with the
> most
> > information is on vacation. As someone who has seen employees go through
> > considerable stress in the last years, the entire executive team is
> working
> > to establish some cultural standards around supporting vacations. We want
> > people here to feel comfortable taking proper vacations and sometimes
> that
> > can even need to happen in a crisis. People often plan their vacations
> well
> > in advance and may not know that something tricky will come up. Just so
> you
> > understand one bias I bring to this conversation.
>
> > […]
>
> I concur with DJ in his initial mail that this is not a use-
> ful practice, and I doubt very much that it relieves employ-
> ees' stress.  It conveys the organizational expectation that
> employees are SPOFs without any backup.  An employee should
> not experience their time off as a period where his work
> load is just temporarily buffered until his return, but
> where colleagues will step in and take care of business.
> Especially such a major decision like "pausing" a team
> should not depend on the inner thoughts of one employee, but
> be backed and explainable by others.
>
> Tim
>
>
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 
>



-- 
"If you have knowledge, let others light their candles in it." - Margaret
Fuller

Anna Stillwell
Director of Culture
Wikimedia Foundation
415.806.1536
*www.wikimediafoundation.org *
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Tim Landscheidt
Anna Stillwell  wrote:

> […]

> I also hear that the pause on the interactive work is temporary. I’ve heard
> them request time. I am comfortable granting that request, but no one is
> required to agree with me. They’ve also said that the person with the most
> information is on vacation. As someone who has seen employees go through
> considerable stress in the last years, the entire executive team is working
> to establish some cultural standards around supporting vacations. We want
> people here to feel comfortable taking proper vacations and sometimes that
> can even need to happen in a crisis. People often plan their vacations well
> in advance and may not know that something tricky will come up. Just so you
> understand one bias I bring to this conversation.

> […]

I concur with DJ in his initial mail that this is not a use-
ful practice, and I doubt very much that it relieves employ-
ees' stress.  It conveys the organizational expectation that
employees are SPOFs without any backup.  An employee should
not experience their time off as a period where his work
load is just temporarily buffered until his return, but
where colleagues will step in and take care of business.
Especially such a major decision like "pausing" a team
should not depend on the inner thoughts of one employee, but
be backed and explainable by others.

Tim


___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Lane Rasberry
Hello,

I have just been informed that Yuri is no longer with the WMF. I was not
aware. I think he might have left within the past 10 days, or perhaps I am
just way out of touch.

Whatever the case - that is all the more reason to seize the moment!
Brilliant people come and go in the wiki community, and when they are gone,
it becomes more difficult to access the institutional knowledge they had.
Catch people when they are presenting!

Yuri is a Wikipedian to the core and I expect him to be around as a
volunteer, but still - I wish it were easier for more people to present
their stories more often in more attractive formats, whether video,
interviews, or anything else that has a human element of reporting in it.

yours,



On Wed, Jan 25, 2017 at 1:39 PM, Lane Rasberry 
wrote:

> Hello,
>
> I do not know the situation with the Interactive Team but among other
> things, there is a wiki community request for better communication about
> projects. I would like to share something positive that already happens,
> and which is an opportunity for better communication going forward.
>
> I happen to live in New York City, and one of the developers on this team
> happens to live here also.
>
> Yuri Astrakhan
> 
>
> In NYC in the last year we have 1-2 administrative meetups a month for
> people to talk about coordinating Wikimedia projects. Yuri has presented at
> several of these local meetups to 200+ people total in the past few months.
> He is a great speaker who pleases audiences of developers, and audiences of
> general Wikipedians, and audiences of people who come to Wikipedia meetups
> without ever having edited any wiki before. Among others, he works on the
> projects mentioned in this email thread -
>
> 
> 
> 
>
> I cannot speak to the entire challenge of improving communication among
> WMF developers, the regular Wiki community like subscribers to this list,
> people who request better on-wiki documentation, and the general public,
> but I can say that I have felt that there was some loss when someone like
> Yuri is so personable, involved, and talented as a speaker and yet has
> limited opportunity to be heard. He is great in person, and when I hear
> him, I wish his presentations could be recorded and shared. Here is one
> attempt that we in NYC made to record him on Wikipedia Day, 15 January.
>  Jan_15_2017_-_04_Multimedia_-_Tech_Panel.ogg>
>
> If the presentations which people like Yuri already make were recorded and
> better circulated, then perhaps some problems related to lack of
> communication would be lessened.
>
> I think there is some demand in the wiki community for more access to time
> in front of a camera to give presentations. NYC has the privilege of
> getting to hear a lot of great speakers in person. Globally at local
> meetups everywhere and even at Wikimania events, many talented people put a
> lot of labor and insight into the presentations they do. Usually those
> presentations do not persist beyond the live performance. When the
> presentation is video recorded, it usually has low quality audio and video
> that is not of the standard that many people expect from YouTube and other
> similar sites, and I think that the challenge of producing good video is
> more of a barrier to communication than lack of great presenters with
> interesting things to say. Encouraging people to do video presentations
> might not be the solution to communication challenges, but when there is
> someone who puts the work into making a great in-person presentation, then
> I wish it were easier to record and share it. I have not been satisfied
> with most of the wiki-related recordings produced, except for the most
> professional ones made with professional equipment and editing. I wish that
> there could be more video support getting more interviews and updates from
> more people at wiki events around the world.
>
> I have been very pleased with the quality of in-person, in NYC
> presentations that Yuri has shared about maps and graphs. I think that he
> and others like him would use opportunities to be interviewed and better
> presented in wiki community media, and I think that the community wants
> better in-community media coverage. I feel grateful to have heard Yuri in
> my own city and the WMF should be glad to have someone who is a developer
> and such a great speaker.
>
> yours,
>
>
> On Wed, Jan 25, 2017 at 11:11 AM, Anna Stillwell  > wrote:
>
>>  Hey DJ
>>
>> These seem like reasonable concerns and I am glad you and others are
>> raising them. I hope you continue to do so. We’re all getting better at
>> working together and it is clear that the foundation has made mistakes in
>> the past, so it is right and good to hold 

Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Lane Rasberry
Hello,

I do not know the situation with the Interactive Team but among other
things, there is a wiki community request for better communication about
projects. I would like to share something positive that already happens,
and which is an opportunity for better communication going forward.

I happen to live in New York City, and one of the developers on this team
happens to live here also.

Yuri Astrakhan


In NYC in the last year we have 1-2 administrative meetups a month for
people to talk about coordinating Wikimedia projects. Yuri has presented at
several of these local meetups to 200+ people total in the past few months.
He is a great speaker who pleases audiences of developers, and audiences of
general Wikipedians, and audiences of people who come to Wikipedia meetups
without ever having edited any wiki before. Among others, he works on the
projects mentioned in this email thread -





I cannot speak to the entire challenge of improving communication among WMF
developers, the regular Wiki community like subscribers to this list,
people who request better on-wiki documentation, and the general public,
but I can say that I have felt that there was some loss when someone like
Yuri is so personable, involved, and talented as a speaker and yet has
limited opportunity to be heard. He is great in person, and when I hear
him, I wish his presentations could be recorded and shared. Here is one
attempt that we in NYC made to record him on Wikipedia Day, 15 January.


If the presentations which people like Yuri already make were recorded and
better circulated, then perhaps some problems related to lack of
communication would be lessened.

I think there is some demand in the wiki community for more access to time
in front of a camera to give presentations. NYC has the privilege of
getting to hear a lot of great speakers in person. Globally at local
meetups everywhere and even at Wikimania events, many talented people put a
lot of labor and insight into the presentations they do. Usually those
presentations do not persist beyond the live performance. When the
presentation is video recorded, it usually has low quality audio and video
that is not of the standard that many people expect from YouTube and other
similar sites, and I think that the challenge of producing good video is
more of a barrier to communication than lack of great presenters with
interesting things to say. Encouraging people to do video presentations
might not be the solution to communication challenges, but when there is
someone who puts the work into making a great in-person presentation, then
I wish it were easier to record and share it. I have not been satisfied
with most of the wiki-related recordings produced, except for the most
professional ones made with professional equipment and editing. I wish that
there could be more video support getting more interviews and updates from
more people at wiki events around the world.

I have been very pleased with the quality of in-person, in NYC
presentations that Yuri has shared about maps and graphs. I think that he
and others like him would use opportunities to be interviewed and better
presented in wiki community media, and I think that the community wants
better in-community media coverage. I feel grateful to have heard Yuri in
my own city and the WMF should be glad to have someone who is a developer
and such a great speaker.

yours,


On Wed, Jan 25, 2017 at 11:11 AM, Anna Stillwell 
wrote:

>  Hey DJ
>
> These seem like reasonable concerns and I am glad you and others are
> raising them. I hope you continue to do so. We’re all getting better at
> working together and it is clear that the foundation has made mistakes in
> the past, so it is right and good to hold us accountable. I mean that
> sincerely.
>
> I’ve heard a few preliminary answers offered. As I see it, it seems like
> rather than waiting to get everything perfect (and likely with a bit of
> spin), these people are trying to communicate what they know when they know
> it. I support them for doing so and hope that all of us in the foundation
> continue in this direction. But there is a challenge to this approach also…
> when you share early, you might not yet have all of the answers. Sometimes,
> but not always, mutual disclosure may require some patience while we all
> muddle through and arrive at shared understanding.
>
> I also hear that the pause on the interactive work is temporary. I’ve heard
> them request time. I am comfortable granting that request, but no one is
> required to agree with me. They’ve also said that the person with the most
> information is on vacation. As someone who has seen employees go through
> 

Re: [Wikimedia-l] Fwd: [discovery] Interactive Team putting work on pause

2017-01-25 Thread Anna Stillwell
 Hey DJ

These seem like reasonable concerns and I am glad you and others are
raising them. I hope you continue to do so. We’re all getting better at
working together and it is clear that the foundation has made mistakes in
the past, so it is right and good to hold us accountable. I mean that
sincerely.

I’ve heard a few preliminary answers offered. As I see it, it seems like
rather than waiting to get everything perfect (and likely with a bit of
spin), these people are trying to communicate what they know when they know
it. I support them for doing so and hope that all of us in the foundation
continue in this direction. But there is a challenge to this approach also…
when you share early, you might not yet have all of the answers. Sometimes,
but not always, mutual disclosure may require some patience while we all
muddle through and arrive at shared understanding.

I also hear that the pause on the interactive work is temporary. I’ve heard
them request time. I am comfortable granting that request, but no one is
required to agree with me. They’ve also said that the person with the most
information is on vacation. As someone who has seen employees go through
considerable stress in the last years, the entire executive team is working
to establish some cultural standards around supporting vacations. We want
people here to feel comfortable taking proper vacations and sometimes that
can even need to happen in a crisis. People often plan their vacations well
in advance and may not know that something tricky will come up. Just so you
understand one bias I bring to this conversation.

Last, but not least, it’s not always as easy as it seems. This
communication thing is hard, especially when people are involved. Sometimes
there are laws that constrain what we say. Sometimes we don’t know whether
we are right yet and we need a further unpacking of the facts. The truth is
that there can be a whole host of reasons for partial communication that
aren’t related to competence or the intent to deceive.

I’m wondering if we can grant their two requests, can we wait for a return
from vacation and a clarification of some kind will follow?

Next time I see you, I hope we can have a beer and argue about something
something.

Warmly,
/a

On Tue, Jan 24, 2017 at 2:26 PM, Derk-Jan Hartman <
d.j.hartman+wmf...@gmail.com> wrote:

> > Hi all,
> > The Interactive Team in Discovery is in the process of putting its work
> on
> > pause. The team's aim during this period is to get its work to a stable
> and
> > maintainable state.
> > Currently, work on new features is on hold. It is not yet known what the
> > timeline is for this transition to a paused state, or whether there will
> be
> > further deployments of features that have already been completed. I will
> > update this list when there is more information.
> > Thanks,
> > Dan
> > --
> > Dan Garry
> > Lead Product Manager, Discovery
> > Wikimedia Foundation
>
>
> So it seems all work on Maps, Graphs and other interactive features is
> going to be halted pretty soon. I was directed at this notification after a
> Maps ticket mentioned:
>
> With the team winding down
>
>
> To which I asked:
>
> > Why is the team winding down ?
>
>
> To which Dan Garry responded:
>
> > There were expectations that were set regarding things such as team
> goals,
> > working collaboratively with stakeholders, and advance notice to
> > communities, that were repeatedly not met by the team.
>
>
> And he pointed me to this discovery mailing list announcement, which well
> isn't really an explanation as much as a statement on the effect that
> 'winding down' will have.
>
> My interpretation of the information up to here was: "we are dissolving
> this team because it didn't perform and by posting to discovery mailing
> list we did the minimal effort required to notify people, but lets hope
> nobody notices what the notification really means"
> At the same time Dan's words are a rather hefty review on the performance
> of a team, which I'm not used to seeing from WMF. Refreshing, but unusual.
>
> This annoys me and I answer:
>
> > 1: I'd expect this to be announced on wikimedia-l, if we start a team we
> > always seem more than anxious to do so.
> > 2: I'd like some details. I thought we had left behind all the "let's try
> > and hide this and hope no one notices it"-shit in 2016.
> > 3: Thank you team ! You did some great work, and it was more productive
> > and groundbreaking than many other teams have been able to do in 5 years.
>
>
> A bit hyperbolic on all fronts, I admit.
>
> To which Dan responds with:
>
> > I am not the person who made this decision. I do not know all of the
> > reasons it was made. The person who made the decision is on vacation for
> > the next few weeks. I am trying my best to communicate as much as I can
> in
> > her absence, which is why I made a public announcement of all that I know
> > now rather than waiting weeks for my manager to return. I am afraid that
> > some patience 

Re: [Wikimedia-l] Wikimedia Foundation Board Recruitment Kick-Off

2017-01-25 Thread Nataliia Tymkiv
Hello!

Thank you for the question, Lodewijk.

The Board Elections Committee kickoff meeting

is planned for January 31st, and I hope the discussion

about how the two processes can support each other

would be on the table as soon as the Committee will

determine its own timeline for the process.

Personally I would like us working together:

the BGC and the Board and the ED have identified some

expertise we lack, and the development of these three profiles

is the result from those discussions. A possible role of the

Elections Committee was discussed before, but the vision on

how exactly was not finalized, so it indeed ended up

not being possible at this point and with this timeline.

Ideally I would see us working on the whole picture:

what we need at all, and then filling the positions we need

through whatever selection processes there are.

If we couldn't find somebody with the expertise we needed

during the appointed seats search, we can continue looking for them

during the community selection, etc.

But for this to happen the timelines should not be so close.

Even though we have three profiles developed for two seats,

the profile we were unable to find via appointed seats search

will be known too late for the Elections Committee

to take it into consideration. The fourth profile

(discussed, but not prioritized for this appointed seats search)

was Technology Innovation. It would be nice to have it on the table

via the community selection process.

To be clear, as with all Trustee roles, this competency

is not someone who will get involved in the technical details

or day-to-day operations.

I think that a discussion involving the community about what more

the Board needs would be welcome before the selection process starts,

so we can concentrate on recruiting candidates with the competences

that we need to stand for election. But I do believe that it greatly
depends on how

the Committee will organize its work and the selection process.

Best regards,
antanana / Nataliia Tymkiv

*NOTICE: You may have received this message outside of your normal working
hours/days, as I usually can work more as a volunteer during weekend. You
should not feel obligated to answer it during your days off. Thank you in
advance!*


On Wed, Jan 25, 2017 at 1:23 AM, Lodewijk 
wrote:

> Hi Anna,
>
> Thanks for the quote. I read that in the email as well - but it doesn't
> answer the interaction between the two timelines though. It's mostly the
> interaction between the two processes I'm interested in at this point.
>
> The moment that the candidates join the board could be many months later
> than when the decision has been made. This actually was suggested as a best
> practice, if I recall correctly, for an effective transfer of knowledge to
> the incoming board members before they take up their duties.
>
> I hope the board took this interaction between processes into account while
> planning, but I suspect it at least didn't end up being possible. But maybe
> Nataliia sees other ways how the timelines can support each other. I hope
> they are not being developed in vacuum.
>
> Best regards,
> Lodewijk
>
> 2017-01-24 19:09 GMT+01:00 Anna Stillwell :
>
> > Hello Lodewijk,
> >
> > Good to hear from you.
> >
> > In Nataliia's original email she wrote:
> >
> > The Wikimedia Foundation Board of Trustees currently has two vacant
> > appointed seats. We also have a vacant community-selected seat, but this
> > seat will be filled through the community selection process. *The
> Election*
> > *Committee, who runs the election process for community-selected seats,
> > will*
> > *provide further information about the process and timeline at a later
> > date.*
> > We hope to have all three candidates join the Board no later than
> Wikimania
> > in August.
> >
> > Hope that helps.
> > Warmly,
> > /a
> >
> > On Tue, Jan 24, 2017 at 1:35 AM, Lodewijk 
> > wrote:
> >
> > > Hi Nataliia,
> > >
> > > Thanks for the update. It's promising to see a closed timeline for the
> > > board recruitment.
> > >
> > > I am wondering though, when do you expect to wrap up the process for
> the
> > > appointed seats? There's always been a lot of talk that the community
> and
> > > affiliates don't take the needs of the board in certain areas into
> > account
> > > - and it would probably be good if the board could communicate back
> > before
> > > the election process starts what kind of expertise they're looking for.
> > >
> > > I guess that is not going to fly this time around, as you will be in
> the
> > > middle of a search for the expert seats? Any chance these timelines may
> > > support each other?
> > >
> > > Best,
> > > Lodewijk
> > >
> > > 2017-01-23 19:44 GMT+01:00 Nataliia Tymkiv :
> > >
> > > > Dear all,
> > > >
> > > > We would like to announce that we are officially beginning
> recruitment
> > > for
> > > > two open 

Re: [Wikimedia-l] Introducing the Wikimedia Resource Center

2017-01-25 Thread NC Hasive
Like it! Hope it helps all Wikimedian to know any kind of resourceful
information.

-Hasive
WMBD

On Tue, Jan 24, 2017 at 9:53 PM, Maria Cruz  wrote:

> Hi all,
>
> As we have stated in our annual plan [1], “currently, community members
> must search many pages and places to stay informed about Foundation
> activities and resources.” We have worked in the past two quarters to
> create a single point of entry. We call it the Wikimedia Resource Center,
> and its alpha version is now live on Meta Wikimedia:
> https://meta.wikimedia.org/wiki/Wikimedia_Resource_Center
>
> As the movement expands to include more affiliates and more programmatic
> activities every year, newer Wikimedians are faced with lack of experience
> in the movement and its various channels for requesting support. In order
> to expand Wikimedia communities’ efforts, we want to provide easy access to
> resources that support their very important work. The [[m:Wikimedia
> Resource Center]] is a hub designed in response to this issue: it is
> intended to evolve into a single point of entry for Wikimedians all over
> the world to the variety of resources and types of staff support they may
> need to develop new initiatives or also expand existing ones.
>
> This version of the Resource Center is only the beginning. For phase two of
> the project, we will enable volunteer Wikimedians to add resources
> developed by other individuals or organizations to the Wikimedia Resource
> Center, and in phase three, the Wikimedia Resource Center will include
> features to better connect Wikimedians to other Wikimedians that can
> support them.
>
> We want to hear what you think about this prototype and our plans for it!
> If you have comments about the Wikimedia Resource Center, you can submit
> your feedback publicly, on the Talk Page, or privately, via a survey hosted
> by a third party, that shouldn’t take you more than 4 minutes to complete.
> A feedback button is on the top right corner on every page of the hub.
>
> Looking forward to more collaborations!
>
> Best,
>
> María
>
>
> [1]
> https://meta.wikimedia.org/wiki/Wikimedia_Foundation_
> Annual_Plan/2016-2017/draft#Program_3:_Develop_capacity-
> building_tools_and_resources_for_core_Wikimedia_programs
>
> --
> María Cruz
> Communications and Outreach Project Manager, Community Engagement
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines
> New messages to: Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 




-- 
*Nurunnaby Chowdhury (Hasive) **:: **নুরুন্নবী চৌধুরী (হাছিব)*
User: Hasive  |
GSM/WhatsApp/Viber: +8801712754752
​
Administrator | Bengali Wikipedia 
Board Member | Wikimedia Bangladesh 
fb.com/Hasive  | @nhasive
 | www.nhasive.com
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,