Dear Users,
I have the great honour to inform you that the Call for Proposals for WikiIndaba 2018 is now open. WikiIndaba 2018 is the 3rd conference of African Wikimedia movement and will give to participants the opportunity to share their Wikimedia-related experience and skills with a wide and active African Wikimedia audience. The conference will be held in Tunisia from 16 to 18 March 2018. If you want to participate to WikiIndaba and share your works and thoughts with African Wikimedians, feel free to submit your proposal in https://meta.m.wikimedia.org/wiki/WikiIndaba_conference_2018/Submissions. The deadline for giving proposals will be January 15th, 2018.
If you need a scholarship to attend WikiIndaba 2018, you can apply to it in https://docs.google.com/forms/d/e/1FAIpQLSdJJ2I0FBqp4SuiW5ypj-9lnLaAidUmhMs….
Looking forward to seeing you in Tunis next March.
Yours Sincerely,
Houcemeddine Turki
Felix Nartey
Isla Haddow-Flood
*Forwarded as received from Wikitech-l*
Hi all,
I'm an Outreachy <https://www.outreachy.org/alums/> intern and as a part of
the internship, I'm working on a project - WikiCV
<https://en.wikipedia.org/wiki/Wikipedia:WikiCV>.
Through this project we (my mentors - Gergő Tisza and Stephen LaPorte and
I) want to create a contribution summarizing tool which (unlike the
existing ones that focus on statistics and are hard to interpret for
someone not familiar with Wikipedia editing) highlights contributions in an
easy-to-understand manner.
I'm writing this to gather inputs from prospective users of this tool, that
is all the Wikipedia editors!
Basically I want to understand what all things would you like to see in a
tool like this? Or what all would you write in your Wikipedia CV?
You can give in your inputs through mail (I'd be more than happy to get one
:)) or fill out this form <https://goo.gl/forms/slmOreey5iVPWzFx1>. My work
is largely dependent on your inputs, so please pour in your comments/views.
Your help will be quite appreciated!
Eagerly waiting for your inputs :)
Thanks,
Megha Sharma
*(Forwarded as received)*
Reminder: Technical Advice IRC meeting again **tomorrow, Wednesday 4-5 pm
UTC** on #wikimedia-tech.
The Technical Advice IRC meeting is open for all volunteer developers,
topics and questions. This can be anything from "how to get started" over
"who would be the best contact for X" to specific questions on your project.
If you know already what you would like to discuss or ask, please add your
topic to the next meeting: https://www.mediawiki.org/wiki/Technical_Advice_
IRC_Meeting
**Please note:** We will do a two week break due to the holiday season!
This will be the last Meeting for 2017, the next meeting after this will be
on January 3rd 2018!
Hope to see you there!
Michi (for WMDE’s tech team)
--
Michael F. Schönitzer
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/681/51985.
Google Code-in 2017 just started:
https://www.mediawiki.org/wiki/Google_Code-in/2017
You might remember the announcement email from a few weeks ago.[1]
In the next seven weeks, many young people are going to make their
first contributions to Wikimedia. Expect many questions on IRC and
on mailing lists by newcomers who have never used IRC or lists
before. Your help and patience is welcome to provide a helping hand!
Thanks to all mentors who have already registered & provided tasks!
You have not become a mentor yet? Please consider it!
You get some smaller tasks fixed and it is fun!
* Think of easy tasks in your area that you could mentor.
Areas are: Code, docs/training, outreach/research, quality
assurance, and user interface. "Easy" means 2-3h to complete for
you, or less technical ~30min "beginner tasks" for onboarding).
* OR: provide an easy 'clonable' task (a task that is generic and
could be repeated many times by different students).
* Note that you commit to answer to students' questions and to
evaluate their work within 36 hours (but the better your task
description the less questions. No worries, we're here to help!)
For the full info, please check out
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
and ask if something is unclear.
Thank you again for giving young contributors the opportunity to learn
about and work on all aspects of Free & Open Source Software projects.
Now bring your tasks!
Cheers,
andre
[1] https://lists.wikimedia.org/pipermail/wikitech-l/2017-
October/088956.html
*FYI, Forwarded as Received*
**
Dear all,
*TL;DR: *If you don't want to wait until you run into a real edit conflict
to tryout *Two Column Edit Conflict View* [1], you can now test the new
interface on a temporary testpage where you will get simulated edit
conflicts.
*About Two Column Edit Conflict View*
Improving the current UI of the edit conflict resolution page was wish #1
in the 2015 Technical wishes survey of the German-speaking community [2].
The TwoColConflict extension ("Two Column Edit Conflict View") [3]
highlights differences between the editor's and the conflicting change
directly in the textfield for an easy possibility to copy and paste desired
pieces of the text and resolving the conflict. It has been a beta feature
on all wikis for 5 months now and users have been invited to test it and
give feedback. [4]
Here is a rough visualisation of how the Two Column Edit Conflict view
works:
https://commons.wikimedia.org/wiki/File:Two_Column_Edit_
Conflict_View_-_rough_visualization_of_the_functionality.png
:-)
*The challenge*
We got some feedback on the beta feature, but not enough to get a good
feeling if the product is already great as it is now, or if some changes
are still needed. We assume that's because in order to give feedback,
people have to have the beta feature activated AND have an edit conflict
AND share their feedback - that's a pretty rare combination.
*More testing!*
We've implemented a temporary Special page that serves as a *test page* [5]
where you will get simulated edit conflicts: The new interface can be
tested now without actually having an edit conflict, and without the risk
of messing up real wiki pages.
We'd like to invite everyone to test the new interface with the test page
until November 9, 2017!
Please go to *https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/
Edit_Conflicts/Feedback_Round_Test_Page
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/
Edit_Conflicts/Feedback_Round_Test_Page>
*for more informations.
If you know people who might be interested in testing, please spread the
word!
Thank you so much,
Birgit (for the Technical Wishes team)
Links:
[1] Multilingual help page
<https://www.mediawiki.org/wiki/Help:Two_Column_Edit_Conflict_View>
[2] Main project page
<https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts>
[3] Extension manual
<https://www.mediawiki.org/wiki/Extension:TwoColConflict>
[4] Central feedback page
<https://www.mediawiki.org/wiki/Help_talk:Two_Column_Edit_Conflict_View>
[5] Ticket on Phab for the Special page
<https://phabricator.wikimedia.org/T170375>
--
Birgit Müller
Community Communications Manager
Software Development and Engineering
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/681/51985.
Hello everyone,
I would like to share the first edition of the New Developers Quarterly
Report <https://www.mediawiki.org/wiki/New_Developers/Quarterly/2017-10>
that the Developer Relations team has produced. This report covers metrics,
survey analysis and lessons learned from new developers focused activities
in the previous quarter (July-September 2017).
If you have questions and feedback that you would like to share with us,
please add them on the discussion
<https://www.mediawiki.org/wiki/Talk:New_Developers/Quarterly/2017-10>
page.
To receive a notification when a new report is published, subscribe here
<https://www.mediawiki.org/wiki/Special:Newsletter/11/subscribe>.
We plan to release a report every quarter and take action items identified
from the key findings for improving our existing methods and processes. The
next release will be in January 2018.
If you have any questions, comments, and concerns, we will be more than
happy to hear them!
Thanks,
Srishti
*N*
*OTE: *Forwarded as Received!**
Hello all,
We are pleased to announce Google Summer of Code 2018 <http://g.co/gsoc>,
the 14th consecutive year of the program.
We have announced
<https://opensource.googleblog.com/2017/09/announcing-google-summer-of-code-…>
the main dates (org apps open, etc.) on the program timeline
<https://developers.google.com/open-source/gsoc/timeline>. Additional dates
will be added into the timeline later in 2017.
Students -- Be sure visit the program site February 12th when participating
mentoring organizations are announced. At that point it is in your best
interest to research the organizations that have projects ideas that
intrigue you and reach out to them early, before the student application
process even starts. Communication is one of the most important parts of
the program.
Organizations -- If you would like to apply for the 2018 program please
start thinking about the projects you would like students to work on and
also reach out to your community members to ask if they would like to be
mentors for the program.
We are looking forward to another exciting year of GSoC!
Last week we also announced the Google Code-in 2017 <http://g.co/gci> (GCI)
contest for 13-17 year old students. GCI is open for past GSoC mentoring
organizations to apply to be a part of this exciting contest from October
9th - October 24th. GCI opens for student participants on November 28th!
You can read more about the contest on our blog
<https://opensource.googleblog.com/2017/09/announcing-google-code-in-2017.ht…>
.
For any questions about the programs please email us at
gsoc-support(a)google.com
Best,
Google OSPO team
*Forwarded as Received!*
Hello,
We are pleased to announce Google Code-in 2017 <http://g.co/gci>, the 8th
straight year of the program for pre-university students ages 13-17.
The GCI timeline, FAQs, Rules and flyers have been updated on the contest
site <http://g.co/gci>.
Organizations -- If you would like to apply for the 2017 program please
start thinking about the tasks you would like students to work on and also
reach out to your community members to ask if they would like to be mentors
for the program. Applications open for GCI orgs very soon - on October 9th,
and close 2 weeks later on October 24th. We will announce
organizations on Thursday,
October 26th giving orgs over a month to create their tasks before the
contest begins on November 28th.
We are looking to continue the growth of this program and reach a record
number of teenagers this year! Read more on today’s blog post
<https://opensource.googleblog.com/2017/09/announcing-google-code-in-2017.ht…>
.
If you have any questions about Google Code-in please contact us at
gci-support(a)google.com
Best,
Stephanie
*Forwarded as Received!*