[Wikitech-l] Platform Evolution Update

2019-02-12 Thread Corey Floyd
Hi all,
The PE Program team has been preparing for the Wikimedia Foundation midterm
(3 year) planning by reviewing and organizing all of the followup from
TechConf. We published an update of this work on Wiki here:
https://www.mediawiki.org/wiki/Platform_Evolution/Updates/Feb_2019

A list of oiuyr proposed Goals and Outcomes for the next 3 years is here:
https://www.mediawiki.org/wiki/Platform_Evolution/Goals

We are currently looking for feedback on the work we have done so far,
please check out the update for more info.

Thanks everyone!

-- 
Corey Floyd
Director of Engineering, Core Platform
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Platform Evolution post-TechConf update

2018-11-27 Thread Corey Floyd
Hi everyone,


It has been a month since the Wikimedia Technical Conference[1] and the
year is winding down, so it seemed like a good time to send an update on
the Platform Evolution Program[2]. Specifically, I wanted to let you all
know how the Core Platform Team will be following up on the great work
coming out the conference.


For those who didn’t attend, the primary goal of the conference was to
produce the building blocks to develop a 3-5 year platform roadmap, which
in turn will enable us to achieve our program goal: Evolve our technology
platform and development processes to empower the Wikimedia Movement.


Each session was designed to generate action items, decisions, and goals
that will become the building blocks of the roadmap. Session leaders,
scribes, facilitators and attendees worked hard to capture these outcomes
in notes on wiki[3] and in Phabricator[4] (thanks again to all who helped
with this process! )


Following TechConf, the Core Platform Team along with members of the
Conference Committee has been reviewing all of the session notes and
aggregating major outcomes into a single document. We are working to
publish this document on MediaWiki.org by the new year and will send out
another email when we do so that you will know where to find them. We will
also be asking attendees to review this wiki to ensure we didn’t miss
anything important.


There are also teams and attendees are independently following up on
TechConf outcomes alongside this formal process - this includes authoring
RFCs and planning projects. Once the initial review of the materials is
complete, we will be reaching out to individuals and teams to see how the
Platform Evolution Program and Core Platform Team can support their work.


In addition to guiding the 3-5 year platform roadmap, the outcomes from
TechConf will be used as input into annual planning and the Q3/Q4 work for
the Platform Evolution Program. The WMF officially begins the 3-5 year
strategy and annual planning in January, so we will have more updates as
that process kicks off.


On behalf of the the Conference Committee, Core Platform Team and the
Platform Evolution Program, I would again like to thank everyone who
attended and contributed to the conference. Your time, work and input were
essential to the success of the event and will be invaluable to the
development of the Platform Evolution Program.


Corey



[1] https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018

[2]

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

[3]

https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2018/Session_notes

[4]

https://phabricator.wikimedia.org/tag/wikimedia-technical-conference-2018/

-- 
Corey Floyd
Director of Engineering, Core Platform
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wmfall] Honor roll for Nuria Ruiz!

2018-09-21 Thread Corey Floyd
Congrats Nuria! Well deserved :)

On Fri, Sep 21, 2018 at 12:59 PM Leon Ziemba 
wrote:

> Esto es increíble!!! ¡Felicitaciones, Nuria! You've always been a rock star
> to me. Nice to see the press finally picked up on it, hehe! ;)
>
> ~Leon
>
> On Fri, Sep 21, 2018 at 11:45 AM Sarah R  wrote:
>
> > This is great, Nuria! Congratulations!!!
> >
> > On Fri, Sep 21, 2018 at 8:22 AM Samuel Patton 
> > wrote:
> >
> >> That's really impressive. Congratulations, Nuria!
> >>
> >> On Fri, Sep 21, 2018 at 9:50 AM Deb Tankersley <
> dtankers...@wikimedia.org>
> >> wrote:
> >>
> >>> *THIS* *IS* *AWESOME*! :)
> >>>
> >>>
> >>> Deb
> >>>
> >>> --
> >>>
> >>> deb tankersley
> >>>
> >>> program manager, engineering
> >>>
> >>> Wikimedia Foundation
> >>>
> >>>
> >>> On Fri, Sep 21, 2018 at 3:29 AM Christel Steigenberger <
> >>> csteigenber...@wikimedia.org> wrote:
> >>>
> >>>> Exciting, wonderful news!!! Congratulations, Nuria!!! 
> >>>>
> >>>> Christel Steigenberger
> >>>> Trust and Safety Specialist
> >>>> Wikimedia Foundation
> >>>> preferred pronoun: she/her
> >>>>
> >>>> On Fri, Sep 21, 2018 at 4:25 AM, Yunita Clerici <
> ycler...@wikimedia.org
> >>>> > wrote:
> >>>>
> >>>>> Wow! Really cool!! Congrats, Nuria :)
> >>>>>
> >>>>>
> >>>>> On Thursday, September 20, 2018, Sydney Poore 
> >>>>> wrote:
> >>>>>
> >>>>>> Fantastic news! Congratulations
> >>>>>> Sydney
> >>>>>>
> >>>>>> On Thu, Sep 20, 2018 at 3:32 PM Victoria Coleman <
> >>>>>> vcole...@wikimedia.org> wrote:
> >>>>>>
> >>>>>>> Hi everyone,
> >>>>>>>
> >>>>>>> I am delighted to share the news of our own Nuria Ruiz being
> >>>>>>> recognized by Cnet as one of the 20 most influential Latinos in
> the tech
> >>>>>>> industry in 2018!
> >>>>>>>
> >>>>>>> https://www.cnet.com/es/noticias/wikipedia-wikimedia-nuria-ruiz/
> >>>>>>>
> >>>>>>>  It is an incredible honor accorded to an equally incredible
> person.
> >>>>>>> Nuria leads our efforts in Analytics but her contributions don’t
> stop
> >>>>>>> there. She leads on culture, on hiring, on team building and
> fighting for
> >>>>>>> the privacy of our communities. I could not be more proud or
> thankful to
> >>>>>>> have her in our team!
> >>>>>>>
> >>>>>>> Nuria,  Bien hecho!! You are making your mark!
> >>>>>>>
> >>>>>>> Victoria
> >>>>>>>
> >>>>>>>
> >>>>>>> ___
> >>>>>>> Wmfall mailing list
> >>>>>>> wmf...@lists.wikimedia.org
> >>>>>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Sydney Poore
> >>>>>> Trust and Safety Specialist
> >>>>>> Wikimedia Foundation
> >>>>>> Trust and Safety team;
> >>>>>> Anti-harassment tools team
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Yunita Citro Clerici
> >>>>> Accounting Manager
> >>>>> Wikimedia Foundation
> >>>>> ycler...@wikimedia.org
> >>>>> +1-415-839-6885 ext. 6698
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> *“Imagine a world in which every single human being can freely share
> >>>>> in the sum of all knowledge. That's our commitment.” **Donate.
> >>>>> <https://donate.wikimedia.org/> *
> >>>>>
> >>>>>
> >>>>> ___
> >>>>> Wmfall mailing list
> >>>>> wmf...@lists.wikimedia.org
> >>>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
> >>>>>
> >>>>>
> >>>> ___
> >>>> Wmfall mailing list
> >>>> wmf...@lists.wikimedia.org
> >>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
> >>>>
> >>> ___
> >>> Wmfall mailing list
> >>> wmf...@lists.wikimedia.org
> >>> https://lists.wikimedia.org/mailman/listinfo/wmfall
> >>>
> >> ___
> >> Wmfall mailing list
> >> wmf...@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/wmfall
> >>
> >
> >
> > --
> > Sarah R. Rodlund
> > Technical Writer, Developer Advocacy
> > <https://meta.wikimedia.org/wiki/Developer_Advocacy>
> > srodl...@wikimedia.org
> >
> >
> > *“I am a jug filled with water both magic and plain; I have only to lean
> > over, and a stream of beautiful thoughts flows out of me.” *
> >
> > ― Bohumil Hrabal, Too Loud a Solitude
> > ___
> > Wmfall mailing list
> > wmf...@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wmfall
> >
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Corey Floyd
Director of Engineering, Core Platform
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

2017-12-15 Thread Corey Floyd
e 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) <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
> > ___
> > 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

-- 
Corey Floyd
Engineering Manager
Readers
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

2017-12-12 Thread Corey Floyd
Admin assistance is definitely an interesting use case… there is also the
possibility of including incorporating ORES scores to see what changes are
actually good or not.

Since the API is primarily based off of edits, it isn’t too surprising that
a contributor / admin use case may be a better fit here. So the Trending
may yet have another life as a tool for administrators. It is definitely
something to test out to see if it is useful…

As Jon said, the Cloud VPS version may not be as reliable as Kafka, but
hopefully it is enough to evaluate this type of use… and maybe, as others
have mentioned, a good reason to get production Kafka events flowing into
Cloud VPS backed projects.


On Tue, Dec 12, 2017 at 3:27 PM Jonathan Morgan <jmor...@wikimedia.org>
wrote:

> 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 <jdlrob...@gmail.com> 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/en.wikipedia/Ed%20Lee%20(politician)>):
>> 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 <https://ifttt.com/wikipedia> 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 <rkald...@wikimedia.org> 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 <cfl...@wikimedia.org>
>> 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 <cfl...@wikimedia.org>
>> wrote:
>> > >
>> > > > Hi all,
>> > > >
>> > > > The experimental Trending Service[1] will be sunset on December
>> 14th,
>> > > 2017.
>> > > >
>> > > > We initially deployed this service to evaluate some real

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

2017-12-12 Thread Corey Floyd
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 <cfl...@wikimedia.org> 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
> Readers
> Wikimedia Foundation
> cfl...@wikimedia.org
>
-- 
Corey Floyd
Engineering Manager
Readers
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

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

2017-12-01 Thread Corey Floyd
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
Readers
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] RFC call for comments on Reading List Service

2017-06-05 Thread Corey Floyd
Hi all!

The Reading Infrastructure Team has created an RFC for a Reading List
Service to be used both by the platforms within Reading and by 3rd party
developers as well.

RfC: Reading List service <https://phabricator.wikimedia.org/T164990>

If you have used the Wikipedia Android app, you may already be using
Reading Lists. While many Android users love Reading Lists, unfortunately
there is no way to sync them across devices. This new service will allow
users to sync these lists for the first time while keeping them private.

The current plan is to develop this service for beta usage in the Android
app. And then after testing and feedback, evaluate the service for roll out
it out the rest of the reading platforms: iOS, mobile web, and desktop web
with consultation from the community.

For more details please check out the RFC and post comments and questions
in there.

Thanks everyone!
-- 
Corey Floyd
Engineering Manager
Reading
Wikimedia Foundation
cfl...@wikimedia.org
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Wikimedia Developer Summit Weekly

2016-11-10 Thread Corey Floyd
 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) <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
>



-- 
Corey Floyd
Software Engineer
Reading / iOS
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Key-value store API for MediaWiki

2016-07-19 Thread Corey Floyd
Super awesome!

Thanks for putting this together Brad

On Tue, Jul 19, 2016 at 2:07 PM, Dmitry Brant <dbr...@wikimedia.org> wrote:

> Much appreciated! Thanks for putting that together, and for aggregating all
> the questions.
>
>
>
> On Tue, Jul 19, 2016 at 1:44 PM, Brad Jorsch (Anomie) <
> bjor...@wikimedia.org
> > wrote:
>
> > Some of the mobile apps teams have been wanting some way to store data
> "in
> > the cloud", so they can sync things like app preferences and reading
> lists
> > between devices. They asked us (Reading Infrastructure) to help draft an
> > RFC, which is now posted in https://phabricator.wikimedia.org/T128602.
> > Please comment there, there are several open questions. Thanks!
> >
> > --
> > Brad Jorsch (Anomie)
> > Senior Software Engineer
> > Wikimedia Foundation
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> Dmitry Brant
> Senior Software Engineer / Product Owner (Android)
> Wikimedia Foundation
> https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
> _______
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Corey Floyd
Software Engineer
Reading / iOS
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] X-Wikimedia-Debug, your new secret side-kick

2016-03-31 Thread Corey Floyd
Bookmarked!

On Thu, Mar 31, 2016 at 2:49 PM, Eric Evans <eev...@wikimedia.org> wrote:

> On Wed, Mar 30, 2016 at 8:32 PM, Ori Livneh <o...@wikimedia.org> wrote:
> > Cool? Cool.
>
> Cool.
>
> --
> Eric Evans
> eev...@wikimedia.org
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
Corey Floyd
Software Engineer
Mobile Apps / iOS
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] What does it take to have a project hosted on the Wikimedia git server?

2015-03-13 Thread Corey Floyd
I was researching this the past week for the iOS team. I found this for
replicating pull requests as patch sets on gerrit:

https://gerrit.googlesource.com/plugins/github/

I am going to see if its possible we can get this plugin installed on our
gerrit - may help out with this.

On Fri, Mar 13, 2015 at 4:33 PM, Brian Wolff bawo...@gmail.com wrote:

 Yuvi used to have a bot i thought...

 --bawolff
 On Mar 13, 2015 4:10 PM, Florian Schmidt 
 florian.schmidt.wel...@t-online.de wrote:
 
  Iirc, but i'm not sure, actually it's not possible to merge pull requests
 from github :/
 
  Florian
 
  -Ursprüngliche Nachricht-
  Von: Strainu [mailto:strain...@gmail.com]
  Gesendet: Freitag, 13. März 2015 19:48
  An: florian.schmidt.wel...@t-online.de; Wikimedia developers
  Betreff: Re: [Wikitech-l] What does it take to have a project hosted on
 the Wikimedia git server?
 
  2015-03-13 14:27 GMT+02:00 florian.schmidt.wel...@t-online.de
  florian.schmidt.wel...@t-online.de:
   WMF git repos are already (automatically) mirrored to github :) See,
   e.g. https://github.com/wikimedia/mediawiki-extensions-MobileFrontend
   as a mirror of
   https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/M
   obileFrontend (also available on git.wikimedia.org
   https://git.wikimedia.org/summary/mediawiki%2Fextensions%2FMobileFront
   end )
 
  I knew about those, but I always assumed these are downstream-only (e.g.
 only pull from Gerrit, but no push). If we could accept pull-requests from
 github and have them pushed to Gerrit we would basically have the best of
 both worlds. :)
 
  Strainu
 
  
   Best,
   Florian
  
   Freundliche Grüße
   Florian Schmidt
   -Original-Nachricht-
   Betreff: Re: [Wikitech-l] What does it take to have a project hosted on
 the Wikimedia git server?
   Datum: Fri, 13 Mar 2015 13:16:06 +0100
   Von: Strainu strain...@gmail.com
   An: Wikimedia developers wikitech-l@lists.wikimedia.org
  
   2015-03-13 13:53 GMT+02:00 Magnus Manske magnusman...@googlemail.com
 :
   Why not github, or bitbucket?
  
   They're on the list as well, we're exploring all our options. Any
   special reason why you'd prefer those over Wikimedia?
  
   2015-03-13 13:54 GMT+02:00 Brian Wolff bawo...@gmail.com:
   See https://www.mediawiki.org/wiki/Gerrit/New_repositories
  
   Basically you just have to ask.
  
   I think its a nice thing to keep wiki related code, including bots in
   our git repos as that makes it easier for others to find.
  
   I am personally a bit worried about the complexity of the process on
   gerrit, but I hope that as long as we don't require formal code review
   it should be as simple as git pull/git push, right?
  
   Another related question would be: how hard is it to maintain a github
   mirror of a WMF repository?
  
   Thanks,
  Strainu
  
   ___
   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




-- 
Corey Floyd
Software Engineer
Mobile Apps / iOS
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Investigating building an apps content service using RESTBase and Node.js

2015-02-04 Thread Corey Floyd
On Wed, Feb 4, 2015 at 11:41 AM, Gabriel Wicke gwi...@wikimedia.org wrote:

 Regarding general-purpose APIs vs. mobile: I think mobile is in some ways a
 special case as their content transformation needs are closely coupled with
 the way the apps are presenting the content. Additionally, at least until
 SPDY is deployed there is a strong performance incentive to bundle
 information in a single response tailored to the app's needs. One strategy
 employed by Netflix is to introduce a second API layer
 
 http://techblog.netflix.com/2012/07/embracing-differences-inside-netflix.html
 
 on
 top of the general content API to handle device-specific needs. I think
 this is a sound strategy, as it contains the volatility in a separate layer
 while ensuring that everything is ultimately consuming the general-purpose
 API. If the need for app-specific massaging disappears over time, we can
 simply shut down the custom service / API end point without affecting the
 general API.



I can definitely understand that motivation for providing mobile specific
service layer - so if the services team wants to implement the API in this
way and support that architecture, I am totally on board.

My remaining hesitation here is that from the reading of this proposal, the
mobile team is the owner of implementing this service, not the services
team (Maybe I am misreading?).

This leads me to ask questions like:
Why is the mobile apps team investigating which is the best server side
technology? That seems outside of our domain knowledge.
Who will be responsible for maintaining this code?
Who will be testing it to make sure that is performant?

I'm new, so maybe these answers are obvious to others, but to me they seem
fuzzy when responsibilities are divided between two teams.

I would propose that this be a project that the Services Team owns. And
that the Mobile Apps Team defines specs on what they need the new service
to provide.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Investigating building an apps content service using RESTBase and Node.js

2015-02-03 Thread Corey Floyd
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Corey Floyd
Software Engineer
Mobile Apps / iOS
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Github access?

2015-01-26 Thread Corey Floyd
Does anyone know who has the administrative privlidges to add me to the
github wikimedia organization?

I need to cleanup/maintain our external pull requests.

Thanks!

-- 
Corey Floyd
Software Engineer
Mobile Apps / iOS
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l