[Wikitech-l] MOSS launches COVID-19 Solutions Fund

[Jonathan Morgan]

FYI:
https://blog.mozilla.org/blog/2020/03/31/moss-launches-covid-19-solutions-fund/

From the announcement: *"Mozilla is announcing today the creation of a
COVID-19 Solutions Fund as part of the Mozilla Open Source Support Program
(MOSS). Through this fund, we will provide awards of up to $50,000 each to
open source technology projects which are responding to the COVID-19
pandemic in some way. *

*The MOSS Program, created in 2015, broadens access, increases security,
and empowers users by providing catalytic funding to open source
technologists. We have already seen inspiring examples of open source
technology being used to increase the capacity of the world’s healthcare
systems to cope with this crisis. For example, just a few days ago, the
University of Florida Center for Safety, Simulation, and Advanced Learning
Technologies released an open source ventilator
.
We believe there are many more life-saving open source technologies in the
world.*

*As part of the COVID-19 Solutions Fund, we will accept applications that
are hardware (e.g., an open source ventilator), software (e.g., a platform
that connects hospitals with people who have 3D printers who can print
parts for that open source ventilator), as well as software that solves for
secondary effects of COVID-19 (e.g., a browser plugin that combats COVID
related misinformation)."*

-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
(Uses He/Him)

*Please note that I do not expect a response from you on evenings or
weekends*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Change page’s content model

[Jonathan Morgan]

Thanks XaosFlux and Gergo,

Gergo: Diego is working on the templates in his userspace, but our plan is
to move them to the template namespace when we're done testing, etc.

Thanks again for the quick turnaround on this!

- J

On Tue, Mar 10, 2020 at 11:14 AM Gergo Tisza  wrote:

> Hi Diego!
>
> On Tue, Mar 10, 2020 at 9:28 AM Diego Quintana 
> wrote:
>
> > So my question is, could you change my CSS page’s content model to
> > sanitized-css, or is there a way to create a new .css page and have it be
> > sanitized-css from its creation.
> >
>
> The content model is usually determined by the namespace when the page is
> created, and stays the same after that (administrators can change it, as
> you say). So you can create the page in the Template namespace with a .css
> extension, which will make it a sanitized-css page, and then move it
> elsewhere.
>
> In my opinion it's better to keep such pages in the template namespace
> though. User CSS subpages in particular are not ideal because they are
> protected from editing by anyone other than the owner, making it difficult
> to collaborate on them.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
(Uses He/Him)

*Please note that I do not expect a response from you on evenings or
weekends*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] A potential new way to deal with spambots

[Jonathan Morgan]

Brian,

I think we may be talking past each other. I'm Mr. Socio-technical systems.
I thought what was being requested was a way to detect bots.

I maintain my own bots, work extensively with product teams, and have a
deep and abiding familiarity with the complexity of designing effective
tools for WIkipedia.

- J

On Wed, Feb 13, 2019 at 4:14 AM bawolff  wrote:

> I actually meant a different type of maintenance.
>
> Maintaining the encyclopedia (and other wiki projects) is of course an
> activity that needs software support.
>
> But software is also something that needs maintenance. Technology,
> standards, circumstances change over time. Software left alone will
> "bitrot" over time. A long term technical strategy to do anything needs to
> account for that, plan for that. One off feature development does not.
> Democratically directed one-off feature development accounts for that even
> less.
>
> In response to Johnathan:
> So lets say that ORES/magic AI detects something is a bot. Then what?
> That's a small part of the picture. In fact you don't even need AI to do
> this, plenty of the vandal bots have generic programming language
> user-agents (AI could of course be useful for long-tail here, but there's
> much simpler stuff to start off with). Do we expose this to abusefilter
> somehow? Do we add a tag to mark it in RC/watchlist? Do we block it? Do we
> rate limit it? What amount of false positives are acceptable? What is the
> UI for all this? To what extent is this hard coded, and to what extent do
> communities control the feature? etc
>
> We don't need products to detect bots. Making products to detect bots is
> easy. We need product managers to come up with socio-technical systems that
> make sense in our special context.
>
> --
> Brian
>
> On Tue, Feb 12, 2019 at 8:36 PM Pine W  wrote:
>
> > Since we're discussing how the Tech Wishlist works then I will comment
> on a
> > few points specifically regarding that wishlist.
> >
> > 1. A gentle correction: the recommendations are ranked by vote, not by
> > consensus. This has pros and cons.
> >
> > 2a. If memory serves me correctly, the wishlist process was designed by
> WMF
> > rather than designed by community consensus. I may be wrong about this,
> but
> > in my search of historical records I have not found evidence to the
> > contrary. I think that redesigning the process would be worth
> considering,
> > and I hope that a redesign would help to account for the types of needs
> > that bawolff described in his second paragraph.
> >
> > 2b.. I think that it's an overstatement to say that "nobody ever votes
> for
> > maintenance until its way too late and everything is about to explode". I
> > think that many non-WMF people are aware of our backlogs, the endless
> > requests for help and conflict resolution, and the many challenges of
> > maintaining what we have with the current population of skilled and good
> > faith non-WMF people. However, I have the impression that there is a
> common
> > *tendency* among humans in general to chase shiny new features instead of
> > doing mostly thankless work, and I agree that the tech wishlist is
> unlikely
> > even in a redesigned form to be well suited for long term planning. I
> think
> > that WMF's strategy process may be a better way to plan for the long
> term,
> > including for maintenance activities that are mostly thankless and do not
> > necessarily correlate with increasing someone's personal power, making
> > their resume look better, or having fun. Fortunately the volunteer
> > mentality of many non-WMF people means that we do have people who are
> > willing to do mostly thankless, mundane, and/or stressful work, and I
> think
> > that some of us feel that our work is important for maintaining the
> > encyclopedia even when we do not enjoy it, but we have a finite supply of
> > time from such people.
> >
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> > ___
> > 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



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] A potential new way to deal with spambots

[Jonathan Morgan]

Couple thoughts:

1. ORES platform (ores.wikimedia.org) was designed to host a wide range of
machine learning models, not just the ones built by Aaron Halfaker himself.
So, if there is a computer scientist out there who is interested in
training and maintaining a new bot-detection model, it can be hosted on and
surfaced through ORES. Then anyone with some bot- or web-development skills
can build tools on top of that model. Noting this because that's one of the
main points of having a "scoring platform": it separates the (necessarily
WMF-led) work of production platform development from the development of
purpose-built tools.
2. If anyone knows a computer scientist who is interested in developing and
piloting a model like this please send them our way. Members of the
Research team, or Aaron, *may* have capacity to support a formal
collaboration
3. This seems way too complex for a GSOC project to me, but I'd love to be
wrong about that. If there are students who are interested in working on
this, please send them our way (no promises, obvs).
4. Modifying the charter of an existing WMF product team seems somewhat out
of scope for this ask, task, and venue. :)

- J

On Mon, Feb 11, 2019 at 2:19 PM Pine W  wrote:

> Thanks for the replies.
>
> I think that detailed discussion of the pros and cons of the Tech Wishlist
> should be separate from this thread, but I agree that one way to get a
> subject like unflagged bot detection addressed could be through the Tech
> Wishlist assuming that WMF is willing to devote resources to that topic if
> it ranked in the top X places.
>
> It sounds like there are a few different ways that work in this area could
> be resourced:
>
> 1. As mentioned above, making it be a tech wishlist item and having
> Community Tech work on it;
> 2. Having the Anti-Harrassment Tools team work on it;
> 3. Having the Security team work on it;
> 4. Having the ORES team work on it;
> 5. Funding work through a WMF grants program;
> 6. Funding through a mentorship program like GSOC. I believe that GSOC
> previously supported work on CAPTCHA improvements.
>
> Of the above options I suggest first considering 2 and 4. Having AHAT staff
> work on unflagged bot detection might be scope creep under the existing
> AHAT charter but perhaps AHAT's charter could be modified into something
> that would resemble the charter for an "Administrators' Tools Team". And if
> the ORES team has already done some work on unflagged bot detection then
> perhaps ORES and AHAT staff could collaborate on this topic.
>
> In the first half of the next WMF fiscal year, I think that planning for an
> existing WMF team or combination of staff from existing teams to work on
> unflagged bot detection would be good. If WMF does not resource this topic,
> then if community people want unflagged bot detection be resourced, we can
> consider other options such as 1 and 5.
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] A potential new way to deal with spambots

[Jonathan Morgan]

This may be naive, but... isn't the wishlist filling this need? And if not
through a consensus-driven method like the wishlist, how should a WMF team
prioritize which power user tools it needs to focus on?

Or is just a matter of "Yes, wishlist, but more of it"?

- Jonathan

On Mon, Feb 11, 2019 at 2:34 AM bawolff  wrote:

> Sure its certainly a front we can do better on.
>
> I don't think Kasada is a product that's appropriate at this time. Ignoring
> the ideological aspect of it being non-free software, there's a lot of easy
> things we could and should try first.
>
> However, I'd caution against viewing this as purely a technical problem.
> Wikimedia is not like other websites - we have allowable bots. For many
> commercial websites, the only good bot is a dead bot. Wikimedia has many
> good bots. On enwiki usually they have to be approved, I don't think that's
> true on all wikis. We also consider it perfectly ok to do limited testing
> of bots before it is approved. We also encourage the creation of
> alternative "clients", which from a server perspective looks like a bot.
> Unlike other websites where anything non-human is evil, here we need to
> ensure our blocking corresponds to social norms of the community. This may
> sound not that hard, but I think it complicates botblocking more than is
> obvious at first glance.
>
> Second, this sort of thing is something that tends to far through the
> cracks at WMF. AFAIK the last time there was a team responsible for admin
> tools & anti-abuse was 2013 (
> https://www.mediawiki.org/wiki/Admin_tools_development). I believe
> (correct
> me if I'm wrong) that anti-harrasment team is all about human harassment
> and not anti-abuse in this sense. Security is adjacent to this problem, but
> traditionally has not considered this problem in scope. Even core tools
> like checkuser have been largely ignored by the foundation for many many
> years.
>
> I guess this is a long winded way of saying - I think there should be a
> team responsible for this sort of stuff at WMF, but there isn't one. I
> think there's a lot of rather easy things we can try (Off the top of my
> head: Better captchas. More adaptive rate limits that adjust based on how
> evilish you look, etc), but they definitely require close involvement with
> the community to ensure that we do the actual right thing.
>
> --
> Brian
> (p.s. Consider this a volunteer hat email)
>
> On Sun, Feb 10, 2019 at 6:06 AM Pine W  wrote:
>
> > To clarify the types of unwelcome bots that we have, here are the ones
> that
> > I think are most common:
> >
> > 1) Spambots
> >
> > 2) Vandalbots
> >
> > 3) Unauthorized bots which may be intended to act in good faith but which
> > may cause problems that could probably have been identified during
> standard
> > testing in Wikimedia communities which have a relatively well developed
> bot
> > approval process. (See
> > https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval.)
> >
> > Maybe unwelcome bots are not a priority for WMF at the moment, in which
> > case I could add this subject into a backlog. I am sorry if I sound
> grumpy
> > at WMF regarding this subject; this is a problem but I know that there
> are
> > millions of problems and I don't expect a different project to be dropped
> > in order to address this one.
> >
> > While it is a rough analogy, I think that this movie clip helps to
> > illustrate a problem of bad bots. Although the clip is amusing, I am not
> > amused by unwelcome bots causing problems on ENWP or anywhere else in the
> > Wikiverse. https://www.youtube.com/watch?v=lokKpSrNqDA
> >
> > Thanks,
> >
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> >
> >
> >
> > On Sat, Feb 9, 2019, 1:40 PM Pine W  >
> > > OK. Yesterday I was looking with a few other ENWP people at what I
> think
> > > was a series of edits by either a vandal bot or an inadequately
> designed
> > > and unapproved good faith bot. I read that it made approximately 500
> > edits
> > > before someone who knew enough about ENWP saw what was happening and
> did
> > > something about it. I don't know how many problematic bots we have, in
> > > addition to vandal bots, but I am confident that they drain a
> nontrivial
> > > amount of time from stewards, admins, and patrollers.
> > >
> > > I don't know how much of a priority WMF places on detecting and
> stopping
> > > unwelcome bots, but I think that the question of how to decrease the
> > > numbers and effectiveness of unwelcome bots would be a good topic for
> WMF
> > > to research.
> > >
> > > Pine
> > > ( https://meta.wikimedia.org/wiki/User:Pine )
> > >
> > >
> > > On Sat, Feb 9, 2019 at 9:24 PM Gergo Tisza 
> wrote:
> > >
> > >> On Fri, Feb 8, 2019 at 6:20 PM Pine W  wrote:
> > >>
> > >> > I don't know how practical it would be to implement an approach like
> > >> this
> > >> > in the Wikiverse, and whether licensing proprietary technology would
> > be
> > >> > required.
> > >> >
> > >>
> > >> They are talking 

Re: [Wikitech-l] Wikistats gets a facelift - Alpha Launch of Wikistats 2

[Jonathan Morgan]

This is fabulous! Thank you, Erik Zachte, Analytics team, and everyone else
involved in this project for giving us the powerful, usable stats dashboard
we deserve :)

- J

On Thu, Dec 14, 2017 at 5:10 AM, Niharika Kohli 
wrote:

> This is awesome. Great job A-team!
>
> On Thu, Dec 14, 2017 at 12:12 PM, Victoria Coleman  >
> wrote:
>
> > Nuria and team, fabulous work!  Wikistats 2 is such a huge improvement!
> > Thank you!
> >
> >
> > Best wishes,
> >
> > Victoria Coleman
> >
> > Chief Technology Officer
> > Wikimedia Foundation
> > 1 Montgomery Street, Suite 1600
> > San Francisco, CA 94104
> >
> > +1-650-703-8112
> >
> > vcole...@wikimedia.org
> >
> >
> >
> >
> >
> >
> >
> >
> > > On Dec 13, 2017, at 8:26 PM, Nuria Ruiz  wrote:
> > >
> > > Hello from Analytics Team!
> > >
> > > We are happy to announce the Alpha release of Wikistats 2. Wikistats
> has
> > > been redesigned for architectural simplicity, faster data processing,
> > and a
> > > more dynamic and interactive user experience. First goal is to match
> the
> > > numbers of the current system, and to provide the most important
> reports,
> > > as decided by the Wikistats community (see survey) [1].  Over time, we
> > will
> > > continue to migrate reports and add new ones that you find useful. We
> can
> > > also analyze the data in new and interesting ways, and look forward to
> > > hearing your feedback and suggestions. [2]
> > >
> > > You can go directly to Spanish Wikipedia
> > > https://stats.wikimedia.org/v2/#/es.wikipedia.org
> > >
> > > or browse all projects
> > > https://stats.wikimedia.org/v2/#/all-projects
> > >
> > > The new site comes with a whole new set of APIs, similar to our
> existing
> > > Pageview API but with edit data. You can start using them today, they
> are
> > > documented here:
> > >
> > > https://wikitech.wikimedia.org/wiki/Analytics/AQS/Wikistats
> > >
> > >
> > > FAQ:
> > >
> > > Why is this an alpha?
> > > There are features that we feel a full-fledged product should have that
> > are
> > > still missing, such as localization. The data-processing pipeline for
> the
> > > new Wikistats has been rebuilt from scratch (it uses
> > distributed-computing
> > > tools such as Hadoop) and we want to see how it is used before calling
> it
> > > final. Also while we aim to update data monthly, it will happen a few
> > days
> > > after the month rolls because of the amount of data to move and
> compute.
> > >
> > > How about comparing data between two wikis?
> > > You can do it with two tabs but we are aware this UI might not solve
> all
> > > use cases for the most advanced Wikistats users. We aim to tackle those
> > in
> > > the future.
> > >
> > > How do I file bugs?
> > > Use the handy link in the footer:
> > > https://phabricator.wikimedia.org/maniphest/task/edit/?
> > title=Wikistats%20Bug=Analytics-Wikistats,Analytics
> > >
> > > How do I comment on design?
> > > The consultation on design already happened but we are still watching
> the
> > > talk page:
> > > https://www.mediawiki.org/wiki/Wikistats_2.0_Design_
> > Project/RequestforFeedback/Round2
> > >
> > >
> > > [1]
> > > https://www.mediawiki.org/wiki/Analytics/Wikistats/
> > DumpReports/Future_per_report
> > > [2] https://wikitech.wikimedia.org/wiki/Talk:Analytics/
> Systems/Wikistats
> > > ___
> > > 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
> >
>
>
>
> --
> Niharika
> Software Engineer
> Community Tech
> Wikimedia Foundation
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Sunsetting Trending Edits Service before the holiday

[Jonathan Morgan]

FWIW, I did the research comparing Trending edits to top pageviews, and I
*also* think Trending edits is a promising tool and am glad to hear that it
going forward in some fashion even if it's being pulled from production
(for now?). I hope we can continue to develop the model, and I'm confident
that we will find valuable use cases for it.

- J

On Tue, Dec 12, 2017 at 12:12 PM, Jon Robson  wrote:

> (Volunteer hat on)
>
> I'm a little sad we didn't find a place for this in the Wikipedia apps or
> web products, but I plan to maintain a labs instance going forward:
> https://wikipedia-trending.wmflabs.org/
> And a web presentation with a push notification feature (which notified be
> this morning of the death of Ed Lee
> ):
> https://trending.wmflabs.org/
>
> This is a little inferior to the production version as it is unable to use
> production kafka and if it has any outages it will lose data.
>
> I'm hoping to get this onto IFTTT  with help
> from Stephen Laporte in my volunteer time, as I think this feature is a
> pretty powerful one which has failed to find its use case in the wiki
> world. As Kaldari points out it's incredibly good at detecting edit wars
> and I personally have learned a lot about what our editors see as important
> and notable in the world (our editors really seem to like wrestling). I
> think there are ample and exciting things people could build on top of this
> api.
>
> The gadget script is crude (as there is no way to install a service worker
> via a user script) but will continue to work if you want to try it (but
> Firefox only) -  I just updated it to use the new endpoint.
>
> I will continue to explore trending's place in the Wikimedia universe :)
>
>
> On Tue, 12 Dec 2017 at 10:43 Ryan Kaldari  wrote:
>
> > One interesting thing that I noticed about the trending edits API is that
> > it was fairly useful in identifying articles that were under attack by
> > vandals or experiencing an edit war. A lot of times a vandal will just
> sit
> > on an article and keep reverting back to the vandalized version until an
> > admin shows up, which can sometimes take a while. If you tweak the
> > parameters passed to the API, you can almost get it to show nothing but
> > edit wars (high number of edits, low number of editors).
> >
> > This makes me think that this API is actually useful, it's just targeted
> to
> > the wrong use case. If we built something similar, but that just looked
> for
> > high numbers of revert/undos (rather than edits), and combined it with
> > something like Jon Robson's trending edits user script (
> > https://en.wikipedia.org/wiki/User:Jdlrobson/Gadget-trending-edits.js),
> we
> > could create a really powerful tool for Wikipedia administrators to
> > identify problems without having to wait for them to be reported at AN/I
> or
> > AIV.
> >
> > On Tue, Dec 12, 2017 at 7:25 AM, Corey Floyd 
> wrote:
> >
> > > Just a reminder that this is happening this Thursday. Please update any
> > > tools you have before then. Thanks!
> > >
> > >
> > > On Fri, Dec 1, 2017 at 3:30 PM Corey Floyd 
> wrote:
> > >
> > > > Hi all,
> > > >
> > > > The experimental Trending Service[1] will be sunset on December 14th,
> > > 2017.
> > > >
> > > > We initially deployed this service to evaluate some real time
> features
> > in
> > > > the mobile apps centered on delivering more timely information to
> > users.
> > > > After some research [2], we found that it did not perform well with
> > users
> > > > in that use case.
> > > >
> > > > At this point there are no further plans to integrate the service
> into
> > > our
> > > > products and so we are going to sunset the service to reduce the
> > > > maintenance burden for some of our teams.
> > > >
> > > > We are going to do this more quickly than we would for a full stable
> > > > production API as the usage of the end point is extremely low and
> > mostly
> > > > from our own internal projects. If you this adversely affects any of
> > your
> > > > work or you have any other concerns, please let the myself or the
> > Reading
> > > > Infrastructure team know.
> > > >
> > > > Thanks to all the teams involved with developing, deploying,
> > researching
> > > > and maintaining this service.
> > > >
> > > > P.S. This service was based off of prototypes Jon Robson had
> developed
> > > for
> > > > detecting trending articles. He will be continuing his work in this
> > > area. I
> > > > encourage you to reach out to him if you were interested in this
> > project.
> > > >
> > > > [1] https://en.wikipedia.org/api/rest_v1/#!/Feed/trendingEdits
> > > > [2]
> > > > https://meta.wikimedia.org/wiki/Research:Comparing_most_
> > > read_and_trending_edits_for_Top_Articles_feature
> > > >
> > > >
> > > >
> > > > --
> > > > Corey Floyd
> > > > Engineering Manager
> > > > 

Re: [Wikitech-l] [AI] Scoring Platform Team update

[Jonathan Morgan]

Congratulations to the new Scoring Platform team! - J

On Wed, Jul 12, 2017 at 4:07 PM, Aaron Halfaker 
wrote:

> Hey folks!
>
> I just posted a new update to the blog.   This update covers roughly the
> last month.
>
> https://phabricator.wikimedia.org/phame/post/view/58/status_
> update_july_11th_2017/
>
> As of July 1st, we are officially the Scoring Platform team. We're
> welcoming Adam Wight to the team officially.  There will be a nice
> announcement that we'll post to the Wikimedia Blog in a few days.
>
> The last ~month was very productive, but we had two major production
> issues[1,2]. As you will see in the blog post, there's a series of tasks
> that address problems that were related to these issues.
>
> Despite dealing with production issues, we've been able to get a very
> substantial change to the revscoring library merged. This change will make
> accessing information about models (build environment, test statistics,
> scoring thresholds, etc.) much easier. This will cause a breaking change in
> ORES UI so we'll be making an announcement when we roll it out. Stay tuned.
>
> We've also increased our language and model coverage substantially. We
> even built and deployed a totally new type of model to help out French
> Wikisource!
>
> See the post for more details :)
>
> 1. https://wikitech.wikimedia.org/wiki/Incident_
> documentation/20170613-ORES
> 2. https://wikitech.wikimedia.org/wiki/Incident_
> documentation/20170623-ORES
>
> -Aaron
> Principal research scientist
> Lead of the Scoring Platform team
> Defender of the universe
> Eater of toast
> Wiki of the media foundation
>
> ___
> AI mailing list
> a...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/ai
>
>


-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Congratulations to accepted candidates for Google Summer of Code 2017 & Outreachy Round 14

[Jonathan Morgan]

Welcome (back!) Sejal!

- Jonathan

On Fri, May 5, 2017 at 2:49 PM, Sejal Khatri 
wrote:

> Hello Everyone!
>
> I am Sejal Khatri, a Final year undergraduate student of computer science
> from India, graduating in 2017. I have been a part of Wikimedia Community
> since December'16 as I was selected for Outreachy winter internship round.
> I had worked on improving the user profile pages of the Wiki Education
> Foundation's Dashboard project . I really
> admire the community support provided and would like to thank the
> administrators for making it all possible. I am super excited for my GSoC
> journey and being able to interact with the community at such a large
> scale.
>
> GSoC Project:
> *To provide enhanced usability for Wikimedia Programs & Events Dashboard
> managed by Wiki Education foundation .*
> Wikimedia Programs & Events Dashboard
>  is a Project used by global
> Wikimedia community to organize all kinds of programs, including
> edit-a-thons, education programs, and other events.
>
> The Aim of this project is to add/improve various new features to the
> Dashboard and increase the overall scope of the project.
>
> I'll start by connecting with some Dashboard users and setting up the
> priorities for the improvements to be made accordingly. I am thrilled
> thinking about the impact I will make by my contributions.
>
> Thanks and regards,
> Sejal
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Congratulations to accepted candidates for Google Summer of Code 2017 & Outreachy Round 14

[Jonathan Morgan]

Congratulations! I think this will be a lot of fun for everyone involved :)

- Jonathan

On Thu, May 4, 2017 at 4:25 PM, Alangi Derick 
wrote:

> Hello,
>
> I want to cease this opportunity to congratulate all selected GSoC +
> Outreachy participants. Congratulations and do code the summer away .
> Happy Hacking!!!
>
> Kind regards
> Alangi Derick N
>
> On May 4, 2017 11:58 PM, "Pine W"  wrote:
>
> Welcome GSOC and Outreachy people.
>
> I'm especially glad to learn of the planned improvements to the Wiki Ed
> dashboard and the Quiz extension.
>
> Good luck in your new roles,
>
> Pine
> ___
> 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
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Turkey ban

[Jonathan Morgan]

And now, this:
https://arstechnica.com/tech-policy/2017/05/2-chinese-writers-will-create-their-own-wikipedia-competitor/

On Sun, Apr 30, 2017 at 1:39 AM, Amir Ladsgroup  wrote:

> The Iranian government by blocking several major websites (youtube,
> facebook, twitter) actually made people aware of anonymizers and people
> were able to use a wide range of them.
> Most popular ones that people in Turkey can use is: 1- Psiphon (a little
> bit slow, has an android app) 2- Hotspot shield (great, also andriod app)
> 3- Lantern (the only one that supports linux)
> Tor is good too but we have editing problems with that.
>
> Best
>
> On Sun, Apr 30, 2017 at 12:57 PM Bináris  wrote:
>
> > When I was in Iran, I could reach all the blocked sites (such as
> Facebook)
> > with Psiphon.
> > https://en.wikipedia.org/wiki/Psiphon
> > And so do the local people.
> > Citizens of dictatorships are very efficient in using client-side
> > solutions.
> > ___
> > 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
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Analytics] Monthly page view stats that can now be queried via Pageview API.

[Jonathan Morgan]

Awesome. Thanks Analytics team!

- J

On Wed, Jan 25, 2017 at 3:19 AM, Thomas Steiner  wrote:

> > The Analytics team would like to announce that the Pageview API is able
> to
> > return monthly pageview stats as of this week.
>
> Thanks, Nuria and team, very useful addition to the API. I have
> updated pageviews.js accordingly:
> https://github.com/tomayac/pageviews.js/commit/
> 643d3f2e2840e06b82b7d007b3611d4702376261.
>
> Cheers,
> Tom
>
> --
> Dr. Thomas Steiner, Employee (https://blog.tomayac.com,
> https://twitter.com/tomayac)
>
> Google Germany GmbH, ABC-Str. 19, 20354 Hamburg, Germany
> Managing Directors: Matthew Scott Sucherman, Paul Terence Manicle
> Registration office and registration number: Hamburg, HRB 86891
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.1.17 (GNU/Linux)
>
> iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DChara
> CTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/
> -END PGP SIGNATURE-
>
> ___
> Analytics mailing list
> analyt...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

[Jonathan Morgan]

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?

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?

Many thanks,
Jonathan

On Thu, Nov 10, 2016 at 6:51 AM, Quim Gil  wrote:

> 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!
> 
>
> *PROPOSALS*
>
>- 70 proposals open
>
>   - 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
>  participation#Selection_process>
> .
>
> *MAIN TOPICS*
>
> No significant news. We hope to have all the wiki pages up to date next
> week.
>
> Check the 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 ).
>
>
> On Mon, Oct 10, 2016 at 3:27 PM, Quim Gil  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
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
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

[Jonathan Morgan]

Thank you, Tony!

This is a great set of projects, and I'm thrilled for the opportunity to
help out this year.

- Jonathan

On Tue, Nov 8, 2016 at 8:58 AM, Tony Thomas <01tonytho...@gmail.com> wrote:

> Hello all,
>
> Happy to announce that we have *four* selections for Outreachy'13 this time
> for the December-March round! You can find the timeline for the event here
> - https://wiki.gnome.org/Outreachy/2016/DecemberMarch#Schedule
>
> Listing down the projects:
>
>1. https://phabricator.wikimedia.org/T147727 - Provide cumulative
>statistics for all programs a user has participated in -  Sejal Khatri.
>Mentors: Ragesoss, Capt_Swing
>2. https://phabricator.wikimedia.org/T148074 - Create Python library to
>serialize Wikimedia Quiz format, GIFT quiz format, etc - Anna Liao.
>Mentors: John Mark Vandenberg, Marielle Volz
>3. https://phabricator.wikimedia.org/T148287- 5 subprojects with the
>Reading Department at Wikimedia  - Zareen Farooqui. Mentors: Tilman
> Bayer,
>Jon Katz
>4. https://phabricator.wikimedia.org/T147953 - Hacking: Wiki Radio -
>Neslihan. Mentors: Nirzar, Adam Baso
>
> Congratulations to all students and mentors invovled.
>
> This time too, we had to turn down couple of strong applications due to
> strict
> outreachy norms on academic and other commitments. We welcome to try again
> for the 2017 Google Summer of Code and Outreachy as well, and continue at a
> volunteer capacity.
>
> Announcement Link:
> https://wiki.gnome.org/Outreachy/2016/DecemberMarch#Wikimedia
>
> Thanks,
> Tony Thomas 
> Home  | Blog 
> |
> ThinkFOSS 
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

[Jonathan Morgan]

Sorry, Florian, I should have clarified: I got sad because I saw a
conversation about a private matter turning into a public indictment (of
WMF).

Obviously there will need to be scrambling to fill Robla's big shoes. And
lots of communication and coordination among relevant stakeholders. I
understand if folks involved in ongoing initiatives are feeling out of the
loop. Not everyone on staff feels in the loop either, FWIW, or knows what
the next steps should be. That's not uncommon in this kind of situation.

Also, we should probably open new discussion on another thread.

- Jonathan

On Thu, Nov 3, 2016 at 3:48 PM, Florian Schmidt <
florian.schmidt.wel...@t-online.de> wrote:

> Thanks Brian!
>
> That's exactly what this e-mail was for. I was also wondering, what
> happened to him personally, however, it's more than ok and his own decision
> to not say anything about it. However, like Brian wrote already, Robla had
> (as far as I know) a very good standing in the community and it would be a
> good communication about what happened (in any way), instead of "just"
> disabling his account.
>
> However, this e-mail is (and wasn't at any time) to make anyone sad about
> anything, and it makes me sad, that the thread resulted in this feeling for
> some people :(
>
> Best,
> Florian
>
> -Ursprüngliche Nachricht-
> Von: Wikitech-l [mailto:wikitech-l-boun...@lists.wikimedia.org] Im
> Auftrag von bawolff
> Gesendet: Donnerstag, 3. November 2016 21:07
> An: Wikimedia developers <wikitech-l@lists.wikimedia.org>
> Betreff: Re: [Wikitech-l] What happened to RobLa?
>
> Robla obviously deserves his privacy if he wants that. However I think its
> rather natural for people to wonder "What happened" when an employee who is
> as much in the public spotlight as robla is, suddenly and unexpectedly
> leaves.
>
> Obviously just because it is "natural" doesn't mean we deserve answers. I
> think Wes's short email was sufficient in terms of answering the what
> happened question. However, simply putting a global lock on someone's
> account (Which was the state of things before this
> thread) is not good communication and bound to raise eyebrows.
>
> There is also the more pragmatic question of how Robla's responsibilities
> will be transferred. Robla did a lot for MediaWiki, and transitions are
> scary. Transitions with no information are even scarier. How will Robla's
> initiatives be carried forward? Is the architecture committee mature enough
> to continue on purely its own steam without Robla pushing it forward? How
> does this affect the "vision" for MediaWiki (emphasis on MediaWiki, not
> Wikimedia)? Will development of Wikimedia's technology further devolve into
> independent fiefdoms without Robla balancing the architecture needs of
> different groups? All these concerns are in my mind, and I think the minds
> of others. It would be nice to get some reassurance about what is going to
> happen next.
>
> --
> Brian
> [To be 100% clear, posting with my volunteer hat firmly on]
>
> On Thu, Nov 3, 2016 at 4:17 PM, Jonathan Morgan <jmor...@wikimedia.org>
> wrote:
> > +1 Petr. This thread makes me sad and uncomfortable.
> >
> > - J
> >
> > On Thu, Nov 3, 2016 at 9:03 AM, Toby Negrin <tneg...@wikimedia.org>
> wrote:
> >
> >> Thank you Petr. Well said!
> >> -Toby
> >>
> >> On Thu, Nov 3, 2016 at 2:39 AM, Petr Bena <benap...@gmail.com> wrote:
> >>
> >> > Hello,
> >> >
> >> > I don't like to sound like a bad guy, but I really find it quite
> >> > inappropriate to discuss this sort of stuff on a public mailing list.
> >> > This really is a personal matter. If he didn't post any dramatical
> >> > announcement perhaps he wanted to "leave quietly"?
> >> >
> >> > You know, people sometimes do this sort of stuff for very personal
> >> > reasons, they just don't want to discuss with public, and who
> >> > knows, maybe he would return back one day? He wouldn't be first to
> >> > do that :) Or maybe he is going to stick around as a volunteer?
> >> > Let's be optimistic!
> >> >
> >> > If you really want to know the details, you can always ask him
> >> > directly. Fortunately he is not dead, so no need to mourn him. As
> >> > an employee of WMF, he was always very friendly and extremely
> >> > useful, so indeed I /do/ hope he will stay with us, at least as a
> volunteer.
> >> >
> >> > On Thu, Nov 3, 2016 at 10:16 AM, Tilman Bayer
> >> > <tba...@wikimedia.org>
> >> &g

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

[Jonathan Morgan]

+1 Petr. This thread makes me sad and uncomfortable.

- J

On Thu, Nov 3, 2016 at 9:03 AM, Toby Negrin  wrote:

> Thank you Petr. Well said!
> -Toby
>
> On Thu, Nov 3, 2016 at 2:39 AM, Petr Bena  wrote:
>
> > Hello,
> >
> > I don't like to sound like a bad guy, but I really find it quite
> > inappropriate to discuss this sort of stuff on a public mailing list.
> > This really is a personal matter. If he didn't post any dramatical
> > announcement perhaps he wanted to "leave quietly"?
> >
> > You know, people sometimes do this sort of stuff for very personal
> > reasons, they just don't want to discuss with public, and who knows,
> > maybe he would return back one day? He wouldn't be first to do that :)
> > Or maybe he is going to stick around as a volunteer? Let's be
> > optimistic!
> >
> > If you really want to know the details, you can always ask him
> > directly. Fortunately he is not dead, so no need to mourn him. As an
> > employee of WMF, he was always very friendly and extremely useful, so
> > indeed I /do/ hope he will stay with us, at least as a volunteer.
> >
> > On Thu, Nov 3, 2016 at 10:16 AM, Tilman Bayer 
> > wrote:
> > > On Tue, Nov 1, 2016 at 3:54 AM, Federico Leva (Nemo) <
> nemow...@gmail.com
> > >
> > > wrote:
> > >
> > >> As a reminder on goodbyes, WMF HR used to announce everyone's last day
> > at
> > >> https://identi.ca/wikimediaatwork (can't take more than a couple
> > >> minutes); then the announcements became monthly, then quarterly; then
> we
> > >> lost this courtesy as well https://meta.wikimedia.org/wik
> > >> i/Talk:Wikimedia_Foundation_reports#Staff .
> > >
> > >
> > > As already noted higher up on that talk page, that's a misconception.
> > > Timely updates now happen on the WMF wiki instead, where RobLa's
> > departure
> > > had already been recorded by HR before you sent this email:
> > > https://wikimediafoundation.org/w/index.php?title=Template:Staff_and_
> > > contractors=history
> > >
> > >
> > >>
> > >
> > >
> > > --
> > > Tilman Bayer
> > > Senior Analyst
> > > Wikimedia Foundation
> > > IRC (Freenode): HaeB
> > > ___
> > > 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
> >
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New mirror of 'other' datasets

[Jonathan Morgan]

Awesome! Great to hear that we're making these resources more widely
available. Nice to have good partners :) - Jonathan

On Wed, May 4, 2016 at 5:33 AM, Ariel Glenn WMF  wrote:

> I'm happy to announce a new mirror for datasets other than the XML dumps.
> This mirror comes to us courtesy of the Center for Research Computing,
> University of Notre Dame, and covers everything "other" [1] which includes
> such goodies as Wikidata entity dumps, pageview counts, titles of all files
> on each wiki (daily), titles of all articles of each wiki (daily), and the
> so-called "adds-changes" dumps, among other things. You can access it at
> http://wikimedia.crc.nd.edu/other/ so please do!
>
> Ariel
>
> [1] https://dumps.wikimedia.org/other/
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Feelings

[Jonathan Morgan]

I would start the conversation here:
https://en.wikipedia.org/wiki/Wikipedia_talk:Teahouse/Host_lounge

Cullen328 and DESiegel are probably the most experienced/involved hosts
right now. Their voices are respected. But of course there's no leader :)

Jonathan

On Thu, Apr 7, 2016 at 12:08 PM, C. Scott Ananian 
wrote:

> Keeping the teahouse thread alive...
>
> ...for some time I've wanted to prototype some real-time chat and editing
> features with the Teahouse folks (eg,
> https://www.mediawiki.org/wiki/Extension:TogetherJS) to make the
> "conversations" Risker mentions easier/more natural.  If anyone has
> suggestions about who to talk to about this, let me know.
>  --scott
>
> On Thu, Apr 7, 2016 at 10:58 AM, Aaron Halfaker 
> wrote:
>
> > Ori said:
> >
> > > I would like us to consider the contribution that modifications to the
> > user experience make to the
> > > interpersonal climate on the wikis.
> > >
> > > I think that this is important.  Our social experience in computer
> > mediated spaces is intertwined with the technologies that manage our
> > interactions.  This is certainly true to Wikipedia[1] and I think it is
> > true generally[2].  While we may find it easy to discuss the technology
> and
> > social things separately, it is very important that we don't interpret
> this
> > as a real separation.  Our social patterns affect how we choose and
> design
> > our digital technologies and our digital technologies -- in turn --
> affect
> > our social patterns(for more discussion, see [3]).
> >
> > J-Mo said:
> >
> > > If WMF ever supports any additional Teahouse-related development, it
> > should
> > > be focused on giving more new editors, on more Wikis, access to
> Teahouses
> > > and Teahouse-like tools and resources—rather than doing anything to the
> > > Enwiki Teahouse itself, which is doing just fine.
> > >
> > > But J-Mo, we're literally planning to explore supporting the Teahouse
> > with
> > more digital technologies right now -- you and I!  E.g. using ORES
> >  to identify more good-faith newcomers to
> route
> > to the Teahouse & building a search interface to help newcomers explore
> > past questions.  Maybe it's OK because we don't plan to do anything *to*
> > the Teahouse, but rather to work *with* the hosts to figure out how to
> > build up capacity.   I suspect that, if the technologies we develop are
> > able to make the positive social interactions that the Teahouse excels in
> > available to more newcomers -- we'll succeed.  And hopefully, if our
> > technological investments into the Teahouse fail and somehow make
> positive,
> > human interactions more difficult or otherwise less common, we'll have
> the
> > insight to not deploy them beyond an experiment.
> >
> > This thread started out as a harmless (and humorous!) joke and it has
> > turned into a debate around our values with regards to technologies that
> we
> > intentionally integrate with social behaviors.  I think this is a
> > conversation we ought to have, but I'd really like to see us move beyond
> > platitudes.  Technology isn't good or bad.  It certainly isn't easy to
> get
> > right, but I believe we can co-evolve our tech and our social structures.
> > In a computer mediated environments such as ours, this socio-technical
> > co-evolution is our only hope to actually making real progress.
> >
> > 1. https://meta.wikimedia.org/wiki/Research:The_Rise_and_Decline
> > 2. https://en.wikipedia.org/wiki/Sociotechnical_system
> > 3. https://www.youtube.com/watch?v=-We4GZbH3Iw#t=34m04s (my "Paramecium
> > talk")
> >
> > -Aaron
> >
> > On Wed, Apr 6, 2016 at 7:30 PM, Matthew Flaschen <
> mflasc...@wikimedia.org>
> > wrote:
> >
> > > On 04/02/2016 09:37 PM, Ori Livneh wrote:
> > >
> > >> Why am I going on about this? I guess I'm a bit bummed out that the
> idea
> > >> of
> > >> designing user interfaces that seek to improve the emotional
> environment
> > >> by
> > >> making it easier to be warm and personal to one another is a joke.
> > >>
> > >
> > > For what it's worth, as someone who wasn't involved in that April
> Fools's
> > > "feature", but joke-reviewed it, I did not intend to to discourage any
> > > serious efforts to encourage a warm and productive editor community.
> > >
> > > Matt
> > >
> > > ___
> > > 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
> >
>
>
>
> --
> (http://cscott.net)
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 

Re: [Wikitech-l] [WikimediaMobile] The future of Related Pages feature

[Jonathan Morgan]

On Wed, Mar 23, 2016 at 3:18 PM, Moushira Elamrawy 
wrote:

> ...
>
In fact, we are not sure if an rfc is the best strategy to move forward
> with product decisions, but lets see how the discussion evolves, and we
> might explore the need for a different process, as we move on with this one.
>
>
I don't think an RFC on its own is *ever* the best way to move forward with
product decisions. From what I've seen, that approach inevitably leads to
the conflation of design issues ("does this work as designed, for whom, why
or why not?") with implement issues ("do the people who participate in this
discussion want this feature to exist on some wiki in some form, why or why
not?"). Too often this simply pits the WMF product team, who obviously want
feature to be liked and used, against a cohort of community members who
*dislike* the feature enough that they're willing to spend their private
time slugging it out. Things escalate, mug is thrown, new epithets are
coined, and the product--often as not--just continues to hang in limbo.

In future, I would suggest we always conduct some user research first—with
editors and readers, to understand what value, if any, different
stakeholders find in the product, as well as what's working and what's not
in the current design. Then bring the findings of that research into the
RFC, to provide an additional set of criteria with which to view the
product's general worthiness, and to anchor discussions of the various
benefits and drawbacks of implementing it (in some form, at some point, on
some wiki) in direct evidence from a more diverse set of stakeholders.

Jonathan


> [0] https://meta.wikimedia.org/wiki/Requests_for_comment/Related_Pages
>
> ___
> Mobile-l mailing list
> mobil...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Feelings

[Jonathan Morgan]

eelings: happy, love, surprise, anger, and fear. Editors can pick one
> > > of those options instead of just a plain thanks, to indicate how they
> > > really feel, which the recipient will see[3].
> > >
> >
> > Of the many initiatives to improve editor engagement and retention that
> the
> > Wikimedia Foundation has launched over the years, the only one that had a
> > demonstrable and substantial impact (AFAIK) was the Teahouse.
> >
> > The goal of the Teahouse initiative was "learning whether a social
> approach
> > to new editor support could retain more new editors there"; its stated
> > design goal was to create a space for new users which would feature "warm
> > colors, inviting pictorial and thematic elements, simple mechanisms for
> > communicating, and a warm welcome from real people."[0]
> >
> > Several studies were made of the Teahouse's impact on editors. One study,
> > conducted by Jonathan Morgan and Aaron Halfaker, found that new editors
> who
> > were invited to participate in the Teahouse were 10% more likely to have
> > met the thresholds for survival in the weeks and months after
> > registration.[1]
> >
> > Another significant fact about the Teahouse is the substantial
> > participation from women. Women make up 9% of the general editor
> > population, but 29% percent of Teahouse participants.[2]
> >
> > When new editors who had been invited to the Teahouse were asked (in a
> 2012
> > survey) to described what they liked about their experiences, many
> > respondents spoke about the positive emotional environment, saying things
> > like: "the fact that there is somebody 'out there', that there is a
> sincere
> > community, gives a professional and safe feeling about Wikipedia", and
> "the
> > editors are very friendly and patient, which is great when compared to
> the
> > rest of Wikipedia in how new editors are treated."[2]
> >
> > Why am I going on about this? I guess I'm a bit bummed out that the idea
> of
> > designing user interfaces that seek to improve the emotional environment
> by
> > making it easier to be warm and personal to one another is a joke. I
> don't
> > think any topic is sacrosanct, this topic included. But humor works best
> > when it provides a counterpoint and a foil to "serious" discourse, and
> > there just isn't very much serious discourse on this topic to go around.
> I
> > also worry that people in and around our community who feel a need for
> more
> > opportunities for positive emotional interactions will feel invalidated,
> > ridiculous, ashamed, or at any rate less confident about ever speaking up
> > about this topic in a serious way, and less hopeful about being heard.
> >
> >   [0]: https://meta.wikimedia.org/wiki/Research:Teahouse
> >   [1]:
> >
> >
> https://meta.wikimedia.org/wiki/Research:Teahouse_long_term_new_editor_retention#Results
> >   [2]:
> > https://meta.wikimedia.org/wiki/Research:Teahouse/Phase_2_report/Metrics
> > ___
> > 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
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) <https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Ideas for tech-related IdeaLab Campaigns?

[Jonathan Morgan]

On Tue, Dec 8, 2015 at 3:11 AM, Quim Gil  wrote:
>
> On the collateral topic of where to publish project concepts... it's
> complicated. I think this deserves its own discussion in the context
> of the WMF product development process in the drafts. I have created a
> topic at https://www.mediawiki.org/wiki/Topic:Su5sgwsd967s1nya.


Hi Quim. How are IdeaLab ideas related to the WMF product development
process?



> There
> are other ongoing discussions related to the first steps of proposals
> and experiments willing to be prioritized, and so far all of them are
> referenced at the related task
> https://phabricator.wikimedia.org/T115659.
>
> On Tue, Dec 8, 2015 at 7:48 AM, Oliver Keyes  wrote:
> > As a long-time phabricator user (and long-time community member) I
> > really don't get the desire to push this to Phabricator. This is not
> > to say it is bad: it is good at what it is designed to do (handling
> > technical tasks in an all-encompassing sorta way). But lately it feels
> > like every conversation about a process involves debating whether that
> > too goes to Phabricator - in this case, a non-technical process.
> >
> > Funded IdeaLab projects /that are technical/ ending up on Phabricator
> > sounds great: treat it as we would any other code. But the
> > consultations and discussions themselves are very deliberately
> > oriented towards our community - because IdeaLab projects are - a
> > community that tends not to have Phabricator accounts, not to have
> > experience using the system, and tends to conduct discussion in a much
> > more prose-based and conversational style than Phabricator easily
> > supports: it's designed for bug-tracking, not 100-comment threads.
> > MediaWiki, however, is designed (for a given value of "designed" ;p)
> > for those sorts of discussions, and additionally is software that
> > literally everyone people reach out to about the IdeaLab is likely to
> > be somewhat familiar with.
> >
> > So I'd rather we kept the discussions there - in a venue that is
> > already used, for an audience that is familiar with that venue - than
> > shift them over to a project that isn't designed for these kinds of
> > interactions and doesn't offer familiarity to the users the IdeaLab
> > tries to reach. Phabricator should be for transparency and process
> > when a project with technical components is funded.
> >
> > On 8 December 2015 at 01:14, Rob Lanphier  wrote:
> >> Hi Chris,
> >>
> >> I wonder if we can use Phabricator as an incubator for IdeaLab
> proposals?
> >> We already have the #possible-tech-projects tag in Phabricator [1],
> which
> >> seems like a sensible place to discuss the ideas amongst the people who
> >> have ideas in this area.
> >>
> >> I know there is some cynicism about the upcoming Wikimedia Developer
> Summit
> >> in January, because it seems like a great opportunity to talk about
> what we
> >> want, but then not have a strategy for getting it done.  That seems
> >> justified, since "resourcing" seems a constant refrain in these
> >> conversations.  Would anyone from IdeaLab be available to be at WikiDev
> >> '16, looking out for appropriate opportunities to get from ideas to
> >> IdeaLab(tm) grant proposals?
> >>
> >> Rob
> >>
> >> [1]  The board: <
> >> https://phabricator.wikimedia.org/tag/possible-tech-projects/> and the
> >> description: 
> >>
> >> On Mon, Dec 7, 2015 at 12:54 PM, Chris Schilling <
> cschill...@wikimedia.org>
> >> wrote:
> >>
> >>> Hey everyone,
> >>>
> >>> I've recently initiated a consultation to help decide on topics for
> IdeaLab
> >>> campaigns for the future, and I'm very interested in your input on what
> >>> technical issues, gaps, or general features we could consider focusing
> our
> >>> attention upon.  These campaigns can generate novel proposals for
> tools and
> >>> improvements to address needs in the Wikimedia projects to which you
> >>> contribute:
> >>>
> >>> <
> https://meta.wikimedia.org/wiki/Grants:IdeaLab/Future_IdeaLab_Campaigns>
> >>>
> >>> You can offer feedback and add your own campaign topics through a
> survey
> >>> conducted through AllOurIdeas <
> >>> http://www.allourideas.org/idealab_campaigns>
> >>> in addition to participating on the IdeaLab talk page.
> >>>
> >>> I’m looking forward to seeing your feedback and exploring potential
> >>> directions we can take IdeaLab campaigns starting next year.
> >>>
> >>> Take care,
> >>>
> >>> Jethro
> >>>
> >>> --
> >>> Chris "Jethro" Schilling
> >>> I JethroBT (WMF) <
> https://meta.wikimedia.org/wiki/User:I_JethroBT_(WMF)>
> >>> Community Organizer, Wikimedia Foundation
> >>> 
> >>> ___
> >>> Wikitech-l mailing list
> >>> Wikitech-l@lists.wikimedia.org
> >>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> >> 

Re: [Wikitech-l] Tech Talk: Introduction to Free and Open Source Licensing at Wikimedia: October 23

[Jonathan Morgan]

I just watched this. Thanks, Stephen for the excellent overview! Very
approachable.

This may be slightly off-topic for this particular list, but: have there
been any similar talks focusing on content licenses for article text and
(perhaps especially) images?

Jonathan

On Fri, Oct 23, 2015 at 9:09 AM, Rachel Farrand 
wrote:

> Reminder: this tech talk starts in 50 minutes
>
> On Tue, Oct 20, 2015 at 12:22 PM, Rachel Farrand 
> wrote:
>
> > Please join for the following tech talk:
> >
> > *Tech Talk**:* Introduction to Free and Open Source Licensing at
> Wikimedia
> > *Presenter:* Stephen LaPorte
> > *Date:* October 23, 2015
> > *Time: *17:00 UTC
> > <
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=Tech+Talk%3A+Introduction+to+Free+and+Open+Source+Licensing+at+Wikimedia=20151023T17=%3A=1>
> -
> > 17:30 UTC
> > Link to live YouTube stream 
> > *IRC channel for questions/discussion:* #wikimedia-office
> > Google+ page
> > <
> https://plus.google.com/u/0/b/103470172168784626509/events/caldda1kv3bnde8d50qi4nkf82s>,
> another
> > place for questions
> >
> > *Summary: *The Wikimedia Foundation maintains and contributes to some
> > significant free and opens source projects. This talk will discuss free
> and
> > open source licensing best practices and why it's important for
> Wikimedia.
> > We'll review different types of licenses, common terms, and how to use
> > them. This talk will be introductory, and there will be an opportunity
> for
> > questions and discussion.
> >
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] mattermost.org (open source Slack alternative)

[Jonathan Morgan]

me too. I like IRC, but a lot of my colleagues aren't on it because it's...
well, IRC. If there's a more inclusive OSS option, let's try it.

J

On Thu, Oct 22, 2015 at 7:36 AM, Stephen Niedzielski <
sniedziel...@wikimedia.org> wrote:

> I think this might be a dividing subject. I speak only for myself in saying
> that I am on board with trying open source IRC alternatives. If you have a
> test group going somewhere, please sign me up!
>
>
> --stephen
>
> On Thu, Oct 22, 2015 at 8:20 AM, Brian Gerstle 
> wrote:
>
> > Mattermost.org
> >
> > Not only does it look pretty cool, but I really, really like their
> > community
> > portal
> > <
> >
> http://forum.mattermost.org/t/welcome-to-mattermost-community-discussion/8
> > >.
> > It looks incredibly easy 
> to
> > file bugs, submit feature requests, vote for and discuss existing feature
> > requests, and find a features ready to accept volunteer contributions.
> >
> > I'm curious what others about it as a potential chat client* and as an
> open
> > source project in general.  Seems like it could be easy to evaluate,
> > especially if we use our fancy new kubernetes infrastructure to spin up a
> > container
> > <
> >
> https://github.com/mattermost/platform/blob/master/doc/install/Docker-Single-Container.md#one-line-docker-install
> > >
> > for
> > one or more teams to try out.
> >
> > Thoughts?
> >
> > Brian
> >
> > * FYI, there's already a feature request for an IRC bridge
> > <
> >
> http://mattermost.uservoice.com/forums/306457-general/suggestions/9425586-irc-bridge
> > >
> >
> > --
> > EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle
> > IRC: bgerstle
> > ___
> > 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
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Collaboration team reprioritization

[Jonathan Morgan]

On Fri, Sep 4, 2015 at 1:25 AM, Brian Wolff  wrote:
>
> I seriously doubt any form of technology will solve the problem of
> independent groups with overlapping interests discussing things in
> multiple venues.
>
> My reading of the original email is that they want to work on things
> that have rather fixed bureaucratic procedures (e.g. Discussions about
> what content to delete). Relatively free-form discussion across many
> locations, seems like the opposite of that imo. I would love to hear
> in more detail what the team concretely plans to work on, although I
> imagine that's still in the process of being planned.
>
>
You're correct, as far as I know. I can't/won't speak for Danny about the
product roadmap (I'm sure he will jump in here again), but one component of
what's planned is indeed support for these so-called "bureaucratic
procedures". I did some initial research before Wikimania (still-drafty
wikipage report[1], internal presentation[2]), and Danny incorporated some
of this into his Wikimania presentation.[3]

I've heard of several other components from the team, but "workflows" is
definitely part of it.

Thanks to you, Pine, Risker and others for the good-faith assessments, btw.

J

1.
https://www.mediawiki.org/wiki/Flow/Community_process_workflow_interviews_(June_2015)
2.
https://www.mediawiki.org/wiki/File:Flow_workflow_interviews_-_initial_findings_June_2015.pdf
3.
https://www.mediawiki.org/wiki/File:User(s)_Talk(ing)_-_Wikimania_2015.pdf


> --
> -bawolff
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [recommended reading] the hamburger menu is broken

[Jonathan Morgan]

FYI Ori also shared this link on the design list today, and there's been
some interesting discussion there:
https://lists.wikimedia.org/pipermail/design/2015-August/002366.html

J

On Tue, Aug 11, 2015 at 3:47 AM, Brian Gerstle bgers...@wikimedia.org
wrote:

 Interesting article about how various sites/apps switched away from the
 hamburger and to the more conventional tab bar, with tangible results:

 http://deep.design/the-hamburger-menu/

 --
 EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle
 IRC: bgerstle
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month

[Jonathan Morgan]

+1

thanks for putting that list together!

On Wed, Jul 8, 2015 at 11:12 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org
 wrote:

 On Wed, Jul 8, 2015 at 11:55 AM, Mr. Stradivarius misterst...@gmail.com
 wrote:

  I'm sure there are still some out there, but probably not as many as you
  think. I know that there aren't any gadgets or user scripts on enwiki or
  mediawikiwiki that use the old syntax, because I cleaned them up
  personally. I also got myself global interface editor rights and fixed
 all
  the gadgets in the MediaWiki namespace on every Wikimedia wiki.

 [...]

  Also, if anyone is interested, I have compiled a list of scripts on all
  WMF wikis that may need updating.[1] It has 129 pages in at the moment,
  although some are false positives, and some are personal scripts for
  inactive users that we don't need to bother with.
 

 Have I mentioned you are awesome for doing all that? Because you are!


 --
 Brad Jorsch (Anomie)
 Software Engineer
 Wikimedia Foundation
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month

[Jonathan Morgan]

I run GrantsBot, which is listed here.

I've updated all GrantsBot API requests to use rawcontinue=1. But as I read
through this thread, it's not clear to me that that's the problem. I can't
find a single instance in my code where I'm actually continuing a query.
Does this breaking change only apply be an issue if you were using
querycontinue in the first place?

I'm sure this has been covered elsewhere or I'm missing something obvious,
but I'd be grateful for specific confirmation :)

Best,
Jonathan

On Wed, Jun 10, 2015 at 12:01 PM, Brad Jorsch (Anomie) 
bjor...@wikimedia.org wrote:

 On Wed, Jun 3, 2015 at 12:43 PM, Brad Jorsch (Anomie) 
 bjor...@wikimedia.org
  wrote:

  On Wed, Jun 3, 2015 at 7:29 AM, John Mark Vandenberg jay...@gmail.com
  wrote:
 
  If possible, could you compile a list of bots affected at a lower
  threshold - maybe 1,000.  That will give us a better idea of the scale
  of bots operators that will be affected when this lands - currently in
  one months time.
 
 
  I already have the list of *accounts* affected: there are 510 with
 between
  1000 and 1 hits. Of those, 454 do not contain bot (case
  insensitively), so they might be human users with user scripts, or AWB if
  that's not fixed (someone please check!), or the like. For comparison, in
  the over-1 group there were 30 such that I filtered out.
 
  I'll want to check with Legal to make sure the additional release of
  account names is still compliant with the privacy policy (I'm almost but
  not entirely sure it would be ok).
 

 Legal recommended we only post the list of bots, not the human accounts.
 These are:

 AHbot
 AsuraBot
 Autobot
 BattyBot
 Bibcode_Bot
 Bottuzzu
 ChenzwBot
 Cydebot
 DickensBot
 DrTrigonBot
 DSisyphBot
 DumbBOT
 DYKHousekeepingBot
 DYKUpdateBot
 FBot
 GiftBot
 GrantsBot
 HangsnaBot
 HangsnaBot2
 ImageRemovalBot
 InceptionBot
 JackBot
 JBot
 Jimmy-bot
 Kenrick95Bot
 KrBot
 KrinkleBot
 LivingBot
 MalafayaBot
 MaraBot
 MauroBot
 MBHbot
 Mr.Z-bot
 NowCommons-Sichtbot
 Olafbot
 PereBot
 PseudoBot
 QianBot
 Rainbot
 Reports_bot
 RFF-Bot
 Salebot
 Sanjeev_bot
 SemperBlottoBot
 SergoBot
 SHBot
 Steenthbot
 TurkászBot
 UWCTransferBot
 VlsergeyBot
 VriuBot
 YiFeiBot
 Yobot
 ZacheBot
 Zlobot

 Note this list is still from May 23–29; a bot appearing in this list may
 have been updated since then.


 --
 Brad Jorsch (Anomie)
 Software Engineer
 Wikimedia Foundation
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] API BREAKING CHANGE: Default continuation mode for action=query will change at the end of this month

[Jonathan Morgan]

Thanks Yuri and Brad!

On Mon, Jun 29, 2015 at 11:10 AM, Brad Jorsch (Anomie) 
bjor...@wikimedia.org wrote:

 On Mon, Jun 29, 2015 at 1:53 PM, Yuri Astrakhan yastrak...@wikimedia.org
 wrote:

  It is much better than to use rawcontinue, because
  that flag will keep telling us someone needs the old system.
 

 I doubt we'll ever get rid of rawcontinue. There's practically no code to
 maintain there (it's just a one-line function[1] and a trivial if-block to
 call it[2]) so it's highly unlikely to be worth even minimal effort.

  [1]:

 https://git.wikimedia.org/blob/mediawiki%2Fcore.git/26288853/includes%2Fapi%2FApiContinuationManager.php#L163
  [2]:

 https://git.wikimedia.org/blob/mediawiki%2Fcore.git/26288853/includes%2Fapi%2FApiQuery.php#L295


 --
 Brad Jorsch (Anomie)
 Software Engineer
 Wikimedia Foundation
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wmfall] Welcome Frances Hocutt

[Jonathan Morgan]

Welcome, Frances!

It was a pleasure working with (and learning from) you during our work on
the Inspire campaign and the Co-op. I look forward to the opportunity to
work together again soon!

- Jonathan

On Mon, May 25, 2015 at 12:39 PM, Bryan Davis bd...@wikimedia.org wrote:

 I'm excited to announce that Frances Hocutt has been hired as a Software
 Engineer on the Community Tech team starting 2015-05-26.

 She has gotten a good start on getting things done by writing a great
 introduction blurb for me to forward on:

 Frances is looking forward to starting on a [new team doing cool but
 unspecified stuff]. Frances has been with the WMF for most of the last
 year, first as an OPW intern and then as a developer for Community
 Resources. Frances has primarily worked in the MediaWiki API ecosystem: she
 wrote the standard for API client libraries, evaluated a number of them,
 and developed wiki bots to support this Inspire campaign and the Co-op
 mentorship project on English Wikipedia. She also has contributed patches
 and product management to Wikimetrics. Before starting work in F/OSS,
 Frances worked as a medicinal chemist, studied organic chemistry and
 materials science, and founded a hackerspace. She moved to the Bay Area in
 January. She enjoys giving talks, mentoring new programmers, and practicing
 various fiber arts.

 Frances can be found as fhocutt on IRC, Fhocutt as a volunteer, and
 Fhocutt (WMF) officially.


 --
 Bryan Davis  Wikimedia Foundationbd...@wikimedia.org
 [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
 irc: bd808v:415.839.6885 x6855

 ___
 Wmfall mailing list
 wmf...@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wmfall




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wmfall] Welcome Niharika Kohli

[Jonathan Morgan]

Welcome, Naharika!

Your grant review application is awesome. I'm glad we get to keep drawing
on your skills!

Best,
Jonathan

On Mon, May 25, 2015 at 1:20 PM, Bryan Davis bd...@wikimedia.org wrote:

 Community Tech is glad to welcome Niharika Kohli as a Software Engineer.
 Her first day will be 2015-05-26.

 Here's the great blurb she wrote for me to forward on to the lists:

 Niharika lives in New Delhi, India where she's recently completed her
 undergraduate in IT. She's formerly been an OPW (now Outreachy) intern with
 Wikimedia for Round 7 where she had fun working on the compact language
 selector project with the Language Engineering team. She's also been a
 Google Summer of Code intern where she worked on a whacky Django project in
 a tiny five person organization.
 Niharika's been working as a contractor with the Foundation since November
 on the Wikimania Scholarships and Grants Review applications. She's also
 been having a lot of fun bullying around Wikimedia's GSoC and Outreachy
 interns (one of the perks of being an org-administrator).
 Niharika enjoys cooking Indian food in her spare time. She's also fond of
 travelling, roller coasters, board games, messing around with gadgets and
 other nerdy stuff like solving the Rubik's cube. She's thrilled to be
 working with Wikimedia which is her first real job.


 --
 Bryan Davis  Wikimedia Foundationbd...@wikimedia.org
 [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
 irc: bd808v:415.839.6885 x6855

 ___
 Wmfall mailing list
 wmf...@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wmfall




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Community project ideas

[Jonathan Morgan]

On Tue, May 19, 2015 at 6:52 AM, MZMcBride z...@mzmcbride.com wrote:


 What is Community Tech? How does it differ from the work the rest of the
 engineering and product team is doing? Are there people working for the
 Wikimedia Foundation who are doing design and development that is not for
 the Wikimedia community? That would be pretty worrying.


Really? It's worrying that the Wikimedia Foundation would devote design and
development resources towards projects that don't directly benefit 5+/month
editors?* Like, for example, readers?




 I looked at
 https://wikimediafoundation.org/wiki/Staff_and_contractors#Community_Tech
 
  and I can't say that I'm very impressed with what I see. Three cordoned
 off positions, one vacant, to serve the tens of thousands of volunteers
 that create and build the wiki projects and drive the Wikimedia movement
 forward? Clearly I'm just misunderstanding, as it would be pretty
 unimaginable for anyone to seemingly be this insulting.



Yes, you are misunderstanding. I'm sorry the team fails to impress you. The
community tech team is a product of the recent Engineering reorganization,
and I assume our colleagues will make an announcement once the team is
fully assembled. In the meantime, they're eliciting ideas. What exactly is
so insulting about a new team, still in the process of being formed,
eliciting ideas for projects to work on?


*active Wikimedia editors mentioned on the meta page


-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Per-user search query limiting being deployed to wmf wikis

[Jonathan Morgan]

On Mon, May 18, 2015 at 5:08 PM, Bahodir Mansurov bmansu...@wikimedia.org
wrote:

 I doubt all 200 students will be making concurrent searches.



I can easily imagine a scenario where 200 students in a large lecture
classroom might be instructed to open their laptops, go to Wikipedia, and
search for a particular topic at the same time. Similar to how teachers
[used to] say now everyone in the class turn to Chapter 8

If that is indeed what we're talking about here, it will be disruptive.

- Jonathan



  On May 18, 2015, at 7:57 PM, John phoenixoverr...@gmail.com wrote:
 
  This will bring such a idea to a screeching halt. Any kind of shared IPs
  will be unable to search
 
  On Mon, May 18, 2015 at 7:54 PM, Pine W wiki.p...@gmail.com wrote:
 
  While I understand the intent of conserving search resource use, will
 this
  change have adverse effects in situations like professors instructing
 their
  200-student classes to search for a particular topic and its related
  articles on Wikipedia?
 
  Pine
  On May 18, 2015 12:35 PM, Erik Bernhardson 
 ebernhard...@wikimedia.org
  wrote:
 
  In a few hours a patch will be going out which limits the number of
  concurrent searches a single user will be able to make to 5.  This
  applies
  to logged in and anonymous users.  The failure message is `You have too
  many concurrent searches running.  If you are sharing an IP address
 with
  other users you can log in to get your own limits.` for anonymous
 users,
  or
  just `You have too many concurrent searches running.` for logged in
  users.
  These are the `cirrussearch-too-busy-for-you-anonymous-error` and
  `cirrussearch-too-busy-for-you-logged-in-error` i18n messages.
 
  I will be monitoring the logs when this goes out, and intermittently
  throughout the week as well. If necessary we will whitelist certain ip
  ranges that seem to be shared among large numbers of users.
 
  Erik B.
  ___
  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
 
  ___
  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




-- 
Jonathan T. Morgan
Senior Design Researcher
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] GRAPH extension is now live everywhere!

[Jonathan Morgan]

This is wicked exciting. Thanks to everyone involved!

- J

On Tue, May 5, 2015 at 1:24 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:

 Starting today, editors can use *graph* tag to include complex graphs and
 maps inside articles.

 *Demo:* https://www.mediawiki.org/wiki/Extension:Graph/Demo
 *Vega's demo:* http://trifacta.github.io/vega/editor/?spec=scatter_matrix
 *Extension info:* https://www.mediawiki.org/wiki/Extension:Graph
 *Vega's docs:* https://github.com/trifacta/vega/wiki
 *Bug reports:* https://phabricator.wikimedia.org/ - project tag #graph

 Graph tag support template parameter expansion. There is also a Graphoid
 service to convert graphs into images. Currently, Graphoid is used in case
 the browser does not support modern JavaScript, but I plan to use it for
 all anonymous users - downloading large JS code needed to render graphs is
 significantly slower than showing an image.

 Potential future growth (developers needed!):
 * Documentation and better tutorials
 * Visualize as you type - show changes in graph while editing its code
 * Visual Editor's plugin
 * Animation https://github.com/trifacta/vega/wiki/Interaction-Scenarios

 Project history: Exactly one year ago, Dan Andreescu (milimetric) and Jon
 Robson demoed Vega visualization grammar https://trifacta.github.io/vega/
 
 usage in MediaWiki. The project stayed dormant for almost half a year,
 until Zero team decided it was a good solution to do on-wiki graphs. The
 project was rewritten, and gained many new features, such as template
 parameters. Yet, doing graphs just for Zero portal seemed silly. Wider
 audience meant that we now had to support older browsers, thus Graphoid
 service was born.

 This project could not have happened without the help from Dan Andreescu,
 Brion Vibber, Timo Tijhof, Chris Steipp, Max Semenik,  Marko Obrovac,
 Alexandros Kosiaris, Jon Robson, Gabriel Wicke, and others who have helped
 me develop,  test, instrument, and deploy Graph extension and Graphoid
 service. I also would like to thank the Vega team for making this amazing
 library.

 --Yurik
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Community Research Lead
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
jmor...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] VisualEditor support for table copy-and-paste from Word

[Jonathan Morgan]

+1 on blog post. I think it's finally time to celebrate success here. I was
using VE for table editing the other day, and it worked amazingly well.
Nice job, y'all. - J

On Thu, Apr 16, 2015 at 4:07 AM, Katherine Maher kma...@wikimedia.org
wrote:

 On Apr 16, 2015 6:55 AM, David Gerard dger...@gmail.com wrote:
 
  On 15 April 2015 at 09:38, Trevor Parscal tpars...@wikimedia.org
 wrote:
 
   I'm glad to hear VE had your back. This actually reminds me, there's a
   feature we never really advertised in VisualEditor where a CSV file can
 be
   dragged into the editor and a table is created from its contents.
 
 
  We need a blog post about what VE is like these days. I suspect too
  many people who tried it at release think it still intrinsically
  sucks, and need to give it a spin again now, two years later.

 We're planning one, if not a few! Fabrice and the blog team are thinking
 about how to best showcase VE on the blog, from user and technical
 perspectives. (Posts highlighting engineering work are among of the most
 highly trafficked on the blog).

 I'd welcome thoughts on what you think we should specifically cover.

 
 
   Give it a try. And thank Ed Sanders for all things tables and
 Copy/Paste.
 
  In particular, listing all the cool stuff you can do with tables. You
  can take out a column with a click instead of tediously going through
  each line and trying not to make a mistake!! The VE is the *only* sane
  way to edit tables.
 
  Seriously, it warrants the hype these days.
 
  And, three cheers for Ed. Hip hooray! Hip hooray! Hip hooray!
 
 
  - d.
 
  ___
  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




-- 
Jonathan T. Morgan
Community Research Lead
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
jmor...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Phabricator monthly statistics - 2015-03

[Jonathan Morgan]

Hi Pine,

I understand your concern, but in all fairness Phabricator is used by a lot
of people for a lot of different things, and without a better understanding
of what kind of tasks are being marked as unbreak now (and by whom), I
don't think it makes sense to set thresholds (which will always end up
being arbitrary, without better data).

It might be useful to dig a little bit into these Unbreak Now tasks: who
is proposing them? What products/features do they address? How many have
been claimed/scoped/pointed/commented on? Phabricator has a pretty good
query interface that should make it easier to filter and browse tasks to
answer these questions. If you were interested in taking a stab at this,
I'm sure folks on this list would be interested in the results :)

Cheers,
Jonathan

On Wed, Apr 1, 2015 at 9:31 AM, Pine W wiki.p...@gmail.com wrote:

 Hi Quim and team practices folks,

 Do you have any suggestions about how to shorten the average time for bug
 fixes shown here? In particular, it seems to me that unbreak now bugs
 should be fixed in something like 10 days max. If something is seriously
 broken, 48 days is long time to wait for a fix.

 Thanks,
 Pine
 On Apr 1, 2015 8:56 AM, communitymetr...@wikimedia.org wrote:

 
  Hi Community Metrics team,
 
  this is your automatic monthly Phabricator statistics mail.
 
  Number of accounts created in (2015-03): 388
  Number of active users (any activity) in (2015-03): 838
  Number of task authors in (2015-03): 461
  Number of users who have closed tasks in (2015-03): 215
  Number of tasks created in (2015-03): 3461
  Number of tasks closed in (2015-03): 2830
 
  Number of open and stalled tasks in total: 20757
 
  Median age in days of open tasks by priority:
  Unbreak now: 48
  Needs Triage: 88
  High: 113
  Normal: 373
  Low: 668
  Needs Volunteer: 498
 
  TODO: Numbers which refer to closed tasks might not be correct, as
  described in T1003.
 
  Yours sincerely,
  Fab Rick Aytor
 
  (via community_metrics.sh on iridium at Wed Apr  1 00:00:05 UTC 2015)
 
  ___
  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




-- 
Jonathan T. Morgan
Community Research Lead
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
jmor...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] post project funding

[Jonathan Morgan]

Responses to BAWolf inline.

On Sat, Feb 21, 2015 at 12:05 PM, Brian Wolff bawo...@gmail.com wrote:

 On 2/21/15, Pine W wiki.p...@gmail.com wrote:
  In general WMF has a conservative grant policy (with the exception of
 IEG,
  grant funding seems to be getting more conservative every year, and some
  mission-aligned projects can't get funding because they don't fit into
 the
  current molds of the grants programs). Spontaneous cash awards for
 previous
  work are unlikely. However, if there is an existing project that could
 use
  some developer time, it may be possible to get grant funding for future
  work.
 

 [Rant]

 I find this kind of doubtful when IEG's (which for an individual
 developer doing a small project is really the type of funding that
 applies) have been traditionally denied for anything that even
 remotely touches WMF infrastructure. (Arguably the original question
 was about toollabs things, which is far enough away from WMF
 infrastructure to be allowed as an IEG grant, but I won't let that
 stop my rant...). Furthermore, it appears that IEGs now seem to be
 focusing primarily on gender gap grants.



Couple quick clarifications:
1. There have been many IEGs that focus on tool development, including
those from the most recent round
https://meta.wikimedia.org/wiki/Grants:IEG#ieg-engaging. There's no
tradition of denying software projects: they're quite well represented
among completed IEG projects too
https://meta.wikimedia.org/wiki/Category:IEG/Proposals/Completed. In the
past, there have been concerns from members of Product/Engineering that
IEGs would divert resources from established development priorities, so
projects that rely on MediaWiki integration were sometimes a tough sell.
2. IEG accepts applications twice a year; this coming round (April) the
focus will be on gender-gap themed projects. The focus of the September
2015 round, if there is one, has not been established yet. But it's
unlikely to be gender gap.




 I find it odd, that we have grants through GSOC and OPW to people who
 are largely newbies (although there are exceptions), and probably
 not in a position to do anything major. IEG provides grants as long
 as they are far enough away from the main site to not actually change
 much. But we do not provide grants to normal contributors who want to
 improve the technology of our websites, in big or important ways.



That would be totally awesome.


 Ostensibly this is done in the name of:
 Any technical components must be standalone or completed on-wiki.
 Projects are
 completed without assistance or review from WMF engineering, so MediaWiki
 Extensions or software features requiring code review and integration
 cannot be
 funded. On-wiki tech work (templates, user scripts, gadgets) and
 completely
 standalone applications without a hosting dependency are allowed.

 Which on one hand is understandable. WMF-tech has its own priorities,
 and can't spend all its time babysitting whatever random ideas get
 funded. So I understand the fear that brought this about. On the other
 hand it is silly, since a grant to existing tech contributors is going
 to have much less review burden than gsoc/opw, and many projects might
 have minimal review burden, especially because most review could
 perhaps be done by non-wmf employees with +2, requiring only a final
 security/performance sign off. In fact, we do already provide very
 limited review to whatever randoms submit code to us over the internet
 (regardless of how they are funded, or lack thereof). If IEG grants
 were allowed in this area, it would be something that the grantee
 would have to plan and account for, with the understanding that nobody
 is going to provide a team of WMF developers to make someone else's
 grant happen. We should be providing the same amount of support to IEG
 grantees that we would to anyone who submitted code to us. That is,
 not much, but perhaps a little, and the amount dependent on how good
 their ideas are, and how clean their code is.



That would be totally awesome.



 [End rant]

 Politically, I think its dangerous how WMF seems to more and more
 become the only stakeholder in MediaWiki development (Not that there
 is anything wrong with the WMF, I just don't like there being only 1
 stakeholder). One way for there to be a more diverse group of
 interests is to allow grants to groups with goals consistent with
 Wikimedia's. While not exactly super diverse (all groups have similar
 goals), at least there would then be more groups, and hopefully result
 in more interesting and radical projects.

 --bawolff

 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Community Research Lead
Wikimedia Foundation
User:Jmorgan (WMF) https://meta.wikimedia.org/wiki/User:Jmorgan_(WMF)
jmor...@wikimedia.org
___
Wikitech-l 

Re: [Wikitech-l] Help on Research

[Jonathan Morgan]

Hi Igor,

Sounds like an interesting  worthwhile project. Have you heard about our
upcoming Research Hackathon Day[1]? That could be a good opportunity for
you to connect with community members and other researchers who might be
able to assist with your study or connect you with people who you can talk
to.

If you haven't done so yet, it's a very good idea to write up a description
of your project on-wiki. You can create a new project here[2], and read
some of the best practices for Wikipedia research here[3].

There are several other links that I'm tempted to put here too... but I
don't want to overwhelm you if you're new to research in this domain :)
Follow up with me personally if you want.

Cheers,
Jonathan

1.
https://meta.wikimedia.org/wiki/Research:Labs2/Hackathons/November_9th,_2013
2. https://meta.wikimedia.org/wiki/Research:Projects
3.
https://meta.wikimedia.org/wiki/Notes_on_good_practices_on_Wikipedia_research

On Mon, Oct 28, 2013 at 10:37 AM, Igor Steinmacher 
igorsteinmac...@gmail.com wrote:

 Hello

 My name is Igor Steinmacher and I am a Research Scholar at University of
 California,
 Irvine. I am conducting a research aiming at finding how to support new
 contributors
 during their first steps in the project.  My final goal is to verify what
 kind of tooling is
 appropriate  to  support  the  newcomers  overcoming  their  difficulties
 when  they  are
 willing to contribute to the project.

 The first step of my research is to find out what are the main obstacles
 and difficulties
 faced by these newcomers. My goal is to hear from the community itself,
 interviewing
 new contributors and core members.

 By having the information regarding the main problems, I will start
 figuring out which
 mechanisms  can  be  applied  to  provide  the  support.  I  will  keep
 the  anonymity  of
 interviewers and I have the commitment to publish/return the results
 of myresearch to
 the community.

 I need your help answering my interview. We will conduct the interviews via
 textual
 chat, and we can schedule it at the time that fits better for you. Please
 send me a private
 email if you are interested in supporting my research.

 I  also  request  your  help  reaching  out  core contributors  so  that
 I  can  gather  the  best
 information. The data will help gain insights about newcomer issues, and
 allow us to
 propose initiatives to alleviate the problems faced by newcomers, as a
 tentative to retain
 them.

 To volunteer you must be 18 years or older, be English speaking, and have
 experience
 in software development.

 Feel free to contact me in case you have any doubt or question
 regarding myresearch or
 the interview process.

 Thanks in advance
 --
 Igor Fabio Steinmacher
 Visiting Scholar in Dept of Informatics at UCI (http://www.informatics.uci
 .edu/)
 Faculty in Dept. of Computing at Universidade Tecnológica Federal do Paraná
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Learning Strategist
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] input requested re: metrics for hackathons

[Jonathan Morgan]

Hi all,

OrenBachman has asked several questions about how to evaluate the impact of
Hackathon events on the Evaluation Portal*[1]* and I'm hoping some folks
from this list can share their advice and perspectives.

Please read and respond there if you have input. Several outstanding
questions are:

1. do you know of any available publicly stats on how many first time
MediaWiki hackers make use of git/gerrit?

2. can you share any good strategies for getting as many attendees as
possible to set up git/gerrit userids prior to the event?

3. can you provide any examples of reports from previous Hackathons that do
a good job of describing various impact/participation metrics?

4. Safe space policy - How have breaches to the safe space policy been
handled in recent events? How have they been reported?

I'm going to follow up elsewhere about the legal issues OrenBachman raises,
but feel free to share your experiences with those as well.

Thanks for your assistance,
Jonathan

*[1]*
https://meta.wikimedia.org/wiki/Programs:Evaluation_portal/Parlor/Questions#What_are_the_established_Goals_and_Metrics_used_to_evaluate_Hackathons

-- 
Jonathan T. Morgan
Learning Strategist
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Operations team announcements: Ryan and Leslie

[Jonathan Morgan]

Congratulations, Ryan and Leslie! Glad to have you two running the place :)

- Jonathan


On Wed, Oct 16, 2013 at 12:40 AM, Ken Snider ksni...@wikimedia.org wrote:

 Hello!

 I'm extremely pleased to announce that we've had two promotions within the
 Technical Operations team!

 Leslie Carr has been promoted to Senior Operations Engineer (Networking).
 As many of you know, along with Mark, Leslie has been instrumental in
 securing preferred rates and contracts with with connectivity providers and
 vendors on the networking side of our infrastructure - in a world where
 human connections are every bit as important as topographic ones, Leslie
 has maintained a vast network of contacts to help ensure that we're
 receiving competitive pricing, fair peering, and a plethora of other perks
 that come part and parcel with maintaining solid relationships in the
 networking arena, while also taking point on many of the technical aspects
 of our network infrastructure as well.

 We're lucky to have her, and I look forward to working with her as the
 team completes the setup of ULSFO and begins work on our next data-centre
 project.

 Ryan Lane has also been promoted to Senior Operations Engineer. Ryan has
 served as the lead on the Labs project, a component of our infrastructure
 that has become increasingly critical to projects both within WMF
 engineering (with Beta Labs), as well as with various volunteer projects
 (via Tool Labs). Ryan is about to head up the migration of this
 infrastructure from Tampa to Ashburn as part of our plan to sunset the
 Tampa data-centre.

 Additionally, Ryan has also played a key role in several non-labs-related
 projects, including most recently our HTTPS-as-default project, as well as
 work on integrating git-deploy into the mediawiki deployment pipeline.
 Ryan's work has been invaluable, and this promotion well-deserved.

 Thanks!

 --Ken.



 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Jonathan T. Morgan
Learning Strategist
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Bug 35306: Global (to a wiki farm or family) message delivery (thoughts)

[Jonathan Morgan]

Necromancy? I'll jump on that bandwagon.

On Thu, Oct 10, 2013 at 9:01 AM, Dan Garry dga...@wikimedia.org wrote:


 *The question: do we need an interim solution for message delivery, until a
 future-proofed solution is developed?*
 *
 *
 How I answer this question depends on questions that I don't have the
 answer to yet.

 1) How much of a performance problem is EdwardsBot?.
 a) If it's a big problem for site performance, then I think working on
 something to alleviate that problem in the mean time (i.e. MassMessage)
 could be worthwhile. Platform now has a performance engineer, Ori, who I
 can explore that question with. If the answer is Not a performance problem
 at all, then that helps us rule out the need for an interim solution.

 2) How long will the future-proofed solution take to make?.
 a) If it's going to be a long time (for some definition of long), then
 polishing off MassMessage into a form we're all happy with, so it can be
 used, may make sense. This also means we don't have a long term commitment
 to maintaining it, as we will be kicking it out when we're done with it.

 If the solution is that there is zero need for an interim solution, then we
 needn't discuss any of the details.
 *
 *


I submit one more question for consideration here:
3) How much easier is MassMessage to use than
GlobalMessageDelivery/EdwardsBot?
a) I tested it, and I think it's a substantially improved workflow. Others
may disagree. Even if we are able to fast-track a permanent solution, those
of us who spam with any frequency stand to save time and frustration in the
interim with MassMessage.






 On 3 October 2013 20:22, Terry Chay tc...@wikimedia.org wrote:

  I am posting this to wikitech-l, ee-l, and will cross-post this to
  https://bugzilla.wikimedia.org/show_bug.cgi?id=35306 because it's
  important to keep frank discussions in the open.
 
  When I use to loaded words like back-dooring etc, I believe that no
  malice was intended and the discussions so far have been in good faith
 from
  all parties. I think people have a valid concern and want it addressed
 and
  are wondering honestly how decisions have been made. In particular, my
  decision to not allow the MassMessage Extension to roll out onto
 MediaWiki
  last week, since that occurred during a meeting that didn't even involve
 or
  derive have consultation (except ex-post-facto) with any product manager
 or
  engineer here.
 
  Here is why I am inijating this thread:
 
  1)
 
 https://wikitech.wikimedia.org/w/index.php?title=Deploymentsdiff=83188oldid=83134
 
  2) On Sep 30, 2013, at 4:25 PM, MZMcBride z...@mzmcbride.com wrote:
 
  Hi Fabrice, Terry, and Howie,
 
  https://bugzilla.wikimedia.org/show_bug.cgi?id=35306#c19 is awaiting
  feedback (if you have any).
 
  MZ
 
 
  3)
 
 https://wikitech.wikimedia.org/w/index.php?title=Deploymentsdiff=84903oldid=84888
 
  …
 
  We have two separate but related bugs here:
 
  https://bugzilla.wikimedia.org/show_bug.cgi?id=35306
  https://bugzilla.wikimedia.org/show_bug.cgi?id=52723
 
  bug 35306 is an tracking bug MZMcBride posted for a solution to deal with
  EdwardsBot. I believe it dates to around the time I was first employed
  almost two years ago.
 
  bug 52723 is a recent bug to deploy Legoktm's MassMessage extension as a
  solution to bug 35306, it is less than a month old there has been little
  public discussion, and until it appeared on the deploy calendar last
 week,
  I wasn't even aware of its existence.
 
  The problem with moving on bug 52723 as a solution to bug 35306 is it
  commits Features Engineering to maintaining an extension that is a stop
 gap
  solution with no or very little discussion in a manner that doesn't
 serve a
  broad strategic goal about how messages, notifications, etc. should be
  handled on the wikis. To the first, maybe there is something wrong with
 my
  e-mail client, but I have yet to find this discussion on wikitech-l or
  anywhere outside the bug.
 
  Because of the above, my view is that this solution is being back-doored
  in and just moves the technical debt from one sheet (the community and
  tool labs) to another that has even less capability. I am biased against
  that because the latter sheet (WMF Features Engineering) is my
  responsibility. This is just my view, *I'm open for us coming to
 consensus on
  a solution for this bug*, but what I have seen is not consensus.
 
  It is along these lines that, I asked to remove MassMessage from the
  deploy calendar when it was added to the deploy calendar without
 discussion
  from Features, Design, or Product last week. After discussion during that
  Friday meeting among the EPMs, I *compromised* to let it to go out on two
  test wikis, but not on mediawiki. Nobody made the case that it should go
  out on mediawiki. I demurred because no person at the WMF, including me
 as
  Director of Features Engineering, should fiat a decision when unaware of
  the status of discussions involved.
 
  But let frank: *if