Hi everyone,
There's been a minor change to how the Gerrit groups are setup. This
shouldn't really
affect that many people in practice, but I wanted to let everyone know.
In case you didn't already know, up until now Gerrit groups have been
self-managing--
this means they could add and remove users from their own groups. In
practice, not many
people actually did this, since we've been asking all access changes
to go through
MediaWiki.org[0] for documentation purposes.
I've just changed the owner of all groups (other than a handful of
sensitive ones that belong
to administrators & ops, plus the training group) to the "Project &
Group Creators" group[1].
I did this for 2 reasons:
1) These users need to be able to manage groups, since they're
creating them...since
some permissions tweaks I did last week, they've been unable to do
this (although I
don't think anyone noticed ;-)
2) To insure that access isn't getting granted without a paper trail.
This is more to
prevent accidents rather than malice. It's easy to mess up settings
in gerrit. That
and we can now be sure everyone goes through the same process :)
Again, almost nobody should be affected (unless you've been adding
users), but just
FYI.
-Chad
[0] https://gerrit.wikimedia.org/r/#/admin/groups/119,members
[1] https://www.mediawiki.org/wiki/Git/Gerrit_project_ownership
PS: If you are doing group creation/editing and you have any
questions, please let
me know.
Hey all.
As some of you may already know, I have a busy real-life period coming up
in the next two weeks. As such, I'm unable to write my regular Technology
Report [1] for the English Wikipedia-based (but cross-project) ''Signpost''
online newspaper. I know plenty of people on this list are familiar with
the report, so I wondered if we couldn't crowdsource the effort in a
totally commitment-free way.
Specifically, I've put some skeleton notes up at [2] (this week's report) -
so if you're interested and even moderately familiar with the house style
(or capable of reading a couple of reports to deduce it), please please
please flesh out one of the sections (it needn't take long: the In briefs
only take 10 minutes each, I find). Or if you know something interesting
that's happening that fits the Wikimedia/MediaWiki+Technology+News
criterion for inclusion, please do add it. (Do remember to add plenty of
context though.)
It would be a shame to miss a report that's read every week by 800 to 1000
people across the globe. Oh, and it's one of the few times you get to put
your name at the top on an article :)
Thanks,
Harry (User:Jarry1250)
[1] e.g. last week's
https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-06-04/Techn…
[2]
https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2012-06-11/Techn…
Hi all,
Thanks to everyone who contributed user stories about ways that would
like to see OAuth incorporated into MediaWiki!
A few of us here at WMF have looked at the stories, and I've distilled
them down to some general statements about what it seems like the
community wants from the project here:
http://www.mediawiki.org/wiki/OAuth/User_stories#Requirements
Please continue to add to the user stories if you have ideas about how
you would like to use OAuth in MediaWiki.
Next steps will be to prioritize the features, and hopefully start
code sprints starting in early July.
Thanks!
Chris
On Thu, Jun 7, 2012 at 8:30 AM, John W. Foster <jfoster81747(a)verizon.net> wrote:
>> So now I'm asking you guys. Any interest?
>
> Interested yes...but I use the Debian stable to run my servers, and have
> adopted the process of using the tarballs myself as there is absolutely
> no reason to use a "debianized version". That being said if you want to
> increase the user base then by all means allow the 'debian developers'
> to repackage the tarballs as they see fit. I see no reason to do
> otherwise. I do suggest setting up a website to manage this separate
> from any of the mediawiki sites complete with all the tools to manage
> the software source code and the process of distribution. I would gladly
> assist in this.
Moving the distribution of MediaWiki off of mediawiki.org will just
fork the efforts in the long run, imho. I think we can accomplish the
goal of packaging without creating a new site.
-Chad
I'm having trouble getting a simple one-line User JS working on Wiktionary.
$('#p-navigation').removeClass('first persistent').addClass('collapsed');
It works fine from Google Chrome's dev console. It makes the
navigation portal collapsible like the other portals in the sidebar.
But when I add it to my User:XXX/vector.js the result is not the same.
The class I add is there but the ones I remove are also still there
and the result is the standard navigation portal.
I suspect there is some other js executed after the user's vector.js
but I'm not sure how to check that.
I have tried setting a breakpoint on the node in Google Chrome's dev
tools and reloading the page, but it is never triggered.
Apologies if this is not the right mailing list. None of the lists
seemed fit according to http://www.mediawiki.org/wiki/Mailing_lists
Andrew Dunbar (hippietrail)
We now have three mirror sites, yay! The full list is linked to from
http://dumps.wikimedia.org/ and is also available at
http://meta.wikimedia.org/wiki/Mirroring_Wikimedia_project_XML_dumps#Curren…
Summarizing, we have:
C3L (Brazil) with the last 5 good known dumps,
Masaryk University (Czech Republic) with the last 5 known good dumps,
Your.org (USA) with the complete archive of dumps, and
for the latest version of uploaded media, Your.org with http/ftp/rsync
access.
Thanks to Carlos, Kevin and Yenya respectively at the above sites for
volunteering space, time and effort to make this happen.
As people noticed earlier, a series of media tarballs per-project
(excluding commons) is being generated. As soon as the first run of
these is complete we'll announce its location and start generating them
on a semi-regular basis.
As we've been getting the bugs out of the mirroring setup, it is getting
easier to add new locations. Know anyone interested? Please let us
know; we would love to have them.
Ariel
But both my page and the Wikipedia page both have only the site logo, and 'powered by' footer icons.
How does Facebook know not to mistakenly show a 'powered by' icon for Wikipedia but not my site?
Unfair!
Welcome aboard, Munaf!
I look forward to working with you soon,
Fabrice
__________________________________
Fabrice Florin
Product Manager,
Editor Engagement
Wikimedia Foundation
+1 (415) 839-6885 ext. 6827 work
+1 (415) 860-6484 mobile
fflorin(a)wikimedia.org
We help engage editors on Wikipedia:
https://en.wikipedia.org/wiki/Wikipedia:Editor_Engagement
On Jun 4, 2012, at 11:03 PM, wikitech-l-request(a)lists.wikimedia.org wrote:
> From: Steven Walling <steven.walling(a)gmail.com>
> Subject: Re: [Wikitech-l] Welcoming Munaf Assaf, UX Designer
> Date: June 4, 2012 4:43:52 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Cc: Munaf Assaf <massaf(a)wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> On Mon, Jun 4, 2012 at 3:40 PM, Howie Fung <hfung(a)wikimedia.org> wrote:
>
>> Everyone,
>>
>> I’m pleased to welcome Munaf Assaf, a new member of the Product Group.
>> Munaf is starting today as UX Designer and will work mainly on the
>> Editor Engagement Experiments projects. Almost all of these projects
>> have a user-facing component, and Munaf will help us design interfaces
>> to make these experiments and features more user-friendly.
>>
>> Munaf joins us from the University of Michigan (UM), where he worked
>> as a Research Associate in the Office of Enabling Technologies. At UM,
>> he worked on a variety of projects, including mobile informatics
>> applications and engagement tools for visiting hospital patients. His
>> most recent project was the design of a high-tech collaboration space
>> in conjunction with the Taubman School of Architecture. Earlier in his
>> career, Munaf was an Algorithm Design Engineer at General Motors,
>> where he worked on control systems for improving vehicle fuel
>> efficiency.
>>
>> He has a BS in Electrical Engineering from Kettering University, as
>> well as an MSI in Human-Computer Interaction from the University of
>> Michigan at Ann Arbor. For more information on his background, please
>> see his public profile [1].
>>
>> Please join me in welcoming Munaf!
>>
>> Howie
>>
>> [1] http://www.linkedin.com/in/munafassaf
>>
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>
> Welcome Munaf! Glad to have you on the team. :)
>
> Steven
>
>
>
>
> From: John Du Hart <compwhizii(a)gmail.com>
> Subject: Re: [Wikitech-l] Facebook grabs the Mediawiki logo instead of the site logo
> Date: June 4, 2012 4:47:55 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> Yeah I remember that.
> On Jun 4, 2012 7:45 PM, "Chad" <innocentkiller(a)gmail.com> wrote:
>
>> On Mon, Jun 4, 2012 at 7:35 PM, <jidanni(a)jidanni.org> wrote:
>>> Here Facebook grabs the Mediawiki logo instead of the site logo.
>>>
>>>
>> http://www.facebook.com/groups/tg.taiwan/permalink/374509135949001/?comment…
>>>
>>> Doing the same experiment with e.g.,
>>> http://en.wikipedia.org/wiki/1st_clan_chief ,
>>> a page also without any user embedded images,
>>> oddly does not cause the mediawiki logo to be chosen.
>>>
>>> Though it does not choose the site logo, at least it doesn't choose the
>>> mediawiki logo.
>>>
>>
>> Didn't we discuss this almost a year ago?
>>
>> Indeed, we did:
>> http://lists.wikimedia.org/pipermail/mediawiki-l/2011-July/037710.html
>>
>> -Chad
>>
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>
>
>
>
> From: Nasir Khan <nasir8891(a)gmail.com>
> Subject: Re: [Wikitech-l] Welcoming Munaf Assaf, UX Designer
> Date: June 4, 2012 6:29:54 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> Congrats :)
> On Jun 5, 2012 5:44 AM, "Steven Walling" <steven.walling(a)gmail.com> wrote:
>
>> On Mon, Jun 4, 2012 at 3:40 PM, Howie Fung <hfung(a)wikimedia.org> wrote:
>>
>>> Everyone,
>>>
>>> I’m pleased to welcome Munaf Assaf, a new member of the Product Group.
>>> Munaf is starting today as UX Designer and will work mainly on the
>>> Editor Engagement Experiments projects. Almost all of these projects
>>> have a user-facing component, and Munaf will help us design interfaces
>>> to make these experiments and features more user-friendly.
>>>
>>> Munaf joins us from the University of Michigan (UM), where he worked
>>> as a Research Associate in the Office of Enabling Technologies. At UM,
>>> he worked on a variety of projects, including mobile informatics
>>> applications and engagement tools for visiting hospital patients. His
>>> most recent project was the design of a high-tech collaboration space
>>> in conjunction with the Taubman School of Architecture. Earlier in his
>>> career, Munaf was an Algorithm Design Engineer at General Motors,
>>> where he worked on control systems for improving vehicle fuel
>>> efficiency.
>>>
>>> He has a BS in Electrical Engineering from Kettering University, as
>>> well as an MSI in Human-Computer Interaction from the University of
>>> Michigan at Ann Arbor. For more information on his background, please
>>> see his public profile [1].
>>>
>>> Please join me in welcoming Munaf!
>>>
>>> Howie
>>>
>>> [1] http://www.linkedin.com/in/munafassaf
>>>
>>> _______________________________________________
>>> Wikitech-l mailing list
>>> Wikitech-l(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>>
>>
>> Welcome Munaf! Glad to have you on the team. :)
>>
>> Steven
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>
>
>
>
> From: Ori Livneh <ori.livneh(a)gmail.com>
> Subject: Re: [Wikitech-l] Welcoming Munaf Assaf, UX Designer
> Date: June 4, 2012 10:04:41 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> On Mon, Jun 4, 2012 at 3:40 PM, Howie Fung <hfung(a)wikimedia.org> wrote:
>
>>
>> Please join me in welcoming Munaf!
>>
>>
> Hi Munaf! Glad you're here.
>
>
>
>
> From: Ori Livneh <ori.livneh(a)gmail.com>
> Subject: Re: [Wikitech-l] Give create gerrit repo right to all WMF engineers
> Date: June 4, 2012 10:50:50 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> On Fri, Jun 1, 2012 at 8:41 AM, Chad <innocentkiller(a)gmail.com> wrote:
>
>>
>> So yeah, its not as easy as it sounds on the tin, so I don't want to hand
>> this out en masse. In an ideal world, I want us to have a special page
>> where people can request repos and we can automate the icky backend stuff.
>>
>
> If it isn't easy, let's make it easy. I'm a new developer and not having a
> repository to develop in has been absolutely paralyzing. (I requested one
> on May 23, for what it's worth).
>
> Gerrit is not just an SCM: there is a rapidly growing ecosystem of services
> that integrate with it -- and if your code isn't there, you're persona non
> grata. I've whipped up two iterations of a data collection backend for my
> team and got it set up on a labs instance, but that was a week ago, and
> since then things are at a standstill. It's been hard to get anyone to look
> at it, because everyone's workflow and attentional habits are interwoven
> with Gerrit now.
>
> This particular side-project is a useful illustration of another important
> point: Git's usefulness isn't limited to managing mature projects like
> Mediawiki -- it has a crucial role to play in the earliest stages of
> development, too. I have no idea if what I wrote is usable and scalable,
> and it would've been good to get some feedback early. In the past, I have
> found it useful and productive to whip up quick prototypes and put them up
> on GitHub for feedback, instead of trading in inchoate ideas, or sitting on
> them until the ideas feel mature (which *never* happens for me until I sit
> down and start writing code). The ideas that stick get developed into
> full-fledged products. Using Git in this way has been such a tremendous
> boon for me as a developer, and not having that has been really frustrating.
>
> I don't think expanding git-creation rights to a few more individuals goes
> far enough, because the point at which you need a repository is antecedent
> to the point in time at which you feel comfortable describing your work to
> someone. For cool projects to happen, people need to feel empowered to
> start repos for projects that seem speculative and maybe even a little
> silly, and that won't happen when you make it necessary to ask for
> permission.
>
> At this point I expect someone to come along and point out that you don't
> need Gerrit to start a Git repository -- "git init" will suffice. And
> that's true, as long as you don't need to collaborate with anyone, or
> develop on more than one machine (say rsync & I'll bop you on the head!),
> or have stable urls to share with people.
>
>
>
>
> From: Jeremy Baron <jeremy(a)tuxmachine.com>
> Subject: Re: [Wikitech-l] Give create gerrit repo right to all WMF engineers
> Date: June 4, 2012 11:00:49 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> On Tue, Jun 5, 2012 at 1:50 AM, Ori Livneh <ori.livneh(a)gmail.com> wrote:
>> If it isn't easy, let's make it easy. I'm a new developer and not having a
>> repository to develop in has been absolutely paralyzing. (I requested one
>> on May 23, for what it's worth).
>>
>> Gerrit is not just an SCM: there is a rapidly growing ecosystem of services
>> that integrate with it -- and if your code isn't there, you're persona non
>> grata. I've whipped up two iterations of a data collection backend for my
>> team and got it set up on a labs instance, but that was a week ago, and
>> since then things are at a standstill. It's been hard to get anyone to look
>> at it, because everyone's workflow and attentional habits are interwoven
>> with Gerrit now.
>>
>> This particular side-project is a useful illustration of another important
>> point: Git's usefulness isn't limited to managing mature projects like
>> Mediawiki -- it has a crucial role to play in the earliest stages of
>> development, too. I have no idea if what I wrote is usable and scalable,
>> and it would've been good to get some feedback early. In the past, I have
>> found it useful and productive to whip up quick prototypes and put them up
>> on GitHub for feedback, instead of trading in inchoate ideas, or sitting on
>> them until the ideas feel mature (which *never* happens for me until I sit
>> down and start writing code). The ideas that stick get developed into
>> full-fledged products. Using Git in this way has been such a tremendous
>> boon for me as a developer, and not having that has been really frustrating.
>>
>> I don't think expanding git-creation rights to a few more individuals goes
>> far enough, because the point at which you need a repository is antecedent
>> to the point in time at which you feel comfortable describing your work to
>> someone. For cool projects to happen, people need to feel empowered to
>> start repos for projects that seem speculative and maybe even a little
>> silly, and that won't happen when you make it necessary to ask for
>> permission.
>>
>> At this point I expect someone to come along and point out that you don't
>> need Gerrit to start a Git repository -- "git init" will suffice. And
>> that's true, as long as you don't need to collaborate with anyone, or
>> develop on more than one machine (say rsync & I'll bop you on the head!),
>> or have stable urls to share with people.
>
> I mostly agree with what you've said.
>
> Just wanted to point out gerrit projects (aka repos) can never be
> destroyed. so if you e.g. typo or rename a project or kill it 5 days
> after you started it's still there forever. Only very recently have we
> even been able to hide projects from project listings in the UI.
>
> -Jeremy
>
>
>
>
>
> From: Ori Livneh <ori.livneh(a)gmail.com>
> Subject: Re: [Wikitech-l] Give create gerrit repo right to all WMF engineers
> Date: June 4, 2012 11:13:24 PM PDT
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> On Mon, Jun 4, 2012 at 11:00 PM, Jeremy Baron <jeremy(a)tuxmachine.com> wrote:
>>
>> I mostly agree with what you've said.
>>
>> Just wanted to point out gerrit projects (aka repos) can never be
>> destroyed. so if you e.g. typo or rename a project or kill it 5 days
>> after you started it's still there forever. Only very recently have we
>> even been able to hide projects from project listings in the UI.
>>
>
> Isn't the same basically true of Wiki articles? I understand the desire to
> keep things tidy, okay. But what would be the big deal about having ten or
> even a hundred thousand abandoned repositories, so long as they are hidden,
> and do not clutter the UI? The repositories that would be candidates for
> deletion are the ones that got no further than an initial stab, and those
> measure in kilobytes.
>
>
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Similar to last month's event with the Weekend Testing group, this Saturday
WMF is teaming with Openhatch.org for a "test event" to get critical
eyeballs on the near-final version of the Article Feedback Tool before AFT
gets rolled out to a wide audience in the very near future.
Like last time, we anticipate some Bugzilla issues being created for AFT on
Saturday.
The test session is from 10AM-noon Pacific time.
The openhatch announcement is:
https://openhatch.org/blog/2012/june-9-help-wikipedia-test-some-software-an…
The test plan for the event is:
http://www.mediawiki.org/wiki/QA/Article_Feedback_Test_Plan