Information sent to African Wikimedians as well as Wikimedia mailing
lists. Please do not hesitate to relay to anyone you think could be
interested.
-----
What is Wikipack Africa ?
WikiPack Africa is an action pack containing devices, material and
content to facilitate the outreach work done by local Wikimedia
chapters, local Wikimedia User Groups and isolated individuals in
African countries. The pack allows for ongoing training and contribution
even when technology, access and electricity outages fail or are not
available at all.
It operates thanks to a Raspberry server and an off-line editing
environment that mimics the Wikipedia called WikiFundi. WikiFundi, the
offline editing environment, is to be used in the training of
Wikipedians and the development of articles by groups.
In addition to WikiFundi, the Raspberry PI will also be loaded with
off-line copies of Wikipedia, select WikiBooks, Wiktionary and a
resource pack that will assist with and support contribution to
Wikipedia. Other outreach and reading resources will also be part of the
packs. All digital resources and the application platform are available
under a free licence. When delivered, the Wikipack Africa will also
comprise some offline materials (posters, leaflets, pull-up banner,
tee-shirts, etc.).
The langages implemented are French and English.
More information available at
* https://meta.wikimedia.org/wiki/Wikipack_Africa
* https://meta.wikimedia.org/wiki/WikiFundi
Documentation on meta is available in both langages
The current call for application is meant to be a pilot for the Wikipack
Africa. We have a limited number of servers available, so please only
make a request if you really intend to use the pack and are confronted
to connectivity issues.
Please note: should your request be granted, there will be an obligation
to provide details of its use, and usefulness as a tool for outreach in
the form of a survey. This could be requested several times up to 12
months after you have received the unit. This is meant to evaluate the
userfulness of the tool as well as identify issues or to help us take
into account improvement requests in a future release.
How to apply
Link : http://tinyurl.com/j78yyk3
Answers may be provided in French or English.
For any further information, please contact Anthere or Isla.
Who did that ?
The project has been conceptualised and conceived by Florence Devouard
and Isla Haddow-Flood.
The project is run in partnership with Wikimedia CH and the Orange
Foundation and is primarily implemented by Florence, Isla, and Emmanuel
Engelhart (the Kiwix master).
I'm partly in agreement with Pine, this is more about policy than a bug and it should be being discussed on meta not phabricator.
I disagree with Pine re the IRC channels. If the people running a particular IRC channel want it to continue as the recommended channel from a particular Wikimedia wiki then it is reasonable for the community to require that channel to comply with community norms. What happens on IRC channels that are unconnected with the movement is arguably out of our control. IRC has been a problem area in the past, I doubt I'm the only person on this list who has discovered, sometimes long after the event that community IRC channels were misused either to canvas against them or to say things that you'd be blocked for saying on wiki. Clearly we can't implement an IRC policy on freenode channels that conflicts with freenode policy. But I'd be surprised if we couldn't require a stricter policy than freenode seems to for IRC channels promoted on wiki.
More broadly my concern with the approach is that it misses the main target. The nastiest trolling, personal attacks and certainly the rape and murder threats will get people blocked anywhere in the movement except maybe, definitely in the past but hopefully not today, on IRC. We need to think how to protect members of our community from people who barely count as members of our community and who may not even consider themselves as such.
There is an argument for being stricter about incivility amongst the community, I suspect with the ongoing greying of our communities this will happen regardless. My main concern is not with shifting the boundary of what is or isn't acceptable but with dealing more effectively with the worst stuff that is currently happening. That has implications both technical and for legal/privacy. I'd like to change our privacy and Checkuser policies to presume in favour of "fishing trips". If members of our community are being seriously harassed on wiki I think it should be the norm to check the IP address and see if any good hand accounts are also run by the same person. We all as individuals have patterns around our editing, it shouldn't be beyond the capabilities of modern technology to flag up a warning to the check users when a new editor appears with a similar pattern to a banned troll. Dealing with off wiki harassment is more complex, the technology and social mores may be outside our control. But some of the nastiest stuff that happens online such as revenge porn is illegal or at least culturally unacceptable pretty much everywhere. Tracking down where servers are, whose jurisdiction they are in and liaising with local law enforcement are big tasks. I'd like to see the movement and specifically the foundation and chapters as trail blazers in this.
Regards
Jonathan/wereSpielChequers
> On 20 Nov 2016, at 12:00, wikimedia-l-request(a)lists.wikimedia.org wrote:
>
> Send Wikimedia-l mailing list submissions to
> wikimedia-l(a)lists.wikimedia.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
> or, via email, send a message with subject or body 'help' to
> wikimedia-l-request(a)lists.wikimedia.org
>
> You can reach the person managing the list at
> wikimedia-l-owner(a)lists.wikimedia.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Wikimedia-l digest..."
>
>
> Today's Topics:
>
> 1. Discussion about proposed Technical Code of Conduct (TCC) (Pine W)
> 2. Re: Implementing Katherine's Vision: "Discussing Discussions"
> (Pine W)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 19 Nov 2016 21:45:42 -0800
> From: Pine W <wiki.pine(a)gmail.com>
> To: Wikimedia Mailing List <Wikimedia-l(a)lists.wikimedia.org>, Matthew
> Flaschen <mflaschen(a)wikimedia.org>
> Subject: [Wikimedia-l] Discussion about proposed Technical Code of
> Conduct (TCC)
> Message-ID:
> <CAF=dyJiSgR_5+yTQ7Ynm4WnTDmfC1kwQjHxZ=_TwHs1jfo2vQA(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> I'm forking this discussion from the (no subject) thread.
>
> I think it might be a good idea to have some sort of guidance, such as a
> TCC, for how incivility is handled in technical spaces beyond reporting
> problems with WMF employees to their WMF managers and/or HR, because not
> everyone works for WMF, so it might be good to have a way to handle
> situations when someone who is not a WMF employee causes problems in
> technical spaces.
>
> However, I'm not sure that I agree that the TCC is "a (draft) community
> policy, being approved by the community. The community has already
> approved a large fraction of it. It's not a (draft) WMF policy."
>
> A substantial proportion of the comments on the talk page (and the
> archives) are from WMF employees, not community members. I realize, Matt,
> that you have been attempting to recruit broader participation, but it
> looks like the results have been less than one would have hoped.
> Given WMF's history of clashing with the community about subjects such as
> Superprotect, VisualEditor, and ACTRIAL, it seems to me that while WMF
> participation in discussions such as this is good, the high proportion of
> WMF representation on the talk page makes the resulting document more
> likely to reflect the view of WMF and its employees rather than the larger
> community. So, no, I would not consider this draft to be a community
> document at this time. The proportion of participation from WMF staff is
> too high.
>
> However, there are some paths forward: (1) Proceed with this as a policy
> that applies to WMF staff only, (2) get the WMF Board to approve the
> document as a policy, or (3) get the document to pass a community RFC,
> closed by a community steward.
>
> My advice, if WMF wants this TCC to hold weight with the community, is to
> put a lot of distance between WMF and this document. WMF can support the
> document's creation, but should not be in a leadership role, and WMF staff
> should be far less prominent on the talk page. That the lower the
> proportion of WMF involvement in the creation of this document, the more
> likely the document is to be viewed in a positive light by the community.
>
> I don't mean to sound like I intend to halt the entire TCC process, but I
> would advise proceeding with it differently than the talk page suggests has
> been happening so far.
>
> Regarding the applicability of the proposed policy to IRC, I view the
> proposed TCC as requiring explicit opt-in from IRC channels through their
> own internal governance processes. The TCC's assertion that it applies to
> IRC channels does not, by itself, actually make that happen without
> explicit opt-in from those channels; similarly, my drafting a policy on
> English Wikipedia that claims to apply to #wikipedia-en would have no
> validity without opt-in from #wikipedia-en.
>
> I need to attend to other matters so I won't participate in further
> discussions on this topic for the near future, but I welcome comments (and
> differing opinions) from others. To reiterate: I think that there could be
> benefits from a TCC, but I would suggest (1) softening the WMF's role in
> the creation of this document and (2) stating that the TCC applies to IRC
> channels on an opt-in basis.
>
> Pine
>
I'm forking this discussion from the (no subject) thread.
I think it might be a good idea to have some sort of guidance, such as a
TCC, for how incivility is handled in technical spaces beyond reporting
problems with WMF employees to their WMF managers and/or HR, because not
everyone works for WMF, so it might be good to have a way to handle
situations when someone who is not a WMF employee causes problems in
technical spaces.
However, I'm not sure that I agree that the TCC is "a (draft) community
policy, being approved by the community. The community has already
approved a large fraction of it. It's not a (draft) WMF policy."
A substantial proportion of the comments on the talk page (and the
archives) are from WMF employees, not community members. I realize, Matt,
that you have been attempting to recruit broader participation, but it
looks like the results have been less than one would have hoped.
Given WMF's history of clashing with the community about subjects such as
Superprotect, VisualEditor, and ACTRIAL, it seems to me that while WMF
participation in discussions such as this is good, the high proportion of
WMF representation on the talk page makes the resulting document more
likely to reflect the view of WMF and its employees rather than the larger
community. So, no, I would not consider this draft to be a community
document at this time. The proportion of participation from WMF staff is
too high.
However, there are some paths forward: (1) Proceed with this as a policy
that applies to WMF staff only, (2) get the WMF Board to approve the
document as a policy, or (3) get the document to pass a community RFC,
closed by a community steward.
My advice, if WMF wants this TCC to hold weight with the community, is to
put a lot of distance between WMF and this document. WMF can support the
document's creation, but should not be in a leadership role, and WMF staff
should be far less prominent on the talk page. That the lower the
proportion of WMF involvement in the creation of this document, the more
likely the document is to be viewed in a positive light by the community.
I don't mean to sound like I intend to halt the entire TCC process, but I
would advise proceeding with it differently than the talk page suggests has
been happening so far.
Regarding the applicability of the proposed policy to IRC, I view the
proposed TCC as requiring explicit opt-in from IRC channels through their
own internal governance processes. The TCC's assertion that it applies to
IRC channels does not, by itself, actually make that happen without
explicit opt-in from those channels; similarly, my drafting a policy on
English Wikipedia that claims to apply to #wikipedia-en would have no
validity without opt-in from #wikipedia-en.
I need to attend to other matters so I won't participate in further
discussions on this topic for the near future, but I welcome comments (and
differing opinions) from others. To reiterate: I think that there could be
benefits from a TCC, but I would suggest (1) softening the WMF's role in
the creation of this document and (2) stating that the TCC applies to IRC
channels on an opt-in basis.
Pine
On Fri, Nov 18, 2016 at 7:04 PM, Matthew Flaschen <mflaschen(a)wikimedia.org>
wrote:
On 11/17/2016 10:30 PM, Pine W wrote:
> As a reminder: IRC is governed by Freenode. Channels can have their own
> rules, and there are widely varying systems of internal governance for
> Wikimedia IRC channels. I think it's important to note that WMF and the
> Wikimedia community are guests on Freenode, and I'm uncomfortable with the
> proposition to extend a WMF policy into IRC channels without explicit
> consent from the ops of those channels; it seems to me that the TCC would
> be a per-channel opt-in on IRC, not a WMF blanket standard.
>
I just wanted to note that this is a (draft) community policy, being
approved by the community. The community has already approved a large
fraction of it. It's not a (draft) WMF policy.
(It is subject to Legal requirements like some other community policies,
but it seems this will only affect a small section.)
Thanks,
Matt Flaschen
Jimmy Wales wrote: "it is possible and welcomed to bring forward issues to
board members at any time".
It would be most helpful to know where and how the Board in general would
welcome such issues being raised and how much resource they will have to
sustain those discussions. Attempting to raise issues at
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Board_noticeboard for
example, has not met with great success: indeed, one Board member has
written there "I honestly disagree that "additional effort" is a realistic
opportunity",
It is fair to say that at least one other Board member has taken a very
positive attitude, and we have had some constructive engagement for which I
am duly grateful.
"Rogol"
Dear Wikimedians,
The Funds Dissemination Committee (FDC) meets twice a year to make
recommendations about how to effectively allocate movement funds to achieve
the Wikimedia movement's mission, vision, and strategy. This is now the
9th round of allocations made by the FDC, and we met in person from
November 13-17 in San Francisco to deliberate on 11 proposals submitted
this round. We would like to thank all of the participating organizations
for the hard work they put into this round’s proposals.
Our recommendations for Round 1 2016-2017 on the annual plan grants to the
Wikimedia Foundation Board of Trustees have now been posted on Meta.[1] The
Board will review our deliberations and make a decision by January 1, 2017.
We received grant requests for approximately USD 3,467,000 this round
(including two requests for two-year funding). Before we met, committee
members reviewed all of the proposals and documents submitted. We were
assisted in this review with input from the FDC staff assessments which
included analysis on impact, finances, and programs, as well as community
comments on the proposals.
As you may know, there is a formal process to submit complaints or appeals
about these recommendations. Here are the steps for both:
Any organization that would like to submit an appeal on the FDC’s Round 1
recommendation should submit it to the Board representatives to the FDC by
23:59 UTC on 8 December 2016 in accord with the appeal process outlined in
the FDC Framework [2]. A formal appeal to challenge the FDC’s
recommendation should be in the form of a 500-or-fewer word summary
directed to the two non-voting WMF Board representatives to the FDC,
Dariusz Jemielniak and Guy Kawasaki. The appeal should be submitted
on-wiki, and must be submitted by the Board Chair of a funding-seeking
applicant. The Wikimedia Foundation Board will publish its decision on this
and all recommendations by January 1, 2017.
Anyone can file a complaint about the FDC process [3] with the Ombudsperson
at any time. The complaint should be submitted on wiki, as well. The
Ombudsperson will publicly document the complaint, and investigate as
needed.
On behalf of the FDC,
Anne Clin / Risker
FDC Chair
[1]
https://meta.wikimedia.org/wiki/Grants:APG/FDC_recommendations/2016-2017_ro…
[2]
https://meta.wikimedia.org/wiki/Grants:APG/Appeals_to_the_Board_on_the_reco…
[3]
https://meta.wikimedia.org/wiki/Grants:APG/Complaints_about_the_FDC_process
The biggest privacy problem in Wikipedia has always been the permanent
public exposure of casual editors' IP addresses.
Secondarily, we store logged-in editors' IP addresses for a limited time,
exposing all editors' IP addresses to access by staff and volunteer
accounts which could be stolen or misused as well as to any potential
attacker who gains sufficient access to the database systems.
I would like to suggest that the Wikimedia editor community, along with the
Wikimedia Foundation as steward of the software and servers, have a serious
consultation about committing to fix this:
1) Eliminate IP address exposure for non-logged-in editors. Those editors
should be either given a random, truly anonymous identifier, or required to
create a pseudonym as a login.
2) Seriously think about how this will affect workflows tracking and
fighting vandalism, and provide tools that do not depend on public exposure
of network addresses.
3) Avoid public exposure or long-term logging of any other
location-specific or network-specific information about anonymous users.
4) Consider stronger controls on storage of IP addresses in the databases
and how they are secured, in the face of possible attacks through social
engineering, security vulnerabilities, or state action. Think about what
really needs to be stored and what types of data recovery are possible when
storing truly personal-private data in shared databases.
-- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
Lead Software Architect, Wikimedia Foundation
Dear Wikimedia friends,
Following Christian’s invitation two weeks ago and Daniela’s and
Wenke’s email some minutes ago, we will now provide you with
information regarding program related next steps of the Wikimedia
Conference 2017 (WMCON17). A more detailed version of this email can
be found on Meta. Please use the talk pages for your questions and
comments.[1]
Together with you, we want to make this Wikimedia Conference a great
experience for all participants. Cornelius Kibelka (Program and
Engagement Coordinator, PEC) and Nicole Ebber (International Advisor,
Curator of WMCON) will work together with the facilitators as well as
the participants to create the conference program in the coming weeks
and months. The conference will have three programmatic tracks:
== 1: Movement Strategy ==
Developing a strategic vision for the future of our movement is one of
the top priorities for 2017. Although the Wikimedia Foundation is
playing the primary coordinating role, this is meant to be a community
process with involvement from across the movement, and all volunteers
interested in engaging in its development are invited and strongly
encouraged to participate. The Wikimedia Conference will serve as one
of the platforms for participation and input from movement affiliates
and allies.
== 2: Movement Partnerships ==
Wikimedia organizations and groups have a wide variety of experiences
and knowledge in working with partners to achieve our mission.
However, we have never talked about what kind of partnerships we can
build nor how an excellent partnership looks like. Being able to
achieve our mission together with movement and external partners has
been the subject of occasional sessions at past WMCONs. This time we
will deepen the conversation, try to develop a joint language and
understanding of partnerships and open up opportunities for peer
sharing and consultation.
== 3: Capacity Building & Learning ==
Based on the experiences of the last Wikimedia Conferences, we will
have again a programmatic track that focuses on shared learning and
buildings capacities among Wikimedia organizations and groups.
Learning sessions will be built according to the needs, wishes,
experiences and knowledge expressed in the registration form.
== How to select the delegates ==
WMCON is all about participation. To make the conference a success it
will be essential for the invited affiliates to deliberately select
their delegates. Participants should come to Berlin to learn and to
share, but also to bring the information and learnings back home. We
are seeking delegates who will be actively engaged before, during and
after the conference and can represent their affiliates. Ideal
delegates are those who are involved in the decision making processes
in the organization, striving to help shape the future of the
movement, partnerships specialists or program leaders[2].
== How to prepare for the registration ==
Registration has opened today and closes on January 8, 2017. In the
months between the registration and WMCON, the PEC will work on the
program with the registered participants. Because we want to build the
program to fit participant needs and experiences, we would like to
learn a little more about your interests in advance. We have published
an overview of the questions[3] that we are using in the registration
form. Please make yourself familiar with these questions, as they can
also help you to select the delegates.
== What’s next ==
We have opened the registration today. Daniela Gentner will be the
main contact for all questions regarding the logistics, you can reach
out to her via wmcon(a)wikimedia.de.
Cornelius Kibelka is your main contact for all questions related to
the program of the Wikimedia Conference. You can contact him via
cornelius.kibelka(a)wikimedia.de.
We are looking forward to welcoming many of you in Berlin in March next year.
Nicole + Cornelius
[1] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Program_Design_Pr…
[2] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Program_Design_Pr…
[3] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Program_Design_Pr…
--
Cornelius Kibelka
Program and Engagement Coordinator (PEC)
for the Wikimedia Conference
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
Tel. (030) 219 158 26-0
http://wikimedia.de
Stellen Sie sich eine Welt vor, in der jeder Mensch an der Menge allen
Wissens frei teilhaben kann. Helfen Sie uns dabei!
http://spenden.wikimedia.de/
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.
V. Eingetragen im Vereinsregister des Amtsgerichts
Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig
anerkannt durch das Finanzamt für Körperschaften I Berlin,
Steuernummer 27/029/42207
Dear Wikimedians,
We are delighted to announce that the registration for the Wikimedia
Conference 2017 [1], which will be held in Berlin from Friday, March
31, through Sunday, April 2, is now open!
Following Christian’s invitation from November 4, we would like to
provide you with important information regarding the eligibility for
participation, participant number regulation, registration procedure,
specifics in regards to the travel and hotel booking as well as the
visa application process.
== Eligibility criteria and participant number regulation ==
The eligibility criteria for participating in the Wikimedia Conference
2017 are aligned to the Affiliates’ Agreements with the Wikimedia
Foundation. Chapters, Thematic Organizations and User Groups must have
shown signs of recent activity (within the last six months) and be
up-to-date on their reporting [2] by the eligibility deadline
(December 1, 2016). Moreover, affiliations need to have been
officially recognized by the Wikimedia Foundation before March 30,
2016. Before registering for the conference, please check the
eligibility and status overview of your affiliate as well as the
participant number regulation on meta [3].
==Registration information==
To make the conference a success, it will be essential for the invited
affiliates to deliberately choose their delegates. Affiliates are
asked to only send delegates that are well-informed in goings-on at
the affiliate, able to confidently answer questions about it and share
experience from their group. They should also be empowered to commit
their group to involvement in proposed projects or initiatives. We
recommend to follow the “How to select the delegates” information,
which is published on meta [4].
Persons, who are selected by their organization to represent them at
the conference, need to register via the registration form [5]. The
registration deadline is Sunday, January 8, 2017. Please note that we
won’t be able to accept and process registrations after this deadline.
We are looking forward to also welcoming members of the Wikimedia
Foundation Board of Trustees and staff, the Funds Dissemination
Committee as well as the Affiliations Committee in Berlin. We see a
huge advantage in having their representatives participate on site.
Please also register via the registration link [5].
In addition to the core-conference, pre-conference Learning Days on
Wednesday and Thursday, March 29-30, are organized by the WMF Learning
and Evaluation team [6]. Should you be interested in participating in
these Learning Days, you can indicate your interest in the
registration form as well. There is also a Boards Training Workshop
[7] organized by Frans Grijzenhout (chair of Wikimedia Nederland) and
Tim-Moritz Hector (chair of Wikimedia Deutschland), invitations for
this workshop are sent via the chairs mailing list.
For the purpose of helping affiliates to check that only their
selected representatives have registered and enable participants to
connect before the conference and stay involved afterwards, we will
publish all participants’ names on the meta page [8] shortly after
registration.
Further information on the registration process can be retrieved from meta [9].
==Hotel and travel booking==
The Wikimedia Conference will take place at the Mercure Hotel Berlin
Tempelhof Airport[10] in Berlin’s neighbourhood Neukölln. A high
number of hotel rooms, which are conveniently located on the levels
above the conference venue, have been reserved for the conference
participants. All rooms include Wifi, breakfast and have their own
bathroom.
Representatives of affiliates with an annual plan grant (group 1) will
need to book and pay for their hotel rooms as well as travel
individually. The hotel booking form and price information can be
found on meta [11].
Affiliates, which don’t receive funding via an annual plan grant
(group 2), will be supported by WMDE for their hotel needs and WMF for
their travel booking.
Members of the WMF Board, FDC, AffCom or WMF staff (group 3) receive
travel and hotel booking support by the WMF Travel department.
We advise you to check meta [3] to which group you belong to.
==Visa information==
In case you are in need of a visa, WMDE will assist you with the
application process. All relevant information and necessary steps to
undertake are described on meta [12].
Wikimedia Deutschland is looking forward to welcoming you in Berlin in March!
Please do not hesitate to reach out to us any time via
wmcon(a)wikimedia.de should you have any questions or comments.
Best regards,
Wenke and Daniela
Organizing Team WMCON
Wikimedia Deutschland
wmcon(a)wikimedia.de
[1] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017
[2] https://meta.wikimedia.org/wiki/Reports
[3] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Eligibility_Crite…
[4] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Program_Design_Pr…
[5] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Registration_Info…
[6] https://meta.wikimedia.org/wiki/Grants:Evaluation/News/Learning_Days_for_Wi…
[7] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Pre-Conference_Bo…
[8] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Participants%27_L…
[9] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Registration_Info…
[10] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Conference_Venue
[11] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Travel_and_Hotel_…
[12] https://meta.wikimedia.org/wiki/Wikimedia_Conference_2017/Visa_Process_and_…
Dear all,
It is my pleasure to announce, on behalf of the Affiliations Committee,
the recognition of another Wikimedia User Group: WikiDonne [1]
As the name indicates, their area of focus is content related to women
across the different Wikimedia projects, especially in Italian. They
also look to cooperate with other affiliates and especially with those
focused on the same topic, such as WikiWomen and WikiMujeres, and are
already cooperating with other external entities :-)
Welcome!!
1: https://meta.wikimedia.org/wiki/WikiDonne
--
"*Jülüjain wane mmakat* ein kapülain tü alijunakalirua jee wayuukanairua
junain ekerolaa alümüin supüshuwayale etijaanaka. Ayatashi waya junain."
Maor Malul
Socio, A.C. Wikimedia Venezuela | RIF J-40129321-2 |
www.wikimedia.org.ve <http://wikimedia.org.ve>
Member, Wikimedia Israel | www.wikimedia.org.il <http://wikimedia.org.il>
Chair, Wikimedia Foundation Affiliations Committee
Phone: +972-52-4869915
Twitter: @maor_x
Dear all,
I am pleased to announce the recognition of another Wikimedia User
Group, this time based in the USA: WikiConference North America [1]
At the end of WikiConference North America 2016, celebrated last month
in San Diego, the organizing team announced the creation of a permanent
group that will focus on the planning and hosting of WikiConference
North America in future years, as well as documenting best practices and
experiences learned with other affiliates planning and hosting
conferences and similar events. And some outreach, too :-)
Welcome!
1: https://meta.wikimedia.org/wiki/WikiConference_North_America
--
"*Jülüjain wane mmakat* ein kapülain tü alijunakalirua jee wayuukanairua
junain ekerolaa alümüin supüshuwayale etijaanaka. Ayatashi waya junain."
Maor Malul
Socio, A.C. Wikimedia Venezuela | RIF J-40129321-2 |
www.wikimedia.org.ve <http://wikimedia.org.ve>
Member, Wikimedia Israel | www.wikimedia.org.il <http://wikimedia.org.il>
Chair, Wikimedia Foundation Affiliations Committee
Phone: +972-52-4869915
Twitter: @maor_x