Re: [Wikimedia-l] Community Engagement reorg - the official announcement

[Quim Gil]

On Tue, Feb 9, 2016 at 4:15 AM, Maggie Dennis  wrote:

> As some of you know, Community Engagement had a small realignment last
> quarter.





> Now that it’s further along, we thought it was a good time to
> formally share. :)
>

...


>Technical Collaboration (grouping Community Liaisons and Developer
>Relations), under Quim Gil, tasked with improving collaboration between
>software development teams, Wikimedia contributors, readers, and
> volunteer
>developers.


We welcome your feedback and participation in our projects and plans:

*  https://meta.wikimedia.org/wiki/Technical_Collaboration
* Quarterly goals:
https://meta.wikimedia.org/wiki/Technical_Collaboration/Goals
* Annual Plan: https://phabricator.wikimedia.org/T124420
* Strategy: https://meta.wikimedia.org/wiki/Technical_Collaboration/Strategy

In the day to day your points of contact keep being Community Liaisons
(content creators) and Developer Relations (developers).

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
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] Community Engagement reorg - the official announcement

[Edward Galvez]

On Thu, Feb 11, 2016 at 12:05 AM, Pine W  wrote:

> I've been stewing for awhile to sort out my thoughts about the search for a
> new department lead for CE. Since I might be busy on Friday, and the choice
> of the new department is likely a topic of broad public interest, I'll
> share some thoughts here:
>

Hi Pine,

Thanks for your comments and for searching your thoughts. It would be great
if we could also hear the stories about your work and how this position
might influence your organization's or your personal daily work in the
movement. We need to hear how the list you bring up is affecting your work
in Cascadia.

A few other questions that might help (For everyone):

 Where are your group(s) now in their work and what does it need from
the WMF in a Community Engagement director?

 What are your organizations/project's highest priorities right now and
how does that relate to a new director for the department?

 What values do you expect a Community Engagement Director to have as
it relates to your _own_ work?

I am hoping these questions are helpful to everyone.

Also for everyone - reach out directly with other people, both within the
organization and with others to listen to what they need as well, or
perhaps invite them into the broader conversation. I need to do this as
well.

Thanks,
Edward
___
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] Community Engagement reorg - the official announcement

[Pine W]

I've been stewing for awhile to sort out my thoughts about the search for a
new department lead for CE. Since I might be busy on Friday, and the choice
of the new department is likely a topic of broad public interest, I'll
share some thoughts here:

1. This is a highly public community facing role. Whoever gets the job
should be comfortable with transparency by default, and with the need to
maintain privacy about some situations.
2. The department lead needs to be someone who can get up to speed with our
incredibly complex community *quickly*. For this reason, I would strongly
suggest considering an internal hire.
3. This can be is a highly political and emotional role.
4. Whoever gets the job should have demonstrated good management skills in
a public-facing role and with development and supervision of a comparable
budget, including supervision of grants budgets and staff, and preferably
staff with comparable roles to Technical Collaboration and Support &
Safety.
5. Familiarity with the many legal aspects of the department would be
helpful, such as with contracts, online safe environments, and employment
law.
6. The leader should be comfortable with processes and software tools of
similar kind and complexity to the tools that are used by WMF CE, such as
OTRS, Phabricator, and the various kinds of financial and performance
analysis software and tools that are used by the department.
7. Familiarity with hiring and supervision of international and remote
staff would be valuable.
8. Language proficiency is of great value in this role. I would suggest
that the leader should have EN-5 or native proficiency in English, and at
least basic conversational proficiency in one additional language that is
commonly used in the Wikimedia movement.
9. Experience with managing community-facing technology projects would be
valuable.
10. Experience with conducting business in environments outside of the US
and Canada world would be valuable, including management of international
contracts and maintenance of relationships with international business
partners.

I feel the need to mention an additional issue which I think should be
addressed and could negatively impact recruiting for this position, which
is the current situation with the governance of the WMF. The amount of
staff turnover and the results of the staff survey are likely to have
negative impacts on recruiting among candidates who are well qualified for
this position and are looking for a job in which they can be successful.
Also, I feel that the opacity, decisions, and errors of the WMF Board in
the past few months cast a long shadow over the senior director of
community. Finally, the continued reports that I am hearing about the
relationship between the WMF ED and the WMF staff are also significant
causes of concern. I would suggest that before looking for external
candidates who are likely to do due diligence on WMF before accepting this
position, that WMF should remedy some of these matters of concern. I have
faith in Maggie to be a good temporary lead for the department while the
governance situation is addressed.

Writing in my personal capacity only,

Pine

On Mon, Feb 8, 2016 at 7:15 PM, Maggie Dennis  wrote:

> Hello, all.
>
> As some of you know, Community Engagement had a small realignment last
> quarter. Now that it’s further along, we thought it was a good time to
> formally share. :)
>
> So, welcome to the reformed Community Engagement!
>
> What’s the major change?
>
> We've restructured Community Engagement, to four primary groups:
>
>-
>
>Program Capacity and Learning (integrating Learning & Evaluation,
>Education, and Library), under Rosemary Rein, tasked with supporting
> community partnerships, programs and learning.
>-
>
>Resources, under Siko Bouterse, tasked with supporting community-led
>impact through grants and other resources.
>-
>
>Support & Safety (formerly known as Community Advocacy), under me
>(Maggie Dennis), tasked with helping improve trust, safety and
> collegiality
>within our projects as well as facilitating communication and
> understanding
>broadly between the WMF and contributors,
>-
>
>Technical Collaboration (grouping Community Liaisons and Developer
>Relations), under Quim Gil, tasked with improving collaboration between
>software development teams, Wikimedia contributors, readers, and
> volunteer
>developers.
>
> Four people within Community Engagement have changed which teams they
> report to: Floor and Jake (to Program, Capacity, and Learning), Haitham (to
> Support and Safety), and Sati (to Resources). This will more closely align
> their leadership and reporting structure with the work they’re doing.
> Rachel will also be stepping back from leadership of the Liaisons team and
> supporting Quim in annual plan and strategic work.
>
> Why did we do this?
>
> For most people outside of the department, this will have very little
> 

Re: [Wikimedia-l] Community Engagement reorg - the official announcement

[Gerard Meijssen]

Hoi,
Thank you for writing in your personal capacity so the other things need
not have any consideration. Thank you for a profile that reads American.

Thank you for continuing with the sniping at the WMF. What is your point or
is that personal? How do you help things move in the right direction? In my
opinion you show a lack of good faith, personally speaking, and why would
that not be seen as impacting your professional/other capacity?

But that is me personally.
Thanks,
   GerardM

On 11 February 2016 at 09:05, Pine W  wrote:

> I've been stewing for awhile to sort out my thoughts about the search for a
> new department lead for CE. Since I might be busy on Friday, and the choice
> of the new department is likely a topic of broad public interest, I'll
> share some thoughts here:
>
> 1. This is a highly public community facing role. Whoever gets the job
> should be comfortable with transparency by default, and with the need to
> maintain privacy about some situations.
> 2. The department lead needs to be someone who can get up to speed with our
> incredibly complex community *quickly*. For this reason, I would strongly
> suggest considering an internal hire.
> 3. This can be is a highly political and emotional role.
> 4. Whoever gets the job should have demonstrated good management skills in
> a public-facing role and with development and supervision of a comparable
> budget, including supervision of grants budgets and staff, and preferably
> staff with comparable roles to Technical Collaboration and Support &
> Safety.
> 5. Familiarity with the many legal aspects of the department would be
> helpful, such as with contracts, online safe environments, and employment
> law.
> 6. The leader should be comfortable with processes and software tools of
> similar kind and complexity to the tools that are used by WMF CE, such as
> OTRS, Phabricator, and the various kinds of financial and performance
> analysis software and tools that are used by the department.
> 7. Familiarity with hiring and supervision of international and remote
> staff would be valuable.
> 8. Language proficiency is of great value in this role. I would suggest
> that the leader should have EN-5 or native proficiency in English, and at
> least basic conversational proficiency in one additional language that is
> commonly used in the Wikimedia movement.
> 9. Experience with managing community-facing technology projects would be
> valuable.
> 10. Experience with conducting business in environments outside of the US
> and Canada world would be valuable, including management of international
> contracts and maintenance of relationships with international business
> partners.
>
> I feel the need to mention an additional issue which I think should be
> addressed and could negatively impact recruiting for this position, which
> is the current situation with the governance of the WMF. The amount of
> staff turnover and the results of the staff survey are likely to have
> negative impacts on recruiting among candidates who are well qualified for
> this position and are looking for a job in which they can be successful.
> Also, I feel that the opacity, decisions, and errors of the WMF Board in
> the past few months cast a long shadow over the senior director of
> community. Finally, the continued reports that I am hearing about the
> relationship between the WMF ED and the WMF staff are also significant
> causes of concern. I would suggest that before looking for external
> candidates who are likely to do due diligence on WMF before accepting this
> position, that WMF should remedy some of these matters of concern. I have
> faith in Maggie to be a good temporary lead for the department while the
> governance situation is addressed.
>
> Writing in my personal capacity only,
>
> Pine
>
> On Mon, Feb 8, 2016 at 7:15 PM, Maggie Dennis 
> wrote:
>
> > Hello, all.
> >
> > As some of you know, Community Engagement had a small realignment last
> > quarter. Now that it’s further along, we thought it was a good time to
> > formally share. :)
> >
> > So, welcome to the reformed Community Engagement!
> >
> > What’s the major change?
> >
> > We've restructured Community Engagement, to four primary groups:
> >
> >-
> >
> >Program Capacity and Learning (integrating Learning & Evaluation,
> >Education, and Library), under Rosemary Rein, tasked with supporting
> > community partnerships, programs and learning.
> >-
> >
> >Resources, under Siko Bouterse, tasked with supporting community-led
> >impact through grants and other resources.
> >-
> >
> >Support & Safety (formerly known as Community Advocacy), under me
> >(Maggie Dennis), tasked with helping improve trust, safety and
> > collegiality
> >within our projects as well as facilitating communication and
> > understanding
> >broadly between the WMF and contributors,
> >-
> >
> >Technical Collaboration (grouping 

Re: [Wikimedia-l] Community Engagement reorg - the official announcement

[Maria Cruz]

Hi all,
to follow up on Maggie's email, I wanted to share that Program Capacity and
Learning team is reaching out to community members to comment on our draft
roadmap [1]. In this coming year, we look forward to our shared learning
and support to leaders across the movement.

Importantly, we could use some help in defining what that year looks like!
Between now and February 19th, we are asking for your input in prioritizing
support to program leaders and affiliates through our newly integrated
Program Capacity and Learning Team. Our new team, in addition to supporting
 education programs, libraries, and learning and evaluation, will also
support GLAM and Affiliate Partnerships. We have been consulting with
different program and community leaders and have developed a few ideas for
which we would like your input [1].  Please share your views on our
criteria for resources as well as concepts for support. Your input will
help guide our 2016-2017 Annual Plan submission. We will host office hours
on IRC on Tuesday, February 16, at 8 am PST. Sign up to the event via
Google [2] or Facebook [3].

Hope to see many of you on Meta!

Best,


*María Cruz * \\  Communications and Outreach Coordinator, PC Team
\\ Wikimedia
Foundation, Inc.
mc...@wikimedia.org  |  :  @marianarra_ 
[1] https://meta.wikimedia.org/wiki/Program_Capacity_and_Learning
[2] https://plus.google.com/events/c2u2adh301qqtdp137glrl09qqk
[3] https://www.facebook.com/events/970720156351099/

On Mon, Feb 8, 2016 at 7:15 PM, Maggie Dennis  wrote:

> Hello, all.
>
> As some of you know, Community Engagement had a small realignment last
> quarter. Now that it’s further along, we thought it was a good time to
> formally share. :)
>
> So, welcome to the reformed Community Engagement!
>
> What’s the major change?
>
> We've restructured Community Engagement, to four primary groups:
>
>-
>
>Program Capacity and Learning (integrating Learning & Evaluation,
>Education, and Library), under Rosemary Rein, tasked with supporting
> community partnerships, programs and learning.
>-
>
>Resources, under Siko Bouterse, tasked with supporting community-led
>impact through grants and other resources.
>-
>
>Support & Safety (formerly known as Community Advocacy), under me
>(Maggie Dennis), tasked with helping improve trust, safety and
> collegiality
>within our projects as well as facilitating communication and
> understanding
>broadly between the WMF and contributors,
>-
>
>Technical Collaboration (grouping Community Liaisons and Developer
>Relations), under Quim Gil, tasked with improving collaboration between
>software development teams, Wikimedia contributors, readers, and
> volunteer
>developers.
>
> Four people within Community Engagement have changed which teams they
> report to: Floor and Jake (to Program, Capacity, and Learning), Haitham (to
> Support and Safety), and Sati (to Resources). This will more closely align
> their leadership and reporting structure with the work they’re doing.
> Rachel will also be stepping back from leadership of the Liaisons team and
> supporting Quim in annual plan and strategic work.
>
> Why did we do this?
>
> For most people outside of the department, this will have very little
> impact on your day-to-day relationships with Community Engagement, but
> we’re hoping for major impact within our department! The main goal of the
> reorganization was more responsive leadership, decision making and improved
> lines of communication within, into and out of the department, with a
> strong secondary goal of giving the affected teams more flexibility and
> clarity around their missions, so that they can adapt better to our
> evolving work. When we began this transformation last quarter, we expected
> that it would mean most teams (and especially the affected leaders) would
> be more engaged, receive more day-to-day mentorship, and that they'd be
> able to work more constructively with peers to better craft shared goals
> and projects. At the same time we hoped that the team executive would be
> able to put more into handling upcoming planning efforts like the strategic
> and annual plans. While we are still fine-tuning, this seems to be bearing
> out, and we hope that it will continue.
>
> Our ultimate goal, of course, is to figure out the best ways to serve our
> communities and our movement through better internal and external
> collaboration and through well-defined roles, responsibilities and
> processes that are clear and work well for everyone. While this is one step
> towards that goal, we are working on others through the strategic process
> and the upcoming Annual Plan and through other conversations with you.
>
> We are hosting an office hour on IRC on Friday February 12th at 1900 UTC to
> talk over the reorganization and also to discuss the qualities we should be
> looking for in a new department lead.[1] (As 

Re: [Wikimedia-l] Community Engagement reorg - the official announcement

[Leigh Thelmadatter]

Im curious to see how this might affect Wiki Learning Tec de Monterrey, as we 
are both an education program and an affiliate.


> Date: Wed, 10 Feb 2016 16:19:17 -0800
> From: mc...@wikimedia.org
> To: wikimedia-l@lists.wikimedia.org
> Subject: Re: [Wikimedia-l] Community Engagement reorg - the official  
> announcement
> 
> Hi all,
> to follow up on Maggie's email, I wanted to share that Program Capacity and
> Learning team is reaching out to community members to comment on our draft
> roadmap [1]. In this coming year, we look forward to our shared learning
> and support to leaders across the movement.
> 
> Importantly, we could use some help in defining what that year looks like!
> Between now and February 19th, we are asking for your input in prioritizing
> support to program leaders and affiliates through our newly integrated
> Program Capacity and Learning Team. Our new team, in addition to supporting
>  education programs, libraries, and learning and evaluation, will also
> support GLAM and Affiliate Partnerships. We have been consulting with
> different program and community leaders and have developed a few ideas for
> which we would like your input [1].  Please share your views on our
> criteria for resources as well as concepts for support. Your input will
> help guide our 2016-2017 Annual Plan submission. We will host office hours
> on IRC on Tuesday, February 16, at 8 am PST. Sign up to the event via
> Google [2] or Facebook [3].
> 
> Hope to see many of you on Meta!
> 
> Best,
> 
> 
> *María Cruz * \\  Communications and Outreach Coordinator, PC Team
> \\ Wikimedia
> Foundation, Inc.
> mc...@wikimedia.org  |  :  @marianarra_ <https://twitter.com/marianarra_>
> [1] https://meta.wikimedia.org/wiki/Program_Capacity_and_Learning
> [2] https://plus.google.com/events/c2u2adh301qqtdp137glrl09qqk
> [3] https://www.facebook.com/events/970720156351099/
> 
> On Mon, Feb 8, 2016 at 7:15 PM, Maggie Dennis <mden...@wikimedia.org> wrote:
> 
> > Hello, all.
> >
> > As some of you know, Community Engagement had a small realignment last
> > quarter. Now that it’s further along, we thought it was a good time to
> > formally share. :)
> >
> > So, welcome to the reformed Community Engagement!
> >
> > What’s the major change?
> >
> > We've restructured Community Engagement, to four primary groups:
> >
> >-
> >
> >Program Capacity and Learning (integrating Learning & Evaluation,
> >Education, and Library), under Rosemary Rein, tasked with supporting
> > community partnerships, programs and learning.
> >-
> >
> >Resources, under Siko Bouterse, tasked with supporting community-led
> >impact through grants and other resources.
> >-
> >
> >Support & Safety (formerly known as Community Advocacy), under me
> >(Maggie Dennis), tasked with helping improve trust, safety and
> > collegiality
> >within our projects as well as facilitating communication and
> > understanding
> >broadly between the WMF and contributors,
> >-
> >
> >Technical Collaboration (grouping Community Liaisons and Developer
> >Relations), under Quim Gil, tasked with improving collaboration between
> >software development teams, Wikimedia contributors, readers, and
> > volunteer
> >developers.
> >
> > Four people within Community Engagement have changed which teams they
> > report to: Floor and Jake (to Program, Capacity, and Learning), Haitham (to
> > Support and Safety), and Sati (to Resources). This will more closely align
> > their leadership and reporting structure with the work they’re doing.
> > Rachel will also be stepping back from leadership of the Liaisons team and
> > supporting Quim in annual plan and strategic work.
> >
> > Why did we do this?
> >
> > For most people outside of the department, this will have very little
> > impact on your day-to-day relationships with Community Engagement, but
> > we’re hoping for major impact within our department! The main goal of the
> > reorganization was more responsive leadership, decision making and improved
> > lines of communication within, into and out of the department, with a
> > strong secondary goal of giving the affected teams more flexibility and
> > clarity around their missions, so that they can adapt better to our
> > evolving work. When we began this transformation last quarter, we expected
> > that it would mean most teams (and especially the affected leaders) would
> > be more engaged, receive more day-to-day mentorship, and that they'd be
> >