Welcome Željko :-) to the Wikimedia world! Great to have you onboard
to help improve our QA support.
On Tue, Oct 2, 2012 at 9:03 AM, Melanie Brown <mbrown(a)wikimedia.org> wrote:
> Welcome, Željko!
> On Tue, Oct 2, 2012 at 8:22 AM, Steven Walling <swalling(a)wikimedia.org>
>> On Oct 2, 2012 7:25 AM, "Chris McMahon" <cmcmahon(a)wikimedia.org> wrote:
>>> Hello everyone,
>>> I am pleased to announce that Željko Filipin joins WMF this week as QA
>>> Željko is is a world-class expert on browser test automation, software
>>> testing, and related systems and tools. He will be leading our browser test
>>> automation effort as well as doing other QA and testing work.
>>> Željko writes an authoritative blog about test automation, and is active
>>> (and highly visible) on Github and Stackoverflow. He hosted the Watir (Web
>>> Application Testing In Ruby) podcast for a long time, and is a long-standing
>>> member of the Watir Core Team.
>>> Željko lives with his family in Zagreb, Croatia, where he is a
>>> competitive table tennis player.
>>> I am particularly pleased, proud, and excited to make this announcement
>>> because Željko and I have been acquainted for many years. He and I were
>>> both early adopters of Watir, the first viable open source browser test
>>> automation tool in history. This is the first time we have worked together
>>> professionally, and I could not be happier that he is our new QA Engineer.
>>> Wmfall mailing list
>> Wmfall mailing list
> Melanie L. Brown
> HR Administrator
> Wikimedia Foundation
> 415.839.6885 ext 6690
> 415.882.0495 (fax)
> Imagine a world in which every single human being can freely share in the
> sum of all knowledge. That's our commitment. https://donate.wikimedia.org/
> Wmfall mailing list
Director of Engineering
Now that it's been a few months since this summer's Berlin hackathon,
I've closed up the survey and looked at whether we met the goals we'd
set. The answer: mostly. You can read our summary, TODO, and survey
You can also view the videos of almost all of the tutorials:
The video that hasn't made it onto Commons yet is the video of Roan &
Timo's Gadgets tutorial, but it is on Vimeo in the WMDE "Berlin
Hackathon 2012" album:
and we're trying to get it onto Commons.
Thanks again to WMDE, Nicole Ebber, Maria Roessler, Daniel Kinzler,
Rachel Farrand, Lydia Pintscher, and everyone who made this event possible.
Engineering Community Manager
I have just noticed that Jenkins lost its connection to Gerrit for 13
hours this monday. A job was locking the build queue waiting for Gerrit
to reply, I have killed it and Jenkins is now processing the backlog.
Antoine "hashar" Musso
> Message: 8
> Date: Wed, 23 May 2012 21:49:57 +0200
> From: Platonides <Platonides(a)gmail.com>
> To: wikitech-l(a)lists.wikimedia.org
> Subject: Re: [Wikitech-l] HTMLMultiSelectField as <select
> Message-ID: <jpjf1s$b23$1(a)dough.gmane.org>
> Content-Type: text/plain; charset=ISO-8859-1
> On 23/05/12 19:16, Daniel Werner wrote:
> > Right now I am implementing a new option (as part of
> > https://bugzilla.wikimedia.org/show_bug.cgi?id=36425) for which I'd
> > use a <select multiple="multiple"/> html element with options. Right now
> > MediaWiki always generates a list of selectboxes instead of that when
> > the HTMLMultiSelectField class. We are talking about 280+ selectable
> > here, so for now we came to the conclusion that a real multi <select/>
> > would be nicer and less space consuming for now
> > I have already managed to implement this multiple select,
> > modifying HTMLMultiSelectField adding a new option 'usecheckboxes' which
> > can be set to false to disable the known behavior and use a select
> > instead.
> > enabled, we could still do something nicer, for example with something
> > jQuery chosen plugin here.
> > My question would just be, how I should implement these changes
> > Is it ok with the new option for HTMLMultiSelectField or should this be
> > new class inheriting from HTMLMultiSelectField? I think
> > HTMLMultiSelectField sounds more like describing what I just implemented
> > rather than a bunch of select boxes, but of course renaming the existing
> > one could "break" extensions (even though both are fully compatible and
> > interchangeable). So one option would be simply naming the new one
> > HTMLMultiSelectField2 if we don't want to stick with an additional
> > here.
> No. You shouldn't need to know that HTMLMultiSelectField2 is a
> MultiSelect but HTMLMultiSelectField uses checkboxes.
> Your useCheckboxes looks good.
> I recommend you to make it a tri-state value, so you could force
> checkboxes, select or let it decide (eg. checkboxes for < 100 elements,
> select for more)
Alright, just submitted this for review to gerrit:
I implemented it as tri-state now. By default 'usecheckboxes' will be true,
not set to a number. This could be changed (would make sense imo) but for
now I didn't want to do this since it could for example affect the default
search namespace user preference in wikis with many search namespaces. I
think the plain multiple select HTML element is not that nice because it is
not very obvious that you can do multiple selects by holding the control
having JS enabled I think before using this as default for huge multiselect
options. I think if all of that were implemented, 15 or 20 would be a good
default value for the option.