Re: [Wikimedia-l] [Foundation-l] Single login - decision 2004

2015-04-21 Thread Ori Livneh
On Tue, Apr 21, 2015 at 11:34 PM, Keegan Peterzell  wrote:

> This is now complete [2]. That wasn't too bad.
>
> 1.
> https://lists.wikimedia.org/pipermail/wikimedia-l/2004-November/061327.html
> 2.
> https://lists.wikimedia.org/pipermail/wikimedia-l/2015-April/077576.html


Congratulations, and hats off to you, Kunal, and the rest of the team for
pulling this off. The layers of legacy code and complex social conundrums
you have had to negotiate in order to see this project through were
terrifyingly large, and it's pretty incredible that you have been able to
see it through with minimal disruption to users. Kudos and thank you.
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] [Foundation-l] Single login - decision 2004

2015-04-21 Thread Keegan Peterzell
On Nov 11, 2004, at 03:27:00 UTC , Erik Moeller  wrote
[1]:

> Hi,
> there's been some movement forward on the Single User Login (SUL) issue. I
>
> ask the Board to review this mail carefully as this has significant long-
> term implications and we need Board input to go ahead. I also ask other
> developers to correct me if I misrepresent anything.
> There are currently three competing strategies. Before I describe these
> strategies, let me point out that one important consideration for any
> system is scalability. That is, single login will be used on all existing
> and future Wikimedia projects, and potentially even on non-Wikimedia sites
>
> which we allow to participate in our system.
> The three strategies are:
> 1) GLOBAL NAMESPACE, IMMEDIATE CONFLICT RESOLUTION
> We try to move towards a single global user namespace for all Wikimedia
> wikis. If a name is already taken in the global namespace, you have to
> find one which isn't.
> For the migration, any names which clearly belong to the same user are
> combined into one. If passwords and email addresses are different, the
> user can manually link together any accounts which belong to him by
> providing the passwords.
> For cases of true name conflicts between the existing wikis, there is a
> resolution phase, where factors like seniority, use on multiple wikis vs.
> a single one, etc., are weighed in - the "loser" has to choose a new
> account name.
> After the manual resolution phase, any remaining accounts are converted to
>
> the new system automatically by making them unique, e.g. by adding a
> number to the username. The transition is now complete. The old system no
> longer exists.

---

> 1) is very complex, and we may not find someone willing to deal with the
> name conflict resolution issue and take the blame from annoyed users at
> the same time. Naming conflicts will always be an issue in this scheme, as
>
> e.g. all common first names will be taken, and any small wiki hooking up
> with our SUL system would feel this impact. People can mutate these
> usernames relatively easily to make them unique - Erik333 - and the system
>
> can offer such mutations, but it's still a bit annoying.


This is now complete [2]. That wasn't too bad.

1.
https://lists.wikimedia.org/pipermail/wikimedia-l/2004-November/061327.html
2. https://lists.wikimedia.org/pipermail/wikimedia-l/2015-April/077576.html

--
Keegan Peterzell
Community Liaison, Product
Wikimedia Foundation
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] Wikimedia Foundation quarterly reviews

2015-04-21 Thread Tilman Bayer
Hi all,

the quarterly reviews for the past quarter (January-March 2015) took
place last week. Minutes and slides are now available for the
following meetings:

Community Engagement, Advancement (Fundraising and Fundraising Tech):
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Community_Engagement_and_Advancement/April_2015

Mobile Web, Mobile Apps, Wikipedia Zero:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Mobile_and_Wikipedia_Zero,_April_2015

Parsoid, Services, MediaWiki Core, Tech Ops, Release Engineering,
Multimedia, Labs, Engineering Community:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Parsoid,_Services,_MW_Core,_Ops,_RelEng,_MM,_Labs_and_ECT,_April_2015

Editing (covering VisualEditor), Collaboration (covering Flow),
Language Engineering:
https://meta.wikimedia.org/wiki/WMF_Metrics_and_activities_meetings/Quarterly_reviews/Editing,_Collaboration_and_Language_Engineering,_April_2015


As mentioned in February [1], the quarterly review process has been
extended to basically all groups in the Foundation since Lila took the
helm last year, and it was further refined this quarter, reducing the
number of meetings to six overall, each combining several areas.
Minutes and slides from the remaining two meetings should come out
soon, too. (And naturally, all the engineering team names above refer
to the structure before the reorganization that has just been
announced.)

[1] https://lists.wikimedia.org/pipermail/wikimedia-l/2015-February/076835.html

On Wed, Dec 19, 2012 at 6:49 PM, Erik Moeller  wrote:
>
> Hi folks,
>
> to increase accountability and create more opportunities for course
> corrections and resourcing adjustments as necessary, Sue's asked me
> and Howie Fung to set up a quarterly project evaluation process,
> starting with our highest priority initiatives. These are, according
> to Sue's narrowing focus recommendations which were approved by the
> Board [1]:
>
> - Visual Editor
> - Mobile (mobile contributions + Wikipedia Zero)
> - Editor Engagement (also known as the E2 and E3 teams)
> - Funds Dissemination Committe and expanded grant-making capacity
>
> I'm proposing the following initial schedule:
>
> January:
> - Editor Engagement Experiments
>
> February:
> - Visual Editor
> - Mobile (Contribs + Zero)
>
> March:
> - Editor Engagement Features (Echo, Flow projects)
> - Funds Dissemination Committee
>
> We’ll try doing this on the same day or adjacent to the monthly
> metrics meetings [2], since the team(s) will give a presentation on
> their recent progress, which will help set some context that would
> otherwise need to be covered in the quarterly review itself. This will
> also create open opportunities for feedback and questions.
>
> My goal is to do this in a manner where even though the quarterly
> review meetings themselves are internal, the outcomes are captured as
> meeting minutes and shared publicly, which is why I'm starting this
> discussion on a public list as well. I've created a wiki page here
> which we can use to discuss the concept further:
>
> https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings/Quarterly_reviews
>
> The internal review will, at minimum, include:
>
> Sue Gardner
> myself
> Howie Fung
> Team members and relevant director(s)
> Designated minute-taker
>
> So for example, for Visual Editor, the review team would be the Visual
> Editor / Parsoid teams, Sue, me, Howie, Terry, and a minute-taker.
>
> I imagine the structure of the review roughly as follows, with a
> duration of about 2 1/2 hours divided into 25-30 minute blocks:
>
> - Brief team intro and recap of team's activities through the quarter,
> compared with goals
> - Drill into goals and targets: Did we achieve what we said we would?
> - Review of challenges, blockers and successes
> - Discussion of proposed changes (e.g. resourcing, targets) and other
> action items
> - Buffer time, debriefing
>
> Once again, the primary purpose of these reviews is to create improved
> structures for internal accountability, escalation points in cases
> where serious changes are necessary, and transparency to the world.
>
> In addition to these priority initiatives, my recommendation would be
> to conduct quarterly reviews for any activity that requires more than
> a set amount of resources (people/dollars). These additional reviews
> may however be conducted in a more lightweight manner and internally
> to the departments. We’re slowly getting into that habit in
> engineering.
>
> As we pilot this process, the format of the high priority reviews can
> help inform and support reviews across the organization.
>
> Feedback and questions are appreciated.
>
> All best,
> Erik
>
> [1] https://wikimediafoundation.org/wiki/Vote:Narrowing_Focus
> [2] https://meta.wikimedia.org/wiki/Metrics_and_activities_meetings
> --
> Erik Möller
> VP of Engineering and Product Development, Wikimedia Found

Re: [Wikimedia-l] [Wikimedia Announcements] Fwd: A new structure for WMF Engineering.

2015-04-21 Thread Brian Wolff
>
> In particular, I wanted to share more about the plans for the Community
> Tech team. The creation of this team is a direct response to community
> requests for more technical support. Their mission is to understand and
> support the technical needs of core contributors, including improved
> support for expert-­focused curation and moderation tools, bots, and other
> features. Their mandate is to work closely with you, and the Community
> Engagement department, to define their roadmap and deliverables. We are
> hiring for a leader for this team, as well as additional engineers. We will
> be looking within our communities to help. Until then, it will be incubated
> under Toby Negrin, with support from Community Engagement.

I look forward to seeing how this works out. I sometimes worry that it
seems like over the years that developers have become more and more
separate from the "community". Our community is our heart; It is why
we are all here. Having teams dedicated to working closely with our
communities sounds like an excellent idea.


--
bawolff

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


[Wikimedia-l] [Wikimedia Announcements] Fwd: A new structure for WMF Engineering.

2015-04-21 Thread Lila Tretikov
Dear Wikimedians,

Today we had a meeting at the Foundation to announce changes in our Product
and Engineering team structure. They represent the outcome of many
conversations with people from across the Wikimedia community and within
the Foundation. These changes will organize our teams around the needs of
people they serve, and empower them to focus deeply on their audiences to
deliver great outcomes.

We’re bringing together our Product and Engineering departments to form new
audience teams, reporting to Damon Sicore, our VP of Engineering. We’re
grouping core research, architecture, performance, and security functions
together, and will begin the search for a Chief Technology Officer (CTO) to
lead our engineering future. And we’re integrating support for Community
Engineering into the broader Community Engagement team. These changes are
effective today.

Earlier this year we set out some goals for our work at the Foundation,
described in our Call to Action

for 2015. These goals came out of conversations with you, and with
Foundation staff. You’ll see that the first thing we identified was the
need to improve our technology and execution. These goals focused on
defining commitments, data-driven decision making, support for community
engineering requests, and a commitment to engineering leadership.

The new changes reflect these commitments. We have organized our product
engineering around six teams each with unique audiences. This includes a
Community Tech team dedicated to supporting tools for core contributors, as
well as teams for Editing, Reading, Search & Discovery, Infrastructure, and
Fundraising Tech.

In particular, I wanted to share more about the plans for the Community
Tech team. The creation of this team is a direct response to community
requests for more technical support. Their mission is to understand and
support the technical needs of core contributors, including improved
support for expert-­focused curation and moderation tools, bots, and other
features. Their mandate is to work closely with you, and the Community
Engagement department, to define their roadmap and deliverables. We are
hiring for a leader for this team, as well as additional engineers. We will
be looking within our communities to help. Until then, it will be incubated
under Toby Negrin, with support from Community Engagement.

We’re also committed to our long-term technology future. A new CTO will
support teams and functions dedicated to performance, architecture,
security, privacy, structured data, user experience, and research. Their
mandate is to keep Wikimedia fast, reliable, stable, and secure -- and to
support the Engineering team in their development of excellent products and
features.

You may notice there is no standalone Product department. We are moving
away from a matrix management structure. Instead, product managers,
designers, analysts, engineers, and others working together will report to
the same manager, who will report through to the VP of Engineering. This is
because we believe that everyone is responsible for user experience and
each team is ultimately responsible for delivering on the product vision
and a roadmap. It also gives teams ability to make decisions that are best
for their audiences, based on their user’s feedback. This represents a
maturation of our organization and processes, and will give each new teams
more focus, dedicated focus, and more support.

I want to thank everyone who has worked so hard to bring this new structure
together. Thank you to everyone in the community, for being thoughtful and
honest with your needs, criticisms and encouragements. Thank you to our
engineers, designers, researchers, and product managers, who have given us
extensive feedback about what works best for you. Thank you to our new team
managers and leads for stepping up into new roles. And thank you to Erik
and Damon, who have worked closely for many months to make this happen.

You can find more information about this new structure, the new teams,
their missions, and leadership, as well as other questions in a FAQ on
Metawiki
.
We will update the Wikimedia Foundation site Staff page soon to reflect
these new teams.

Lila
___
Please note: all replies sent to this mailing list will be immediately directed 
to Wikimedia-l, the public mailing list of the Wikimedia community. For more 
information about Wikimedia-l:
https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
___
WikimediaAnnounce-l mailing list
wikimediaannounc...@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikimediaannounce-l
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mai

[Wikimedia-l] A new structure for WMF Engineering.

2015-04-21 Thread Lila Tretikov
Dear Wikimedians,

Today we had a meeting at the Foundation to announce changes in our Product
and Engineering team structure. They represent the outcome of many
conversations with people from across the Wikimedia community and within
the Foundation. These changes will organize our teams around the needs of
people they serve, and empower them to focus deeply on their audiences to
deliver great outcomes.

We’re bringing together our Product and Engineering departments to form new
audience teams, reporting to Damon Sicore, our VP of Engineering. We’re
grouping core research, architecture, performance, and security functions
together, and will begin the search for a Chief Technology Officer (CTO) to
lead our engineering future. And we’re integrating support for Community
Engineering into the broader Community Engagement team. These changes are
effective today.

Earlier this year we set out some goals for our work at the Foundation,
described in our Call to Action

for 2015. These goals came out of conversations with you, and with
Foundation staff. You’ll see that the first thing we identified was the
need to improve our technology and execution. These goals focused on
defining commitments, data-driven decision making, support for community
engineering requests, and a commitment to engineering leadership.

The new changes reflect these commitments. We have organized our product
engineering around six teams each with unique audiences. This includes a
Community Tech team dedicated to supporting tools for core contributors, as
well as teams for Editing, Reading, Search & Discovery, Infrastructure, and
Fundraising Tech.

In particular, I wanted to share more about the plans for the Community
Tech team. The creation of this team is a direct response to community
requests for more technical support. Their mission is to understand and
support the technical needs of core contributors, including improved
support for expert-­focused curation and moderation tools, bots, and other
features. Their mandate is to work closely with you, and the Community
Engagement department, to define their roadmap and deliverables. We are
hiring for a leader for this team, as well as additional engineers. We will
be looking within our communities to help. Until then, it will be incubated
under Toby Negrin, with support from Community Engagement.

We’re also committed to our long-term technology future. A new CTO will
support teams and functions dedicated to performance, architecture,
security, privacy, structured data, user experience, and research. Their
mandate is to keep Wikimedia fast, reliable, stable, and secure -- and to
support the Engineering team in their development of excellent products and
features.

You may notice there is no standalone Product department. We are moving
away from a matrix management structure. Instead, product managers,
designers, analysts, engineers, and others working together will report to
the same manager, who will report through to the VP of Engineering. This is
because we believe that everyone is responsible for user experience and
each team is ultimately responsible for delivering on the product vision
and a roadmap. It also gives teams ability to make decisions that are best
for their audiences, based on their user’s feedback. This represents a
maturation of our organization and processes, and will give each new teams
more focus, dedicated focus, and more support.

I want to thank everyone who has worked so hard to bring this new structure
together. Thank you to everyone in the community, for being thoughtful and
honest with your needs, criticisms and encouragements. Thank you to our
engineers, designers, researchers, and product managers, who have given us
extensive feedback about what works best for you. Thank you to our new team
managers and leads for stepping up into new roles. And thank you to Erik
and Damon, who have worked closely for many months to make this happen.

You can find more information about this new structure, the new teams,
their missions, and leadership, as well as other questions in a FAQ on
Metawiki
.
We will update the Wikimedia Foundation site Staff page soon to reflect
these new teams.

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


Re: [Wikimedia-l] The Wikipedia store relaunch

2015-04-21 Thread Ricordisamoa

Il 21/04/2015 23:13, Victoria Shchepakina ha scritto:

Hello everyone,

The Wikipedia store has been relaunched. We closed doors temporarily for a
few months to redesign the website and also to introduce new items.
Besides, we wanted to re-think our store structure and visual identity, as
well as provide creative items made in partnership with socially
responsible and mission aligned partners. So check us out
!

As a reminder, the store is engaged in giveaway programs rewarding
volunteers, supporting editathons and engaging in hackathons and other
community conferences. As usual, all sales support and reward contributors
all over the world.

The Wikipedia store looks forward to collaborating with the community,
vendors, designers, artists, and people with similar visions to create
meaningful merchandise for our community and readers. Soon you will see
creative representations of Wikipedia and its sister projects originating
from these collaborations. The vision for our merchandise is to motivate
you and people around you to help spread knowledge via Wikimedia projects.

Wikipedia volunteers are special. Without them, we would not exist. We
can’t thank them enough - but we’re trying. That’s why we created the
Merchandise
Giveaway Program ,
amongst other giveaway projects. Through it, any Wikipedia user can
nominate a Wikipedia contributor to receive a free gift in the mail.


https://meta.wikimedia.org/wiki/Merchandise_giveaways#Can_I_nominate_someone_from_the_X_language_Wikipedia_or_Y_Wikimedia_project_.3F



Spread the word about the Wikipedia store 
and please follow us @wikipediastore on Twitter
 and on Instagram
!

Thank you!

Best,

Victoria Shchepakina


Fundraising Associate
Wikimedia Foundation
office +1 (415) 839 6885

vshchepak...@wikimedia.org
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
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
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


[Wikimedia-l] The Wikipedia store relaunch

2015-04-21 Thread Victoria Shchepakina
Hello everyone,

The Wikipedia store has been relaunched. We closed doors temporarily for a
few months to redesign the website and also to introduce new items.
Besides, we wanted to re-think our store structure and visual identity, as
well as provide creative items made in partnership with socially
responsible and mission aligned partners. So check us out
!

As a reminder, the store is engaged in giveaway programs rewarding
volunteers, supporting editathons and engaging in hackathons and other
community conferences. As usual, all sales support and reward contributors
all over the world.

The Wikipedia store looks forward to collaborating with the community,
vendors, designers, artists, and people with similar visions to create
meaningful merchandise for our community and readers. Soon you will see
creative representations of Wikipedia and its sister projects originating
from these collaborations. The vision for our merchandise is to motivate
you and people around you to help spread knowledge via Wikimedia projects.

Wikipedia volunteers are special. Without them, we would not exist. We
can’t thank them enough - but we’re trying. That’s why we created the
Merchandise
Giveaway Program ,
amongst other giveaway projects. Through it, any Wikipedia user can
nominate a Wikipedia contributor to receive a free gift in the mail.

Spread the word about the Wikipedia store 
and please follow us @wikipediastore on Twitter
 and on Instagram
!

Thank you!

Best,

Victoria Shchepakina


Fundraising Associate
Wikimedia Foundation
office +1 (415) 839 6885

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


Re: [Wikimedia-l] Partnership policy - Wikimédia France

2015-04-21 Thread Jens Best
Great inspiritional definitions and listing, Anne-Laure. Also it's good to
see some facts which always thought to be "self-evident and understood"
written down in such a well-structured form.
Thanks for posting.


Jens

2015-04-20 16:10 GMT+02:00 Anne-Laure Prévost <
annelaure.prev...@wikimedia.fr>:

> Hi everyone,
>
> Wikimédia France has recently issued its partnership policy :
> you can find it on Meta both in French [1] and in English [2].
>
> The objective of such a policy is to help communicate our vision of
> partnerships and share it with future partners and stakeholders. It
> includes our "service offering" (which is almost finalized) to clarify our
> scope of activity.
>
> If you have any questions/remarks or your own example of such a policy,
> please feel free to get in touch !
>
> Regards,
> Anne-Laure
>
> [1] https://meta.wikimedia.org/wiki/Wikimédia_France/Démarche_partenariale
> [2]
> https://meta.wikimedia.org/wiki/Wikimédia_France/Démarche_partenariale/en
>
>
>
> *Anne-Laure Prévost*
> CONSEILLÈRE SPÉCIALE PARTENARIATS ET RELATIONS INSTITUTIONNELLES /
> SPECIAL ADVISOR PARTNERSHIPS & INSTITUTIONAL RELATIONSHIPS
>
> *Tél  +33 7 62 93 42 02 /* *+33 1 42 36 97 72*
> *www.wikimedia.fr  *
> *40 rue de Cléry, 75002 Paris*  >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> 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
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Partnership policy - Wikimédia France

2015-04-21 Thread Ilario Valdelli
Hi Anne-Laure,
really grateful to read this document, I think that the direction is
correct and it may be a good approach to the creation of a "portfolio" of
services.

Anyway any service is a combination of people, processes and tools.

Some indications can be extracted from this document but a real good
evolution could be to think about processes and tools behind these services
and may be also about the profile of people that can take them in charge.

Thank you for sharing


On Mon, Apr 20, 2015 at 4:10 PM, Anne-Laure Prévost <
annelaure.prev...@wikimedia.fr> wrote:

> Hi everyone,
>
> Wikimédia France has recently issued its partnership policy :
> you can find it on Meta both in French [1] and in English [2].
>
> The objective of such a policy is to help communicate our vision of
> partnerships and share it with future partners and stakeholders. It
> includes our "service offering" (which is almost finalized) to clarify our
> scope of activity.
>
> If you have any questions/remarks or your own example of such a policy,
> please feel free to get in touch !
>
> Regards,
> Anne-Laure
>
> [1] https://meta.wikimedia.org/wiki/Wikimédia_France/Démarche_partenariale
> [2]
> https://meta.wikimedia.org/wiki/Wikimédia_France/Démarche_partenariale/en
>
>
>
> *Anne-Laure Prévost*
> CONSEILLÈRE SPÉCIALE PARTENARIATS ET RELATIONS INSTITUTIONNELLES /
> SPECIAL ADVISOR PARTNERSHIPS & INSTITUTIONAL RELATIONSHIPS
>
> *Tél  +33 7 62 93 42 02 /* *+33 1 42 36 97 72*
> *www.wikimedia.fr  *
> *40 rue de Cléry, 75002 Paris*  >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 




-- 
Ilario Valdelli
Wikimedia CH
Verein zur Förderung Freien Wissens
Association pour l’avancement des connaissances libre
Associazione per il sostegno alla conoscenza libera
Switzerland - 8008 Zürich
Wikipedia: Ilario 
Skype: valdelli
Facebook: Ilario Valdelli 
Twitter: Ilario Valdelli 
Linkedin: Ilario Valdelli 
Tel: +41764821371
http://www.wikimedia.ch
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 


Re: [Wikimedia-l] Partnership policy - Wikimédia France

2015-04-21 Thread Luis Villa
Hi, Anne-Laure-
This is a very thoughtful approach to a complicated and important problem.
Congratulations on creating it, and thanks for sharing it. I look forward
to hearing what you (and prospective partners!) learn from it in coming
years.

Luis

On Mon, Apr 20, 2015 at 7:10 AM, Anne-Laure Prévost <
annelaure.prev...@wikimedia.fr> wrote:

> Hi everyone,
>
> Wikimédia France has recently issued its partnership policy :
> you can find it on Meta both in French [1] and in English [2].
>
> The objective of such a policy is to help communicate our vision of
> partnerships and share it with future partners and stakeholders. It
> includes our "service offering" (which is almost finalized) to clarify our
> scope of activity.
>
> If you have any questions/remarks or your own example of such a policy,
> please feel free to get in touch !
>
> Regards,
> Anne-Laure
>
> [1] https://meta.wikimedia.org/wiki/Wikimédia_France/Démarche_partenariale
> [2]
> https://meta.wikimedia.org/wiki/Wikimédia_France/Démarche_partenariale/en
>
>
>
> *Anne-Laure Prévost*
> CONSEILLÈRE SPÉCIALE PARTENARIATS ET RELATIONS INSTITUTIONNELLES /
> SPECIAL ADVISOR PARTNERSHIPS & INSTITUTIONAL RELATIONSHIPS
>
> *Tél  +33 7 62 93 42 02 /* *+33 1 42 36 97 72*
> *www.wikimedia.fr  *
> *40 rue de Cléry, 75002 Paris*  >
> ___
> Wikimedia-l mailing list, guidelines at:
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> 




-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,