Re: [Wikitech-l] [AI] Deployment of ORES review tool in Englis Wikipedia as a beta feature

[Luis Villa]

Thanks for the detailed explanation, Aaron. As always your work is a model
in transparency for the rest of us :)

On Tue, Aug 23, 2016 at 12:40 PM Aaron Halfaker <aaron.halfa...@gmail.com>
wrote:

> Hi Luis!  Thanks for taking a look.
>
> First, I should say that false-positives should be expected.  We're
> working on better signaling in the UI so that you can differentiate the
> edits that ORES is confident about and those that it isn't confident about
> -- but are still worth your review.
>
> So, in order to avoid a bias feedback loop, we don't want to feed any
> observations you made *using* ORES back into the model -- since ORES'
> prediction itself could bias your assessment and we'd re-perpetuate that
> bias.  Still, we can use these misclassification reports to direct our
> attention to problematic behaviors in the model.  We use the Wiki Labels
> system[1] to gather reviews of random samples of edits from Wikipedians in
> order to train the model.
>
> *Misclassification reports:*
> See
> https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service/Misclassifications/Edit_quality
>
> We're still working out the Right(TM) way to report false positives.
> Right now, we ask that you do so on-wiki and in the future, we'll be
> exploring a nicer interface so that you can report them while using the
> tool.  We review these misclassification reports manually to focus our work
> on the models and to report progress made.  This data is never directly
> used in training the machine learning models due to issues around bias.
>
> *Wiki labels campaigns:*
> In order to avoid the biases in who gets reviewed and why, we generate
> random samples of edits for review using our Wiki Labels[1] system.  We've
> completed a labeling campaign for English Wikipedia[2], but we could run an
> additional campaign to gather more data.  I'll get that set up and respond
> to this message when it is ready.
>
> 1. https://meta.wikimedia.org/wiki/Wiki_labels
> 2. https://en.wikipedia.org/wiki/Wikipedia:Labels/Edit_quality
>
> -Aaron
>
> On Tue, Aug 23, 2016 at 1:30 PM, Luis Villa <l...@lu.is> wrote:
>
>> Very cool! Is there any way for users of this tool to help train it? For
>> example, the first four things it flagged in my watchlist were all false
>> positives (next 5-6 were correctly flagged.) It'd be nice to be able to
>> contribute to training the model somehow when we see these false-positives.
>>
>> On Tue, Aug 23, 2016 at 11:10 AM Amir Ladsgroup <ladsgr...@gmail.com>
>> wrote:
>>
>>> We (The Revision Scoring Team
>>> <https://meta.wikimedia.org/wiki/Research:Revision_scoring_as_a_service#Team>)
>>> are happy to announce the deployment of the ORES
>>> <https://meta.wikimedia.org/wiki/ORES> review tool
>>> <https://www.mediawiki.org/wiki/ORES_review_tool> as a beta feature
>>> <https://en.wikipedia.org/wiki/Special:Preferences#mw-prefsection-betafeatures>
>>>  on *English Wikipedia*. Once enabled, ORES highlights edits that are
>>> likely to be damaging in Special:RecentChanges
>>> <https://en.wikipedia.org/wiki/Special:RecentChanges>, Special:Watchlist
>>> <https://en.wikipedia.org/wiki/Special:Watchlist> and
>>> Special:Contributions
>>> <https://en.wikipedia.org/wiki/Special:Contributions> to help you
>>> prioritize your patrolling work. ORES detects damaging edits using a
>>> basic prediction model based on past damage
>>> <https://meta.wikimedia.org/wiki/Research:Automated_classification_of_edit_quality>.
>>> ORES is an experimental technology. We encourage you to take advantage of
>>> it but also to be skeptical of the predictions made. It's a tool to support
>>> you – it can't replace you. Please reach out to us with your questions and
>>> concerns.
>>> Documentationmw:ORES review tool
>>> <https://www.mediawiki.org/wiki/ORES_review_tool>, mw:Extension:ORES
>>> <https://www.mediawiki.org/wiki/Extension:ORES>, and m:ORES
>>> <https://meta.wikimedia.org/wiki/ORES>Bugs & feature requests
>>> https://phabricator.wikimedia.org/tag/revision-scoring-as-a-service-backlog/
>>> IRC#wikimedia-aiconnect
>>> <http://webchat.freenode.net/?channels=#wikimedia-ai>
>>> Sincerely,Amir from the Revision Scoring team
>>> ___
>>> AI mailing list
>>> a...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/ai
>>>
>>
>> ___
>> AI mailing list
>> a...@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/ai
>>
>>
> ___
> AI mailing list
> a...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/ai
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [AI] Deployment of ORES review tool in Englis Wikipedia as a beta feature

[Luis Villa]

Very cool! Is there any way for users of this tool to help train it? For
example, the first four things it flagged in my watchlist were all false
positives (next 5-6 were correctly flagged.) It'd be nice to be able to
contribute to training the model somehow when we see these false-positives.

On Tue, Aug 23, 2016 at 11:10 AM Amir Ladsgroup  wrote:

> We (The Revision Scoring Team
> )
> are happy to announce the deployment of the ORES
>  review tool
>  as a beta feature
> 
>  on *English Wikipedia*. Once enabled, ORES highlights edits that are
> likely to be damaging in Special:RecentChanges
> , Special:Watchlist
>  and
> Special:Contributions
>  to help you
> prioritize your patrolling work. ORES detects damaging edits using a
> basic prediction model based on past damage
> .
> ORES is an experimental technology. We encourage you to take advantage of
> it but also to be skeptical of the predictions made. It's a tool to support
> you – it can't replace you. Please reach out to us with your questions and
> concerns.
> Documentationmw:ORES review tool
> , mw:Extension:ORES
> , and m:ORES
> Bugs & feature requests
> https://phabricator.wikimedia.org/tag/revision-scoring-as-a-service-backlog/
> IRC#wikimedia-aiconnect
> 
> Sincerely,Amir from the Revision Scoring team
> ___
> AI mailing list
> a...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/ai
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Medical leave

[Luis Villa]

Sorry to hear this; Frances, you're an under-appreciated buffer for many
people and processes at the Foundation. Take care of yourself, please.

Luis

On Tue, Feb 16, 2016 at 11:52 PM aude  wrote:

> On Wed, Feb 17, 2016 at 2:16 AM, Frances Hocutt 
> wrote:
>
> > Dear all,
> >
> > I’m writing to give a heads-up that I expect to be taking medical leave
> > from today through March 9, due in part to stress caused by the recent
> > uncertainty and organizational departures. In my absence, my work will be
> > in the capable hands of Ryan Kaldari and the rest of the Community Tech
> > team. Any questions you would have directed to me, direct to Ryan.
> >
>
> :(
>
> Please take care.  Look forward to see you around again in March.
> Hopefully the situations will improve soon / by then. (really needs to...)
>
> Cheers,
> Katie
>
>
> >
> > I hope to return as promptly as circumstance allows.
> >
> > All the best,
> > Frances
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
> --
> @wikidata
> ___
> 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

Re: [Wikitech-l] Image editor prototype

[Luis Villa]

On Tue, Dec 8, 2015 at 5:39 PM, Trevor Parscal <tpars...@wikimedia.org>
wrote:

> I think right now we are scratching the surface. We have some big ideas
> about everything from basic adjustments to full on derivative tracking
> and non-detailed destructive image editing.
>

Cool!


> While we are prototyping and proving the concept, it's all really going to
> come down to what features we can pull off easily and the community will
> benefit from and embrace the most.
>

Very reasonable prioritization :) Thanks!

Luis


-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Image editor prototype

[Luis Villa]

Very cool! 

Totally personal thing: a task I've done several times on-wiki is rotate an 
image by <90 degrees just to make it level (e.g., 1 
<https://commons.wikimedia.org/w/index.php?title=File%3ACoral_Gables_FL_Biltmore04.jpg=revision=138202095=130094742>,
 
2 
<https://commons.wikimedia.org/w/index.php?title=File:Biblioteca_malatestiana,_ingresso_03.JPG=prev=119816525>).
 
Any chance that is in the roadmap?

On Tue, Dec 8, 2015 at 1:08 PM, Mark Holmquist <mtrac...@member.fsf.org> 
wrote:

> Hi, all!
>
> I'm writing to share a prototype image editor that our very own Prateek 
> (prtksxna) has been working on. We're hoping to write an extension around 
> this and provide it on-wiki as a replacement for several bots and off-wiki 
> tools. It's only an experiment, but honestly, our upload pipeline lacks an 
> editing tool, which is *so* 2003. I'm looking towards getting this released 
> on Commons, as a BetaFeature™, within the next few months.
>
> Feedback can be shared here, on GitHub in the form of issues, on IRC in 
> #wikimedia-multimedia, or via private e-mail to myself or Prateek, if you 
> prefer.
>
> The code is here: https://github.com/prtksxna/ImageEditor
>
> You can try a demo here: http://prtksxna.github.io/ImageEditor/
>
> And finally, there's a sneak peek at the API documentation here:
> http://prtksxna.github.io/ImageEditor/docs/index.html
>
> Thanks for your eyeballs and time!
>
> -- 
> Mark Holmquist
> Lead Engineer, Multimedia
> Wikimedia Foundation
> mtrac...@member.fsf.org
> http://marktraceur.info
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share 
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Yandex?

[Luis Villa]

Sorry, fell back into lawyer mode - specifically, PII is "personally 
identifiable information" - in our case, usually IP addresses. A badly designed 
system could send that to the translation system, but we didn't do that - 
Yandex does not have access to it, so they know nothing about the editors who 
use the system. 


Sorry I was unclear, and thanks to the person who sent me a personal note 
asking for clarification! 
Luis







— Snt frm a dvice

On Tue, Nov 10, 2015 at 7:07 PM, Luis Villa <lvi...@wikimedia.org> wrote:

> I haven't been directly involved in a while, but we were certainly not
> paying Yandex last time I looked at the arrangement. Appropriate legal
> steps were also taken to protect the licensing of the content, and
> appropriate technical steps to protect PII of editors, among other things.
> FWIW-
> Luis
> On Tue, Nov 10, 2015 at 1:12 PM, C. Scott Ananian <canan...@wikimedia.org>
> wrote:
>> According to my listening of that Metrics meeting, it does seem like
>> WMF is going to have to pay Yandex for using its service.  But as you
>> say, that doesn't infect the actual translation text, which goes into
>> wikipedia and extends the free content available for everyone.
>>  --scott
>>
>> On Tue, Nov 10, 2015 at 3:31 PM, John Mark Vandenberg <jay...@gmail.com>
>> wrote:
>> > On Wed, Nov 11, 2015 at 5:47 AM, Legoktm <legoktm.wikipe...@gmail.com>
>> wrote:
>> >> On 07/02/2015 12:55 PM, Legoktm wrote:
>> >>> On 07/01/2015 06:50 PM, Ricordisamoa wrote:
>> >>>> Il 02/07/2015 03:28, Legoktm ha scritto:
>> >>>>> I noticed: "Yandex coming up soon!" under ContentTranslation. Are
>> there
>> >>>>> more details about what this means?
>> >>>>
>> >>>> https://phabricator.wikimedia.org/T89844 I think
>> >>>
>> >>> Thanks for the pointer. After some more digging, I found
>> >>> <
>> https://www.mediawiki.org/wiki/Thread:Talk:Content_translation/Specification/Yandex_backend
>> >.
>> >>>
>> >>> So it appears that ContentTranslation will be contacting a third-party,
>> >>> closed source service? Are users going to be informed that this is the
>> >>> case? What data is being sent?
>> >>>
>> >>
>> >> It appears[1] this has quietly gone ahead without any response here,
>> >> which is disappointing.
>> >>
>> >> [1]
>> >>
>> https://www.mediawiki.org/w/index.php?title=Content_translation/Documentation/FAQ=1935992=1780766
>> >
>> > As the user is isolated from the communication with Yandex , I don't
>> > see it as a huge problem.  Using Qualtrics seems to be a much more
>> > serious problem, and nobody seems to care about that.
>> >
>> > Yandex is sort of similar to a "MP4 upload only" support, only without
>> > the patent concerns.  Relying on it comes at the risk that the service
>> > stops, but the free content created is not infected.  More likely,
>> > Yandex will start asking WMF for money, and WMF decides to pay because
>> > it is 'easier' than terminating using the service.
>> >
>> > Anyway, I've added it to
>> >
>> > https://meta.wikimedia.org/wiki/Open_source
>> >
>> > --
>> > John Vandenberg
>> >
>> > ___
>> > 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
>>
> -- 
> Luis Villa
> Sr. Director of Community Engagement
> Wikimedia Foundation
> *Working towards a world in which every single human being can freely share
> in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Yandex?

[Luis Villa]

I haven't been directly involved in a while, but we were certainly not
paying Yandex last time I looked at the arrangement. Appropriate legal
steps were also taken to protect the licensing of the content, and
appropriate technical steps to protect PII of editors, among other things.

FWIW-
Luis

On Tue, Nov 10, 2015 at 1:12 PM, C. Scott Ananian <canan...@wikimedia.org>
wrote:

> According to my listening of that Metrics meeting, it does seem like
> WMF is going to have to pay Yandex for using its service.  But as you
> say, that doesn't infect the actual translation text, which goes into
> wikipedia and extends the free content available for everyone.
>  --scott
>
> On Tue, Nov 10, 2015 at 3:31 PM, John Mark Vandenberg <jay...@gmail.com>
> wrote:
> > On Wed, Nov 11, 2015 at 5:47 AM, Legoktm <legoktm.wikipe...@gmail.com>
> wrote:
> >> On 07/02/2015 12:55 PM, Legoktm wrote:
> >>> On 07/01/2015 06:50 PM, Ricordisamoa wrote:
> >>>> Il 02/07/2015 03:28, Legoktm ha scritto:
> >>>>> I noticed: "Yandex coming up soon!" under ContentTranslation. Are
> there
> >>>>> more details about what this means?
> >>>>
> >>>> https://phabricator.wikimedia.org/T89844 I think
> >>>
> >>> Thanks for the pointer. After some more digging, I found
> >>> <
> https://www.mediawiki.org/wiki/Thread:Talk:Content_translation/Specification/Yandex_backend
> >.
> >>>
> >>> So it appears that ContentTranslation will be contacting a third-party,
> >>> closed source service? Are users going to be informed that this is the
> >>> case? What data is being sent?
> >>>
> >>
> >> It appears[1] this has quietly gone ahead without any response here,
> >> which is disappointing.
> >>
> >> [1]
> >>
> https://www.mediawiki.org/w/index.php?title=Content_translation/Documentation/FAQ=1935992=1780766
> >
> > As the user is isolated from the communication with Yandex , I don't
> > see it as a huge problem.  Using Qualtrics seems to be a much more
> > serious problem, and nobody seems to care about that.
> >
> > Yandex is sort of similar to a "MP4 upload only" support, only without
> > the patent concerns.  Relying on it comes at the risk that the service
> > stops, but the free content created is not infected.  More likely,
> > Yandex will start asking WMF for money, and WMF decides to pay because
> > it is 'easier' than terminating using the service.
> >
> > Anyway, I've added it to
> >
> > https://meta.wikimedia.org/wiki/Open_source
> >
> > --
> > John Vandenberg
> >
> > ___
> > 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
>



-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Inhibitors for Mobile Content Service to use Parsoid output

[Luis Villa]

On Fri, Oct 16, 2015 at 11:14 AM, Bernd Sitzmann <be...@wikimedia.org>
wrote:

> It looks like Mobile Apps and Mobile Web have different priority
> > requirements from Parsoid here. Looking at
> > https://en.wikipedia.org/wiki/Wikipedia:Spoken_articles, I also see that
> > there are only 1243 spoken wikipedia articles (that are probably not all
> > the latest version of these articles). It also doesn't look like the
> video
> > player works currently in mobile web or in mobile apps (except maybe
> > Android ?).
>

With due respect for the hard work people have put in on that project, is
there any indication Spoken Articles has any traction and will grow beyond
that ~1K articles? Wouldn't using Android's TTS API to read the most
up-to-date version of the article be a much better user experience (35M
articles, always up-to-date, instead of 1K articles, almost always out of
date?)

Luis


-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Improving CAPTCHA friendliness for humans, and increasing CAPTCHA difficulty for bots

[Luis Villa]

Just for the record, this is not a matter for my talk page. I don't
encourage using my talk page either to circumvent existing prioritization
processes, or to try to resolve deeply complex CS questions. ;) Wikitech
(or perhaps Phabricator, depending on the team) is a much more appropriate
place than any one individual's talk page to try to adjust department or
team-level prioritization, especially when it is someone who isn't even in
that department.

Luis

On Wed, Aug 19, 2015 at 12:34 AM, Pine W wiki.p...@gmail.com wrote:

 Brian,

 Quite likely. (: But the Wikimedia CAPTCHA workboard suggests a lack of
 emphasis on improving the general CAPTCHA situation for Wikimedia. The two
 high priority tasks on that Phabricator workboard last received comments in
 May and June. Those dates, plus the relative quiet on this mailing list,
 suggest that there could be higher priority placed on CAPTCHA improvements.
 I will discuss this with Luis on his talk page.

 Thanks,
 Pine
 On Aug 18, 2015 11:43 PM, Brian Wolff bawo...@gmail.com wrote:

  On Tuesday, August 18, 2015, Pine W wiki.p...@gmail.com wrote:
   what's happening with regard to improving usability for humans and
   increasing the difficulty for bots?
 
  Generally speaking, isnt that an open problem in computer science?
 
  --
  Bawolff
  ___
  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




-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Tools for dealing with citations of withdrawn academic journal articles

[Luis Villa]

On Tue, Aug 18, 2015 at 4:50 PM, Tilman Bayer tba...@wikimedia.org wrote:

 On Tue, Aug 18, 2015 at 3:59 PM, Luis Villa lvi...@wikimedia.org wrote:
  On Tue, Aug 18, 2015 at 2:06 PM, Pine W wiki.p...@gmail.com wrote:
 
  Researching the possibility of migrating all mailing lists to a newer
  system sounds
  like a good project for Community Tech
 
 
  I've been pushing to keep the team focused on things that can show a
 direct
  impact on contribution/editing; this kind of sysadmin work really isn't
  that?[1] May be a worthwhile clarification to add to
  https://www.mediawiki.org/wiki/Community_Tech_team#Scope though.
 
  Luis
 
  [1] Though I do think that we should think about at least upgrading
  mailman, and potentially switching to Google Groups or (perhaps for some
  lists) to discourse.net.


To be clear, this was the very broad we, not CE/CommTech. :/


 https://phabricator.wikimedia.org/T52864 is the task for the Mailman
 upgrade btw (Upgrading to Version 3 will come, but it won't be soon
 and very very likely won't be this year).


Surprised the bug doesn't mention the multiple python versions it requires.
Some bizarre choices there.

Luis


-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Tools for dealing with citations of withdrawn academic journal articles

[Luis Villa]

On Tue, Aug 18, 2015 at 2:06 PM, Pine W wiki.p...@gmail.com wrote:

 Researching the possibility of migrating all mailing lists to a newer
 system sounds
 like a good project for Community Tech


I've been pushing to keep the team focused on things that can show a direct
impact on contribution/editing; this kind of sysadmin work really isn't
that?[1] May be a worthwhile clarification to add to
https://www.mediawiki.org/wiki/Community_Tech_team#Scope though.

Luis

[1] Though I do think that we should think about at least upgrading
mailman, and potentially switching to Google Groups or (perhaps for some
lists) to discourse.net.

-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Where to store OAuth application information?

[Luis Villa]

On Mon, Aug 10, 2015 at 11:43 PM, Pine W wiki.p...@gmail.com wrote:

 We currently have editable pages on Wikimedia sites with important legal
 strings, and AFAIK no one has caused a noteworthy incident by editing or
 vandalizing them.


There are several cases that I'm aware of where legally-significant text
was edited in legally-meaningful ways for varying lengths of time, ranging
from hours to (in some cases) months. Without going into details, for
example, one edit made us non-compliant with California law in a way that
had opened up other large websites to large fines. Thankfully none of them
have been used against us, that I know of, so perhaps locking them down
would be a case of premature optimization.

Luis

-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Data and Developer Hub protoype

[Luis Villa]

On Fri, Jun 26, 2015 at 5:53 AM, MZMcBride z...@mzmcbride.com wrote:

 I also find the argument that anyone cares about the appearance of
 documentation over its content a bit insulting.


I recommend reading [[Emotional Design
https://en.wikipedia.org/wiki/Emotional_Design]] and [[The Design of
Everyday Things
https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things]]. tl;dr:
appearance and design are extremely important to how people perceive and
interact with, well, just about everything.

Luis


-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Working towards a world in which every single human being can freely share
in the sum of all knowledge.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wikimedia-l] Types of allowed projects for grant funding (renamed)

[Luis Villa]

On Sun, Feb 22, 2015 at 12:24 PM, Pine W wiki.p...@gmail.com wrote:

 Hi Luis,

 Thank you for agreeing to consider grant funding for software projects.

 It sounds like you also plan a broader review of funding for community
 needs and growth.


Yes. The timeline is still somewhat up in the air, but soon - likely
sooner than Berlin.


 I have a list of requests for changes, which boil down to
 removing policy barriers and greatly improving communications and workflows
 so that community growth is fostered and volunteer time is used wisely.


I'd be interested to hear those, though probably on meta rather than here.


  I greatly appreciate
 your interest in supporting communities and contributor growth.


Thanks. Of course, the Foundation has long been active on those areas (we
spend millions of dollars a year doing them!) but I think we're always
interested in doing it better.

Luis


 Pine
 On Feb 21, 2015 6:12 PM, Luis Villa lvi...@wikimedia.org wrote:

  On Sat, Feb 21, 2015 at 5:39 PM, Erik Moeller e...@wikimedia.org
 wrote:
 
   Damon, Luis and members of their teams will need to weigh in on this,
   and will want to think through the implications for their respective
   areas, but it's a good conversation to have -- keeping in mind that
   Luis is just starting in his new role, so please give him at least a
   few days to get up to speed. ;-)
  
 
  Thanks for at least a few hours of cushion, Erik ;)
 
  I'm a big believer in the power of/need for software tools, and at least
  philosophically I'm very open to funding software development outside the
  Foundation (though obviously there are lots of pragmatic difficulties -
  code review, etc.) So, yes, as part of our broader review of how we
 support
  communities and contributor growth, CE will look at funding code very
  seriously.
 
  Luis
 
  --
  Luis Villa
  Sr. Director of Community Engagement
  Wikimedia Foundation
  *Imagine a world in which every single human being can freely share in
 the
  sum of all knowledge. That's our commitment.*
  ___
  Wikimedia-l mailing list, guidelines at:
  https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
  wikimedi...@lists.wikimedia.org
  Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
  mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe
 ___
 Wikitech-l mailing list
 Wikitech-l@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Luis Villa
Sr. Director of Community Engagement
Wikimedia Foundation
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. That's our commitment.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Thoughts: stateless services with open servers?

[Luis Villa]

On Tue, Jan 27, 2015 at 11:20 AM, Brion Vibber bvib...@wikimedia.org
wrote:

  ​Running Parsoid as a public service (with some soft-ish API limits)
 would
  allow us to support the oft-cited user who has a dumb PHP-only box and no
  means to install a node service, so that has my support;


 Yay!


  however, I worry
  that WMF might not be the best organisation to provide this if people
  wanted it at large for commercial use.
 

 Agreed... but if not us, then who?

 /me looks around at folks, wonders if anyone wants to commit to running
 such a service as a third-party that we could make super-easy for shared
 PHP-host users to use...


This is essentially the wordpress.com model for things like anti-spam and
analytics, right? Not that I'm saying they would do it, but clearly it's a
workable model at some scale.

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [WikimediaMobile] WikiGrok deployed

[Luis Villa]

This is terrific- congrats to everyone. I'm a little curious how/when this
is supposed to trigger- I went to a few pages with beta turned on and got
nothing. :/ Under what conditions *should* we be seeing it?

Luis

On Mon, Nov 3, 2014 at 3:52 PM, Tomasz Finc tf...@wikimedia.org wrote:

 Congrats Max and team. Eager to see how our users interact with this.

 On Mon, Nov 3, 2014 at 2:16 PM, Max Semenik maxsem.w...@gmail.com wrote:
  Hi, WikiGrok[0] has been successfully deployed to the English Wikipedia.
  Along with it a first campaign[1] was deployed. Now database is being
 slowly
  populated with suggestions:
 
  MariaDB [enwiki_p] select page_title, pp_value from page, page_props
 where
  pp_page=page_id and pp_propname='wikigrok_questions_v1' limit 100;
 
 +-+--+
  | page_title  | pp_value
  |
 
 +-+--+
  | Richard_Branson |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Tina_Fey|
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Jon_Stewart |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Bill_Maher  |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Jeff_Foxworthy  |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Evadne_Price|
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Dominic_Guard   |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Dilsa_Demirbag_Sten |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | J._Douglas_MacMillan|
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Carol_Bowman|
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Lianella_Carell |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | G._K._Reddy |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Liù_Bosisio |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
  | Matilde_Rodríguez_Cabo  |
 
 a:1:{s:6:author;a:2:{s:8:property;s:4:P106;s:9:questions;a:1:{s:7:Q482980;s:6:author;}}}
  |
 
 +-+--+
  14 rows in set (0.42 sec)
 
  Pages are getting updated when edited (null edit works, but not
  action=purge). According to estimations made with WikiData Query[2], the
  number of potentially affected pages is approximately 33,000. If really
  needed, we could whip up a script to null-edit these pages from server
 side
  in a controlled manner, but I would like to have more data on performance
  and memory consumption first.
 
  == Monitoring ==
  * Graphite: MediaWiki - WikiGrok
  * Exceptions from WikiData: type:mobile in Logstash.
 
  == Firefighting ==
  Most of potentially performance-scary/error causing code with can be
  disabled by commenting out $wgWikiGrokSlowCampaigns in
  wmf-config/mobile.php. If shit hits fan really hard, whole extension can
 be
  disabled through the usual means, with $wmgUseWikiGrok.
 
  == Next steps ==
  I'm working on DB storage for questions[3] which will allow us to avoid
  abusing page_props and give features such as find me pages that could
 use
  this type of fixes and find me a random page to fix.
 
 
  
  [0] https://www.mediawiki.org/wiki/Extension:WikiGrok
  [1] https://gerrit.wikimedia.org/r/#/c/170453/
  [2] http://wdq.wmflabs.org/
  [3] https://gerrit.wikimedia.org/r/170263
 
  --
  Best regards,
  Max Semenik ([[User:MaxSem]])
 
  ___
  Mobile-l mailing list
  mobil...@lists.wikimedia.org
  https://lists.wikimedia.org/mailman/listinfo/mobile-l
 

 ___
 Mobile-l mailing list
 mobil...@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/mobile-l




-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers

Re: [Wikitech-l] third-party icon sets

[Luis Villa]

On Wed, Sep 3, 2014 at 7:11 PM, Ricordisamoa ricordisa...@openmailbox.org
wrote:

 Are there policies/guidelines regarding the use of third-party icons in
 software maintained on WMF's Gerrit instance (e.g. MediaWiki extensions)?


I'm unaware of any formal policies, aside from a general requirement that
icons (like everything else hosted in git) be under an open license of some
sort. It certainly wouldn't hurt to have that written down somewhere.

(I note that there are no icons in the git repo itself, that I can find;
this does not excuse problematic licensing, but does make it slightly less
urgent to resolve.)


 For example, the Chameleon https://www.mediawiki.org/wiki/Skin:Chameleon
 skin appears to use Glyphicons http://glyphicons.com, whose license 
 http://glyphicons.com/license/ is not very clear.


The license looks fairly clear to me: png (free) version is under CC;
version included with bootstrap is MIT; other versions are non-free.

Has the author said things elsewhere to indicate that he(?) doesn't
understand the MIT terms, or somehow believes they aren't under MIT?

Assuming Chameleon uses the icons included with Bootstrap, this looks
fairly straightforward to me.

Even git.wikimedia.org https://git.wikimedia.org uses Glyphicons (the
 free PNG version) without complying with the CC-BY 3.0 license.


If we're using them on git.wikimedia.org, we should probably fix that. (I
see Chad says there is an upstream bug, but I can't find it for the life of
me, despite looking in three different places. gitblit doesn't strike me as
the most... organized project I've ever looked at.)


 Wouldn't it be better to use a really /free/ icon set (such as
 Font-Awesome https://fortawesome.github.io/Font-Awesome/ or Elusive
 Icons http://shoestrap.org/downloads/elusive-icons-webfont/) instead?


As discussed above, parts of Glyphicon are CC and/or MIT, which is really
free. There may be a discussion to be had around development models,
sustainability, community-friendliness, etc., and if you want to have that
discussion, by all means! But please don't confuse/complicate the
discussion by saying things under free licenses aren't really free - if
you're doing that, you're using the terms in a very different way from
common, long-term usage.

Hope that helps-
Luis

-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RFC to close: [[Requests for comment/Alternate disclosure policy]]

[Luis Villa]

Link for those who are looking for it:
https://www.mediawiki.org/wiki/Requests_for_comment/Alternate_disclosure_policy

On Fri, Jul 18, 2014 at 7:47 AM, Sébastien Santoro dereck...@espace-win.org
 wrote:

 So, I hereby request if Tim Starling, Brion Vibber or Mark Bergsma
 could close the discussion, and I also offers my services to be an
 appointed delegate with a mandate strictly limited to the closure of
 the RFC Alternate disclosure policy, so I could be allowed to close
 it. In the last case, I'll then implement it (by documenting on meta
 and creating an help page) immediately.


And to be clear, since someone raised this with me off-list, legal/LCA has
no objection to this. (I did raise a mild quibble on the talk page, but
like I said - a mild quibble.)

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] MediaWiki Bug Bounty Program

[Luis Villa]

On Thu, Jun 26, 2014 at 12:57 PM, MZMcBride z...@mzmcbride.com wrote:

 Jeremy Baron wrote:
 Maybe Max is unaware about
 https://wikitech.wikimedia.org/wiki/Volunteer_NDA

 Err, thanks for the link. As pointed out, that page is less than a week
 old and had not been advertised or linked from anywhere, as far as I can
 tell. I don't think there's a reasonable expectation that anybody would
 have known about it. I'm also not sure any volunteer is following that
 page... i.e., I'm not sure it's active or authoritative (yet?).


Yeah, it's not authoritative yet - we're still figuring out the kinks.

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] new terms of use/paid contributions - do they apply to mediawiki

[Luis Villa]

Hey, all-
Our opinion is that the terms of use applies to wikis, and not to non-wiki
activities like code contributions. That said, we can understand why this
would be confusing, so an opt-out that explicitly lists mediawki code
contributions (or even mediawiki as a whole) would be just fine with us.

Luis


On Mon, Jun 16, 2014 at 1:25 PM, Brian Wolff bawo...@gmail.com wrote:

 Hi,

 So from what I understand, there's now been an amendment to WMF's
 terms of use to require disclosure of paid contributions [1]. Its a
 little unclear how this applies to MediaWiki as a project, but a
 literal reading of the policy makes it seem like MediaWiki is
 included.

 * MediaWiki is arguably a project of the Wikimedia foundation. The
 foundation's website says as much [2]
 *A commit/patchset certainly seems like a contribution.

 Thus the new policy would require anyone submitting code to use to
 declare who they work for. Personally this seems both unnecessary to
 me, as well as unlikely to be followed. For example, I see no reason
 why some person who uses our software should have to declare who they
 work for when they upstream a bug fix, etc.

 I would suggest we follow commons' lead [3], and declare that we do
 not have disclosure requirements for people giving us code.

 --bawolff

 [1]
 https://wikimediafoundation.org/w/index.php?title=Terms_of_Usediff=0oldid=90463
 [2] https://wikimediafoundation.org/wiki/Our_projects
 [3]
 https://commons.wikimedia.org/wiki/Commons:Requests_for_comment/Alternative_paid_contribution_disclosure_policy

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




-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Legal links on dev websites [was Re: new terms of use/paid contributions - do they apply to mediawiki]

[Luis Villa]

On Mon, Jun 16, 2014 at 4:10 PM, Chad innocentkil...@gmail.com wrote:


  That gerrit.wikimedia.org doesn't seem to have any of the standard
  footnote
   links (including the privacy policy, which is perhaps a more significant
  oversight)...is that because of the interface?  One would think a custom
  skin could be developed that would permit inclusion of such links.
 

 One would think. Too bad it's basically impossible to skin Gerrit
 without hacking its core.


We're aware of this, but have held off handling it until the Phabricator
transition, so that we can handle in one place and also put one, more
appropriate policy in place, rather than different ones for different
projects.

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

*This message may be confidential or legally privileged. If you have
received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity. For more
on what this means, please see our legal disclaimer
https://meta.wikimedia.org/wiki/Wikimedia_Legal_Disclaimer.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Tell my favorite conference about your Wikimedia tech

[Luis Villa]

On Thu, Jun 12, 2014 at 9:56 PM, Roan Kattouw roan.katt...@gmail.com
wrote:

 On Jun 12, 2014 4:08 PM, Luis Villa lvi...@wikimedia.org wrote:
  I got a balloon ride the year I spoke. It was trumped the next year by a
  helicopter ride. Definitely an amazing trip.
 
 Wow, when was that?! I got no such thing :)

 In 2012 they did take all the speakers a show (and dinner) at a staged Gold
 Rush town (which is the *the* tourist attraction in Ballarat), in 2014 it
 was just a dinner at the local marina.


'05 for balloons over lovely Canberra, '06 for helicopters over Sydney
harbor. (I only went in '05, heard about '06 later.) Maybe they've toned it
down a little, but still a great conference!

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

Re: [Wikitech-l] Tell my favorite conference about your Wikimedia tech

[Luis Villa]

On Fri, Jun 13, 2014 at 7:07 AM, Tyler Romeo tylerro...@gmail.com wrote:

 I’ve always wanted to submit a cool MediaWiki talk to these conferences,
 but I have no idea what I’d talk about (or whether I’m even experienced
 enough to talk about anything at a conference).


The answer to that second part is yes :) LCA is not TED :) Background on
their speaker selection process and what makes for a good submission
(useful for any conference, not just LCA):
http://opensource.com/life/14/1/get-your-conference-talk-submission-accepted


 Are there any guidelines on what would make a good talk?


http://speaking.io/plan/an-idea/ ?

[All of speaking.io is useful.]

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

Re: [Wikitech-l] Tell my favorite conference about your Wikimedia tech

[Luis Villa]

On Thu, Jun 12, 2014 at 3:49 PM, Roan Kattouw roan.katt...@gmail.com
wrote:

 they treat speakers well,


I got a balloon ride the year I spoke. It was trumped the next year by a
helicopter ride. Definitely an amazing trip.

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

Re: [Wikitech-l] MediaWiki, Cookies and EU Privacy Policy 95/46/EG

[Luis Villa]

Note that the situation is different for Wikimedia projects than for
Mediawiki. Whether or not WMF LCA thinks it is necessary for the
Wikimedia-hosted services, it may still be a useful feature to build for
users of Mediawiki who believe that the rule should apply to them. So don't
let WMF doesn't think it needs to be deployed on WMF wikis stop anyone
from developing it for
Mediawiki-the-community-driven-widely-deployed-FLOSS-project.

Luis


On Tue, Mar 11, 2014 at 4:57 AM, Federico Leva (Nemo) nemow...@gmail.comwrote:

 This conversation would IMHO be more appropriate on mediawiki-l because it
 affects mainly third parties who care about the higher privacy standards of
 EU, but thanks for starting it.

 On asking WMF legals, no worries, they were already pointed to the
 possibility of an issue with 2009/136/EC / EU cookie law / revised
 ePrivacy Directive on Fri, 16 Aug 2013 11:18:32 +0200 (no reply received,
 but I was merely giving a pointer and not interested in following up).
 Some fines were levied just few days ago, as a quick search reveals: 
 http://www.bna.com/spanish-dpa-levies-n17179882151/.

 As for Wikimedia projects, relevant links are
 * stub https://meta.wikimedia.org/wiki/Cookie_jar
 * draft https://meta.wikimedia.org/wiki/Privacy_policy/FAQ#Can_
 you_give_me_some_examples_of_types_of_cookies_and_how_you_
 use_local_storage.3F
 * https://www.mediawiki.org/wiki/Requests_for_comment/
 Performance_standards_for_new_features#Scope_and_issues

 I believe most issues with cookies are currently/usually caused by some
 extensions which unconditionally add one or more. The biggest drive for
 their removal, so far, has been performance. Sometimes they are replaced
 with localStorage, which is better for performance, but I have no idea how
 better for privacy.

 Nemo


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




-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] .wiki gTLD

[Luis Villa]

On Thu, Feb 20, 2014 at 4:23 PM, Antoine Musso hashar+...@free.fr wrote:

 Le 20/02/2014 22:51, Brion Vibber a écrit :
  TLD proliferation is a scam by money-hungry registrars who want people to
  register (and thus pay) in multiple TLDs to protect their brands.
 
  I recommend we boycott/ignore these various things and just avoid them,
 but
  I know we're going to end up registering a bunch for the brand
 protection
  (racket).

 To the lawyers around there:

 Can a trademark owner sue the registrar directly? After all it sold a
 product (the domain) using your trademark.


Remember that wiki is not a WMF trademark :) But presumably if someone
registered something like pedia.wiki we'd have a variety of tools to have
to address the problem.

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Wmfall] Shahyar Ghobadpour joins Wikimedia Core features team as Software Engineer

[Luis Villa]

On Mon, Jan 6, 2014 at 4:36 PM, Shahyar Ghobadpour 
sghobadp...@wikimedia.org wrote:


 Lastly, I don't know what the poutine situation is in San Francisco.


I have seen only one place with poutine in the entire city, and it is
conveniently two and a half blocks from the office.

Luis (also, welcome!)


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New Bugzilla users have restricted accounts

[Luis Villa]

On Fri, Nov 8, 2013 at 6:52 AM, Andre Klapper aklap...@wikimedia.orgwrote:

 On Thu, 2013-11-07 at 08:28 -0800, Quim Gil wrote:
  In order to get somewhere with this discussion, it would be useful to
  know the current practice of other free software projects, using
  Bugzilla or not. As a newcomer, can I assign bugs to myself in GNOME,
  KDE, Ubuntu, Debian... etc?


It has been a while, but to my recollection, the answer is no.

Luis

-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Engineering] Roadmap updates - Sept 6th, 2013

[Luis Villa]

On Mon, Sep 16, 2013 at 10:55 AM, Erik Moeller e...@wikimedia.org wrote:

 On Sat, Sep 7, 2013 at 2:01 PM, Steven Walling swall...@wikimedia.org
 wrote:

  Weekly deployment plans/notes
  This monthly roadmap spreadsheet/wiki page
  Quarterly plans, as represented in
  https://www.mediawiki.org/wiki/Wikimedia_Engineering/2013-14_Goals and
 other
  places
  Yearly/annual plans
 
  This is too much.

 Agreed, let's rationalize this a bit. Part of the point of the Roadmap
 with monthly breakdowns was to create an overview where people can
 more easily anticipate e.g. architectural conversations and inter-team
 sync-ups that need to happen. It's not working for that, because it's
 not part of anyone's workflow.


For what it is worth, *reading* it is a part of my workflow. But it does
appear to this outsider that (based on the ebb and flow of updates) it
doesn't look like *updating* it is part of anyone's workflow.

Luis

-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMFs stance on non-GPL code

[Luis Villa]

On Wed, Aug 28, 2013 at 5:52 AM, Tim Starling tstarl...@wikimedia.orgwrote:

 On 27/08/13 03:12, C. Scott Ananian wrote:
  Stated more precisely: a non-GPL-compatible license for an extension
 means
  that the extension can never be distributed with core.

 That is incorrect, the GPL does not say that. The GPL allows verbatim
 copies of source code, with no restrictions on the license of any
 bundled or dynamically linked code. Only non-source forms (or
 binaries in v2) have more restrictive conditions. Since the
 MediaWiki core and extensions are distributed solely in source form,
 the non-source (binary) conditions do not apply.


Yup. In retrospect, an odd oversight for GPL v3; perhaps more
understandable for v2.

Luis

-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMFs stance on non-GPL code

[Luis Villa]

Just out of curiosity, what code are you using to do license parsing? If
you want seriously robust parsing, you might take a peek at
https://github.com/dmgerman/ninka

Luis


On Wed, Aug 28, 2013 at 1:36 PM, Ryan Kaldari rkald...@wikimedia.orgwrote:

 Just for fun, I added some license-parsing logic to Template:Extension on
 mediawiki.org. I think the job queue is still updating the categories, but
 so far we have:
 Extensions with no license specified: 596
 Extensions with an unknown license: 779
 GPL licensed extensions: 667
 MIT licensed extensions: 44
 BSD licensed extensions: 23
 AGPL licensed extensions: 10
 MPL licensed extensions: 1

 I was actually surprised to see how few MIT and BSD extensions we have
 considering how much animosity there is towards the GPL, but I suppose most
 people just want to match the licensing of MediaWiki.

 If you haven't specified the license of your extension, now would be a good
 time to do so :)

 Ryan Kaldari


 On Wed, Aug 28, 2013 at 9:10 AM, Luis Villa lvi...@wikimedia.org wrote:

  On Wed, Aug 28, 2013 at 5:52 AM, Tim Starling tstarl...@wikimedia.org
  wrote:
 
   On 27/08/13 03:12, C. Scott Ananian wrote:
Stated more precisely: a non-GPL-compatible license for an extension
   means
that the extension can never be distributed with core.
  
   That is incorrect, the GPL does not say that. The GPL allows verbatim
   copies of source code, with no restrictions on the license of any
   bundled or dynamically linked code. Only non-source forms (or
   binaries in v2) have more restrictive conditions. Since the
   MediaWiki core and extensions are distributed solely in source form,
   the non-source (binary) conditions do not apply.
  
 
  Yup. In retrospect, an odd oversight for GPL v3; perhaps more
  understandable for v2.
 
  Luis
 
  --
  Luis Villa
  Deputy General Counsel
  Wikimedia Foundation
  415.839.6885 ext. 6810
 
  NOTICE: *This message may be confidential or legally privileged. If you
  have received it by accident, please delete it and let us know about the
  mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
  reasons I cannot give legal advice to, or serve as a lawyer for,
 community
  members, volunteers, or staff members in their personal capacity.*
  ___
  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




-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMFs stance on non-GPL code

[Luis Villa]

On Wed, Aug 28, 2013 at 5:40 PM, K. Peachey p858sn...@gmail.com wrote:

 On Thu, Aug 29, 2013 at 6:41 AM, Luis Villa lvi...@wikimedia.org wrote:

  Just out of curiosity, what code are you using to do license parsing? If
  you want seriously robust parsing, you might take a peek at
  https://github.com/dmgerman/ninka
 
  Luis
 
  standard parser functions via the template

 {{lc:{{{license|}}} }}
 |gpl|gplv2|gplv2 or later|gpl v2|gpl v2 or later|gplv2+|gplv3|gpl v3 = GPL
 licensed extensions
 |agpl|agplv2|agplv3 = AGPL licensed extensions
 |mit|expat|expat (mit)|x11 = MIT licensed extensions
 |bsd|new bsd|revised bsd|modified bsd|freebsd = BSD licensed extensions
 |mpl|mplv2|mpl v2 = MPL licensed extensions
 |#default = Extensions with unknown license
 }}]]


Oh, the template, not the code itself. Makes sense; ignore lil 'ol me ;)

Luis


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




-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMFs stance on non-GPL code

[Luis Villa]

On Mon, Aug 26, 2013 at 10:12 AM, C. Scott Ananian
canan...@wikimedia.orgwrote:


 The idea that deployment of software on a server entails license
 obligations is a GPLv3 feature;


To be clear, that's AGPL-only, not GPL v3.

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Australia (was Re: conferences, Hacker School, Code for America)

[Luis Villa]

On Sat, Jul 6, 2013 at 11:45 PM, Roan Kattouw roan.katt...@gmail.comwrote:

 
 I went to (and presented at) linux.conf.au in 2012, and I had an
 awesome time. The quality of the talks and the number of high-quality
 talks is amazing. I highly recommend it.


Historically they also treat speakers *really* well. The year I spoke I got
a hot air balloon ride. ;)

Luis


-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Javascript + GPL [was Re: File Licensing Guidelines]

[Luis Villa]

My apologies for not weighing in earlier. I'm actually subscribed to
the list (no need to cc me) but have been extremely busy with... well,
among other things, hiring someone to free me up to do more things
like this. :)

On Wed, Apr 24, 2013 at 11:59 PM, David Gerard dger...@gmail.com wrote:

 On 25 April 2013 00:36, Tyler Romeo tylerro...@gmail.com wrote:
  On Wed, Apr 24, 2013 at 6:27 PM, Brian Wolff bawo...@gmail.com wrote:

  Says who? I do not believe this is a requirement. It perhaps would be nice,
  if done sanely, but not a requirement.

  Says the GPL. To be specific:


 I understand Luis was working on sane ways to do this in minified JS
 (and whether it is in fact required, or that counts as a compiled
 binary; though obviously it would be nice). So AIUI we're waiting on
 him.

Suffice to say that GPL was never designed or drafted with this use
case in mind, making all the usual disclaimers about the difficulty of
GPL interpretation even stronger. Frankly, I don't see much benefit to
spending list cycles arguing about the precise meaning.[1][2]

With that as background, I think it would be compatible with our
mission/culture, and with some interpretations of the license, to
provide licensing information (including links to relevant source
code) for any embedded third-party javascript as part of a default MW
install. If the solution for that also provides relevant information
on the non-minified-javascript parts of the source code base, that
would be a terrific side effect.

In a nutshell, there are two primary approaches to doing this (not
necessarily either-or):

* Add licensing information to About:Version or something similar.
Obviously some of this is already there (general GPL v2 license
statement) but having per-extension information, and in particular
ensuring that any extension with javascript has the necessary
metadata, would be useful. (I'm happy to help straighten out the
metadata for any extension where the licensing is unclear or messy.)

* Improve LibreJS so that it uses less obtrusive metadata, and then
work on Mediawiki to publish that metadata.

If someone on the list has interest *and time* to write code for
either/both of the above projects I'd be happy to talk to you about
the details, including introducing you to relevant other people
outside of Mediawiki where that makes sense.

Thanks-
Luis

[1] Relatedly: even if you disagree, and see a benefit in having a
discussion, I'm not going to engage in it. It isn't just a waste of
time unless it is paired with code; there are also people who'd love
to have a public statement so they can say see, WMF agrees with me,
and I'm not going to place myself (or WMF) in any such camp.

[2] The utter annoying-ness of having this discussion at all is
basically why jquery is now solely MIT-licensed, which is a loss for
the GPL community.

--
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about
the mistake. As an attorney for the Wikimedia Foundation, for
legal/ethical reasons I cannot give legal advice to, or serve as a
lawyer for, community members, volunteers, or staff members in their
personal capacity.

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

Re: [Wikitech-l] File Licensing Guidelines

[Luis Villa]

On Wed, Apr 24, 2013 at 2:46 PM, Matthew Walker mwal...@wikimedia.org wrote:
 At the risk of starting another huge bikeshed like [1] I feel like we need
 some good guidance on just how in the heck we are required to license
 extensions/images/source code files. With the help of Marktraceur we now
 have
 http://www.mediawiki.org/wiki/Manual:Coding_conventions#Source_File_Headers
 which is somewhat specific to PHP but could be generalized to JS, CSS, and
 SQL.

If I can find some time (more likely, intern time) would it be useful
to do something broader, like:

https://www.mozilla.org/MPL/headers/
https://www.mozilla.org/MPL/license-policy.html

?

No promises! But I can put it on the TODO list if people are interested.

 [1] http://lists.wikimedia.org/pipermail/wikitech-l/2013-March/067217.html

 But I have some additional questions... breaking this up into bits; my
 current thought matrix is that:

 == Extensions ==
 * Must have a LICENSE file in the root with the full text of the license for
 the extension,

Yes.

 and appended any additional licenses for libraries/resources
 they've pulled in
 ** How do we specify what license goes to what included component?

In practice, most people who are sophisticated enough to care about
this are also sophisticated enough to grep for the details. This is
probably why there is no consistent way to handle this.

That said, one convention for this that I like has been separate files
for each component:

LICENSE.component name

That file includes the component name, file/directory path the
component can be found in, any other relevant notes, and the full text
of the license.

Then the master LICENSE file mentions that there are components under
other licenses and details and full license texts in LICENSE.*.

In cases where there are many, many subcomponents, but only one or two
licenses, you can flip the convention - LICENSE.Apache would list all
Apache-licensed components + have the Apache text, etc.

Of course, any existing license information in the sub-component
should be preserved (assuming that it is a different license because
it came to us as a standalone third-party library/tool).

For those of you who want to dive very deeply into this issue, a good
read is 
https://www.softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html

 == PHP Files ==
 * For generic files, include a statement like
 http://www.mediawiki.org/wiki/Manual:Coding_conventions#Source_File_Headers
 * If it's the Extension.php file $wgExtensionCredits array should have the
 following items
 ** author
 ** version
 ** url
 ** license?
 ** If we include additional libraries, so we add another entry to the
 wgExtensionCredits array?

Can't speak enough to the details here to usefully comment, but happy
to discuss details. See also the other thread, where I (implicitly)
suggest that it might be a good idea for extension metadata to have a
pointer to a source download location.

 == Image Files ==
 Really shouldn't be licensed under GPLv2; but right now they implicitly are.
 Is there a way to explicitly identify image/binary content as being CC
 licensed? Do we just add a line to the license file about this?

In a dreamy ideal world, we all embed license metadata directly in our images!

In the meantime, yes - an explanation at the beginning of the LICENSE
file, probably with a separate LICENSE.images file with a detailed
explanation of what files are covered + the text of the license, is
probably the best way to go.

Hope that helps-
Luis


--
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about
the mistake. As an attorney for the Wikimedia Foundation, for
legal/ethical reasons I cannot give legal advice to, or serve as a
lawyer for, community members, volunteers, or staff members in their
personal capacity.

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

Re: [Wikitech-l] Countdown to SSL for all sessions?

[Luis Villa]

On Tue, Apr 30, 2013 at 10:27 AM, Petr Bena benap...@gmail.com wrote:
 SSL is requiring more CPU,

Not really.

In January this year (2010), Gmail switched to using HTTPS for
everything by default. Previously it had been introduced as an option,
but now all of our users use HTTPS to secure their email between their
browsers and Google, all the time. In order to do this we had to
deploy no additional machines and no special hardware. On our
production frontend machines, SSL/TLS accounts for less than 1% of the
CPU load, less than 10KB of memory per connection and less than 2% of
network overhead. Many people believe that SSL takes a lot of CPU time
and we hope the above numbers (public for the first time) will help to
dispel that.

http://www.imperialviolet.org/2010/06/25/overclocking-ssl.html

Luis



 both on server and client and disable all
 kinds of cache (such as squid or varnish), and some browsers may have
 problems with it OR in some countries encryption may be even illegal.

 Whatever you are going to do, you should let people turn it off.
 Wikimedia project itself has horrible security (in this thread I
 started some time ago -
 http://www.gossamer-threads.com/lists/wiki/wikitech/277357?do=post_view_threaded#277357
 I was even told that wikimedia doesn't need good security at all,
 because user accounts aren't so critical there), forcing SSL will not
 improve it much

 On Tue, Apr 30, 2013 at 6:30 AM, Paul Selitskas p.selits...@gmail.com wrote:
 On Tue, Apr 30, 2013 at 5:55 AM, Tyler Romeo tylerro...@gmail.com wrote:
 On Mon, Apr 29, 2013 at 9:07 PM, Paul Selitskas 
 p.selits...@gmail.comwrote:

 There are some situations when HTTPS won't work (for example, blocked
 by provider or government). How does one disable HTTPS without
 actually accessing a HTTPS version if the user is redirected from HTTP
 automatically?

 HTTPS was once blocked in Belarus, thus disabling access to above
 mentioned GMail, Facebook, Twitter and so on. There should be always
 an option (like ?noSecure=1).


 Well, with $wgSecureLogin the idea is that it is completely disallowed to
 log in, i.e., enter a password, over an insecure connection.


 Ah, I missed that moment. Thanks.

 --
 З павагай,
 Павел Селіцкас/Pavel Selitskas
 Wizardist @ Wikimedia projects

 ___
 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



--
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about
the mistake. As an attorney for the Wikimedia Foundation, for
legal/ethical reasons I cannot give legal advice to, or serve as a
lawyer for, community members, volunteers, or staff members in their
personal capacity.

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

Re: [Wikitech-l] Seemingly proprietary Javascript

[Luis Villa]

On Tue, Mar 5, 2013 at 10:10 AM, Caroline E Willis
cewillism...@gmail.comwrote:

 Is there a Counsel we can refer this to?


Yes. :) This was already on my radar, and I am following this discussion
(which has been useful; specifically, I did not know about the bug already
filed on the issue).

For those of you who don't know me, I'm new to the foundation, but have
been around foss and foss licensing for a while; a good backgrounder on me
is here:
http://www.mail-archive.com/wikimediaannounce-l@lists.wikimedia.org/msg00523.html

Luis


 On Mar 5, 2013 11:47 AM, Isarra Yos zhoris...@gmail.com wrote:

  The licensing information is on the page itself, of which the minified js
  winds up a part. For every file or other object that makes up the page to
  all contain the licensing information would be pretty unusual.
 
  It's like taking a file out of a page and then complaining that it has no
  licensing information when said information was in the page text right
  under it.
 
  On 05/03/13 17:36, Tyler Romeo wrote:
 
  On Tue, Mar 5, 2013 at 12:25 PM, Marc A. Pelletier m...@uberbox.org
  wrote:
 
  I think that determination needs to be made by Counsel, not on a guess.
 
I've quite some knowledge of copyright myself, and I know enough that
  the
  matter is subtle enough that this declaration is, at best, an
  oversimplification that cannot possibly reflect reality.
 
 
  Agreed, but even without legal training it's pretty clear this is a
  requirement. Quoting from CC-BY-SA:
 
   You must include a copy of, or the Uniform Resource Identifier for,
 this
 
  License with every copy or phonorecord of the Work You distribute,
  publicly
  display, publicly perform, or publicly digitally perform. [...] ou must
  keep intact all notices that refer to this License and to the disclaimer
  of
  warranties.
 
 
  And then in the GPL:
 
   b) The work must carry prominent notices stating that it is released
 
  under this License and any conditions added under section 7. This
  requirement modifies the requirement in section 4 to “keep intact all
  notices”.
 
 
  Later in the license it specifies that also binary forms of the work
 that
  are conveyed must also comply with these restrictions.
 
  --
  Tyler Romeo
  Stevens Institute of Technology, Class of 2015
  Major in Computer Science
  www.whizkidztech.com | tylerro...@gmail.com
  __**_
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/**mailman/listinfo/wikitech-l
 https://lists.wikimedia.org/mailman/listinfo/wikitech-l
 
 
 
  --
  -— Isarra
 
 
  __**_
  Wikitech-l mailing list
  Wikitech-l@lists.wikimedia.org
  https://lists.wikimedia.org/**mailman/listinfo/wikitech-l
 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




-- 
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810

NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Fwd: [Wmfall] Luis Villa joins WMF as Deputy General Counsel

[Luis Villa]

Hah... I think calling me a developer is, at this point, a bit of a
stretch, but I look forward to working with the tech team :)


On Tue, Feb 19, 2013 at 3:36 PM, Sumana Harihareswara suma...@wikimedia.org
 wrote:

 Luis is also a developer so I wanted you to hear about this. :-)

 -Sumana


  Original Message 
 Subject: [Wmfall] Luis Villa joins WMF as Deputy General Counsel
 Date: Tue, 19 Feb 2013 15:02:07 -0800
 From: Geoff Brigham gbrig...@wikimedia.org
 To: Staff All wmf...@lists.wikimedia.org

 *Hi everyone, *
 * *
 *I’m simply thrilled to welcome Luis Villa to the Foundation as our new
 Deputy General Counsel.*
 *
 Thanks to Kat Walsh, I met Luis during my first months at the Foundation.
  Kat loves Luis, and it is no wonder why.  In addition to being a superb
 lawyer, Luis is an open source developer, has worked with leaders in our
 Internet legal circles, and has a great personality that embraces our
 culture.*
 *
 His most recent adventure took place at the Palo Alto office of Greenberg
 Traurig, one of the top  global law firms.  There he worked with well-known
 Internet lawyers like Ian Ballon and Heather Meeker.   Luis focused on
 technology transactions, helping clients create solutions to licensing
 problems, with a particular emphasis on open source and software standards.
 His clients included Mozilla, the Open Compute Project, and a variety of
 clients large and small.  Luis successfully defended Google in the
 Oracle-Google/Android lawsuit, primarily working on the question of API
 copyrightability. I hired Luis as outside counsel to work on a tough legal
 matter for us, and his answers were on point, clear, and practical. *
 *
 Luis’ first contact with free software came was when he was in college at
 Duke University. There he studied political science and computer science,
 began using Linux, and helped triage Mozilla's bugzilla. A professor paid
 him to play with Lego, resulting in brief maintainership of the GPL’d LegOS
 operating system and co-authorship of the book Extreme Mindstorms. *
 *
 After graduation, Luis worked at Ximian, a Linux desktop startup, doing
 quality assurance and eventually managing the desktop team. As part of
 that, he got heavily involved in the GNOME desktop project, becoming
 bugmaster and then getting elected to the board of directors. After Ximian
 was acquired, Luis became geek in residence at Harvard Law School's
 Berkman Center. At Berkman, he translated from lawyer to geek, and managed,
 maintained, and developed several software projects.*
 *
 After Berkman, Luis started his legal ventures in life at Columbia Law
 School, where he was Editor in Chief of the Science and Technology Law
 Review, was awarded honors each year, and was co-recipient of the class
 prize for excellence in intellectual property scholarship. His thesis dealt
 with the use of software standards as part of antitrust enforcement.
 Outside of class, he participated in the GPL revision process, worked in
 the General Counsel's office at Red Hat, and developed a surprisingly
 strong attachment to New York City.*
 *
 After law school, Luis worked in the legal department at Mozilla, where his
 major project was revising the Mozilla Public License. The license got over
 a thousand words shorter, and gained stronger patent protections and
 compatibility with the Apache and GPL licenses. Luis also worked on
 privacy, contracts, standards bodies, and other issues.*
 *
 Outside of work, Luis is an invited expert to the World Wide Web
 Consortium's Patents and Standards Interest Group, and a board member and
 chair of the Licensing Committee at the Open Source Initiative. He also
 enjoys biking, photography, history, Duke basketball (men's and women's),
 and eating.*
 *
 Luis's first Wikipedia edit under his current user name dates to Feb. 2007.
 Like any good pedant, he has also been making minor spelling and grammar
 corrections anonymously for many years.*
 *
 So, as you can tell, we are extremely excited about having Luis on our team
 and wish him a warm welcome. *
 * *
 *Cheers, *
 * *
 *Geoff*

 --
 Geoff Brigham
 General Counsel
 Wikimedia Foundation


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