[Wikitech-l] New Wikimedia Developer Support channel (test pilot)

[Quim Gil]

(The HTML version of this announcement can be found at
https://discourse-mediawiki.wmflabs.org/t/welcome-to-wikimedia-developer-support/8
)

https://discourse-mediawiki.wmflabs.org/

Wikimedia Developer Support offers a support channel for all developers
working with MediaWiki or other Wikimedia related technologies: APIs,
extensions, skins, gadgets, templates, bots, tools, apps, data sets… If you
need help with a technical problem, just ask.

This website is based on Discourse. If you have questions about how to use
it, check https://www.mediawiki.org/wiki/Discourse/Help

Your feedback about this website is very important! Bug reports, feature
requests and other suggestions are very welcomed.

IMPORTANT

Wikimedia Developer Support is a pilot project running on a test
instance. This is not the final deployment. More about this project at
https://www.mediawiki.org/wiki/Discourse

* Although the migration of users and content to the production server is
theoretically possible, at this point it is not guaranteed (T184461).
* The authentication system for this test instance is not what will be used
if this project makes it to production.
* If you have a Wikimedia account, use the same email when registering
here. This is how your username and content will remain yours if/when
Wikimedia single sign-on is implemented (T124691).
* Do not reuse your “real” passwords when creating an account in this test
instance.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Prehackathon Olot, 2-4 Feb 2018

[Quim Gil]

On Sun, Dec 17, 2017 at 7:36 PM, Toni Hermoso Pulido <toni...@cau.cat>
wrote:

> Dear Wikimedians,
>
> as you likely know, upcoming Wikimedia Hackathon will take place in
> Barcelona from 18 to 20 May 2018*.
>
> https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018
>
> Before that event, some previous activities are being organized, among
> them a one-weekend Prehackathon in Olot (Catalonia) from 2 to 4 February
> 2018 focused on multilingualism and language technical aspects.
>
> More details at:
>
> https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2018/Prehackathon_Olot


Toni, this pre-hackathon is looking very good! Olot is a great venue
indeed, and I personally like a lot your choice of finding good places to
meet out of the metropolitan areas.

Just remember to tell international visitors that expectations of mild
Mediterranean weather will not be fulfilled in Olot around February. :D
Instead, they can enjoy the beautiful Winter that that region offers.

Just checking, have you considered advertising this pre-hackathon focusing
on internationalization / localization in Wikimedia venues more specialized
than wikitech-l?

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposal for a developer support channel

[Quim Gil]

Hi Mathieu,

This pilot doesn't have Wikimedia SUL as a requirement, but a move to
production would. For a discussion about Discourse and single sign-on, see
https://phabricator.wikimedia.org/T124691

The content license would be the same as MediaWiki.org, unless someone has
a better suggestion: https://creativecommons.org/licenses/by-sa/3.0/

On Fri, Nov 24, 2017 at 12:19 PM, mathieu stumpf guntz <
psychosl...@culture-libre.org> wrote:

>
>
> Le 19/11/2017 à 04:33, Brian Wolff a écrit :
>
>> Neither project:support_desk nor project:current_issues is really meant
>> for
>> that purpose - support desk is mainly for user and (external) sysadmin
>> support. And current_issues is the village pump of mediawiki.org (the
>> website not the software)
>>
>> Honestly, I kind of think that lqt was better than flow for support desk.
>> As much as lqt sucked at least search sort of worked.
>>
>> Although the bigger problem probably is that project:support desk is
>> protected so new users arent allowed to ask questions(!)
>>
>> On the subject of search, i do think that
>> https://lists.wikimedia.org/robots.txt is rediculous. At least for
>> technical lists we should let google in, and the privacy concern is silly
>> as there are mirrors that are indexed.
>>
> The foundation is not responsible for, possibly illegal, behaviour of
> external parties. It's not silly to disallow copyrighted content on Commons
> just because you can find them on popular website which publish them
> illegaly.
>
>
>
>> --
>> bawolff
>>
>> On Saturday, November 18, 2017, Sam Wilson <s...@samwilson.id.au> wrote:
>>
>>> Hear hear to being able to properly search past conversations.
>>>
>>> I know it's not the fashionably geek thing to say, but I must admit that
>>> I always find mailing lists to be incredibly annoying, compared to
>>> forums. Not only is searching completely separate from reading, even
>>> browsing old topics is another interface again (assuming one hasn't been
>>> subscribed forever and kept every old message). Then, when you do manage
>>> to find an old message, there's no way to reply to it (short of copying
>>> and pasting and losing context).
>>>
>>> Maybe https://www.mediawiki.org/wiki/Project:Support_desk (and its
>>> sibling https://www.mediawiki.org/wiki/Project:Current_issues ?) is the
>>> best place to ask questions about the software, its development, and
>>> other things. If so, let's make that fact much more well advertised!
>>> (Although, I think Flow is brilliant, when it's for discussing a wiki
>>> page — because the topic is already set (effectively by the title of the
>>> page its attached to). When it's trying to be a host to multiple
>>> unrelated topics, it becomes pretty annoying to use.)
>>>
>>> On Sun, 19 Nov 2017, at 05:57 AM, Niharika Kohli wrote:
>>>
>>>> I'd like to add that having Discourse will provide the one thing IRC
>>>> channels and mailing lists fail to - search capabilities. If you hangout
>>>> on
>>>> the #mediawiki IRC channel, you have probably noticed that we get a lot
>>>> of
>>>> repeat questions all the time. This would save everyone time and effort.
>>>>
>>>> Not to mention ease of use. Discourse is way more usable than IRC or
>>>> mailing lists. Usability is the main reason there are so many questions
>>>> about MediaWiki asked on Stackoverflow instead:
>>>> https://stackoverflow.com/unanswered/tagged/mediawiki
>>>> <https://stackoverflow.com/unanswered/tagged/mediawiki>,
>>>> https://stackoverflow.com/questions/tagged/mediawiki-api?sort=newest
>>>> <https://stackoverflow.com/questions/tagged/mediawiki-api?sort=newest>,
>>>> https://stackoverflow.com/questions/tagged/mediawiki-extensions...
>>>>
>>>> I'd personally hope we can stop asking developers to go to IRC or
>>>> mailing
>>>> lists eventually and use Discourse/something else as a discussion forum
>>>> for
>>>> support.
>>>>
>>>> On Sat, Nov 18, 2017 at 1:31 PM, Quim Gil <q...@wikimedia.org> wrote:
>>>>
>>>> Hi, I have expanded
>>>>> https://www.mediawiki.org/wiki/Discourse#One_place_to_
>>>>> seek_developer_support
>>>>>
>>>>> https://www.mediawiki.org/wiki/Project:Support_desk is the only
>>>>> channel
>>>>> whose main purpose is to provide support. The vo

Re: [Wikitech-l] Proposal for a developer support channel

[Quim Gil]

Hi, just a note to say that a test Discourse instance with a Sandbox for
all kinds of tests is available at https://discourse.wmflabs.org/c/Sandbox

This is an instance that Ad Huikeshoven and others set up almost a couple
of years ago to explore Discourse as a complement to mailing lists (
https://phabricator.wikimedia.org/T124690). *This is not the instance where
the developers support pilot will be run*, but it is just as good to test
Discourse.

Thanks to Sam Wilson for resuscitating this instance, and to Ad and other
promoters for setting it up in the first place.

On Mon, Nov 20, 2017 at 11:15 AM, Jan Dittrich <jan.dittr...@wikimedia.de>
wrote:

> I am admin of a discourse community (https://discourse.
> opensourcedesign.net/)
> and could answer questions about its use, if you are interested.
>
> Jan
>
>
> 2017-11-20 10:10 GMT+00:00 Florian Schmidt <
> florian.schmidt.wel...@t-online.de>:
>
> > I totally agree, that it's very unlikely, that we can solve the problem
> of
> > having newcomers ask the same questions over and over again with a
> > technical tool, however, it's probably easier for people who _wants_ to
> > search before they ask, if they've the possibility to do so. This is most
> > likely not all of the newcomers, but isn't it still worth it? :D
> >
> > Best,
> > Florian
> >
> > -Original-Nachricht-
> > Betreff: Re: [Wikitech-l] Proposal for a developer support channel
> > Datum: 2017-11-19T23:41:29+0100
> > Von: "Brad Jorsch (Anomie)" <bjor...@wikimedia.org>
> > An: "Wikimedia developers" <wikitech-l@lists.wikimedia.org>
> >
> > On Sat, Nov 18, 2017 at 4:57 PM, Niharika Kohli <nko...@wikimedia.org>
> > wrote:
> >
> > > I'd like to add that having Discourse will provide the one thing IRC
> > > channels and mailing lists fail to - search capabilities. If you
> hangout
> > on
> > > the #mediawiki IRC channel, you have probably noticed that we get a lot
> > of
> > > repeat questions all the time. This would save everyone time and
> effort.
> > >
> >
> > No discussion system I've ever seen has managed to solve the problem of
> > people asking the same question instead of searching for past replies.
> I'm
> > skeptical that this new one will be any different.
> >
> > Yes, the existing mailing lists have issues with searchability, although
> to
> > a large extent that's due to a misguided robots.txt policy preventing the
> > archives from being indexed in the first place.
> >
> >
> > --
> > Brad Jorsch (Anomie)
> > Senior Software Engineer
> > Wikimedia Foundation
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >
>
>
>
> --
> Jan Dittrich
> UX Design/ User Research
>
> Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
> Phone: +49 (0)30 219 158 26-0
> http://wikimedia.de
>
> Imagine a world, in which every single human being can freely share in the
> sum of all knowledge. That‘s our commitment.
>
> 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.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposal for a developer support channel

[Quim Gil]

On Sat, Nov 18, 2017 at 11:04 PM, Max Semenik <maxsem.w...@gmail.com> wrote:

> Who's gonna maintain this installation?
>

The current status is explained at
https://www.mediawiki.org/wiki/Discourse#Maintenance

This is a proposal coming from the Technical Collaboration team and we have
more or less everything we need to run the pilot. The draft plan already
says that in the mid term (and before moving to production) we need to
clarify what is the involvement of the Wikimedia Cloud Services team (who
also organizes developer support activities) and Operations. These
conversations are just starting with the publication of the draft plan.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposal for a developer support channel

[Quim Gil]

Hi, I have expanded
https://www.mediawiki.org/wiki/Discourse#One_place_to_seek_developer_support

https://www.mediawiki.org/wiki/Project:Support_desk is the only channel
whose main purpose is to provide support. The volunteers maintaining are
the ones to decide about its future. There is no rush for any decisions
there. First we need to run a successful pilot.

The rest of channels (like this mailing list) were created for something
else. If these channels stop receiving questions from new developers, they
will continue doing whatever they do now.

> I'd like to understand how adding a venue will improve matters.

For new developers arriving to our shores, being able to ask a first
question about any topic in one place with a familiar UI is a big
improvement over having to figure out a disseminated landscape of wiki Talk
pages, mailing lists and IRC channels (especially if they are not used to
any of these environments). The reason to propose this new space is them,
not us.

On Sat, Nov 18, 2017 at 5:01 PM, MZMcBride <z...@mzmcbride.com> wrote:

> Brian Wolff wrote:
> >On Friday, November 17, 2017, Quim Gil <q...@wikimedia.org> wrote:
> >> The Technical Collaboration team proposes the creation of a developer
> >> support channel focusing on newcomers, as part of our Onboarding New
> >> Developer program. We are proposing to create a site based on Discourse
> >> (starting with a pilot in discourse-mediawiki.wmflabs.org) and to point
> >>the many existing scattered channels there.
> >
> >What does point existing channels to discouse mean exactly? Are you
> >planning to shutdown any existing channels? If so, which ones?
>
> Excellent questions. I'd like to know the answers as well.
>
> I raised a similar point at
> <https://www.mediawiki.org/wiki/Talk:Discourse>. I skimmed
> <https://phabricator.wikimedia.org/T155678>, looking for some answers, and
> I didn't find any.
>
> Quim, are you involved in MediaWiki support in places such as the
> #mediawiki IRC channel or the mediawiki-l mailing list? Are you involved
> in MediaWiki support elsewhere? I'm trying to better understand how it
> would be appropriate for you to seemingly suggest disrupting or shutting
> down these established and functioning venues. If this is not your
> suggestion, I'd like to understand how adding a venue will improve matters.
>
> MZMcBride
>
>
>
> _______
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Proposal for a developer support channel

[Quim Gil]

Hi,

The Technical Collaboration team proposes the creation of a developer
support channel focusing on newcomers, as part of our Onboarding New
Developer program. We are proposing to create a site based on Discourse
(starting with a pilot in discourse-mediawiki.wmflabs.org) and to point the
many existing scattered channels there.

This is an initial proposal for a pilot. If the pilot is successful, we
will move it production. For that to happen we still need to sync well with
Wikimedia Cloud Services, Operations and the Wikimedia technical community.

Please check https://www.mediawiki.org/wiki/Discourse and share your
feedback.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fwd: New newsletter: Tech Showcase

[Quim Gil]

Hi Jérémie!

On Fri, Oct 13, 2017 at 7:22 PM, Jérémie Roquet <jroq...@arkanosis.net>
wrote:

> Do you think it would be possible somehow to receive the actual
> content, either by RSS (preferred) or by email (fine as well)?
>

At least for this Tech Showcase, "the actual content" is one title and one
link, by design. We don't want to write articles, just point to the action
where it is happening.

Here, I'm getting an email with only a link to a newsletter with only
> a link to the actual content. That's two levels of indirection


Yes, but the double step in this case (where the destination was a page out
of MediaWiki.org) is due to a missing feature:

Support interwiki links for new Newsletter issues
https://phabricator.wikimedia.org/T174664

When that task is solved (contributors welcome!), you will click the link
in the email or web notification, and you will land directly in the
corresponding non-MediaWiki.org page.

For now, we are trying to bypass this problem creating a topic in the Tech
Showcase Talk page, only to have a MediaWiki.org page to link to... A cheap
solution that I hope embarrasses someone enough to write a patch.  :)

We had a discussion about the ambassadors' announce format a few
> months ago (was it with Benoît or Johan? I think Benoît, but I'm not
> sure) and I already underlined how the mailing-list and RSS formats
> currently in use were great for people who have to deal with hundreds
> of notifications per week.
>
> I understand that this would mean more work for whoever writes the
> newsletter and that the mediawiki newsletter extension may not yet
> provide a way to send more content than just a title, so I'd be
> perfectly fine with a negative answer. I just want to draw attention
> to the the added cost to access the information.
>

It's a trade-off, right? Posting a newsletter issue reusing a title and a
URL that already exist takes literally one minute (in this case
https://meta.wikimedia.org/wiki/WMDE_Technical_Wishes/Edit_Conflicts/Feedback_Round_Test_Page
and the title of the email sent by Birgit to the wikitech-ambassadors
list). Writing a short informative article about the same takes more time,
enough to maybe send the notification tomorrow instead of today, or after
the weekend, or... maybe never because we are all so busy anyway. Besides,
why to write an article when the own creators already are reporting the
news in their own words so well?

The Newsletter extension allows for the distribution of traditional
newsletters (you write everything in a wiki page, you announce it when you
are done). However, the same software allows to create newsletters
consisting in... basically collections of title+link pointing to a wiki or
(some day) to any page that can be expressed with an interwiki link. Tech
Showcase bets on this new paradigm and I personally believe it is going to
be a success and a source of inspiration to others.

PS: and Brian was quicker commenting on the RSS feature request.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: New newsletter: Tech Showcase

[Quim Gil]

Dear Wikimedia developers,

TLDR: Please give this a try, subscribe, and forward the link to other
mailing lists or projects: https://www.mediawiki.org/
wiki/Newsletter:Tech_Showcase.

I am of course biased, but I do believe that this newsletter is interesting
basically for any active contributors. The simplest and easiest way to know
about interesting software being developed by staff or volunteers for our
readers and our contributors.

No tech knowledge needed and no time commitment required either. You will
just receive one sentence notifications linking to the fresh software
showcased.

PS: This is a new concept of newsletter for experienced Wikimedians as
well. The Technical Collaboration team hopes that these types of
newsletters will reach new audiences and new voices beyond the power users
following Village Pumps, mailing lists or Phabricator.


-- Forwarded message --
From: Quim Gil <q...@wikimedia.org>
Date: Fri, Oct 13, 2017 at 12:18 PM
Subject: New newsletter: Tech Showcase
To: Wikimedia Mailing List <wikimedi...@lists.wikimedia.org>


Tech curious? This is for you:

Tech Showcase <https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase>

A newsletter (*) about fresh software for Wikimedia caught on the spot.
Plans, prototypes, releases... Do you have a scoop? Tell us in the Talk
page!

Just click "Subscribe" and you will be notified in your preferred Wikimedia
wiki.
https://www.mediawiki.org/wiki/Newsletter:Tech_Showcase

(*) This is a newsletter powered by the Newsletter extension
<https://www.mediawiki.org/wiki/Help:Extension:Newsletter>. Expect one
sentence notifications linking to the tech showcased, not lengthy articles
and prose.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia-l] Diversity Award for the mentoring program of the 2017 Wikimedia Hackathon in Vienna

[Quim Gil]

FYI

-- Forwarded message --
From: Claudia Garád <claudia.ga...@wikimedia.at>
Date: Thu, Sep 28, 2017 at 3:39 PM
Subject: [Wikimedia-l] Diversity Award for the mentoring program of the
2017 Wikimedia Hackathon in Vienna
To: wikimedi...@lists.wikimedia.org


Hello everyone!

We wanted to share some good news with you: Our international team around
the Wikimedia Hackathon mentoring program won the first Austrian Open
Source Award in the category "Diversity" [1].

The Austrian Open Source Award was established this year in order to raise
awareness and visibility for our local Open Source Communities and their
projects. The jury consisted of representatives from across the various
Open Communities in Austria (Open Knowledge, Linux, and Drupal among
others) and honoured outstanding projects in the categories Open Data, Open
Software, Open Hardware, and Diversity.

The Jury particularly mentioned our comprehensive documentation under a
free license which enables other event organizers to apply our ideas and
concepts and to build on them [2] [3].
We are very happy about this positive signal for inclusive events, which
make it easier for all newcomers to join our great communities and we hope
it encourages even more people to also make our other Wikimedia events more
and more newcomer friendly. A special thanks goes to our awesome mentors
who were the heart and soul of the mentoring program and the Hackathon!

For more information about what we learned around the mentoring program you
can also check out our post from the Wikimedia Blog [4].

[1]: https://www.openminds.at/
[2]:https://www.mediawiki.org/wiki/Hackathons/Handbook
[3]:https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2017/
Mentoring_Program
[4]: https://blog.wikimedia.org/2017/05/31/vienna-hackathon-learnings/
--
Claudia Garád
Executive Director

*Wikimedia Österreich*
Stolzenthalergasse /1
1070 Wien
www.wikimedia.at

___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wik
i/Mailing_lists/Guidelines and https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] The Newsletter extension is now enabled in MediaWiki.org

[Quim Gil]

Hi, after a long long journey...
https://www.mediawiki.org/wiki/Special:Newsletters !

The Newsletter extension is a tool to facilitate subscription and delivery
of newsletters hosted on MediaWiki-based sites. You can learn more about
this extension at https://www.mediawiki.org/wiki/Help:Extension:Newsletter

Any newsletters within the scope of MediaWiki.org can be created. In
previous discussions it was agreed to only allow administrators to create
newsletters. Once a newsletter is created, their publishers can announce
new issues at will without requiring administrators anymore.

If you want to create a newsletter and you need an administrator to do it,
we will be happy to help you at
https://www.mediawiki.org/wiki/Topic:Txn15jri131au12s

If you want to report problems, request features, or get involved in the
project, please check https://phabricator.wikimedia.org/project/board/888/

PS: BIG THANK YOU to everybody involved in this project. Proper attribution
and celebration will come in a blog post summarizing these ~2,5 years of
planning, development, testing, and deployment to a first Wikimedia wiki.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Creation of a Program Committee for Wikimedia developer events

[Quim Gil]

Hi, I just proposed a session for the Wikimania Hackathon next week:

Creation of a Program Committee for Wikimedia developer events
https://phabricator.wikimedia.org/T160996

All the details are in the task. I am mentioning this here to promote the
session among those of you joining the hackathon in Montreal next week, but
most importantly to encourage feedback and discussion before the session
and by anyone anywhere. Preferably in the task itself, to avoid
fragmentation.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Labs-l] Fwd: [Affiliates] Recognition of the Wikimedia Tool Developers Group

[Quim Gil]

Hi!

On Wed, May 24, 2017 at 1:31 AM, Bryan Davis <bd...@wikimedia.org> wrote:

> On Mon, May 22, 2017 at 6:43 AM, Pine W <wiki.p...@gmail.com> wrote:
> > -- Forwarded message --
> > Date: Sun, May 21, 2017 at 5:41 PM
> > Subject: [Affiliates] Recognition of the Wikimedia Tool Developers Group
> >
> > Hi everyone!
> >
> > I'm very happy to announce that the Affiliations Committee has recognized
> > the Wikimedia Tool Developers Group [1] as a Wikimedia User Group.  The
> > group is international cooperative of developers who create
> freely-licensed
> > tools for improving the Wikimedia projects.
> >
> > Please join me in congratulating the members of this new user group!
> > (...snip...)
> > [1] https://meta.wikimedia.org/wiki/Wikimedia_Tool_Developers_Group
>
> It's really awesome for me personally to see communities like this
> form on their own. I'd like to extend an invitation to the new group
> to collaborate with the Cloud Services team [2] and the Tool Labs
> standards committee [3] in their program work. Efforts to make it
> easier for people to develop, maintain, and publicize technical
> contributions to the Wikimedia movement are important work for our
> collective future.


Indeed, I was very happy to see this new group formed as well. Let me
extend the invitation to collaborate with the Onboarding New Developers
program [4] (work in progress), where we are looking for featured projects
[5] (also WIP) willing to get help from newcomers. Tools are clearly a good
entry point for developers approaching Wikimedia with a fresh mind and new
ideas. Current tool developers could also benefit more from our developer
support and activities. Having a representative group might definitely
help. Let's talk!


> [2]: https://www.mediawiki.org/wiki/Wikimedia_Cloud_Services_team
> [3]: https://wikitech.wikimedia.org/wiki/Help:Tool_Labs/Tool_
> Labs_standards_committee


[4]:
https://meta.wikimedia.org/wiki/Technical_Collaboration/Onboarding_New_Developers
[5]: https://www.mediawiki.org/wiki/Featured_Projects


>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation<bd...@wikimedia.org>
> [[m:User:BDavis_(WMF)]] Manager, Cloud Services  Boise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> _______
> Labs-l mailing list
> lab...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Code of Conduct Committee for Wikimedia technical spaces constituted!

[Quim Gil]

Hello everybody,

The Code of Conduct Committee
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee_members>
bootstrapping
process has been completed. Some intermediate updates were posted in
phab:T159923 <https://phabricator.wikimedia.org/T159923>. Starting today,
the Code of Conduct for Wikimedia technical spaces is enforced by the new
Committe formed by Amir Sarabadani (Ladsgroup
<https://www.mediawiki.org/wiki/User:Ladsgroup>), Lucie-Aimée Kaffee (
Frimelle <https://www.mediawiki.org/wiki/User:Frimelle>), Nuria Ruiz (
Nurieta <https://www.mediawiki.org/wiki/User:Nurieta>), Sébastien Santoro (
Dereckson <https://www.mediawiki.org/wiki/User:Dereckson>), and Tony Thomas
(01tonythomas <https://www.mediawiki.org/wiki/User:01tonythomas>).
Congratulations to them, to the additional five auxiliary members
<https://www.mediawiki.org/wiki/Code_of_Conduct/Committee_members#Auxiliary>
 (Απεργός, Léna, Florianschmidtwelzow, Huji, Matanya), and to everybody
else who contributed to this process!

Source:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#Process_completed.2C_CoC_Commitee_constituted


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

[Quim Gil]

Sorry for being so late replying. Isarra asks a good question and I have
been thinking of a good answer.

On Thu, Apr 27, 2017 at 8:35 PM, Isarra Yos <zhoris...@gmail.com> wrote:

> Different events serve very different purposes, though - hackathons, for
> instance, seem to be largely useful for onboarding newcomers and giving
> staff and other occupational contributors an opportunity to work on
> projects separate from their usual work, basically whatever they feel like
> doing, as opposed to what they have to. But these often don't do much for
> established volunteers, as a result, who generally just work on whatever
> they feel like all the time already. Have you looked into how the roles of
> these different events fit together across all the different groups, and
> how scopes affect them (regional, topical, etc)? This would also be useful
> for chapters/groups planning their own events.


Yes, we have started to think seriously how the different developer events
fit together, how can they support better each other, and how can chapters
and other affiliates get better involved organizing local / regional events
or adding a tech component to the events they are already organizing.

Until recently our approach has been quite fragmented, organizing
technically successful events disconnected from each other. We started a
new trend last Summer, at the Wikimania Hackathon in Esino Lario,
discussing with Wikimedia Austria how could we improve the Wikimedia
Hackathon 2017 (in Vienna, in two weeks) after the high bar set by
Wikimedia Israel in Jerusalem. We had this idea of supporting the
organization of smaller hackathons and sponsoring the best participants to
travel to Vienna. The idea is working so far.

Growth paths for volunteers is another idea that has become very important
in our strategy and plans. While we seem to be quite good at organizing
developer events, developer outreach programs, developer community
support... the fact is that we are not doing good at retaining new
volunteer developers. Many come, but most leave. And there are many reasons
for this, but we think that an important one is that we are not offering
clear growth paths that make people stick around. Some volunteers find
these growth paths themselves, and we have many examples in this list, but
many simply don't see them and leave.

Developer events play an important role in these growth paths. Imagine that
a chapter or even a small affiliate organizes a simple local workshop
somewhere. One of the best participants, a total newcomer to Wikimedia
although a fluent JavaScript developer, is invited to travel to the next
hackathon in the nearest regional event (WikiArabia, WikiIndaba, the CEE
conference...) There, the best developers are invited to one of our global
hackathons (invited to South Africa in 2018, how cool is that!?!?).

Actually, the growth paths through events can be connected with related
online activities (self-paced, scheduled), which allows us to work with
more people beyond travel budget and people's possibilities with travel and
calendars. We can also connect them with developer outreach programs (GSoC,
Outreachy...). Who was a newcomer becomes more experienced, maybe a speaker
or a trainer invited to online / offline events, maybe a maintainer, maybe
a mentor, maybe grantee, a professional developer at Wikimedia...

OK, all these are ideas in progress that we are starting to put together at
https://meta.wikimedia.org/wiki/Technical_Collaboration/Onboarding_New_Developers

Now, back to the Summit. The Wikimedia Developer Summit never was an event
crucial for onboarding new developers, and in fact it was not an event easy
to involve volunteers, because of its location (expensive San Francisco, in
a region where there are not many volunteer developers) and also because
the topics were quite focused on what is work mostly for professional
developers (see our cyclic discussions about how to integrate volunteer
developers and the topics crucial for them).

We have tried in several editions, and it has been very difficult to obtain
a mild success. Instead, now we are trying to bring some of the "Summit
topics" to those hackathons based on who is attending anyway (or vice
versa) and then we can focus the Summit around a specific topic and the
people specializing on it, in the terms explained by Victoria. What topics
will be discussed where will be decided by a program committee that will be
active through the year, helping to provide this connection across events
(see https://phabricator.wikimedia.org/T160996 )

Sorry for the long response. It is the first time I write down all these
ideas in a single place. Feedback is very welcome.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Phabricator monthly statistics - 2017-04

[Quim Gil]

On Mon, May 1, 2017 at 2:00 AM, <communitymetr...@wikimedia.org> wrote:

> Tasks created in (2017-04): 2239
> Tasks closed in (2017-04): 2391


More closed than opened? Celebration!

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Presentation Code of Conduct Committee candidates and community review

[Quim Gil]

Hi,

The community review period for the Code of Conduct candidates is over, and
we haven't received any feedback challenging the candidates proposed.
Therefore, all they are confirmed now. Congratulations!

Committee members:

   -

   Amir Sarabadani (Ladsgroup)
   -

   Lucie-Aimée Kaffee (Frimelle)
   -

   Nuria Ruiz (NRuiz-WMF)
   -

   Sébastien Santoro (Dereckson)
   -

   Tony Thomas (01tonythomas)


Auxiliary members:

   -

   Ariel Glenn (ArielGlenn)
   -

   Caroline Becker (Léna)
   -

   Florian Schmidt (Florianschmidtwelzow)
   -

   Huji
   -

   Matanya


https://www.mediawiki.org/wiki/Code_of_Conduct/Committee_members has been
updated accordingly.

Following the process described in the Code of Conduct for Wikimedia
technical spaces <https://www.mediawiki.org/wiki/Code_of_Conduct>, the new
Committee will be constituted six weeks after the nomination of candidates,
on 20 May.

Between now and then the new members will go through some training and
paperwork. You can follow the details at
https://phabricator.wikimedia.org/T159923.

I expect to send the next and last update about this bootstrapping process
when the Committee is constituted.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Wikimedia Hackathon 2018: Looking for Proposals

[Quim Gil]

Hi,

Amical Wikimedia has posted a proposal to organize the Wikimedia Hackathon
2018

https://phabricator.wikimedia.org/T162836

Your reviews and feedback are welcome, in the Phabricator task (preferred)
or here.


On Wed, Feb 8, 2017 at 2:28 AM, Rachel Farrand <rfarr...@wikimedia.org>
wrote:

> Hello!
>
> Is your organization interested in hosting and co-organizing the 2018
> Wikimedia Hackathon? We are looking for proposals!
>
>
> Hackathon information:
>
> Specific to the 2018 Hackathon
>
>
>- *https://www.mediawiki.org/wiki/Hackathons/2018_Decision_Process
><https://www.mediawiki.org/wiki/Hackathons/2018_Decision_Process>*
>- *https://www.mediawiki.org/wiki/Hackathons/Proposing_a_
> hackathon#Hackathon_location_decision_process_for_2018
><https://www.mediawiki.org/wiki/Hackathons/Proposing_a_
> hackathon#Hackathon_location_decision_process_for_2018>*
>
>
> All Hackathons
>
>
>- https://www.mediawiki.org/wiki/Hackathons
>- https://www.mediawiki.org/wiki/Hackathon_101
>- https://www.mediawiki.org/wiki/Hackathons/Hackathon_
> tips_for_organizers
>
>
> This year’s Wikimedia Hackathon 2017
> <https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2017> will be held in
> Vienna, Austria from 19-21 May. Ideally we will announce the host for 2017
> before the end of March, 2017 so that the 2018 organizers can attend the
> Vienna Hackathon and start gathering ideas. If multiple chapters or
> organizations are interested, we hope to work together to figure out the
> the best solution.
>
> Any organizations interested in hosting should please create a Phabricator
> ticket and associate it with the Developer-Relations project. Srishti and I
> are happy to assist if needed.
>
> Examples: https://phabricator.wikimedia.org/T96826,
> https://phabricator.wikimedia.org/T127050
>
> Include as much information as possible from: proposing a hackathon
> <https://www.mediawiki.org/wiki/Hackathons/Proposing_a_hackathon>
>
> Please email me at rfarr...@wikimedia.org with any questions or concerns.
> I
> am not on the chapters@ list, so if there is anything that I should
> respond
> to, make sure to keep me on CC. Also please forward this email anywhere you
> think it might be useful.
>
>
> Looking forward to hearing from you!
>
> Rachel Farrand
> Events and Program Manager
> Wikimedia Foundation
> ___
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: wikimedi...@lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>




-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

[Quim Gil]

On Sun, Apr 9, 2017 at 1:14 AM, Quim Gil <q...@wikimedia.org> wrote:

> Hi, the Wikimedia Foundation has published a draft of its Annual Plan
> FY2017-18
> <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft>
> and it welcomes your review.
>
> I want to highlight here the improvements that we are proposing to the
> developer events (co)organized by the WMF. From local to global:
>
> The Technical Collaboration team proposes to combine multiple activities
> (often disconnected) in a single program focusing on onboarding new
> developers
> <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Community_Engagement#Program_12:_Onboarding_new_developers>.
>  We
> want to work with the Wikimedia technical community to bring a new wave of
> developers to our projects, and events play an important role.
>
> Local developer events
> We want to support developers and organizations willing to reach out to
> specific groups and geographies. We are hoping to see many local developer
> meetups and small hackathons or workshops around the World, starting small
> and simple. We should be able to offer introductory materials, contacts
> with Wikimedia developers in the region, maybe travel budget to send
> experienced volunteers to help mentoring the in the bigger events, maybe
> travel budget to invite the best newcomers to our regional and global
> events.
>
> Adding tech to regional Wikimedia events
> Last year we experimented organizing technical workshops in WikiArabia,
> and others have done similar efforts in other regional events (for
> instance, a small hackathon next to WikiConference India). We want to work
> with the organizers of these regional events in order to attract
> experienced Wikimedia developers and newcomers, organize developer
> activities, and also improve the collaboration between the technical and
> non-technical contributors in these regions.
>
> Better retention of newcomers at the Wikimedia and Wikimania hackathons
> Although we don't expect major changes in the organization of the
> Wikimedia Hackathon and the hackathon at Wikimania, we want to focus better
> on new developers onboarding and retention. In every Hackathon we meet many
> new developers, but the retention rates are very low. We want to review
> what we can do before, during, and after these apparently successful events
> in order to retain newcomers better. One hypothesis is that we should focus
> call for participation, scholarships, and Wikimedia Foundation
> participation in providing a great experience to new volunteers who have
> gone through local and regional events, and also "junior" developers coming
> from wiki projects through the development of bots, gadgets, tools,
> templates.
>
> A smaller and more focused Wikimedia Developer Summit
> After some discussions between Community Engagement, Technology, and
> Product, we have decided to propose a different approach for the Wikimedia
> Developer Summit. Organized by the Technology department as part of their 
> technical
> community building
> <https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Technology#Program_4:_Technical_community_building>
> efforts, we want the Summit to finally become the venue where the toughest
> technical problems are discussed between the stakeholders directly related.
> We want to reduce the size/budget of the event, separate it from the WMF
> AllHands,
>

Due to travel budget considerations, the Summit still might be connected to
the WMF AllHands.


> and define its main themes well in advance.
>
> A Program Committee <https://phabricator.wikimedia.org/T160996> would
> decide these main themes to be discussed at the Summit. We also want to
> explore the possibility of tackling some of these themes at the Wikimedia
> Hackathon and Wikimania, where we could get most stakeholders involved with
> just a little extra effort (since many of them would be attending anyway).
>
> We believe that this approach will serve better the Wikimedia technical
> community that we have, and also the the community that we want to have,
> with a new wave of developers joining our various projects.
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Presentation Code of Conduct Committee candidates and community review

[Quim Gil]

Hi, just a reminder: the community review of the proposed list of
candidates to form the first Code of Conduct Committee for Wikimedia
technical spaces ends this weekend.

On Sat, Apr 8, 2017 at 12:44 AM, Quim Gil <q...@wikimedia.org> wrote:

> Following the process described in the Code of Conduct for Wikimedia
> technical spaces <https://www.mediawiki.org/wiki/Code_of_Conduct>, the
> Wikimedia Foundation’s Technical Collaboration team has selected five
> candidates to form the first Code of Conduct Committee and five candidates
> to become auxiliary members.
>
> Here you have their names in alphabetical order. For details about each
> candidate, please check https://www.mediawiki.org/wiki/Code_of_Conduct/
> Committee_members
>
> Committee member candidates:
>
>-
>
>Amir Sarabadani (Ladsgroup)
>-
>
>Lucie-Aimée Kaffee (Frimelle)
>-
>
>Nuria Ruiz (NRuiz-WMF)
>-
>
>Sébastien Santoro (Dereckson)
>-
>
>Tony Thomas (01tonythomas)
>
>
> Auxiliary member candidates:
>
>-
>
>Ariel Glenn (ArielGlenn)
>-
>
>Caroline Becker (Léna)
>-
>
>Florian Schmidt (Florianschmidtwelzow)
>-
>
>Huji
>-
>
>Matanya
>
>
> This list of candidates is subject to a community review period of two
> weeks starting today. If no major objections are presented about any
> candidate, they will be appointed in six weeks.
>
> You can provide feedback on these candidates, via private email to
> techconductcandida...@wikimedia.org. This feedback will be received by
> the Community Health
> <https://meta.wikimedia.org/wiki/Technical_Collaboration/Community_health>
> group handling this process, and will be treated with confidentiality.
>
> We want to thank all the people who has considered the possibility to
> support the Code of Conduct with their participation in this Committee. 77
> persons have been contacted during the selection process, counting
> self-nominations and recommendations. From these, 21 made it to a short
> list of candidates confirmed and (according to our estimation) a potential
> good fit for the Committee. Selecting the five candidates for the Committee
> has been hard, as we have tried to form a diverse group that could work
> together effectively in the consolidation of the Code of Conduct. Selecting
> the five auxiliary members has been even harder, and we know that we have
> left out candidates who could have contributed just as much. Being the
> first people assuming these roles, we have tended a bit towards more
> technical profiles with good knowledge of our technical spaces. We believe
> that future renewals will offer better chances to other profiles (not so
> technical and/or not so Wikimedia veteran), adding a higher diversity and
> variety of perspectives to the mix.
>
>
> On Thu, Mar 9, 2017 at 12:30 PM, Quim Gil <q...@wikimedia.org> wrote:
>
>> Dear Wikimedia technical community members,
>>
>> https://www.mediawiki.org/wiki/Code_of_Conduct
>>
>> The review of the Code of Conduct for Wikimedia technical spaces has been
>> completed and now it is time to bootstrap its first committee. The
>> Technical Collaboration team is looking for five candidates to form the
>> Committee plus five additional auxiliary members. One of them could be you
>> or someone you know!
>>
>> You can propose yourself as a candidate and you can recommend others
>> *privately* at
>> techconductcandidates AT wikimedia DOT org
>>
>> We want to form a very diverse list of candidates reflecting the variety
>> of people, activities, and spaces in the Wikimedia technical community. We
>> are also open to other candidates with experience in the field. Diversity
>> in the Committee is also a way to promote fairness and independence in
>> their decisions. This means that no matter who you are, where you come
>> from, what you work on, or for how long, you are a potential good member of
>> this Committee.
>>
>> The main requirements to join the Committee are a will to foster an open
>> and welcoming community and a commitment to making participation in
>> Wikimedia technical projects a respectful and harassment-free experience
>> for everyone. The committee will handle reports of unacceptable behavior,
>> will analyze the cases, and will resolve on them according to the Code of
>> Conduct. The Committee will also handle proposals to amend the Code of
>> Conduct for the purpose of increasing its efficiency. The term of this
>> first Committee will be one year.
>>
>> Once we have a list of 5 + 5 candidates, we will announce it he

[Wikitech-l] Improvements to developer events in the WMF Annual Plan draft

[Quim Gil]

Hi, the Wikimedia Foundation has published a draft of its Annual Plan
FY2017-18
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft>
and it welcomes your review.

I want to highlight here the improvements that we are proposing to the
developer events (co)organized by the WMF. From local to global:

The Technical Collaboration team proposes to combine multiple activities
(often disconnected) in a single program focusing on onboarding new
developers
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Community_Engagement#Program_12:_Onboarding_new_developers>.
We
want to work with the Wikimedia technical community to bring a new wave of
developers to our projects, and events play an important role.

Local developer events
We want to support developers and organizations willing to reach out to
specific groups and geographies. We are hoping to see many local developer
meetups and small hackathons or workshops around the World, starting small
and simple. We should be able to offer introductory materials, contacts
with Wikimedia developers in the region, maybe travel budget to send
experienced volunteers to help mentoring the in the bigger events, maybe
travel budget to invite the best newcomers to our regional and global
events.

Adding tech to regional Wikimedia events
Last year we experimented organizing technical workshops in WikiArabia, and
others have done similar efforts in other regional events (for instance, a
small hackathon next to WikiConference India). We want to work with the
organizers of these regional events in order to attract experienced
Wikimedia developers and newcomers, organize developer activities, and also
improve the collaboration between the technical and non-technical
contributors in these regions.

Better retention of newcomers at the Wikimedia and Wikimania hackathons
Although we don't expect major changes in the organization of the Wikimedia
Hackathon and the hackathon at Wikimania, we want to focus better on new
developers onboarding and retention. In every Hackathon we meet many new
developers, but the retention rates are very low. We want to review what we
can do before, during, and after these apparently successful events in
order to retain newcomers better. One hypothesis is that we should focus
call for participation, scholarships, and Wikimedia Foundation
participation in providing a great experience to new volunteers who have
gone through local and regional events, and also "junior" developers coming
from wiki projects through the development of bots, gadgets, tools,
templates.

A smaller and more focused Wikimedia Developer Summit
After some discussions between Community Engagement, Technology, and
Product, we have decided to propose a different approach for the Wikimedia
Developer Summit. Organized by the Technology department as part of
their technical
community building
<https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_Plan/2017-2018/Draft/Programs/Technology#Program_4:_Technical_community_building>
efforts, we want the Summit to finally become the venue where the toughest
technical problems are discussed between the stakeholders directly related.
We want to reduce the size/budget of the event, separate it from the WMF
AllHands, and define its main themes well in advance.

A Program Committee <https://phabricator.wikimedia.org/T160996> would
decide these main themes to be discussed at the Summit. We also want to
explore the possibility of tackling some of these themes at the Wikimedia
Hackathon and Wikimania, where we could get most stakeholders involved with
just a little extra effort (since many of them would be attending anyway).

We believe that this approach will serve better the Wikimedia technical
community that we have, and also the the community that we want to have,
with a new wave of developers joining our various projects.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Presentation Code of Conduct Committee candidates and community review

[Quim Gil]

Following the process described in the Code of Conduct for Wikimedia
technical spaces <https://www.mediawiki.org/wiki/Code_of_Conduct>, the
Wikimedia Foundation’s Technical Collaboration team has selected five
candidates to form the first Code of Conduct Committee and five candidates
to become auxiliary members.

Here you have their names in alphabetical order. For details about each
candidate, please check
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee_members

Committee member candidates:

   -

   Amir Sarabadani (Ladsgroup)
   -

   Lucie-Aimée Kaffee (Frimelle)
   -

   Nuria Ruiz (NRuiz-WMF)
   -

   Sébastien Santoro (Dereckson)
   -

   Tony Thomas (01tonythomas)


Auxiliary member candidates:

   -

   Ariel Glenn (ArielGlenn)
   -

   Caroline Becker (Léna)
   -

   Florian Schmidt (Florianschmidtwelzow)
   -

   Huji
   -

   Matanya


This list of candidates is subject to a community review period of two
weeks starting today. If no major objections are presented about any
candidate, they will be appointed in six weeks.

You can provide feedback on these candidates, via private email to
techconductcandida...@wikimedia.org. This feedback will be received by
the Community
Health
<https://meta.wikimedia.org/wiki/Technical_Collaboration/Community_health>
group handling this process, and will be treated with confidentiality.

We want to thank all the people who has considered the possibility to
support the Code of Conduct with their participation in this Committee. 77
persons have been contacted during the selection process, counting
self-nominations and recommendations. From these, 21 made it to a short
list of candidates confirmed and (according to our estimation) a potential
good fit for the Committee. Selecting the five candidates for the Committee
has been hard, as we have tried to form a diverse group that could work
together effectively in the consolidation of the Code of Conduct. Selecting
the five auxiliary members has been even harder, and we know that we have
left out candidates who could have contributed just as much. Being the
first people assuming these roles, we have tended a bit towards more
technical profiles with good knowledge of our technical spaces. We believe
that future renewals will offer better chances to other profiles (not so
technical and/or not so Wikimedia veteran), adding a higher diversity and
variety of perspectives to the mix.


On Thu, Mar 9, 2017 at 12:30 PM, Quim Gil <q...@wikimedia.org> wrote:

> Dear Wikimedia technical community members,
>
> https://www.mediawiki.org/wiki/Code_of_Conduct
>
> The review of the Code of Conduct for Wikimedia technical spaces has been
> completed and now it is time to bootstrap its first committee. The
> Technical Collaboration team is looking for five candidates to form the
> Committee plus five additional auxiliary members. One of them could be you
> or someone you know!
>
> You can propose yourself as a candidate and you can recommend others
> *privately* at
> techconductcandidates AT wikimedia DOT org
>
> We want to form a very diverse list of candidates reflecting the variety
> of people, activities, and spaces in the Wikimedia technical community. We
> are also open to other candidates with experience in the field. Diversity
> in the Committee is also a way to promote fairness and independence in
> their decisions. This means that no matter who you are, where you come
> from, what you work on, or for how long, you are a potential good member of
> this Committee.
>
> The main requirements to join the Committee are a will to foster an open
> and welcoming community and a commitment to making participation in
> Wikimedia technical projects a respectful and harassment-free experience
> for everyone. The committee will handle reports of unacceptable behavior,
> will analyze the cases, and will resolve on them according to the Code of
> Conduct. The Committee will also handle proposals to amend the Code of
> Conduct for the purpose of increasing its efficiency. The term of this
> first Committee will be one year.
>
> Once we have a list of 5 + 5 candidates, we will announce it here for
> review. You can learn more about the Committee and its selection process at
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask
> questions in the related Talk page (preferred) or here.
>
> You can also track the progress of this bootstrapping process at
> https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#
> Bootstrapping_the_Code_of_Conduct_Committee
>
> PS: We have many technical spaces and reaching to all people potentially
> interested is hard! Please help spreading this call.
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
>



-- 
Quim Gil
Engineering Community Manager @ Wikimed

Re: [Wikitech-l] Call for candidates to form the first Code of Conduct Committee

[Quim Gil]

Source:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#Selection_process_for_CoC_Committee_candidates

Status update: 76 people have been contacted, from which 17 are currently
potential candidates. We are still accepting self-nominations and
recommendations until the end of Monday, April 3rd. We consider our own
outreach completed, and we have started to evaluate potential candidates.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Call for candidates to form the first Code of Conduct Committee

[Quim Gil]

Source: https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#
Selection_process_for_CoC_Committee_candidates

Status update: 37 people have been contacted so far, from which 32 are
currently potential candidates. 6 people are self-nominated, 18 have been
recommended, and 13 have been invited by us. We have started to discuss
selection criteria. With our focus on diversity in mind, we are trying to
cover fairly well aspects like gender, age, location, languages,
affiliation, developer experience, Wikimedia experience, and areas of
specialization.

We are still reaching out to new candidates and we welcome more
self-nominations and recommendations. Instructions:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#Call_for_candidates_to_form_the_first_Code_of_Conduct_Committee

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

[Quim Gil]

On Wed, Mar 15, 2017 at 2:48 AM, Pine W <wiki.p...@gmail.com> wrote:

> Quim,
>
> Thanks for the comments.
>
> A brief note about the goal of "there are no clashes between product
> development teams and communities". That is an ambitious goal around here,
> partly because there are changes planned and happening concurrently in so
> many places that I think it would be a challenge to surface all potential
> conflicts early and make them visible to relevant community members. (As an
> example, a change that might be received favorably on Wiki A might generate
> a commotion on Wiki B because it broke an existing tool, made an existing
> workflow take longer, or conflicts with their community's priorities.


"No clashes" is a complex target indeed, but it is feasible.

It is important to have a definition of clash. Wiktionary offers "a hostile
encounter" and "an angry argument", among others. Discrepancies and ongoing
discussions don't constitute automatically a clash, as long as
collaboration keeps happening.

For instance, your example of a new feature breaking a popular tool would
be certainly a problem, but it would not constitute a clash if the new
feature or the the tool are fixed quickly after the problem is reported, or
the new feature is pulled until a solution is found.


> A current example of this kind of situation is with Flow, which the last I
> heard is viewed favorably on Catalan Wikipedia and unfavorably on English
> Wikipedia).


A discussion in English Wikipedia ended up with the removal of Flow from
that project with the agreement and the patches of the Flow developers.
That would still count as collaboration, not a clash. Sometimes
collaboration is not easy, but the parties still agree on finding the best
next step together.


> I'm not sure that clashes can be 100% prevented, but I'm
> thinking that once the Newsletter extension is working, that might be a
> useful way of informing more interested people in a more timely fashion
> about planned changes, and encouraging people to enroll as beta testers and
> translators, so that there are fewer surprises.
>

I fully agree with you. I personally have big hopes in the Newsletter
extension enabling several specialized points of notifications, allowing
more volunteers with more different interests and backgrounds to be
informed about news and call for feedback interesting to them. Nowadays we
rely too much on generic channels only (Village Pumps, mailing lists...),
and this limits a lot the participation of qualified volunteers not having
the time, patience or desire to join them.

Reaching out to more volunteers sooner and through specialized channels
might prevent the risk of clashes better, not only because more problems
can be detected before, also because discussions can become richer with
more perspectives and experiences.


> I think that what might be a more readily solvable problem would be a
> standardized way of resolving clashes between product teams and communities
> so that, when such clashes almost inevitably happen at some point,
> resolution comes sooner rather than later and hopefully in a way that is
> mutually acceptable. Perhaps that could be discussed in the Technical
> Collaboration Guidance document.
>

This is the intend of
https://www.mediawiki.org/wiki/Technical_Collaboration_Guidance/Community_decisions
and suggestions are welcomed in the Talk page.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Call for candidates to form the first Code of Conduct Committee

[Quim Gil]

Source:
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#Selection_process_for_CoC_Committee_candidates


The call for CoC Committee candidates was announced one week ago. Here goes
a status update.

We
<https://meta.wikimedia.org/wiki/Technical_Collaboration/Community_health>
have received some self-nominations and some recommendations, and we have
shared next steps with all the candidates involved. We have also received
some questions, which we are documenting at
https://www.mediawiki.org/wiki/Code_of_Conduct/FAQ#Committee

We are starting our own search for additional candidates to be invited. Our
current objective is to complete a list of potential candidates. Once we
have a good list, we will start the selection process.

Diversity is the key factor in the Committee that we envision. One way to
search for diverse candidates is to look into different areas in our
technical community, and try to look well in each of these areas (as
opposed to relying on generic lists only, like code review contributors,
participants in hackathons, and so on). The list of areas we have so far
(which welcomes suggestions) is:

* Bots
* CoC Talk page
* Code contributors / reviewers
* Gadgets
* GSoC / Outreachy / GCi
* MediaWiki Stakeholders
* Researchers
* Tech ambassadors / Bug reporters
* Templates / Lua modules
* Tools
* Translators
* Wikidata
* Wikimedia Foundation

The important points about the selection process are:

* We will have a conversation with each candidate selected before the
announcement; we will not announce any candidate before their confirmation
and review.
* Only the candidates selected will be announced publicly; the full list of
candidates will remain private.

Questions or feedback? Please comment here or privately at
techconductcandidates AT wikimedia.org.


On Thu, Mar 9, 2017 at 12:30 PM, Quim Gil <q...@wikimedia.org> wrote:

> Dear Wikimedia technical community members,
>
> https://www.mediawiki.org/wiki/Code_of_Conduct
>
> The review of the Code of Conduct for Wikimedia technical spaces has been
> completed and now it is time to bootstrap its first committee. The
> Technical Collaboration team is looking for five candidates to form the
> Committee plus five additional auxiliary members. One of them could be you
> or someone you know!
>
> You can propose yourself as a candidate and you can recommend others
> *privately* at
> techconductcandidates AT wikimedia DOT org
>
> We want to form a very diverse list of candidates reflecting the variety
> of people, activities, and spaces in the Wikimedia technical community. We
> are also open to other candidates with experience in the field. Diversity
> in the Committee is also a way to promote fairness and independence in
> their decisions. This means that no matter who you are, where you come
> from, what you work on, or for how long, you are a potential good member of
> this Committee.
>
> The main requirements to join the Committee are a will to foster an open
> and welcoming community and a commitment to making participation in
> Wikimedia technical projects a respectful and harassment-free experience
> for everyone. The committee will handle reports of unacceptable behavior,
> will analyze the cases, and will resolve on them according to the Code of
> Conduct. The Committee will also handle proposals to amend the Code of
> Conduct for the purpose of increasing its efficiency. The term of this
> first Committee will be one year.
>
> Once we have a list of 5 + 5 candidates, we will announce it here for
> review. You can learn more about the Committee and its selection process at
> https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask
> questions in the related Talk page (preferred) or here.
>
> You can also track the progress of this bootstrapping process at
> https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#
> Bootstrapping_the_Code_of_Conduct_Committee
>
> PS: We have many technical spaces and reaching to all people potentially
> interested is hard! Please help spreading this call.
>
>
-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Status of Technical Collaboration Guidance discussion

[Quim Gil]

Hi,

On Sun, Mar 12, 2017 at 10:24 AM, Rogol Domedonfors <domedonf...@gmail.com>
wrote:

> If there's not going to be anything to implement, how do you see this as
> having an effect on anything?


Documenting and promoting best practices tends to be useful for the
awareness, adoption and refinement of those best practices.

Pine's answer about guidance/policies in Wikimedia is useful, thank you.


>   What will be done differently or better?
>

The goal is to have more consistent and predictable communication and
decision processes across software projects and communities, allowing for
an increase in awareness and involvement by a wider variety of volunteers,
and the detection of requests and problems in the early stages of
development.


> Why should anyone be doing any work on it?


Because the current communication, discussion, and decision processes are
not as systematic as we wish, this reduces the quantity and diversity of
volunteers engaged, and therefore the quality and efficacy of the
collaboration between product development teams and communities.



> How will we know whether or not
> it has been a success, and whther or not the time effort and effort was
> well-spent?
>

Good question. I think we can consider the TCG as a useful tool when

* a healthy number of wiki projects want to be early adopters of new
features
* a healthy number of wiki projects have volunteers facilitating
communication as tech ambassadors or translators
* product development teams without a community liaison can successfully
organize their community engagement activities following best practices
* satisfaction levels about community engagement in product development are
high
* there are no clashes between product development teams and communities

There are other ideas about targets and metrics being discussed at
https://phabricator.wikimedia.org/T132499

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Call for candidates to form the first Code of Conduct Committee

[Quim Gil]

Dear Wikimedia technical community members,

https://www.mediawiki.org/wiki/Code_of_Conduct

The review of the Code of Conduct for Wikimedia technical spaces has been
completed and now it is time to bootstrap its first committee. The
Technical Collaboration team is looking for five candidates to form the
Committee plus five additional auxiliary members. One of them could be you
or someone you know!

You can propose yourself as a candidate and you can recommend others
*privately* at
techconductcandidates AT wikimedia DOT org

We want to form a very diverse list of candidates reflecting the variety of
people, activities, and spaces in the Wikimedia technical community. We are
also open to other candidates with experience in the field. Diversity in
the Committee is also a way to promote fairness and independence in their
decisions. This means that no matter who you are, where you come from, what
you work on, or for how long, you are a potential good member of this
Committee.

The main requirements to join the Committee are a will to foster an open
and welcoming community and a commitment to making participation in
Wikimedia technical projects a respectful and harassment-free experience
for everyone. The committee will handle reports of unacceptable behavior,
will analyze the cases, and will resolve on them according to the Code of
Conduct. The Committee will also handle proposals to amend the Code of
Conduct for the purpose of increasing its efficiency. The term of this
first Committee will be one year.

Once we have a list of 5 + 5 candidates, we will announce it here for
review. You can learn more about the Committee and its selection process at
https://www.mediawiki.org/wiki/Code_of_Conduct/Committee and you can ask
questions in the related Talk page (preferred) or here.

You can also track the progress of this bootstrapping process at
https://www.mediawiki.org/wiki/Talk:Code_of_Conduct#Bootstrapping_the_Code_of_Conduct_Committee

PS: We have many technical spaces and reaching to all people potentially
interested is hard! Please help spreading this call.

--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Code of Conduct for Wikimedia technical spaces now out of draft state

[Quim Gil]

On Tue, Mar 7, 2017 at 8:16 PM, Brion Vibber <bvib...@wikimedia.org> wrote:

> Per the last round of discussion & votes closing on the amendments section
> some days back, the draft period for the Code of Conduct for technical
> spaces is complete.
>
> I've taken the liberty of removing the 'draft' template and moving the
> pages out of their "/Draft" subpage location to their final locations:
>
> * https://www.mediawiki.org/wiki/Code_of_Conduct
> * https://www.mediawiki.org/wiki/Code_of_Conduct/Cases
> * https://www.mediawiki.org/wiki/Code_of_Conduct/Committee
> * https://www.mediawiki.org/wiki/Code_of_Conduct/Amendments
>
> As I understand, this means the committee will be bootstrapping soon --
> Quim will have more information on the state of things there.
>
> Thanks to everybody for all your input over the last many months.
>

Thank you very much, Brion!

I will announce a call for candidates to join the first Committee,
explaining the next steps as described in the Code of Conduct.

The CoC content is frozen until the Committee starts exercising as such and
the amendments process kicks off. Small edits to i.e. fix red links,
improve navigation to subpages and similar technical improvements are
possible, as long as the content remains untouched.

I also want to thank all contributors, also those who have been watching
the process from a distance (this morning I was checking the page view
statistics, quite impressive for a community of this size). Special thanks
to Matt and Moriel , who have contributed so much, all along, since the
beginning, every week.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Results of the Developer Wishlist are in

[Quim Gil]

On Wed, Feb 15, 2017 at 3:32 AM, Gergo Tisza <gti...@wikimedia.org> wrote:

> Hi all,
>
> voting for the Developer Wishlist [1] has ended. Thanks to everyone who
> participated! And extra thanks to everyone who helped. [2] You can find the
> the results, with links to the full proposals, at:
>
> https://www.mediawiki.org/wiki/User:Community_Tech_bot/
> WishlistSurvey/Votes
>
> As you might have read on the wishlist page, this is a primarily-volunteer
> run experiment. It can only be successful with your help! [3] If you can
> afford the time, please look through the highly-voted propsals and see if
> you can find something you would be interested to work on. I also invite
> everyone to participate in these three follow-up tasks:
>
> https://phabricator.wikimedia.org/T158148 - promote wishlist proposals
> https://phabricator.wikimedia.org/T158149 - find owners for the top10
> proposals
> https://phabricator.wikimedia.org/T158150 - post-mortem
>
>
> thanks
> Gergő
>

Thank *you* very much, Gergő! The first wish of the Developer Wishlist was
to have a Developer Wishlist in the first place. You proposed, promoted,
engaged with others, and worked a damn lot. You made it!

Now it's the turn for the rest of us. I am going to ask the Foundation's
technical management to have this wishlist in mind in the annual plan
discussion that are happening right now. I will discuss with my team which
wishes we could / should commit to.



>
>
> [1] https://www.mediawiki.org/wiki/Developer_Wishlist
> [2] Including, but not limited to: Srishti Sethi who handled most of the
> communications; Quim Gil and James Forrester who helped a lot with the
> planning; Leon Ziemba who ran the survey maintenance bot; Jeph Paul and
> Jonathan Morgan who wrote the original version of the voting button gadget;
> all the people working on the Community Wishlist from which I stole the
> idea and most of the process/design.
> [3] https://i.imgflip.com/1jnzy6.jpg
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia-l] Open call for Project Grant proposals (Feb 13-Mar 14)

[Quim Gil]

FYI

-- Forwarded message --
From: Marti Johnson <mjohn...@wikimedia.org>
Date: Tue, Feb 14, 2017 at 5:00 AM
Subject: [Wikimedia-l] Open call for Project Grant proposals (Feb 13-Mar 14)
To: Wikimedia Mailing List <wikimedi...@lists.wikimedia.org>


Hi everyone,

The Wikimedia Foundation Project Grants program launches its third open
call today, February 13.  We will be accepting proposals through March 14
for new ideas to improve Wikimedia projects. <
https://meta.wikimedia.org/wiki/Grants:Project>

Funds are available to support individuals, groups and organizations to
implement new experiments and proven ideas, whether focused on building a
new tool or gadget, organizing a better process on your wiki, researching
an important issue, coordinating an editathon series or providing other
support for community-building.

Ideas from the current Inspire Campaign on developing outside knowledge
networks are very welcome. <
https://meta.wikimedia.org/wiki/Grants:IdeaLab/Inspire>

We will be hosting weekly proposals clinics via Hangouts for real-time
discussions about the Project Grants Open Call.  Links for Hangouts will be
posted by tomorrow here: <
https://meta.wikimedia.org/wiki/Grants:Project#Upcoming_events>


In addition, we have just launched our new tutorial videos to help guide
applicants through key portions of the proposal writing process: <
https://meta.wikimedia.org/wiki/Grants:Project/Tutorial>

We are excited to see your grant ideas that will support our community and
make an impact on the future of Wikimedia projects.  Put your idea into
motion, and submit your proposal between February 13 and March 14! <
https://meta.wikimedia.org/wiki/Grants:Project/Apply>

Please feel free to get in touch with me (mjohn...@wikimedia.org) or Alex
Wang (aw...@wikimedia.org) with questions about getting started with your
project!

Warm regards,

Marti


*Marti JohnsonProgram Officer*
*Individual Grants*
*Wikimedia Foundation <http://wikimediafoundation.org/wiki/Home>*
+1 415-839-6885
Skype: Mjohnson_WMF

Imagine a world in which every single human being can freely share
<http://youtu.be/ci0Pihl2zXY> in the sum of all knowledge.  Help us make it
a reality!
Support Wikimedia <https://donate.wikimedia.org/>
___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
wiki/Wikimedia-l
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikitech-ambassadors] Developer Wishlist Survey: propose your ideas

[Quim Gil]

Remember, the deadline for proposing developer wishes is TODAY, January 31
at 23:59 UTC
<https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170131T235959=1440>
.

The Developer Wishlist voting phase is planned to start next Monday,
February 6.

https://www.mediawiki.org/wiki/Developer_Wishlist#Timeline

On Sat, Jan 21, 2017 at 12:00 AM, Srishti Sethi <sse...@wikimedia.org>
wrote:

> That's right! At the Wikimedia Developer Summit, we decided to organize a
> Developer Wishlist Survey, and here we go:
>
> https://www.mediawiki.org/wiki/Developer_Wishlist
>
> The Wikimedia technical community seeks input from developers for
> developers, to create a high-profile list of desired improvements. The
> scope of the survey includes the MediaWiki platform (core software, APIs,
> developer environment, enablers for extensions, gadgets, templates, bots,
> dumps), the Wikimedia server infrastructure, the contribution process, and
> documentation.
>
> The best part: we want to have the results published by Wednesday,
> February 15. Yes, in a month, to have a higher chance to influence the
> Wikimedia Foundation annual plan FY 2017-18.
>
> There's no time to lose. *Propose your ideas before the end of January, *
> either by pushing existing tasks in Phabricator or by creating new ones.
> You can find instructions on the wiki page
> <https://www.mediawiki.org/wiki/Developer_Wishlist>. Questions and
> feedback are welcome especially on the related Talk page.
>
> The voting phase is expected to start on February 6 (tentative). Watch
> this space (or even better, the wiki page).
>
> Cheers,
> Srishti Sethi
> Developer Advocate, Technical Collaboration team
> Wikimedia Foundation
>
> https://www.mediawiki.org/wiki/User:SSethi_(WMF)
>
>
> ___
> Wikitech-ambassadors mailing list
> wikitech-ambassad...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>
>


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] +2 request for yurik in mediawiki and maps-dev

[Quim Gil]

On Wed, Jan 25, 2017 at 4:44 AM, Legoktm <legoktm.wikipe...@gmail.com>
wrote:

> Hi,
>
> After speaking with Yurik, I've filed
> <https://phabricator.wikimedia.org/T156219> on his behalf to restore his
> membership in the mediawiki and maps-dev groups.
>
> I would appreciate guidance in whether these rights can be summarily
> granted since he used to have them, or if it needs to go through the
> full process.
>

For the record: Yuri got his permissions restored 52 minutes after the task
was filed, without much discussion. The task is Resolved since then. Can we
resolve this thread with this title as well, please?

The cause for the removal was simple: standard procedure for off-boarding
Wikimedia Foundation employees. If this off-boarding process can be
improved, please propose improvements in a new thread or in a Phabricator
task. Considering how often we have ended in this situation and how quickly
the problem has been resolved, it looks like we can have a constructive
discussion without pressure or blame.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Developer Wishlist Survey: propose your ideas

[Quim Gil]

That's right! At the Wikimedia Developer Summit we decided to organize a
Developer Wishlist Survey, and here we go:

https://www.mediawiki.org/wiki/Developer_Wishlist

The Wikimedia technical community seeks input from developers for
developers, to create a high-profile list of desired improvements. The
scope of the survey includes the MediaWiki platform (core software, APIs,
developer environment, enablers for extensions, gadgets, templates, bots,
dumps), the Wikimedia server infrastructure, the contribution process, and
documentation.

The best part: we want to have the results published by Wednesday, February
15. Yes, in a month, in order to have a higher chance to influence the
Wikimedia Foundation annual plan FY 2017-18.

There's no time to lose. *Propose your ideas before the end of January,*
either pushing existing tasks in Phabricator or creating new ones. You can
find instructions in the wiki page. Questions and feedback are especially
welcome in the related Talk page.

The voting phase is expected to start on February 6 (tentative). What this
space (or even better, the wiki page).

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Your questions and votes for our CTO and VP of Product Q

[Quim Gil]

After 25 days, 40 questions, and 2480 votes, the results are...
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program/Wikimedia_Foundation_Product_and_Technology_Q%26A

Thank you to all participants. This experiment has been very interesting so
far. The Q session will happen next Tuesday at 9:30am Pacific, and there
will be a live-broadcast.

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program#Tuesday.2C_January_10th


On Tue, Jan 3, 2017 at 10:05 AM, Quim Gil <q...@wikimedia.org> wrote:

> Hi,
>
> http://www.allourideas.org/wikidev17-product-technology-questions is
> closed for new questions but still open for votes until the end of
> Thursday. A couple of new questions were added in the past days. Please
> contribute a couple of minutes submitting some more votes!
>
> The results so far: http://www.allourideas.org/wikidev17-product-
> technology-questions/results
>
> On Sat, Dec 31, 2016 at 3:26 AM, Gergo Tisza <gti...@wikimedia.org> wrote:
>
>> On Tue, Dec 20, 2016 at 12:45 AM, Quim Gil <q...@wikimedia.org> wrote:
>>
>> > The questions for this session are being crowdsourced at
>> > http://www.allourideas.org/wikidev17-product-technology-questions.
>> Anyone
>> > can propose questions and vote, anonymously, as many times as you want.
>> At
>> > the moment, we have 25 questions and 451 votes.
>> >
>> > An important technical detail: questions posted later have also good
>> > chances to make it to the top of the list as long as new voters select
>> > them. The ranking is made out of comparisons between questions, not
>> > accumulation of votes. For instance, the current top question is in fact
>> > one of the last that has been submitted so far.
>> >
>>
>> Right now the top question has a score of 70 based on 88 votes; the second
>> question has a score of 67 based on 1 vote. (This is not some super-rare
>> accident, either: number 8 and 9 on the popularity list both have 4
>> votes.)
>>
>
> Right now the top 10 have questions that have received as low as 8-15
> votes and as high as 80-101. These numbers will be more balanced if/when
> more people vote this week.
>
> I will not attempt to make a big fuss over participation theories, but
> IMHO Wikimedia processes are quite biased towards What Is Said By Who Talks
> First. This is a humble and harmless experiment in a different direction.
> While seeing a question with eight votes among the top 10 defies the
> traditional democracy paradigm, it also means that an idea that came later
> had any chance over those who were submitted early on.
>
> At the end what counts is the final result of the experiment. Regardless
> of the numbers, I think the current list makes sense, and I in fact it has
> been making sense all along since its second day or so.
>
>
>> That means that the scores can be heavily underspecified (ie. mostly
>> result
>> from the random numbers generated by their algorithm and not actual votes)
>
>
> Well, I am not sure. If a question with eight votes is among the top ten,
> it probably means that  it has been systematically preferred over other
> questions scoring similarly high.
>
> Currently the very last question has only two votes, which means that the
> same algorithm that can put new questions in the top segment can also bury
> them down.
>
> The solution to these potential biases is simple: more opinions submitted
> by more people, which is the basis of any healthy group participation.
>
> Gergo, I am not saying you are wrong (you have clearly done more research
> than myself). I am just saying that I don't think choosing this tool for
> this purpose was a wrong idea either.  :)
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Your questions and votes for our CTO and VP of Product Q

[Quim Gil]

Hi,

http://www.allourideas.org/wikidev17-product-technology-questions is closed
for new questions but still open for votes until the end of Thursday. A
couple of new questions were added in the past days. Please contribute a
couple of minutes submitting some more votes!

The results so far:
http://www.allourideas.org/wikidev17-product-technology-questions/results

On Sat, Dec 31, 2016 at 3:26 AM, Gergo Tisza <gti...@wikimedia.org> wrote:

> On Tue, Dec 20, 2016 at 12:45 AM, Quim Gil <q...@wikimedia.org> wrote:
>
> > The questions for this session are being crowdsourced at
> > http://www.allourideas.org/wikidev17-product-technology-questions.
> Anyone
> > can propose questions and vote, anonymously, as many times as you want.
> At
> > the moment, we have 25 questions and 451 votes.
> >
> > An important technical detail: questions posted later have also good
> > chances to make it to the top of the list as long as new voters select
> > them. The ranking is made out of comparisons between questions, not
> > accumulation of votes. For instance, the current top question is in fact
> > one of the last that has been submitted so far.
> >
>
> Right now the top question has a score of 70 based on 88 votes; the second
> question has a score of 67 based on 1 vote. (This is not some super-rare
> accident, either: number 8 and 9 on the popularity list both have 4 votes.)
>

Right now the top 10 have questions that have received as low as 8-15 votes
and as high as 80-101. These numbers will be more balanced if/when more
people vote this week.

I will not attempt to make a big fuss over participation theories, but IMHO
Wikimedia processes are quite biased towards What Is Said By Who Talks
First. This is a humble and harmless experiment in a different direction.
While seeing a question with eight votes among the top 10 defies the
traditional democracy paradigm, it also means that an idea that came later
had any chance over those who were submitted early on.

At the end what counts is the final result of the experiment. Regardless of
the numbers, I think the current list makes sense, and I in fact it has
been making sense all along since its second day or so.


> That means that the scores can be heavily underspecified (ie. mostly result
> from the random numbers generated by their algorithm and not actual votes)


Well, I am not sure. If a question with eight votes is among the top ten,
it probably means that  it has been systematically preferred over other
questions scoring similarly high.

Currently the very last question has only two votes, which means that the
same algorithm that can put new questions in the top segment can also bury
them down.

The solution to these potential biases is simple: more opinions submitted
by more people, which is the basis of any healthy group participation.

Gergo, I am not saying you are wrong (you have clearly done more research
than myself). I am just saying that I don't think choosing this tool for
this purpose was a wrong idea either.  :)

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Your questions and votes for our CTO and VP of Product Q

[Quim Gil]

Hi,

On the second day of the Wikimedia Developer Summit (January 10) there will
be a Q session with Victoria Coleman (Wikimedia Foundation CTO) and Wes
Moran (VP of Product). It is a plenary session and it will be
video-streamed.

The questions for this session are being crowdsourced at
http://www.allourideas.org/wikidev17-product-technology-questions. Anyone
can propose questions and vote, anonymously, as many times as you want. At
the moment, we have 25 questions and 451 votes.

An important technical detail: questions posted later have also good
chances to make it to the top of the list as long as new voters select
them. The ranking is made out of comparisons between questions, not
accumulation of votes. For instance, the current top question is in fact
one of the last that has been submitted so far.

Why posting or voting a good question? One obvious reason is to encourage
the Foundation's Technology and Product top managers to bring a good answer
in a public session with minutes taken and video recording.  :) Beyond
that, if the ranking of questions makes sense and is backed by
participation numbers, it has a serious chance to influence plans and
discussions beyond the Summit.

The current ranking does make sense, but maybe you could help covering more
areas, other perspectives?

   1. How do we deal with the lack of maintainers for all Wikimedia
   deployed code?
   2. Do we have a plan to bring our developer documentation to the level
   of a top Internet website, a major free software project?
   3. For WMF dev teams, what is the right balance between pushing own work
   versus seeking and supporting volunteer contributors?
   4. During the next year or so, what balance do you think we should
   strike between new projects and technical debt?
   5. When are we going to work on a modern talk pages system for good?
   6. Whose responsibility is to assure that all MediaWiki core components
   and the extensions deployed in Wikimedia have active maintainers?
   7. How important is to have a well maintained and well promoted catalog
   of tools, apps, gadgets, bots, templates, extensions...?
   8. Will MediaWiki ever become easier to install and manage? (e.g. plugin
   manager à la Wordpress). How much do we care about enterprise users?
   9. What should be the role of the Architecture Committee in WMF planning
   (priorities, goals, resources...) and are we there yet?
   10. In addition to Community Tech, should the other WMF Product teams
   prioritize their work taking into account the Community Wishlist results?

The full list:
http://www.allourideas.org/wikidev17-product-technology-questions/results

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Communication about proposed and planned UI changes

[Quim Gil]

On Tue, Dec 20, 2016 at 5:01 AM, Pine W <wiki.p...@gmail.com> wrote:

> Hi Quim,
>
> Would it be possible to set up a 60-minute Hangouts or Zoom meeting to
> discuss this set of issues (UX change communications, possibly aided by the
> newsletter extension and/or a wiki page with some kind of UX checkpoint)?
> If so, perhaps you and I could have an off-list discussion to find a time
> that works for both of us, and after that we can send a public meeting
> announcement to invite other people who also might like to participate. I'd
> suggest that we have this meeting after January 2nd.
>

Pine, thank you for this invitation, but I am only a Technical
Collaboration Guideline messenger here.

Since the Wikimedia Developer Summit is around the corner and there are
some related Unconference sessions being proposed there, and since we are
working on better support for remote participation... I'd rather focus
everybody's attention on the proposed sessions, so they get the push they
deserve (they have been pretty quiet so far):

* UX Guidelines working session and, potentially, presentation
<https://phabricator.wikimedia.org/T149459>
* Discuss creating a UI/UX design hub on mediawiki or meta
<https://phabricator.wikimedia.org/T117482>
* Technical Collaboration Guideline: A Collaboration
<https://phabricator.wikimedia.org/T148878>

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Communication about proposed and planned UI changes

[Quim Gil]

On Sat, Dec 17, 2016 at 4:38 AM, Pine W <wiki.p...@gmail.com> wrote:

> The Newsletter extension could be useful in all kind of ways, and I
> was glad to see that it's apparently still in active development.
>

Oh yes, check  https://phabricator.wikimedia.org/project/profile/888/

It would be helpful for me to have proposals shown in the newsletter
> divided by approximate time horizon (next week, next month, next
> quarter, etc), as well as their status (proposed but not in
> development, in development, stalled, ready for review by (insert team
> here), deploying soon, under discussion, deployment complete on X
> wikis and deploying to Y soon, etc.)
>

If that UX Review checkpoint would be created (something that needs to be
decided by the Product teams who would maintain it)...

... that information would be available in the UX review checkpoint (a
regular wiki page, updated as reviews come and go).

The UX Review newsletters would consist on something a lot lighter:

* A title, i.e. "New WikiEtc design concept looking for reviews"
* A URL where the news would be explained and discussed.

These newsletters would arrive to users via Echo and/or email notifications
-- their choice via their Preferences.

In other words, there is no need to "write a newsletter". The Newsletter
extension just collects and advertises existing pages.


What would it take to get a newsletter like that launched, when might
> it happen, and who should coordinate and publish it?
>

As a promoter of the Newsletter extension, I feel co-responsible (with Tony
Thomas, lead developer and a lot more) for deploying it in Wikimedia
(getting there, it has been available in the Beta cluster for a while now).
If you are interested about this event, please subscribe to
https://phabricator.wikimedia.org/T110170

Once the extension is deployed, if the idea of checkpoints has been found
interesting indeed, we could start with a pilot. Note that setting up the
checkpoint and the newsletter is relatively easy. The complex part is to
define a reliable process followed by everyone. This is why I would put the
words "experimental" and "pilot" upfront.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Communication about proposed and planned UI changes

[Quim Gil]

On Fri, Dec 16, 2016 at 12:51 AM, Pine W <wiki.p...@gmail.com> wrote:

> The issue which I am attempting to address is not a UI change itself
> (good or bad) but rather communication about proposed and upcoming UI
> changes.


Communication of proposals and changes is a problem indeed. Not just for
UX, the problem is common to other areas of development. We are trying to
define the good practices in the Technical Collaboration Guideline, at
Milestone
communication
<https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication>
.

This is how I personally think that the technical solution should work,
taking UI as an example.

* A UX review checkpoint exists, consisting of a wiki page in MediaWiki.org
where current and past proposals reviewed are logged. Users can see which
proposals are currently under review (with deadlines optionally) and which
ones have been resolved and when.

* Each proposal lives in its own URL (a wiki page, a Phabricator task)
where rationale, updates, and discussion happens.

* Anyone can subscribe to the UX Reviews newsletter
<https://www.mediawiki.org/wiki/Extension:Newsletter>. Teams initiating or
resolving a proposal will announce the move in the newsletter. Users
subscribe to this newsletter will receive updates related exclusively to UX
reviews, no more, no less.

Imagine the same approach for new projects/features, security reviews, new
betas, release plans... This is a good way to scale communications without
drowning central spaces like Tech News, wikitech-ambassadors or your
nearest Village Pump. This is also a good way to attract specialized
contributors and help them shine where they can contribute best (i.e.
design students or professionals happy to volunteer) as opposed to trying
to convince them to follow Tech News, wikitech-ambassadors or your nearest
Village Pump.

This idea doesn't define whether a change of color shade merits a review or
whether the review should last three months, but it helps creating focused
spaces where productive collaboration may happen sooner and more often
without everybody dying out of exasperation or exhaustion.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit DRAFT program

[Quim Gil]

On Tue, Dec 13, 2016 at 2:07 AM, Quim Gil <q...@wikimedia.org> wrote:

> * Wikimedia Foundation Technology and Product Q, with Victoria Coleman
> (CTO) and Wes Moran (VP of Product).
>
> You can propose and vote questions for Victoria and Wes between now and
> the beginning of the Summit:
>
> http://www.allourideas.org/wikidev17-product-technology-questions
>

"216 votes on 23 ideas" -- great!

Some further details:

* Anyone can vote as many times as they wish.

* Anyone can propose new questions. We ask you to check the full list of
questions before, to avoid duplicates.
http://www.allourideas.org/wikidev17-product-technology-questions/results

If you have questions or comments about the organization of this session
and this prior survey, please share them at
https://phabricator.wikimedia.org/T153063

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikimedia Developer Summit DRAFT program

[Quim Gil]

Hi, the Wikimedia Developer Summit Program committee is happy to announce a
draft schedule:

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program#Schedule

This schedule includes two plenary sessions:

* Has our success made it hard to see your own contribution?
<https://phabricator.wikimedia.org/T153024> by Ward Cunningham

* Wikimedia Foundation Technology and Product Q, with Victoria Coleman
(CTO) and Wes Moran (VP of Product).

You can propose and vote questions for Victoria and Wes between now and the
beginning of the Summit:

http://www.allourideas.org/wikidev17-product-technology-questions

We welcome feedback about possible improvements to the schedule. Please
share your suggestions at the related discussion page
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Developer_Summit/2017/Program>.
We plan to confirm the final schedule on Friday, December 23rd.

We are working on the Unconference, the third day of the Summit, and the
social events. We will share more details soon. Stay tuned!

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Changes in colors of user interface

[Quim Gil]

Hi, let me check this incident under the light of the Technical
Collaboration Guideline
<https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline> (draft
under review, feedback welcome in the related discussion pages).

https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Milestone_communication
defines when and where are communications expected.

The change discussed in this thread is a slight variation of the same
colors, for accessibility reasons that haven't been contested. This is not
a new product or a new feature, and it is not even a major bug. Therefore,
not triggering a community announcement & review for this case was correct.

This doesn't forbid anyone to talk about this change, especially when they
are one of the contributors (and a volunteer developer) happily sharing the
results obtained. Sharing the news with wikitech-ambassadors was correct
too.

https://www.mediawiki.org/wiki/Technical_Collaboration_Guideline/Community_decisions
defines the steps for communities in case of disagreement.

If a change (no matter how small is perceived by their authors) causes
problems to a community or an individual, they can file specific blockers
explaining the problem. They can do it in the related Phabricator project
<https://phabricator.wikimedia.org/project/profile/24/> or wiki page
<https://www.mediawiki.org/wiki/Wikimedia_User_Interface>.

So far there haven't been any blockers identified about the change itself,
though? If you have any, please report it in the venues where they can be
addressed effectively. https://phabricator.wikimedia.org/T152025 seems to
be the related task.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] CREDIT in 37 minutes

[Quim Gil]

On Thu, Dec 8, 2016 at 3:25 PM, Adam Baso <ab...@wikimedia.org> wrote:

> ;)
>
> Thanks to Brendan in OIT for getting these CREDIT videos up!
>
> In all seriousness on the dev summit videos, maybe a worth a new side
> thread with the conference organizers.
>

If you are interested in better video coverage at the Wikimedia Developer
Summit 2017, please check T146613 - Improve remote participation at the
Wikimedia Developer Summit 2017
<https://phabricator.wikimedia.org/T146613> (the
discussion specific to video is at the end).

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

The Wikimedia Developer Summit 2017 is less than 6 weeks away!

*PARTICIPANTS*

   - 107 participants confirmed.
  - 12 of them have been sponsored by the Wikimedia Foundation and
  Wikimedia Deutschland's Software Development department.
   - 57 more people have requested an invitation.

Registration is still open. Join us!
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit>

*PROPOSALS*

   - 72 proposals open
   <https://phabricator.wikimedia.org/project/view/2205/>
  - 0 in backlog
  - 33 in Unconference
  - 34 on track (active discussion is especially welcomed here!)
  - 5 to be pre-scheduled

Check the selection process timeline
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Call_for_participation#Selection_process>
.

*WE NEED YOU*

Time to prove your interest in Summit proposals
<https://www.mediawiki.org/wiki/Topic:Tfe8pv9zyrrlyb6d>.

Check the Program
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program>.

*ORGANIZATION*

   - The Program committee is working on a draft schedule
   <https://www.mediawiki.org/wiki/Topic:Tgfl2lt2kjtymnfc> to be published
   on Monday, December 12.
   - Also working on a couple of sessions with invited guests.
   - We are planning an online session before the Summit.
   <https://phabricator.wikimedia.org/T150152>

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

2016-11-24

The Wikimedia Developer Summit 2017 is less than 7 weeks away!

*PARTICIPANTS*

   - 111 participants confirmed.
  - 12 of them have been sponsored by the Wikimedia Foundation and
  Wikimedia Deutschland's Software Development department.
   - 25 more people have requested an invitation.

Registration is still open. Join us!


*PROPOSALS*

   - 69 proposals open
   
  - 0 in backlog
  - 18 in Unconference
  - 45 missing proven interest (deadline on *Monday, November 28)*
  - 1 on track
  - 5 to be pre-scheduled

Check the selection process timeline

.

*WE NEED YOU*

Time to prove your interest in Summit proposals
.

Check the Program
.

*ORGANIZATION*

   - Program committee heading towards the pre-selection of active
   discussions with proven interest.
   - Also working on a couple of sessions with invited guests.
   -

   We sent an email to all registered participants asking them to show
   their support to proposals.
   -

   Improve remote participation
   .
   -

   Create a schedule table for sessions in a grid format
   . (UX review / help
   welcome!)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Triaging Summit proposals for "How to grow our technical community"

[Quim Gil]

The Wikimedia developer Summit main topic "How to grow our technical
community
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_grow_our_technical_community>"
has nine proposals aiming to be accepted as pre-scheduled sessions.
Mathematically speaking, it is very unlikely that we will have slots for
all of them. Please help making a good selection by expressing your
interest in your preferred candidates, by commenting/subscribing to your
preferred tasks, or awarding them a token.

Pre-scheduled sessions are supposed to be preceded by active discussions,
so the best way to support your preferred topics is by joining the
discussion now.

Proposals:

   - Actions to grow the diversity of our technical community
   <https://phabricator.wikimedia.org/T148598>
   - Drawing in new MW tech volunteers with Hackathons, and then what
   <https://phabricator.wikimedia.org/T148557>
   - Better recommending of tasks suitable for new technical contributors
   <https://phabricator.wikimedia.org/T149564>
   - Better code review processes for reviewers
   <https://phabricator.wikimedia.org/T149639>
   - IdeaLab for Wikimedia Foundation technical projects
   <https://phabricator.wikimedia.org/T149948>
   - How to unleash the power of JavaScript
   <https://phabricator.wikimedia.org/T148911>
   - MediaWiki Documentation <https://phabricator.wikimedia.org/T149372>
   - How to unleash the power of 3rd party extension developers
   <https://phabricator.wikimedia.org/T147892>
   - Bringing "Enterprise MediaWiki" to the Wikimedia Foundation
   <https://phabricator.wikimedia.org/T149612>


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

The Wikimedia Developer Summit 2017 is less than 8 weeks away!

*PARTICIPANTS*

   - 111 participants confirmed.
  - 12 of them have been sponsored by the Wikimedia Foundation and
  Wikimedia Deutschland's Software Development department.
   - 8 more people have requested an invitation.

Registration is still open. Join us!
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit>

*PROPOSALS*

   - 67 proposals open
   <https://phabricator.wikimedia.org/project/view/2205/>
  - 0 in backlog
  - 18 in Unconference
  - 45 missing proven interest (deadline on *Monday, November 14)*
  - 1 on track
  - 3 to be pre-scheduled

Check the selection process timeline
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Call_for_participation#Selection_process>
.

*WE NEED YOU*

Time to prove your interest in Summit proposals
<https://www.mediawiki.org/wiki/Topic:Tfe8pv9zyrrlyb6d>.

Check the Program
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program>.

*ORGANIZATION*

   - Backstage work visiting the venue and discussing logistics (WiFi,
   catering, rooms).
   - Program committee heading towards the pre-selection of active
   discussions with proven interest.
   - Also working on a couple of sessions with invited guests.


On Mon, Oct 10, 2016 at 3:27 PM, Quim Gil <q...@wikimedia.org> wrote:

> Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4
>
> The Wikimedia Developer Summit 2017 is 13 weeks away!
>
> PARTICIPANTS
>
> * 68 people have requested an invitation.
> * 19 of them have requested travel sponsorship as well.
>
> Join us: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit.
> The deadline to request travel sponsorship is Monday, October 24th.
>
>
> PROPOSALS
>
> * 8 proposals submitted - https://phabricator.wikimedia.
> org/project/view/2205/
> ** 1 in backlog
> ** 2 in Unconference
> ** 2 missing basic information
> ** 3 to be pre-scheduled
>
> https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/
> Call_for_participation
> The deadline for submitting new proposals is Monday, October 31.
>
>
> MAIN TOPICS
>
> https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program
>
> On track:
> * A plan for the Community Wishlist 2016 top results
> * Building on Wikimedia services: APIs and Developer Resources
> * How to manage our technical debt
>
> Missing basic information
> * A unified vision for editorial collaboration
> * Building a sustainable user experience together
> * How to grow our technical community
>
> Missing two facilitators
> * A unified vision for editorial collaboration
> * How to grow our technical community
>
> Missing one facilitator
> * Handling wiki content beyond plaintext
> * Building a sustainable user experience together
> * Artificial Intelligence to build and navigate content
>
>
> ORGANIZATION
>
> * Meet the Program committee. https://www.mediawiki.org/wiki
> /Wikimedia_Developer_Summit/Program_committee
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia-l] Two internships in the Community Engagement department

[Quim Gil]

Hi, the second role mentioned in the email below is technical, and maybe
someone in this list is interested.

-- Forwarded message --
From: Maria Cruz <mc...@wikimedia.org>
Date: Thu, Nov 17, 2016 at 12:17 AM
Subject: [Wikimedia-l] Two internships in the Community Engagement
department
To: Wikimedia Mailing List <wikimedi...@lists.wikimedia.org>


Hello all,

As some of you may have seen there are two open positions (both paid) in
the Community Engagement department for internships on the Learning &
Evaluation team:


   -

   Communications Intern:. (6 months, up to 30 hours/week) We are looking
   for a candidate who works and / or studies in the field of
communications,
   has excellent verbal and written English communications skills and the
   ability to excel in a fast-paced, multitasking environment. Knowledge
   and/or experience with Wikimedia Projects a plus!


The Communications Iintern will primarily support conference communications
for the Community Engagement Team (including event planning and materials
preparation), help plan workshops and community events for program leaders
(as well as document the outcome of those events), and assist with the
coordination of technology supports for communications and events. You can
find the complete job description here:

https://boards.greenhouse.io/wikimedia/jobs/488571#.WCHxXOErKRs


   -

   Technical Intern (3 months up to 20 hours/week) We are looking for a
   candidate that has experience in Mediawiki mark-up and technical
   communications experience in designing for web content curation and user
   flow, has proficiency in at least three of the following programming
   languages: Javascript, Lua, Python, MySQL, has experience developing or
   administrating MediaWiki websites. The candidate should have a strong
   interest in archival systems, searchability and usable portals on wiki,
and
   technical skills for designing Wikimedia templates and pages.

The Technical Design Intern will work closely with the Communications and
Outreach Coordinator (that would be me!) on the Wikimedia Resource Center,
the redesign of the Evaluation Portal on Meta Wikimedia, and migration and
archiving of L portal pages from existing namespaces to new namespace,
among other tasks. You can find the complete job description here:
<https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs>

https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs

If you are interested, please apply. If you know someone who might fit this
position, please forward the email to them!

Cheers,

María
___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Handling Phabricator notifications

[Quim Gil]

Hi, it seems that there is many people struggling with following
Phabricator notifications. Being overwhelmed by notifications defeats the
purpose of notifications. :)

This is an invitation to share some thoughts.

The main trick is of course to pay attention to what you
subscribe/unsubscribe to. Sometimes I ask myself: why am I receiving this
notification, and after a quick investigation it turns out that I am still
watching some project that I am not really interested anymore, or at least
not at the extent that it would impede me to follow better the projects
that I really want to follow.

I actually unsubscribe from many tasks, and that keeps the signal high vs
noise ratio high.

Email preferences can also help a lot reducing the amount of (what for you
constitutes) noise. Also, many people seem to struggle with volume of
emails received and haven't really tried the alternative of web
notifications, which (at least for me) allow for quicker scanning + the
fabulous button "Mark all as read".

I also set many types of notifications to "ignore", because for me at least
the information they bring doesn't compensate for the noise they create. I
have copied my Maniphest email preferences at
https://www.mediawiki.org/wiki/User:Qgil-WMF/Sandbox just in case someone
finds them useful.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Active/inactive Summit proposals (was Re: Wikimedia Developer Summit Weekly)

[Quim Gil]

Hi Jonathan,

On Thu, Nov 10, 2016 at 7:12 PM, Jonathan Morgan <jmor...@wikimedia.org>
wrote:

> Hi Quim,
>
> Could you provide a little more detail about what is required from session
> proposers for the Nov. 28th deadline? It says "Deadline for consolidating a
> discussion, regularly summarized in the proposal." But I'm not sure yet I'm
> expected to do.
>
> I see that a plurality of submissions are currently in the "missing active
> discussion" lane on the Phab board. To me, that wording implies that unless
> there is active discussion on the phab ticket, the proposal is unlikely to
> be selected. Is that accurate? If so, what kind of discussion should I be
> encouraging, as a session proposer, and how much discussion is enough?
>

Your question is totally fair. :)  We are building this process as we go,
and your ideas and criticism are very important ingredients.

I have tried to explain reasons and expectations about this deadline at
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Call_for_participation#Proven_interest

Additional questions and feedback about this deadline and the selection
process in general are welcome in the related Talk page:
https://www.mediawiki.org/wiki/Talk:Wikimedia_Developer_Summit/2017/Call_for_participation


> It seems clear that I should be letting people know about my session.
> Should I encourage them to post a comment indicating their interest, or to
> ask a question in the thread? Or is it enough if some people subscribe to
> the task?
>

"Passive" demonstrations of interest like subscribing to the related
Phabricator task (or awarding tokens, a possibility that we have started to
discuss) are definitely useful to prove that someone is interested about
the topic beyond the person or small group proposing it.

However, active discussions are the sauce of the Summit. There is a lot of
competition for the pre-scheduled slots. We'd rather assign these slots to
the discussions that are already ongoing and will clearly benefit from,
say, well advertised 90 minutes in one room with video recording.
Theoretically relevant proposed topics relying on a discussion just
starting at the Summit are playing a gable. It might just work, but from
the Program committee perspective that is risky gamble to bet our (rather
expensive) space and participants' attention span.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Original version available at
https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

The Wikimedia Developer Summit 2017 is less than 9 weeks away!

*PARTICIPANTS*

   - 111 participants confirmed.
  - 12 of them have been sponsored by the Wikimedia Foundation and
  Wikimedia Deutschland's Software Development department.

Registration is still open. Join us!
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit>

*PROPOSALS*

   - 70 proposals open
   <https://phabricator.wikimedia.org/project/view/2205/>
  - 2 in backlog
  - 12 in Unconference
  - 19 missing basic information (deadline on *Monday, November 14)*
  - 33 missing active discussion
  - 1 on track
  - 3 to be pre-scheduled

Check the selection process timeline
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Call_for_participation#Selection_process>
.

*MAIN TOPICS*

No significant news. We hope to have all the wiki pages up to date next
week.

Check the Program
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program>.

*ORGANIZATION*

   - The Travel Sponsorship committee reviewed 92 requests and decided on
   12 based on budget available.
   - The Program committee met officially for the first time (meeting logs
   and summary <https://phabricator.wikimedia.org/E356>).


On Mon, Oct 10, 2016 at 3:27 PM, Quim Gil <q...@wikimedia.org> wrote:

> Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4
>
> The Wikimedia Developer Summit 2017 is 13 weeks away!
>
> PARTICIPANTS
>
> * 68 people have requested an invitation.
> * 19 of them have requested travel sponsorship as well.
>
> Join us: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit.
> The deadline to request travel sponsorship is Monday, October 24th.
>
>
> PROPOSALS
>
> * 8 proposals submitted - https://phabricator.wikimedia.
> org/project/view/2205/
> ** 1 in backlog
> ** 2 in Unconference
> ** 2 missing basic information
> ** 3 to be pre-scheduled
>
> https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/
> Call_for_participation
> The deadline for submitting new proposals is Monday, October 31.
>
>
> MAIN TOPICS
>
> https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program
>
> On track:
> * A plan for the Community Wishlist 2016 top results
> * Building on Wikimedia services: APIs and Developer Resources
> * How to manage our technical debt
>
> Missing basic information
> * A unified vision for editorial collaboration
> * Building a sustainable user experience together
> * How to grow our technical community
>
> Missing two facilitators
> * A unified vision for editorial collaboration
> * How to grow our technical community
>
> Missing one facilitator
> * Handling wiki content beyond plaintext
> * Building a sustainable user experience together
> * Artificial Intelligence to build and navigate content
>
>
> ORGANIZATION
>
> * Meet the Program committee. https://www.mediawiki.org/wiki
> /Wikimedia_Developer_Summit/Program_committee
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Congratulations to {4} Outreachy'13 selects from Wikimedia

[Quim Gil]

Neslihan, Sejal, Anna, Zareen, welcome! I wish you interesting, productive,
and fun internships. I also encourage you to take the opportunity to meet
other technical contributors here, and also other Wikimedians (if there are
any) in your whereabouts.

Thank you Tony, Sumit and all the mentors and other supporters involved in
this Outreachy round.

On Tue, Nov 8, 2016 at 8:20 PM, Neslihan Turan <tur.nesli...@gmail.com>
wrote:

> Great!
> I can't wait for this project. Congrats to other 3 friends :)
>
> Neslihan
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Original version with links and HTML: https://www.mediawiki.org/wiki/Topic:
Td5wfd70vptn8eu4
2016-10-31

The Wikimedia Developer Summit 2017 is 10 weeks away!

PARTICIPANTS

60 participants confirmed.
* 111 more people have requested an invitation.
** 81 of them have requested travel sponsorship as well.

Join us!

PROPOSALS

58 proposals submitted

* 8 in backlog
* 10 in Unconference
* 6 missing basic information
* 27 missing active discussion
* 3 to be pre-scheduled
* 4 invalid

Call for participation. The deadline for submitting new proposals is
TODAY Monday, October 31.

MAIN TOPICS

Program

On track:

* A plan for the Community Wishlist 2016 top results
* Building on Wikimedia services: APIs and Developer Resources (T147593)

Missing basic information

* Building a sustainable user experience together

Missing one facilitator

* Handling wiki content beyond plaintext (T147602)
* Building a sustainable user experience together
* Artificial Intelligence to build and navigate content (T147708)
* How to grow our technical community  (T147406)
* How to manage our technical debt (T147937)

Cancelled

* A unified vision for editorial collaboration (related proposals are
welcome)

ORGANIZATION

Promote the Wikimedia Developer Summit beyond the usual circles
* A successful promotion brought more scholarship requests than in the
previous three Summit editions combined.
* Pageviews peaked at 363 on one of the outreach days
* Twitter saw 22,737 ‘impressions’ on this tweet, shared by WMF Comms and
others and 12,601 for this one.

Wikimedia Developer Summit Scholarships
* A new committee is reviewing candidates as we speak

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] What happened to RobLa?

[Quim Gil]

Hi,

On Sun, Oct 30, 2016 at 9:32 AM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:

> what happens to his position in co-organizing the developer summit,
> especially as he was (iirc) part of the "programs committee"? :)
>

Robla has played a key role in the Wikimedia developer Summit and its
previous incarnations. His involvement will be missed in the organization
of the next edition. This year we created a Program Committee
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Program_committee>,
and responsibilities are a lot more distributed than before. For this
reason, I am confident that we will be able to organize a good event.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] How to grow our technical community - Wikimedia Developer Summit

[Quim Gil]

How to grow our technical community? This is a main topic at the upcoming
Wikimedia Developer Summit (San Francisco, January 11-13, 2017).

There is a call for participation open until the end of this month (October
31). Your proposals for discussions related to this main topic are welcome!
There are some ideas about possible topics at

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/How_to_grow_our_technical_community

If you are interested in contributing to the discussions about How to grow
our technical community, please join us at the Summit (the deadline to
request travel sponsorship is next Monday, October 24).

PLEASE ENCOURAGE OTHER PEOPLE to submit a proposal and/or join the Summit.
This email will likely arrive to the core of the Wikimedia technical
community, but the chances to arrive to the periphery and beyond are a lot
smaller. We need your help! We want to discuss how to grow our technical
community including the perspectives of those who haven't joined us yet.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Hi Florian,

On Mon, Oct 17, 2016 at 3:42 PM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:

> Hi Quim,
>
> thanks for the weekly!
>

I'm glad you find it useful.  :)


>
> One difference between the last weekly: You now mentioned "confirmed"
> participant. However, it seems I'm not informed about what "confirmed"
> means, and what I've to do to be confirmed :P Do I get an e-mail or do I
> need to do something (apart from requesting an invitation)?
>

Some people got already a confirmation via email. Their common denominator
is that they didn't need any travel sponsorship.

We plan to evaluate sponsorship requests right after the deadline is closed
next Monday, and we hope to send most resolutions in the following days.



> One more question: "29 of them have requested travel sponsorship as well"
> means, that 29 of the 42 or of the 50? :)
>

Of the 42. I was actually wondering whether I should indent that line, but
I went for visual simplicity.  :)


>
> Thanks for your answer! :)
>
> Best,
> Florian
>
> -Original-Nachricht-
> Betreff: Re: [Wikitech-l] Wikimedia Developer Summit Weekly
> Datum: 2016-10-17T13:32:28+0200
> Von: "Quim Gil" <q...@wikimedia.org>
> An: "Wikimedia developers" <wikitech-l@lists.wikimedia.org>
>
> Source and more links: https://www.mediawiki.org/
> wiki/Topic:Td5wfd70vptn8eu4
>
> The Wikimedia Developer Summit 2017 is 12 weeks away!
>
> PARTICIPANTS
>
> 50 participants confirmed.
> 42 more people have requested an invitation.
> 29 of them have requested travel sponsorship as well.
>
> Join us <https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit>! The
> deadline to request travel sponsorship is Monday, October 24th.
>
> PROPOSALS
>
> 13 proposals submitted
> <https://phabricator.wikimedia.org/project/view/2205/>
>
> 0 in backlog
> 4 in Unconference
> 3 missing basic information
> 3 missing active discussion
> 3 to be pre-scheduled
>
> Call for participation
> <https://www.mediawiki.org/wiki/Wikimedia_Developer_
> Summit/Call_for_participation>.
> The deadline for submitting new proposals is Monday, October 31.
>
> MAIN TOPICS
>
> Program
> <https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program>
>
> On track:
>
> A plan for the Community Wishlist 2016 top results
> Building on Wikimedia services: APIs and Developer Resources (T147593)
> How to manage our technical debt (T147937)
>
> Missing basic information
>
> A unified vision for editorial collaboration
> Building a sustainable user experience together
> How to grow our technical community (T147406)
>
> Missing two facilitators
>
> A unified vision for editorial collaboration
> How to grow our technical community
>
> Missing one facilitator
>
> Handling wiki content beyond plaintext (T147602)
> Building a sustainable user experience together
> Artificial Intelligence to build and navigate content (T147708)
>
> ORGANIZATION
>
> Promote the Wikimedia Developer Summit beyond the usual circles.
> <https://phabricator.wikimedia.org/T146615>
>
> --
> Quim Gil
> Engineering Community Manager @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/User:Qgil
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Source and more links: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

The Wikimedia Developer Summit 2017 is 12 weeks away!

PARTICIPANTS

50 participants confirmed.
42 more people have requested an invitation.
29 of them have requested travel sponsorship as well.

Join us <https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit>! The
deadline to request travel sponsorship is Monday, October 24th.

PROPOSALS

13 proposals submitted
<https://phabricator.wikimedia.org/project/view/2205/>

0 in backlog
4 in Unconference
3 missing basic information
3 missing active discussion
3 to be pre-scheduled

Call for participation
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation>.
The deadline for submitting new proposals is Monday, October 31.

MAIN TOPICS

Program
<https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program>

On track:

A plan for the Community Wishlist 2016 top results
Building on Wikimedia services: APIs and Developer Resources (T147593)
How to manage our technical debt (T147937)

Missing basic information

A unified vision for editorial collaboration
Building a sustainable user experience together
How to grow our technical community (T147406)

Missing two facilitators

A unified vision for editorial collaboration
How to grow our technical community

Missing one facilitator

Handling wiki content beyond plaintext (T147602)
Building a sustainable user experience together
Artificial Intelligence to build and navigate content (T147708)

ORGANIZATION

Promote the Wikimedia Developer Summit beyond the usual circles.
<https://phabricator.wikimedia.org/T146615>

--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Introducing Srishti Sethi, our new Developer Advocate

[Quim Gil]

Hello everybody,

The Technical Collaboration team is very happy to introduce you to Srishti
Sethi <https://meta.wikimedia.org/wiki/User:SSethi_(WMF)>, our new
Developer Advocate. Srishti will lead our efforts to engage volunteer
developers in Wikimedia software projects and to grow the Wikimedia
technical community. In her first assignments, she will help promote
Community Wishlist projects, the Wikimedia Developer Summit, and
Wikimedia’s participation in Google Code-in. Srishti just relocated from
Boston to San Francisco, and she will work at the Wikimedia Foundation
office.

Srishti originally hails from Rajasthan, India. She recently finished her
Masters in Media Arts and Sciences from the MIT Media Lab, where she was
exploring how online platforms for learning could be made more peer-led,
engaging, participatory and accessible to diverse populations. At the Media
Lab, Srishti contributed to the design, development, and research of
Unhangout (http://unhangout.media.mit.edu), a platform for running
large-scale un-conference style events online.

Before joining MIT, she was working as a software developer with a startup
organization in India. As an undergrad, she was involved with the open
source community GNOME and its educational project GCompris.

In her spare time, Srishti likes to play ping-pong, do long bike trips,
take photographs and make masala chai for friends. :)

Please join us in welcoming Srishti!

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia Announcements] Project Grants program will fund 6 community-led projects

[Quim Gil]

d incubator Wikipedia projects in the indigenous languages of Latin
   America. By mapping successes and challenges, the team will develop best
   practices and guidelines for how to support communities that are interested
   in developing their indigenous language community and important learnings
   for both WMF and the Wikimedia community on if and how we can best support
   them.[11][12]


You can read more about this round on the Wikimedia Foundation blog.[13]

The current call for round 2 of Project Grants
<https://meta.wikimedia.org/wiki/Grants:Project> ends October 11th. The
next open call begins December 19th. [14]

Congratulations to the successful grantees!


   1.

   <https://meta.wikimedia.org/wiki/Grants:Project/Browse_applications>
   2.

   <https://meta.wikimedia.org/wiki/Grants:Project/Harej/
   Librarybase:_an_online_reference_library
   
<https://meta.wikimedia.org/wiki/Grants:Project/Harej/Librarybase:_an_online_reference_library>
   >
   3.

   <http://librarybase.wmflabs.org/wiki/Librarybase:About>
   4.

   <https://meta.wikimedia.org/wiki/Grants:Project/Putnik/Wikidata_module>
   5.

   <https://meta.wikimedia.org/wiki/User:Putnik>
   6.

   <https://meta.wikimedia.org/wiki/Grants:Project/WikiFactMine>
   7.

   <https://meta.wikimedia.org/wiki/Grants:Project/A_
   Wikipedian-in-Residence_to_Engage_500_Librarians_and_their_Communities
   
<https://meta.wikimedia.org/wiki/Grants:Project/A_Wikipedian-in-Residence_to_Engage_500_Librarians_and_their_Communities>
   >
   8.

   <https://www.oclc.org/home.en.html>
   9.

   <http://www.knightfoundation.org/articles/knight-news-
   challenge-libraries-awards-16-million-support-innovative-ideas
   
<http://www.knightfoundation.org/articles/knight-news-challenge-libraries-awards-16-million-support-innovative-ideas>
   >
   10.

   <https://meta.wikimedia.org/wiki/Grants:Project/UGGR/Why_
   women_don%E2%80%99t_edit_Wikipedia
   
<https://meta.wikimedia.org/wiki/Grants:Project/UGGR/Why_women_don%E2%80%99t_edit_Wikipedia>
   >
   11.

   <https://meta.wikimedia.org/wiki/Grants:Project/Strengthening_Indigenous-
   Language_Wikipedias_in_Latin_America
   
<https://meta.wikimedia.org/wiki/Grants:Project/Strengthening_Indigenous-Language_Wikipedias_in_Latin_America>
   >
   12.

   <https://globalvoices.org/-/topics/digital-activism/>
   13.

   <https://blog.wikimedia.org/2016/10/07/new-project-grants/ >
   14. <https://meta.wikimedia.org/wiki/Grants:Project>


-- 
Alexandra Wang
Program Officer
Community Resources
Wikimedia Foundation <http://wikimediafoundation.org/wiki/Home>
+1 415-839-6885
Skype: alexvwang

___
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




-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Wikimedia Developer Summit Weekly

[Quim Gil]

Original version: https://www.mediawiki.org/wiki/Topic:Td5wfd70vptn8eu4

The Wikimedia Developer Summit 2017 is 13 weeks away!

PARTICIPANTS

* 68 people have requested an invitation.
* 19 of them have requested travel sponsorship as well.

Join us: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit.
The deadline to request travel sponsorship is Monday, October 24th.


PROPOSALS

* 8 proposals submitted - https://phabricator.wikimedia.
org/project/view/2205/
** 1 in backlog
** 2 in Unconference
** 2 missing basic information
** 3 to be pre-scheduled

https://www.mediawiki.org/wiki/Wikimedia_Developer_
Summit/Call_for_participation
The deadline for submitting new proposals is Monday, October 31.


MAIN TOPICS

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Program

On track:
* A plan for the Community Wishlist 2016 top results
* Building on Wikimedia services: APIs and Developer Resources
* How to manage our technical debt

Missing basic information
* A unified vision for editorial collaboration
* Building a sustainable user experience together
* How to grow our technical community

Missing two facilitators
* A unified vision for editorial collaboration
* How to grow our technical community

Missing one facilitator
* Handling wiki content beyond plaintext
* Building a sustainable user experience together
* Artificial Intelligence to build and navigate content


ORGANIZATION

* Meet the Program committee. https://www.mediawiki.org/
wiki/Wikimedia_Developer_Summit/Program_committee

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Looking for WikiDev Summit main topics and volunteers

[Quim Gil]

Hi Mathieu, let me retry to reply with a generic answer that might be
useful to other people thinking about proposing topics for the Summit.

On Tue, Oct 4, 2016 at 3:28 PM, Mathieu Stumpf Guntz <
psychosl...@culture-libre.org> wrote:

> Hi Quim and everyone on the list,
>
> One of my spare time project is to "translate" programming languages to
> Esperanto. I already achieved a Javascript translation within the
> Babylscript project <http://www.babylscript.com/>. Currently I'm working
> on a translation of Lua <https://github.com/psychoslave/lupa>. I chose
> Lua because I wish I was able to code in (somewhat) plain Esperanto when
> writing Scribunto modules on Esperanto Wikimedia projects.
>
> So, I would be happy to know opinions of other developers about such a
> project, and even more important, what steps would you see as necessary
> to make it possible. Would that be a project interesting for a Wikimedia
> Developer Summit?
>

Let's start with the definition of the Wikimedia developer Summit:

"The annual meeting to push the evolution of MediaWiki and other
technologies supporting the Wikimedia movement."

Is your topic within scope? Then let's continue with the main topics
proposed for this edition:

* A plan for the Community Wishlist 2016 top results
* Handling wiki content beyond plaintext
* A unified vision for editorial collaboration
* Building a sustainable user experience together
* Building on Wikimedia services: APIs and Developer Resources
* How to manage our technical debt
* Artificial Intelligence to build and navigate content
* How to grow our technical community

Does your proposal fit in any of these main topics? If so, you are
especially encourage to submit a proposal for an activity. If not, you
still can propose an Unconference session. The interest raised by your
proposal (in the form of active participation and subscribers) will help
you and us organizers figure out the best time and place for this activity.

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation#Selection_process

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Call for participation: Wikimedia Developer Summit 2017

[Quim Gil]

Hi, the call for participation for the Wikimedia Developer Summit 2017 is
now open:

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation

We welcome especially proposals related to these main topics:

* A plan for the Community Wishlist 2016 top results
* Handling wiki content beyond plaintext
* A unified vision for editorial collaboration
* Building a sustainable user experience together
* Useful, consistent, and well documented APIs
* How to manage our technical debt
* Artificial Intelligence to build and navigate content
* How to grow our technical community

If you want to propose an activity pre-scheduled in the Summit program, you
have time until Monday, October 31. There is no deadline to propose
Unconference sessions.

ABOUT

The Wikimedia Developer Summit is the annual meeting to push the evolution
of MediaWiki and other technologies supporting the Wikimedia movement. We
welcome all Wikimedia technical contributors and third party developers
using the Wikimedia APIs or MediaWiki.

https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit

(This information wants to be forwarded!)

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] WikiDev'17 main topics and their owners (next steps)

[Quim Gil]

(Posted at https://www.mediawiki.org/wiki/Topic:Tcg07knzz72wixak and pasted
here for convenience)

The Wikimedia Developer Summit 2017 aims to focus the call for
participation around these main topics:

* A plan for the Community Wishlist 2016 top results
* Handling wiki content beyond plaintext
* A unified vision for editorial collaboration
* Building a sustainable user experience together
* Useful, consistent, and well documented APIs
* How to manage our technical debt
* How to grow our technical community

You can find more information about these topics and how we selected them at
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit and
https://www.mediawiki.org/wiki/Topic:Tb6bztglijowk8x3

The next steps are:

* Each main topic needs at least one owner, who will assure that the topic
is well promoted in the right places, the right activities are proposed,
and the right people participate in them with common goals. These owners
will join the Program committee
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/About

* Each main topic needs good quality and quantity of proposals submitted,
so a good selection can be made for the pre-scheduled Summit program.

* Each main topic needs its own wiki page for information, coordination,
discussion, and documentation.

If by the end of October a main topic is still missing an owner, a critical
mass of proposals and/or a decent wiki page, then the chances are that such
main topic will be dissolved. If that happens, the activities proposed can
be still pushed by their promoters in the context of the Unconference. Just
like the rest of proposals not fitting under the main topics.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit 2017 discussion

[Quim Gil]

Hi,

I am sorry but this discussion about this basic principle arrives too late.
We have been using Phabricator to submit proposals in the past two years,
and although the feedback about this was "polarizing", all in all it was
considered positive with ideas for improvement [0] [1]. We could have
discussed this topic some weeks ago but not now, in the week where we plan
to open the call for participation (already delayed at least one week).

The promoters of a proposals still have all the freedom to decide where
they prefer the discussion for that activity to happen, in the own task or
elsewhere. I think we all agree that anything worth documented for the long
term should be documented in MediaWiki.org, not in Phabricator tasks (or
etherpads).

I will explain why I believe the current approach is good enough and even
better than MediaWiki pages today:

On Wed, Sep 28, 2016 at 11:27 AM, Legoktm <legoktm.wikipe...@gmail.com>
wrote:

> 1. What things (mentioned above) do you (and others?) prefer about
> Phabricator compared to MediaWiki?
>

Summit sessions are considered tasks themselves, not just a conversation
happening in a room and eventually documented in a wiki page. Having a
Phabricator task as common unit has these advantages:

* Assigned. It is clear to see whether a session is assigned to someone or
not. That someone will have that task in their backlog, together with the
rest of their Wikimedia work. They can set priority accordingly, just like
the rest of work than needs to be done.

* Tags. Tasks can be associated to various related projects, and this
generates notifications to people watching those projects, even if they
have no clue that a Summit is going on. Teams running sprints can add their
related Summit tasks to their sprints, assign points to them, whatever.
Preparing a session is real work that takes real hours from other possible
tasks.

* Blockers / Blocked by. Anyone interested in a session can define what
needs to happen before it, what is depending on it, what actions come after
it. This connects very well the Summit sessions with the work being done
during the rest of the year.

* Board. Having an overview of all the Summit proposals presented and their
status organized by columns is useful. Organizing a board moving tasks
around is easy. Boards show open tasks by default and accept custom
queries, which is useful for organizers and anyone willing to have a
perspective of what is going on beyond their own session. For instance, do
you want to check the sessions from the previous Summit that are still
open, to see whether they could be pushed further in the next Summit?
https://phabricator.wikimedia.org/project/view/1448/



> 2. Should those features also be implemented or improved in MediaWiki?
>

It is easy to reply "yes, of course", but looking at the overall list of
possible improvements of MediaWiki, I think the Wikimedia movement would
prefer the investment of developer time in other areas. These cases are
imho too niche from the perspective of writing free encyclopedias,
dictionaries, media repositories, etc.

In any case, I wouldn't stop anyone willing to work on these features...
but neither would I put the organization of the Summit at the expense of
any of these features being implemented in MediaWiki. Wikimedia Phabricator
is a Wikimedia tool that already provides those features, so...


> 3. Is the lack (or degraded quality) of the feature in MediaWiki a
> blocker to prevent you from doing whatever you wish to do (in a timely,
> stress-free manner, etc.)? If so, do you think that other MediaWiki
> users or Wikimedians are running into the same issue as you?
>

Although I have used MediaWiki as a mechanism to submit conference
proposals (here and in my previous job), I don't think I know any MediaWiki
user or any event organizer out of Wikimedia using MediaWiki to handle a
call for participation. Wikimania and some WikiCons do, but I don't know
the reasons why they do it, neither how happy are the organizers and the
participants using those MediaWiki-based processes for an event.

My personal opinion is that we should know when to use MediaWiki and when
not to use it, instead of using it always at all costs.

[0]
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015/Lessons_learned#Phabricator
[1]
https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016/Lessons_Learned#Use_of_the_combination_of_etherpads.2C_Phabricator_and_wikis_to_coordinate_the_sessions

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit 2017 discussion

[Quim Gil]

Thank you Rob! I am looking forward to Wednesday meeting.

On Tue, Sep 27, 2016 at 6:28 AM, Rob Lanphier <ro...@wikimedia.org> wrote:

> I'm hoping we find a way to work with people who can't
> travel, and noting we're also working to make remote participation
> more rewarding.  This emphasizes the importance of WikiDev17 being a
> better event for online attendance this year, and the primacy of
> online conversations in our community's decision making.
>

Indeed. Anyone interested in improving remote participation in the Summit,
please check https://phabricator.wikimedia.org/T146613

Quim is
> chairing the program committee, and I'm one of the members, but my
> understanding from Quim is that we're still waiting for some invitees
> to respond.
>

Yes, I will send them a reminder. In any case, I think we have critical
mass: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/About


> all of the scheduled topics had Phab IDs associated with them.
>

I agree that RfCs are useful in some cases but not in all of them. However,
I would still keep a single way to submit proposals as Phabricator tasks,
in order to have one place with all the proposals. If the promoters of a
specific proposal want to have the discussion elsewhere (in an RfC page, a
plain wiki page...) then they can simply put a disclaimer in the task
description and move the discussion there.

There are two possible novelties related to proposed and scheduled
activities that we could try at the Summit:

* Phabricator form to submit Wikimedia developer Summit 2017 proposals
(urgent because it blocks the opening of the call for participation)
https://phabricator.wikimedia.org/T146377
* Consider using Phabricator Calendar events to schedule Wikimedia
Developer Summit sessions (we have more time for this one)
https://phabricator.wikimedia.org/T146749

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] WikiDev'17 main topics -- more feedback needed

[Quim Gil]

Hi, we need more voices and perspectives in the definition of the main
topics of the Wikimedia developer Summit 2017. Your participation is very
important!

RobLa went through the suggestions made and has proposed an organization
around main topics, and the discussion has started. Please check
https://www.mediawiki.org/wiki/WikiDev17/Topic_ideas and the discussion
page.

Rachel and I have decided to make a soft-launch of the Summit by opening
the registration and travel sponsorship requests only, because we cannot
keep postponing this step. You should hear news from us tomorrow.

We will launch properly opening the call for participation and promoting
the Summit widely in Wikimedia channels and beyond hopefully next week,
when we have a "good enough" list of main topics.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

[Quim Gil]

Robla and I are trying to nail down the main topics that will bootstrap the
Summit in the next days. Please join the discussion until we make a
decision (and beyond if you wish, of course):
https://www.mediawiki.org/wiki/Topic:Tb6bztglijowk8x3

Remember that at least 50% of time and space will be dedicated to an
Unconference setup that will allow the discussion to any other topic not
making it to this short list.


On Sat, Sep 17, 2016 at 7:27 AM, Bináris <wikipo...@gmail.com> wrote:

> 2016-09-15 18:53 GMT+02:00 Rob Lanphier <ro...@wikimedia.org>:
>
> > This seems apropos:
> > https://vimeo.com/121290570
> >
> > It's good Hollywood is finally paying attention to our people.
> >
> Made my day! :-D
>
>
>
> --
> Bináris
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Congratulations to all GSoC students (passed)

[Quim Gil]

On Thu, Sep 15, 2016 at 8:47 AM, Quim Gil <q...@wikimedia.org> wrote:

> Yaron Koren added useful information about other MediaWiki-related
> projects that were developed by WikiToLearn, another organization
> participating in GSoC 2016.
>

Actually, I have just learned that WikiToLearn was recognized as a
Wikimedia User Group last month:
https://meta.wikimedia.org/wiki/WikiToLearn_User_Group

Another tech-savvy group in the Wikimedia movement, good news!


>
> https://www.mediawiki.org/wiki/Google_Summer_of_Code_
> past_projects#A_mention_to_WikiToLearn_projects
>
> More good news!
>
> On Mon, Sep 5, 2016 at 5:49 PM, Sumit Asthana <asthana.sumi...@gmail.com>
> wrote:
>
>> All the invited are *encouraged* to participate in the showcase, as its a
>> unique opportunity and platform to show your projects to a broader range
>> of
>> people and not to mention get experience and learn the professional skills
>> needed for a technical presentation.
>>
>> -Thanks,
>> Sumit Asthana,
>> B.Tech Final Year,
>> Dept. of CSE,
>> IIT Patna
>>
>> On Mon, Sep 5, 2016 at 5:30 PM, Tony Thomas <01tonytho...@gmail.com>
>> wrote:
>>
>> > Thank you Alangi for starting the thread. Let me add something more over
>> > here.
>> >
>> > Google Summer of Code 2016 has came to an end last week, and 6 of our
>> GSoC
>> > projects could make it till the end. It is a work-done moment for
>> everyone
>> > involved and we hope all of the same become production ready soon. Let
>> me
>> > pull in the projects, and a public report on each:
>> >
>> >1. Extension for page creating/editing notification -
>> >https://www.mediawiki.org/wiki/Extension:EditNotify (Student:
>> Abhinand
>> > N)
>> >2. Accuracy Review of Wikipedia -
>> >https://priyankamandikal.github.io/posts/gsoc-2016-project-overview/
>> >(Student: Priyanka)
>> >3. Automated Testing and Integration of IFTTT support to Wikidata -
>> >https://github.com/wikimedia/ifttt/commits/gsoc?author=ch3nkula
>> >(Student: Alangi)
>> >4. Improving static analysis tools for MediaWiki -
>> >https://docs.google.com/document/d/1whpf9g8ylRwHkzzDqByFRdY
>> > 6pklqHd_92_v1eCDfeAM/edit?usp=sharing
>> >(Student: Lethe)
>> >5. List Of Contributors -
>> >https://docs.google.com/document/d/1GD36m1zQtvYYmX6d0J8c_4b
>> > UkWqihHjfsQG1-qhqBYw/pub
>> >(Student: Devi R)
>> >6. Port catimages.py to pywikibot-core -
>> >https://commons.wikimedia.org/wiki/User:AbdealiJK/file-meta
>> > data/GSoC2016
>> >(Student: Abdeali)
>> >
>> > Hearty congratulations to the mentors and students involved, and to all
>> who
>> > could participate in this round of GSoC/Outreachy. Three of the
>> Outreachy
>> > selects were considered for GSoC, and hence there is no specific results
>> > for Outreachy.
>> >
>> > *Showcase* for GSoC projects along with CREDIT, this week:
>> >
>> > Please join us in the GSoC showcase of all evaluation completed projects
>> > along with CREDIT showcase, this week on Sep 7, 2016 (1800 UTC). Please
>> > find the original email of the same over here[1], which have
>> instructions
>> > for interns to add their projects to the showcase, and other
>> arrangements,
>> > etc. Those interns who cannot can make it to this week CREDIT, are
>> welcome
>> > to do it in the following one.
>> >
>> > The showcase will include a minimum 5 mins demo, which can include a
>> > presentation of some sort and a short and sweet explanation of what was
>> > done as part of the program. We expect the mentors too online and live,
>> to
>> > make this a success! This would be the best time to provide links to
>> blog
>> > posts the interns have done on the same too, so that the community can
>> > catch up!
>> >
>> > [1]
>> > https://lists.wikimedia.org/pipermail/wikitech-l/2016-Septem
>> > ber/086415.html
>> >
>> > Thanks,
>> > Tony Thomas <https://www.mediawiki.org/wiki/User:01tonythomas>
>> > Home <http://www.thomastony.me> | Blog <https://tttwrites.wordpress.c
>> om/>
>> > |
>> > ThinkFOSS <http://www.thinkfoss.com>
>> >
>> >
>> > On Mon, Sep 5, 2016 at 2:23 PM, Quim Gil <q...@wikimedia.org> wrote:
>> >
>> > > Ind

Re: [Wikitech-l] Congratulations to all GSoC students (passed)

[Quim Gil]

Yaron Koren added useful information about other MediaWiki-related projects
that were developed by WikiToLearn, another organization participating in
GSoC 2016.

https://www.mediawiki.org/wiki/Google_Summer_of_Code_past_projects#A_mention_to_WikiToLearn_projects

More good news!

On Mon, Sep 5, 2016 at 5:49 PM, Sumit Asthana <asthana.sumi...@gmail.com>
wrote:

> All the invited are *encouraged* to participate in the showcase, as its a
> unique opportunity and platform to show your projects to a broader range of
> people and not to mention get experience and learn the professional skills
> needed for a technical presentation.
>
> -Thanks,
> Sumit Asthana,
> B.Tech Final Year,
> Dept. of CSE,
> IIT Patna
>
> On Mon, Sep 5, 2016 at 5:30 PM, Tony Thomas <01tonytho...@gmail.com>
> wrote:
>
> > Thank you Alangi for starting the thread. Let me add something more over
> > here.
> >
> > Google Summer of Code 2016 has came to an end last week, and 6 of our
> GSoC
> > projects could make it till the end. It is a work-done moment for
> everyone
> > involved and we hope all of the same become production ready soon. Let me
> > pull in the projects, and a public report on each:
> >
> >1. Extension for page creating/editing notification -
> >https://www.mediawiki.org/wiki/Extension:EditNotify (Student:
> Abhinand
> > N)
> >2. Accuracy Review of Wikipedia -
> >https://priyankamandikal.github.io/posts/gsoc-2016-project-overview/
> >(Student: Priyanka)
> >3. Automated Testing and Integration of IFTTT support to Wikidata -
> >https://github.com/wikimedia/ifttt/commits/gsoc?author=ch3nkula
> >(Student: Alangi)
> >4. Improving static analysis tools for MediaWiki -
> >https://docs.google.com/document/d/1whpf9g8ylRwHkzzDqByFRdY
> > 6pklqHd_92_v1eCDfeAM/edit?usp=sharing
> >(Student: Lethe)
> >5. List Of Contributors -
> >https://docs.google.com/document/d/1GD36m1zQtvYYmX6d0J8c_4b
> > UkWqihHjfsQG1-qhqBYw/pub
> >(Student: Devi R)
> >6. Port catimages.py to pywikibot-core -
> >https://commons.wikimedia.org/wiki/User:AbdealiJK/file-meta
> > data/GSoC2016
> >(Student: Abdeali)
> >
> > Hearty congratulations to the mentors and students involved, and to all
> who
> > could participate in this round of GSoC/Outreachy. Three of the Outreachy
> > selects were considered for GSoC, and hence there is no specific results
> > for Outreachy.
> >
> > *Showcase* for GSoC projects along with CREDIT, this week:
> >
> > Please join us in the GSoC showcase of all evaluation completed projects
> > along with CREDIT showcase, this week on Sep 7, 2016 (1800 UTC). Please
> > find the original email of the same over here[1], which have instructions
> > for interns to add their projects to the showcase, and other
> arrangements,
> > etc. Those interns who cannot can make it to this week CREDIT, are
> welcome
> > to do it in the following one.
> >
> > The showcase will include a minimum 5 mins demo, which can include a
> > presentation of some sort and a short and sweet explanation of what was
> > done as part of the program. We expect the mentors too online and live,
> to
> > make this a success! This would be the best time to provide links to blog
> > posts the interns have done on the same too, so that the community can
> > catch up!
> >
> > [1]
> > https://lists.wikimedia.org/pipermail/wikitech-l/2016-Septem
> > ber/086415.html
> >
> > Thanks,
> > Tony Thomas <https://www.mediawiki.org/wiki/User:01tonythomas>
> > Home <http://www.thomastony.me> | Blog <https://tttwrites.wordpress.com/
> >
> > |
> > ThinkFOSS <http://www.thinkfoss.com>
> >
> >
> > On Mon, Sep 5, 2016 at 2:23 PM, Quim Gil <q...@wikimedia.org> wrote:
> >
> > > Indeed, congratulations to everybody for your hard work -- mentors and
> > org
> > > admins too!
> > >
> > > On Fri, Sep 2, 2016 at 9:10 PM, Alangi Derick <alangider...@gmail.com>
> > > wrote:
> > >
> > > > Hi Bryan Davis,
> > > >
> > > > Thanks. I find FLOSS that way. :)
> > > >
> > > > Regards
> > > > Alangi Derick Ndimnain
> > > >
> > > > On Fri, Sep 2, 2016 at 8:07 PM, Bryan Davis <bd...@wikimedia.org>
> > wrote:
> > > >
> > > > > On Fri, Sep 2, 2016 at 1:01 PM, Alangi Derick <
> > alangider...@gmail.com>
> > > > > wrote:
> > > > > >

[Wikitech-l] Fwd: [Wikimedia-l] Open call for Project Grant proposals (Sep 12-October 11)

[Quim Gil]

FYI

-- Forwarded message --
From: Marti Johnson <mjohn...@wikimedia.org>
Date: Tue, Sep 13, 2016 at 1:34 AM
Subject: [Wikimedia-l] Open call for Project Grant proposals (Sep
12-October 11)
To: Wikimedia Mailing List <wikimedi...@lists.wikimedia.org>


Hi everyone,

The Wikimedia Foundation Project Grants program launches its second open
call today, September 12.  We will be accepting proposals through October
11 for new ideas to improve Wikimedia projects.

Funds are available to support individuals, groups and organizations to
implement new experiments and proven ideas, whether focused on building a
new tool or gadget, organizing a better process on your wiki, researching
an important issue, coordinating an editathon series or providing other
support for community-building.

Ideas from the current Inspire Campaign on addressing harassment are very
welcome. <https://meta.wikimedia.org/wiki/Grants:IdeaLab/Inspire>

Do you have have a good idea, but would like some feedback before
applying?  Put it into the IdeaLab, where volunteers and staff can give you
advice and guidance on how to bring it to life. <
https://meta.wikimedia.org/wiki/Grants:IdeaLab>  Once your idea is ready,
it can be easily migrated into a grant request.

Marti Johnson and I will also be hosting weekly proposals clinics via
Hangouts for real-time discussions about the Project Grants Open Call.
We’ll answer questions and help you make your proposal better.  Dates and
times are as follows:

* Fri, Sep 16, 1400- 1500 UTC

* Tues, Sep 20, 0100 - 0200 UTC

* Wed, Sep 28, 1400 - 1500 UTC

* Tue, Oct 4, 2200 - 2300 UTC

* Tues, Oct 11, 0200 - 0300 UTC

* Tue, Oct 11, 1600 -1700 UTC

Links for Hangouts are available here: <
https://meta.wikimedia.org/wiki/Grants:Project>

We are excited to see your grant ideas that will support our community and
make an impact on the future of Wikimedia projects.  Put your idea into
motion, and submit your proposal between September 12 and October 11! <
https://meta.wikimedia.org/wiki/Grants:Project/Apply>

Please feel free to get in touch with me (mjohn...@wikimedia.org) or Alex
Wang (aw...@wikimedia.org) with questions about getting started with your
project!

Warm regards,

Marti


*Marti JohnsonProgram Officer*
*Individual Grants*
*Wikimedia Foundation <http://wikimediafoundation.org/wiki/Home>*
+1 415-839-6885
Skype: Mjohnson_WMF

Imagine a world in which every single human being can freely share
<http://youtu.be/ci0Pihl2zXY> in the sum of all knowledge.  Help us make it
a reality!
Support Wikimedia <https://donate.wikimedia.org/>
___
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Outreachy-13 mentors needed

[Quim Gil]

On Mon, Sep 12, 2016 at 3:23 PM, Lucie-Aimée Kaffee <
lucie.kaf...@wikimedia.de> wrote:

> Hey,
>
> I got asked by a friend whether there are any projects in Outreachy in
> general and if any projects could be pitched to Wikimedia in particular,
> that are focused on UX or if it's limited to software development.
>

Pitching projects is good, although the usual bottlenecks are community
consensus and availability of mentors. Non-coding technical projects are
fine in Outreachy (not in GSoC).

For what is worth, there is an ongoing conversation that fits this idea at
https://phabricator.wikimedia.org/T87598 (Create a CAPTCHA that is also a
useful micro edit)


> Thanks for the organization of this awesome program!
>
> On Mon, Sep 12, 2016 at 8:58 AM, Sumit Asthana <asthana.sumi...@gmail.com>
> wrote:
>
> > Hello Wikimedians,
> >
> > Gnome's Outreachy-13 <https://wiki.gnome.org/Outreachy> is round the
> > corner
> > and Wikimedia is again participating in yet another internship season (
> Dec
> > 6 to March 6 ). The application deadline is *Oct - 17*.
> >
> > Its interesting to see that candidates have already started to ping on
> > projects and show their interest!
> >
> > Our Outreachy-13 board
> > <https://phabricator.wikimedia.org/project/board/2207/> till now has
> only
> > three projects. A lot of projects are sitting in possible-tech-projects
> > <https://phabricator.wikimedia.org/tag/possible-tech-projects/> board
> > waiting to be mentored. Many of them are tagged as *community-wishlist*
> > showing the community consensus.
> > The *community wishlist* items which could use some love are:
> >
> >1. Make Special:Listfiles show the quantity of globalusage for a file
> -
> >T120748 <https://phabricator.wikimedia.org/T120748>
> >2. Category suggestions based on filename, description and location -
> >T120437 <https://phabricator.wikimedia.org/T120437>
> >3. Create a Timer based reminder for workflows - T88781
> ><https://phabricator.wikimedia.org/T88781>
> >
> > Some others which look interesting:
> >
> >1. Dark archive for Commons - T120454
> ><https://phabricator.wikimedia.org/T120454>
> >2. Create a CAPTCHA that is also a useful micro edit - T87598
> ><https://phabricator.wikimedia.org/T87598>
> >3. Fix TreeViews to provide pageviews statistics for all articles of
> any
> >wikiproject etc. - T56184 <https://phabricator.wikimedia.org/T56184>
> >4. Stash unsaved drafts of articles - T89235
> ><https://phabricator.wikimedia.org/T89235>
> >5. Merge proofread text back into Djvu files - T59807
> ><https://phabricator.wikimedia.org/T59807>
> >
> > Its a gentle request to please go through the projects, and if you could
> > mentor any of those, add yourself to the task as a mentor, and we'll do
> the
> > rest.
> >
> > Also, if you have a lingering task to finish or a new interesting feature
> > waiting to get implemented, add *possbile-tech-projects*, and we'll make
> > sure to feature it. The only scope requirement is that it should take 2-3
> > weeks for an experienced developer to finish.
> >
> > Please come forward to mentor some of the enthusiastic students so that
> we
> > can welcome new members into our community :)
> >
> > -Thanks and Regards,
> > -Sumit,
> > B.Tech Final Year,
> > Dept. of CSE,
> > IIT Patna
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> Lucie-Aimée Kaffee
> [[User:Frimelle]]
> Software Development
>
> Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
> Phone: +49 (0)30 219 158 26-0http://wikimedia.de
>
> Imagine a world in which every single human being can freely share in
> the sum of all knowledge.
> That‘s our commitment.
>
> 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.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Looking for WikiDev Summit main topics and volunteers

[Quim Gil]

On Fri, Sep 9, 2016 at 1:36 AM, MZMcBride <z...@mzmcbride.com> wrote:

> Who specifically are the organizers of the Wikimedia Developer Summit 2017?
>

Rachel Farrand is the event organizer and I am the budget owner. We want to
bootstrap an actual organization team this year, and I have shared our
current idas at https://www.mediawiki.org/wiki/Topic:Tb8g53x15wvhoc5e


> I have a question for the organizers: will the summit be open to anyone or
> will it be invitation-only as it has been in past years? Who decides this?
>

Rachel and I ultimately decide how the Summit registration works.

We are leaning toward invitation-only precisely to support the idea of
"open to anyone". As explained in [0] and [1], we want to reach out to
different audiences that usually haven't got much representation in the
Summit, we have a capacity limit, and we want to avoid that the regular
participants of the Summit takes all seats just because they already know
they want to attend and register sooner.

"Invitation-only" would mean that anyone can fill the form to request
registration free of charge, but their request would need to be accepted in
order to become confirmed participants of the Summit. Another piece of
context is that we are interested in improving remote participation, where
the limitations of event capacity and travel costs don't apply.

[0]
https://lists.wikimedia.org/pipermail/wikitech-l/2016-September/086448.html
("AUDIENCE")
[1]
https://lists.wikimedia.org/pipermail/wikitech-l/2016-September/086468.html


Regarding main topics, I think we should make it easier to log in to
> Wikimedia wikis and control your identity when on-wiki. Specifically,
> supporting login via e-mail address, case-insensitive login, and a
> user-configurable "display name" field that's shown in page histories, on
> user pages, etc.
>

Added to https://www.mediawiki.org/wiki/Topic:Tb6bztglijowk8x3 (anyone with
suggestions for main Summit topics can do so too).



> I'm interested in volunteering to provide feedback about the upcoming
> summit. I've attended one or two summits in the past and I have thoughts.
>

Please go ahead and share your feedback in
https://www.mediawiki.org/wiki/Talk:Wikimedia_Developer_Summit_2017. You
can also provide feedback about specific tasks underhttps://
phabricator.wikimedia.org/tag/wikimedia-developer-summit/, and we keep
monitoring wikitech-l.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Looking for WikiDev Summit main topics and volunteers

[Quim Gil]

Hi Billghost, thank you for your interest!

On Thu, Sep 8, 2016 at 5:03 PM, Bill Morrisson <billmorrisso...@gmail.com>
wrote:

> Hello,
>
> I would love to volunteer, is there any particular task to do??
>

We are bootstrapping the event, and there are two immediate tasks where
everyone's help is welcome:

BRAINSTORMING MAIN TOPICS

Do you have specific proposals for the (say) five main Summit topics that
should be selected? Can you help spreading this question to your contacts
and the venues in our technical community where you are active? All the
suggestions are being collected at
https://www.mediawiki.org/wiki/Topic:Tb6bztglijowk8x3.

For instance, you have gone through a Google Summer of Code project, and
right now you possess a very valuable experience that others haven't
acquired yet, or have forgotten about: the experience of a new developer
dealing for the first time with our collaboration processes, our developer
environment, our documentation, and the people and behaviors in our
community. Your ideas about which main topic should the Summit address are
interesting, and your help spreading the word among other GSoC students,
mentors, and newcomers in general is very important.

Other people reading these lines can apply the same idea to their own case.
Whatever is your background and areas of interest, your perspective and
influence in the definition of the Summit is welcome.

SUMMIT LANDING PAGE

We could use some help on the Summit landing page and related pages. See

Wikimedia Developer Summit Wiki up
https://phabricator.wikimedia.org/T141935

Until now we have got functional wiki pages for Summit participants but no
focus in outreach through those wiki pages at all. Many things could be
done in theory, but what can we realistically do here and now, with the
hands we have? See you in the task?

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Looking for WikiDev Summit main topics and volunteers

[Quim Gil]

Hi, this is a request from the organizers of the Wikimedia Developer Summit
2016 (San Francisco, January 9-11).

We are looking for candidates to become main topics of the next Summit.
Ideally complex topics with a high user impact (direct or indirect) and
ramifications in multiple technical areas. Deciding a few main topics
beforehand will help us inviting the people needing to be involved,
especially non-WMF contributors requiring travel sponsorship.

We are also looking for volunteers who want to get involved in the
organization of the Summit, or want to provide feedback to improve our
plans.

If you have proposals for main topics and/or want to volunteer, please
reply.

Context: https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2017 &
https://lists.wikimedia.org/pipermail/wikitech-l/2016-September/086476.html

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

[Quim Gil]

On Wed, Sep 7, 2016 at 8:45 PM, Rob Lanphier <ro...@wikimedia.org> wrote:

> It's hard for me to read this as anything but "WMF Product selects the
> topics, and then 'listens' for objections on wikitech-l".


Since this is not even remotely what I am trying to say, let me try again,
while I keep iterating on the proposal:

The organizers of the Summit propose to have a few main topics defined
beforehand, so we can invite the people beyond the usual Summit
participants that should be involved in these discussions.

We don't have any opinion about which topics should be selected. However,
we believe that it is important to choose complex topics with a high user
impact (direct or indirect) and ramifications in multiple technical areas.
The Summit with its +200 participants provides a great framework to push
these topics.

We don't have any opinion about who decides these topics and how. However,
we need good enough answers and fast, so we can start organizing the
participation and the program. There will be time to fine tune things as we
go, and there will be enough space for all the topics not selected
beforehand, in the unconference part of the Summit.

We believe that by having the right people focusing on a few main topics
before and during the Summit, the outcome of the event will have a clearer
impact in the strategy and goals that ultimately drive where we put a lot
of our attention and resources.

Is your sense that the
> correct direction for us is for someone to provide more top-down
> direction instead of wikitech-l conversation?
>

My sense is that we need to open registration, call for participation, and
call for travel sponsorship requests as soon as possible. This list, the
Architecture committee, the WMF Technology management team, and the WMF
Product management team are aware of this situation and our request to
define main topics. I will be checking with all these sources with the goal
of having a good enough answer that allows us to move forward with the
Summit organization.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

[Quim Gil]

On Tue, Sep 6, 2016 at 5:55 PM, Rob Lanphier <ro...@wikimedia.org> wrote:

> On Mon, Sep 5, 2016 at 11:14 PM, Quim Gil <q...@wikimedia.org> wrote:
> > GOALS [...] The Summit and its goal have been a moving target over the
> > years, as you can deduce from the many changes of names & goals. [0]
>
> It has been, but given the high satisfaction scores last year, I think
> it behooves us to come up with iterative improvements, not a radical
> rethink.  It seems like last year we got closer to what we've been
> struggling to achieve in previous years.
>

The satisfaction scores about the Summit itself (based on a survey run just
at the end of the event) are indeed high, and I agree that we should keep
the basic model for the three days, just adding iterative improvements
wherever needed. This comprises combination of pre-scheduled and
unconference sessions, the organization in areas with owners, the
organization of sessions with note-takers and other roles...

We have got clear feedback about the need to rethink the phases before and
after the event.

Before, the call for participation and the selection process was felt as
confusing and requiring a lot of energy from everyone (organizers
included), without a clear benefit. By agreeing on a few main focus areas
beforehand and "curating" them (assuring the the right people are invited
and the right topics are addressed), we could leave more freedom of
self-organization to all the rest.

After, the Summit discussions that brought high levels of satisfaction get
frequently colder and stalled, having little or no impact in the daily
work, quarterly planning, longer term strategy. By agreeing on a few main
focus areas that are already connected to our strategy and plans, and by
assuring that all required parties are as involved as the developers, the
Summit will have the impact that its participants expect.


>
> > Widening the audience was a main goal last year. This is why we renamed
> it
> > to Wikimedia (not MediaWiki) Developer Summit, and we invited developers
> of
> > tools, templates, bots, mobile apps, the MediaWiki Stakeholders Group,
> and
> > also non-Wikimedia users of our APIs. It was a half-backed thought that
> > received half-backed support that unsurprisingly brought half-backed
> > results.
>
> I think that's a bit unfair to what we accomplished last year.
>

My evaluation is based on the number of non-WMF developers specializing on
tools, templates, bots, mobile apps, MediaWiki, and other users of our
APIs, and what they got from the event. It is also based on how much
outreach effort we managed to put into assuring that the participation from
these sectors was rich and diverse. Making the assessment above doesn't
make me happy at all, but I think it is a fair and frank one.

> What if the Summit would be product driven, with architecture and the rest
> > following that drive. All we are here to offer better products to our
> > users. All the technical discussions make more sense when there is a
> clear
> > product vision to be either supported or contested with reality checks.
>
> I would like to get Wes's take on this.  Last year, I didn't get the
> sense that Wes was eager to grab the reins on WikiDev16, and I'd be
> surprised if he wants to do it this year.  That seems to dump too much
> of the responsibility on him.
>
> It would seem that the target *participant* for this summit would be
> the future WMF Chief Technology Officer (CTO).  Assuming that we have
> the CTO hired by January, it would set the bar way too high to expect
> that the new CTO will be responsible for running the summit.  We
> should strive to make a big theme of this summit be "onboarding WMF's
> new CTO".  Obviously, the scope should be more than that, but let's
> hope that WikiDev17 is a great introduction to the wikitech-l
> community for our new CTO
>

OK, it looks like I need to define better what I mean by "product driven".
First of all yes, MediaWiki and Wikipedia clearly are products. Then...

When Brion opens this thread proposing to refocus the Summit "to prioritize
and work on things that really matter" to our users, he is basically
proposing to change from a tech-architecture-infrastructure-driven
perspective to a perspective driven by user experiences, the features that
users miss, the problems that bug them most. Let the users talk, and then
we will figure out what that means in terms of technology, architecture,
infrastructure.

I don't think that a reinvented "Dev Summit that asks our users to participate"
is feasible in the literal sense, if that Summit needs to happen in January
and today we are just beginning to discuss the notion of it. But I strongly
agree with Brion's point, and I think that a totally feasible move in that
dir

Re: [Wikitech-l] Wikimedia Developer Summit - Participation

[Quim Gil]

Let's spin-off the topic about Summit participants.

On Tue, Sep 6, 2016 at 3:40 PM, Eran Rosenthal <eranro...@gmail.com> wrote:

> So the capability limit can be soften a bit - this could be a simultaneous
> event in multiple different locations where the main part take in SF, but
> Wikimedia chapters may organize in the same time smaller scale events (it
> could be even 1 room +pizza ++beer).


The capacity limit for 200 is actually a more flexible number, yes. This
number is related to these expectations:

* size of the main room so everyone can fit
* catering so everyone is fed
* social events at night
* accommodation booked by the organizers

While many participants basically "live" at the Summit using all of its
services from beginning to end, others may be interested in participating
without challenging the expectations mentioned, i.e. attending only some
days / sessions, not requiring accommodations, etc. This is something that
can be discussed.

The idea of remote participation needs to be better explored, but at least
for the Summit I would start looking at the case of individual contributors
willing to participate in specific discussions. The Summit is more about
discussing that about hacking.

The idea of complementary locations organized by chapters sounds like a
better fit for the hackathons. There is the aspect of timezones too. In any
case, if a chapter wants to try, we are happy to experiment (WMDE sounds
like a good candidate for experimentation, since they send a good number of
people to the Summit but many more are "left" in Berlin).

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Opening up MediaWiki dev summit in January?

[Quim Gil]

pation, so this may be a
> budgetary issue that needs to be weighed against using those same
> scholarships for active developers. I think some of the comments on this
> thread are correct, that it's likely that at least some of the discussions
> at the Dev Summit will be too esoteric for non-developers.  On the other
> hand, there was a point where I only understood about 3% of what was posted
> on this mailing list, and I think I can quite honestly say I'm all the way
> up to 25% now.  People do learn by assimilation. :-)
>
> A similar process can be done with Wikimania - which has the added
> advantage of already attracting hundreds of community members for other
> reasons.  I'd suggest that a special "developer/community day" be held in
> conjunction with the hackathon.  While it's likely you'd still need to
> offer scholarships, in most cases it would be the cost of an additional
> day's accommodation/per diem rather than flight/accommodation/per diem,
> because you would target people who are already planning to attend
> Wikimania.  I expect that the 2017 Wikimania will be one of the largest
> ones, since it is in North America and easily accessible by just about
> everyone, so there is likely to be a large target audience.  You might want
> to work with Marc-Andre (who is the Wikimania Convenor) to see how this
> could be accommodated.
>
> Thanks Brion for raising the topic - and thanks to everyone in this thread,
> you've all taken this idea to heart and recognized the value of user
> input.
>
> Risker/Anne
>
>
>
> On 1 September 2016 at 13:12, Brion Vibber <bvib...@wikimedia.org> wrote:
>
> > The last couple years we've done a big MediaWiki Dev Summit in January,
> > around the time of the Wikimedia Foundation all-hands meeting.
> Invitations
> > have been fairly broad to known developers, but there's a very strong
> > feeling that newbies, non-technical people, and in general *the people
> > MediaWiki is created and maintained for* are not welcome.
> >
> > I think we should change this.
> >
> > I would really like a broader MediaWiki Dev Summit that asks our users to
> > participate, and asks "developers" to interact with them to prioritize
> and
> > work on things that really matter to them.
> >
> > I want template authors, Lua module authors, template users, power
> editors,
> > folks working on the lines of defense for vandalism patrol and copyvio
> > checking. I want people with opinions on discussion systems. I want
> people
> > who have been editing for years and have experience with what works and
> > what doesn't. I want people who wish they could edit but have a bad
> > experience when they try, and want to share that with us so we can help
> > make it better.
> >
> > Thoughts?
> >
> > -- brion
> > _______
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Congratulations to all GSoC students (passed)

[Quim Gil]

Indeed, congratulations to everybody for your hard work -- mentors and org
admins too!

On Fri, Sep 2, 2016 at 9:10 PM, Alangi Derick <alangider...@gmail.com>
wrote:

> Hi Bryan Davis,
>
> Thanks. I find FLOSS that way. :)
>
> Regards
> Alangi Derick Ndimnain
>
> On Fri, Sep 2, 2016 at 8:07 PM, Bryan Davis <bd...@wikimedia.org> wrote:
>
> > On Fri, Sep 2, 2016 at 1:01 PM, Alangi Derick <alangider...@gmail.com>
> > wrote:
> > > Hi,
> > >
> > > I wish to use this opportunity to congratulate all the 6 students
> > > (including me) that made it to the end of the GSoC program 2016 in the
> > > Wikimedia foundation. It was not easy but we made it to the end. It
> was a
> > > great time working with the Wikimedia Foundation and I had a very great
> > > experience.
> >
> > Congratulations to everyone. I hope that all of you find FLOSS
> > projects to continue to contribute to.
> >
> > Bryan
> > --
> > Bryan Davis  Wikimedia Foundation<bd...@wikimedia.org>
> > [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
> > irc: bd808v:415.839.6885 x6855
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Phab blogs

[Quim Gil]

Hi,

On Wed, Aug 31, 2016 at 8:03 AM, Tilman Bayer <tba...@wikimedia.org> wrote:

> Apparently there hasn't been much discussion or deliberation about the
> advantages and disadvantages of this new feature compared to other
> communication channels.


Excess of communication channels is a big problem in Wikimedia and a
regular topic for complaints from new and experienced contributors
(volunteers or paid, tech or non-tech). I think such discussion about
advantages and disadvantages should happen before we invest too much
content and attention in Phabricator blogs.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] +2 for Glaisher in mediawiki

[Quim Gil]

On Sat, Aug 13, 2016 at 7:23 PM, Legoktm <legoktm.wikipe...@gmail.com>
wrote:

> Hi,
>
> Per[1], I have given Glaisher +2 rights in all mediawiki repositories.
> Congrats, and thanks for all of your contributions so far!
>

Congratulations indeed! In the past months it has been really difficult to
be active in Wikimedia technical spaces and not see Glaisher in action,
always providing answers, feedback and code.


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: Technical Collaboration quarterly goals for October - December 2016

[Quim Gil]

Hi,

We are starting to discuss the Technical Collaboration
<https://meta.wikimedia.org/wiki/Technical_Collaboration> team plans for
October - December. If you or your communities have proposals about goals
or other tasks this team should plan for, please share them at

https://phabricator.wikimedia.org/T142355

For more information about our quarterly goals, see https://meta.wikimedia.
org/wiki/Technical_Collaboration/Goals

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Too many knobs

[Quim Gil]

Just in case you find it interesting:

http://neverworkintheory.org/2016/06/09/too-many-knobs.html summarizes this
paper:

"Hey, You Have Given Me Too Many Knobs! Understanding and Dealing with
Over-Designed Configuration in System Software". ESEC/FSE'15, August 2015,
http://dx.doi.org/10.1145/2786805.2786852,
http://cseweb.ucsd.edu/~tixu/papers/fse15.pdf.

The topic of amount and usefulness of user preferences is relevant to our
software. I dream of a simpler user configuration by default combined with
easier ways to find and enable community supported gadgets.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Job opening: Wikimedia developer advocate

[Quim Gil]

We usually don't post job openings in mailing lists, but I am making an
exception with this one because our best candidate *might* be subscribed /
idling here.

Developer Advocate
http://grnh.se/asv1wu

Your help spreading the news are also appreciated.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Phabricator monthly statistics - 2016-05

[Quim Gil]

On Wed, Jun 1, 2016 at 2:05 AM, Pine W <wiki.p...@gmail.com> wrote:

> I'm impressed by how many new accounts were created; 256 in a single month.
>

See
https://www.mediawiki.org/wiki/Community_metrics#New_accounts_in_Phabricator


> I'd be interested to know what typically prompts people to create accounts.
>

I clicked on a random selection of recently created accounts. There were
several Wikimedians going after projects like Wiki Loves Earth, Wikidata,
other stuff interesting for tech-savvy editors. There were some accounts
without activity and without profile in mediawiki.org (but I didn't check
whether those usernames had contributions in other projects) and there was
at least one clear tester (spammer?) recently blocked in mw.o.

I have the impression that the significant growth is driven by editors who
become aware and familiar with Phabricator, watching technical tasks closer
but also getting involved in less technical projects using Phabricator as
the project management tool that it is. I have no references or data to
back up this assumption, sorry.  :)

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Technical Collaboration goals for July - September 2016

[Quim Gil]

Hi, the Wikimedia Foundation Technical Collaboration team (Community
Liaisons + Developer Relations) is defining individual and team goals for
the next quarter, July - September 2016.

We welcome your feedback. Which tasks should we prioritize? Please share
your suggestions, preferably at https://phabricator.wikimedia.org/T131915

More: https://meta.wikimedia.org/wiki/Technical_Collaboration/Goals

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Which Phabricator project for site issues?

[Quim Gil]

On Sat, May 28, 2016 at 3:24 PM, MZMcBride <z...@mzmcbride.com> wrote:

> You have to know that tasks related to
> "transclusion" are often associated with "MediaWiki-Templates". Finding
> and making that association is difficult currently.
>

Hashtags might help:
https://phabricator.wikimedia.org/project/manage/142/#24156

Feel free to remove this one if you think it is not appropriate. No project
was claiming "transclusion" before.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] update: wikipedia.org portal

[Quim Gil]

Hi,

On Sat, May 21, 2016 at 1:07 AM, MZMcBride <z...@mzmcbride.com> wrote:

> It's frustrating and annoying that your happy team hijacked this portal...

(snip)


Hostility and anger are not welcomed in this mailing list, neither in the
rest of Wikimedia spaces. Any problems can be reported and explained in a
respectful and even friendly way. The topics you are exposing in this
thread are no exception.

Please read https://www.mediawiki.org/wiki/Expected_behavior for more
thoughts about keeping our communities respectful, welcoming, and friendly.
If you want to discuss my reply, please use the discussion page of the URL
above, or reply to me directly. Let's keep this thread on-topic about the
update to the www.wikipedia.org portal. Thank you.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposal to invest in Phabricator Calendar

[Quim Gil]

Hi Faidon,

On Mon, May 16, 2016 at 1:53 PM, Faidon Liambotis <fai...@wikimedia.org>
wrote:

> If we have spare budget for the FY, a good start, I think, would be
> (properly) implementing https://secure.phabricator.com/T5000, by
>

I have reflected your request at
https://phabricator.wikimedia.org/T135327#2304387



> implementing https://secure.phabricator.com/T8092 which in turn depends
> on https://secure.phabricator.com/T8093 and possibly depends on
> https://secure.phabricator.com/T4369 and
> https://secure.phabricator.com/T4245.
>

Copied to https://phabricator.wikimedia.org/T127#2304394 fwiw.


https://secure.phabricator.com/T10691 (depending on all of the above)
> could be potentially interesting for us too.
>

Do we have a related task in Wikimedia Phabricator?

In any case, please reflect your proposals at
https://phabricator.wikimedia.org/T135327 directly, because this is where
we are looking at for candidates. (I moved Faidon's feedback to Phabricator
because he is a nice person and because I probably owe him a KEO beer or
two).  :)

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: [Wikimedia-l] Announcing Rapid Grants

[Quim Gil]

Dear Wikimedia technical community,

If you ever thought of organizing a small event, print some stickers, or
any other activity for the good of Wikimedia that costed money, now Rapid
Grants might be the simple solution you were looking for. Details below.


-- Forwarded message --
From: Alex Wang <aw...@wikimedia.org>
Date: Wed, May 18, 2016 at 5:11 AM
Subject: [Wikimedia-l] Announcing Rapid Grants
To: Wikimedia Mailing List <wikimedi...@lists.wikimedia.org>


Hello Wikimedians,

We are excited to announce the launch of a new Wikimedia Foundation grants
program, Rapid Grants!

Rapid grants fund Wikimedia community members -- individuals, groups, or
organizations contributing to Wikimedia projects -- to organize projects
throughout the year for up to USD 2,000. Projects can include experiments
or standard needs that don't need broad review to get started. Applications
are reviewed weekly by WMF staff.

Read more about the new program and apply here:
https://meta.wikimedia.org/wiki/Grants:Project/Rapid

Questions? Email rapidgra...@wikimedia.org

For more information about next steps and important dates for the grants
program redesign, please visit:
https://meta.wikimedia.org/wiki/Grants:IdeaLab/Reimagining_WMF_grants/Implementation

Cheers,

Alex

--
Alexandra Wang
Program Officer
Community Resources
Wikimedia Foundation <http://wikimediafoundation.org/wiki/Home>
+1 415-839-6885
Skype: alexvwang
___
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: wikimedi...@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Proposal to invest in Phabricator Calendar

[Quim Gil]

I wouldn't base any data analysis on the #Phabricator-Upstream workboard.
Let's look at the tasks themselves.

https://phabricator.wikimedia.org/maniphest/query/Ou8pP.fE9ufA/#R shows 131
tasks with #Phabricator-Upstream tag and status Resolved. In almost every
Phabricator update we are getting some fixes to bugs that were filed in
Wikimedia Phabricator. If anything, I keep being impressed by the capacity
of such small team to do so much work.

Rob is right pointing that our priorities will not be necessarily the
Phabricator maintainers' priorities. Our experience discussing priorities
with Phabricator maintainers is very good. By that I mean that they have a
clear idea of their roadmap, what is aligned and what it isn't. Discussions
about prioritization and funding have been pretty straightforward until
now. Let's have our list defined, and then I'm sure Andre, Mikunda, Chad,
Greg, and myself will be able to reach a good agreement with the
Phabricator maintainers.


On Tue, May 17, 2016 at 2:07 AM, John Mark Vandenberg <jay...@gmail.com>
wrote:

> On Tue, May 17, 2016 at 4:42 AM, Federico Leva (Nemo)
> <nemow...@gmail.com> wrote:
> >> That said, I think we should be careful with our assumptions about how
> >> much influence we can buy with the money we have.
> >
> > Sure. Let's not make assumptions at all then: what makes someone think
> that
> > calendar is amenable to WMF-mandated development? Already one year ago, I
> > proposed that Phacility be hired to upstream our issues (and triage them
> > upstream).
> >
> https://lists.wikimedia.org/pipermail/teampractices/2015-March/000642.html
> >
> > The reason is that so far I'm not aware of a single person in Wikimedia
> > being able to talk with upstream (as opposed to talking past each other).
> > https://phabricator.wikimedia.org/project/board/6/query/all/ seems to
> prove
> > none exists, as the "Solved upstream" column lists a whopping 2 issues
> out
> > of 500+ upstream issues.
>
> And of those two tasks, one is a regression and the other is an
> exception. i.e. not functional improvements.
>
> I have added T109956 to that column, and would do more to help
> categorisation of solved tasks, but I note that "Solved upstream" is
> not explained at the documentation
> https://www.mediawiki.org/wiki/Phabricator/Code , so I wonder if I am
> doing something wrong.
>
> It should be noted that we have successful built some local
> extensions/customisations, such as the Sprint.
> If we are having difficulty providing improvements to the core
> product, then funding incomplete extensions (like Calendar) is a good
> approach.
>
> --
> John Vandenberg
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Prioritizing Phabricator improvements (was Re: Proposal to invest in Phabricator Calendar)

[Quim Gil]

After a first wave of feedback it is clear that we have two different
discussions that need solving:

1. If we use WMF Technical Collaboration budget for Phabricator
improvements, should we invest it the Calendar application? This is a well
framed discussion with a clear deadline for decisions (very soon, or our
FY2015-16 budget will be gone). I have created a task to discuss this
specifically: https://phabricator.wikimedia.org/T135327

2. If we want to improve the announcement and promotion of Wikimedia tech
events, is the best first step to improve Phabricator Calendar? This is a
complex discussion with many ramifications that we can keep discussing at
https://phabricator.wikimedia.org/T1035

On Sat, May 14, 2016 at 3:06 AM, Legoktm <legoktm.wikipe...@gmail.com>
wrote:

> If we're going to be investing money into improving Phabricator upstream
> (a great idea IMO), I think we should start with problem areas that
> affect a large number of users/developers.


Agreed. If I am proposing improvements around Calendar is because our team
believes that we have a problem affecting the announcement and promotion of
technical activities beyond the circle of usual and core contributors. By
improving this area, we believe we could reach better to more casual
technical contributors in our movement, and reach out better to new
contributors out there.


> There's plenty of low-hanging fruit like non-drag-n-drop file uploads[1].


Agreed. This one is being funded already.


> [2] was also mentioned on #wikimedia-tech a few days ago


Good, I wasn't aware. Is there a task in Wikimedia Phabricator reflecting
the level of need, support, consensus? Feel free to propose it as suggested
in https://phabricator.wikimedia.org/T135327


> or some of the UI/UX issues Nemo brought up after the last Phabricator
> upgrade[3].
>

I think https://secure.phabricator.com/T10926 reflects the essence of the
improvements requested after the Phabricator UX update. It looks like the
discussion so far is more about agreement on UX problems/solutions than
complexity of the solution once agreed, but if there is room for funded
prioritization, that also looks like a good candidate for a proposal.


[1] https://phabricator.wikimedia.org/T165#2289766
> [2] https://secure.phabricator.com/T10691#167705
> [3] https://lists.wikimedia.org/pipermail/wikitech-l/2016-May/085489.html
>


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Proposal to invest in Phabricator Calendar

[Quim Gil]

Annoyed by the difficulties of tracking events in the Wikimedia tech
community? Or by the difficulties of announcing events in an effective way?
Check this out:

Consolidate the many tech events calendars in Phabricator's calendar
https://phabricator.wikimedia.org/T1035

The hypothesis is that it is worth improving the current situation with
calendars in the Wikimedia tech community, and that Phabricator Calendar is
the best starting point. If we get a system that works for Wikimedia Tech,
I believe we can get a system that works for the rest of Wikimedia,
probably with some extra steps.

The Technical Collaboration team has some budget that we could use to fund
the Phabricator maintainers to prioritize some improvements in their
Calendar. If you think this is a bad idea and/or you have a better one,
please discuss in the task (preferred) or here. If you think this is a good
idea, your reassuring feedback is welcome too.  ;)

Thank you!

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [GSoC 2016] Community Bonding

[Quim Gil]

On Sun, May 1, 2016 at 6:49 PM, Alangi Derick <alangider...@gmail.com>
wrote:

> Hi everyone
>
> I am Alangi Derick and also d3r1ck on the IRC. I was selected in the GSoC
> 2016 program and was opportuned to work on the project titled "Integration
> of IFTTT support for Wikidata" and I am very happy to be the first African
> GSoCer in Wikimedia Foundation. This is indeed a priviledge and I wish to
> thank everyone that guided me in this movement to attain this level.
>

Alangi, I was very happy to see that you made it. When you started
contributing half year ago we told you that perseverance usually brings
fortune (maybe I didn't say it with these words)  ;)  and here you are,
with a well deserved GSoC internship. And indeed, you seem to be the first
Wikimedia GSoC student from Africa (Cameroon).

Since your project focuses on Wikidata, please consider sending this
message to the wikidata@ mailing list as well. Good luck with your project!

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: Texas Linux Fest 2016 CFP

[Quim Gil]

Below there is an excerpt from one of the organizers of Texas Linux Fest.
They are explicitly interested in Wikimedia participants / speakers. If you
have a proposal for a session, please consider submitting it. Also remember
that we have https://meta.wikimedia.org/wiki/Grants:TPS for sponsoring
travel costs in this type of situations. All the better if you are already
in North America.  :)

-- Forwarded message --
Nate Willis here; amongst my other project pastimes, I'm one of the
organizers
of Texas Linux Fest, which is the leading community Linux-and-FOSS
conference for Texas and the surrounding region.

Our event is July 8th and 9th this year, in downtown Austin, TX.  We'd
really love it if folks from the WikiMedia project & surrounding community
can be
there—be they local or from out of town.

I especially wanted to draw your attention to our call for
participation.  We're intent on attracting a wide variety of speakers
representing open source and free software, both users and developers,
from all corners.  The details are here:

http://2016.texaslinuxfest.org/call-for-papers

and the deadline is approaching.

Please consider submitting a talk proposal yourself, and we would doubly
love it if
you could help us spread the word by sharing the CFP with others in the
community!

If you have any questions, or if you want to know more about Texas
Linux Fest this year or in general, please get in touch!

Thanks, from me and on behalf of the entire TXLF 2016 team,
Nate


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Fwd: Developer metrics workshop next to OSCON

[Quim Gil]

FYI

-- Forwarded message --
From: Quim Gil <q...@wikimedia.org>
Date: Thu, Apr 28, 2016 at 9:37 AM
Subject: Developer metrics workshop next to OSCON
To: "A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics." <analyt...@lists.wikimedia.org>,
Manrique Lopez <jsmanri...@bitergia.com>


Hi, is there anybody in this list planning to attend OSCON (Austin, May
16-19)?

http://conferences.oreilly.com/oscon/open-source-us

Next to that event there will be a workshop about Software Development
Analytics and the new Grimoire toolkit platform, on May 16th (10am - 1pm CDT
):
https://www.eventbrite.com/e/software-development-analytics-workshop-tickets-24878480204

The registration is not free, but the organizers (Bitergia, the developers
of http://korma.wmflabs.org/ ) are offering us a couple of invitations.
Andre and I are not attending OSCON (we have participated in the FOSDEM
edition of this workshop). If you or someone you know is interested,
contact me.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Heads-up: "Write The Docs" conference in Sep 2016

[Quim Gil]

On Mon, Apr 25, 2016 at 4:29 PM, Andre Klapper <aklap...@wikimedia.org>
wrote:

> For those interested + working on Wikimedia documentation:
>
> There is a conf in Prague (Czech Rep) on Sep 18-20 "to explore the art
> and science of documentation" for "writers, developers, support folks".
>
> See http://www.writethedocs.org/conf/eu/2016 for more information.
>

See also Organize a MediaWiki Documentation Day (similar to the Gerrit
Cleanup Day) <https://phabricator.wikimedia.org/T126500>, where some
suggestions to combine a sprint with this conference can be found.


> There is https://meta.wikimedia.org/wiki/Grants which could be helpful
> when it comes to supporting travelling.
>

Seriously. There is this event in Prague, and before there is another one
in Berlin. If there is an interest in organizing a sprint, we might be able
to support a sprint with some travel sponsorships.


> I haven't attended the event myself but I've heard good stuff about it. :)


-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Rob Lanphier appointed to the Architecture Committee

[Quim Gil]

Congratulations! I hope this helps pushing forward the idea of working
groups that Rob has been pushing (among others).

On Tue, Apr 26, 2016 at 11:23 AM, Brion Vibber <bvib...@wikimedia.org>
wrote:

> Woot!
>
> -- brion
>
> On Monday, April 25, 2016, Tim Starling <tstarl...@wikimedia.org> wrote:
>
> > At the previous meeting of the MediaWiki Architecture Committee (April
> > 20), the members present approved the appointment of Rob Lanphier to
> > the committee.
> >
> > Rob was the main instigator in the formation of the committee in 2014.
> > Lately he has been taking an active role, chairing the weekly meetings
> > and writing the meeting agenda. In recognition of the excellent work
> > he has been doing, and in the interests of transparency, we decided to
> > formalise his membership.
> >
> > -- Tim Starling
> >
> >
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org <javascript:;>
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> _______
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Google Summer of Code 2016 and Outreachy results out, Congrats interns

[Quim Gil]

Congratulations to all the candidates selected -- and their mentors!

Also an encouragement to all the candidates that worked hard but could not
get an internship. Our statistics show that applicants going after a second
round have a very high success rate.

I also want to thank volunteer org admins Tony and Sumit, who (with just a
bit of support from Niharika and me) have run the GSoC and Outreachy
selection processes smoothly and on time. Tony, your announcement almost
reads like a Wikimedia Blog post (hint, hint).  :)

On Sat, Apr 23, 2016 at 9:56 AM, Aashaka Shah <aashak...@gmail.com> wrote:

> I had also submitted a GSoC proposal for "Improving static analysis tools
> for MediaWiki", but
>

Aashaka, thank your for your understanding. Without knowing the details of
this decision, let me note that Priyanka (prnk28) was in a situation
similar to yours six months ago, when she was an Outreachy candidate but
saw her application declined. Yet she continued being involved, I guess she
learned a lot, and got more experience in our developer community, and now
that perseverance is paying off.

D3r1ck01 has a similar story, and... can it be that he is our first African
GSoC student? He joined this community half year ago, expressed his clear
interest in this GSoC round, and since then he has been involved as a
volunteer, also learning through practice and informal mentorship from
experienced developers.

To all the participants in this round: don't give up! Wikimedia is a
movement offering many possibilities to volunteer developers. I'm sure
there is a project or two where you can learn, meet interesting people, and
prepare for the next round.

-- 
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l