[CC'ing wikitech-l@ again]
On Thu, 2013-01-24 at 10:50 -0700, Chris McMahon wrote:
> On Thu, Jan 24, 2013 at 10:30 AM, Andre Klapper
> <aklapper(a)wikimedia.org> wrote:
> 1) Bugzilla already has a number of keywords such as
> * need-integration-test (Selenium test should be written for
> this.)
>
>
> I didn't know this existed, and a quick look makes me think it will
> take some gardening to cull actual potential browser tests, but it
> might be a worthwhile exercise.
>
> I'm not totally convinced by these two yet, as both need
> buy-in
> (developers and reporters need to know and remember that QA
> works on
> automated browser tests, and should mark issues accordingly),
> but
> nothing better came to my mind in the last days. :-/
>
> Thanks. I'm not certain either, and I'm still thinking...
Right after clicking the "Send" button a 3rd option came to my mind,
remembering all the Mozilla bugmail that I receive.
Mozilla uses a Bugzilla flag called "in-litmus". It's explained here:
https://quality.mozilla.org/docs/qmo-community/lesson-plans/investigating-i…
In short,
* in-litmus? indicates the bug is nominated for a testcase
* in-litmus+ indicates the bug has a testcase
* in-litmus- indicates the bug does not need a testcase
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
The MediaWiki captcha is literally worse than useless: it doesn't keep
spambots out, and it does keep some humans out.
(I was just reminded of this by a friend I lured into joining
Wikivoyage - who can see and is highly literate, but found the captcha
really troublesome.)
Why are we still using this?
- d.
Hi, next week I will have a casual chat with Siko about the new
Wikimedia Individual Engagement Grants and how MediaWiki contributors
could theoretically benefit from them.
If you have specific questions or feedback there is nothing stopping you
from contact her directly, but maybe it's more useful to start sharing
here. This way I can go with more consolidated questions and feedback.
-------- Original Message --------
Subject: [Wikimedia-l] [Wikimedia Announcements] Announcing the
Individual Engagement Grants program
Date: Tue, 15 Jan 2013 18:03:42 -0800
From: Siko Bouterse <sbouterse(a)wikimedia.org>
Reply-To: wikimedia-l(a)lists.wikimedia.org
To: wikimediaannounce-l(a)lists.wikimedia.org
*Hi all,
Im pleased to announce the launch of a new grantmaking program at the
Wikimedia Foundation: Individual Engagement Grants. These grants will
support Wikimedians as individuals or small teams to complete projects that
benefit the Wikimedia movement, lead to online impact, and serve the
mission, community, and strategic priorities. This new program is intended
to complement WMFs other grantmaking programs as well as the grants that
chapters and affiliate organizations provide.
The first round of proposals will be accepted from now until 15 February
2013. Were also seeking committee members to help select the first round
of grantees. Please help spread the word to other lists!
To get involved, share your thoughts, submit a proposal, or join the
committee:
https://meta.wikimedia.org/wiki/Grants:IEG
For more information on all of WMFs grantmaking programs:
https://meta.wikimedia.org/wiki/Grants:Start
Best wishes,*
Siko
--
Siko Bouterse
Head of Individual Engagement Grants
Wikimedia Foundation, Inc.
sbouterse(a)wikimedia.org
*Imagine a world in which every single human being can freely share in the
sum of all knowledge. *
*Donate <https://donate.wikimedia.org> or click the "edit" button today,
and help us make it a reality!*
Hey,
I have observed a difference in opinion between two groups of people on
gerrit, which unfortunately is causing bad blood on both sides. I'm
therefore interested in hearing your opinion about the following scenario:
Someone makes a sound commit. The commit has a clear commit message, though
there is a single typo in it. Is it helpful to -1 the commit because of the
typo?
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
I'd like to use html comment into raw wiki text, to use them as effective,
server-unexpensive "data containers" that could be read and parsed by a js
script in view mode. But I see that html comment, written into raw wiki
text, are stripped away by parsing routines. I can access to raw code of
current page in view mode by js with a index.php or an api.php call, and I
do, but this is much more server-expensive IMHO.
Is there any sound reason to strip html comments away? If there is no sound
reason, could such a stripping be avoided?
Alex brollo
I'd like to notify you that thanks to the generosity and cooperation if
the previous owner, wikimania.org and wikimania.com are now owned by
Wikimedia CH.
The domain is currently set up in the same way as it was before but we
have now the possibility tu use ssl.wikimania.org for the registrations
and scholarship tools already hosted by Wikimedia CH.
Regards,
Manuel
--
Wikimedia CH - Verein zur Förderung Freien Wissens
Lausanne, +41 (21) 34066-22 - www.wikimedia.ch
There is a Firefox extension to get past the captchas...
---------- Forwarded message ----------
From: Graham Pearce <grahamwp(a)jazi.net>
Date: Wed, Jan 23, 2013 at 5:41 PM
Subject: Re: Fwd: [Wikitech-l] Why are we still using captchas on WMF sites?
To: John Vandenberg <jayvdb(a)gmail.com>
Yes, I have. There isn't an essay about it as such, but in this edit to the help
page about using JAWS:
http://en.wikipedia.org/w/index.php?title=Wikipedia:Using_JAWS&diff=3201666…
I offered to help people use WebVisum, a Firefox extension to get past
the captchas:
http://webvisum.com
It's an invite-only system. Nobody took up my offer, but I notice now
that there's a page to request invitations:
http://www.webvisum.com/en/main/invitationrequest
So maybe it's not so necessary ...
Feel free to pass this reply on to whoever you like.
Graham
On 23/01/2013 12:07 PM, John Vandenberg wrote:
>
> Have you heard about this?
>
> is there a wiki essay about this accessibility problem?
>
>
> ---------- Forwarded message ----------
> From: Chris Grant <chrisgrantmail(a)gmail.com>
> Date: Wed, Jan 23, 2013 at 2:33 PM
> Subject: Re: [Wikitech-l] Why are we still using captchas on WMF sites?
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>
>
> On Wed, Jan 23, 2013 at 3:53 AM, Bawolff Bawolff <bawolff(a)gmail.com> wrote:
>>
>> Someone should write a browser addon to automatically decode and fill in
>> captchas for blind users. (Only half joking)
>
> Don't joke, I have a blind relative who's screen reader does just that
> (simple captchas only).
>
> There are other services like http://www.azavia.com/zcaptcha which is
> specifically for the blind, but hell its probably cheaper to use the same
> captcha reading services that the spammers do.
>
> -- Chris
>
> On Wed, Jan 23, 2013 at 3:53 AM, Bawolff Bawolff <bawolff(a)gmail.com> wrote:
>
>> On 2013-01-22 3:30 PM, "aude" <aude.wiki(a)gmail.com> wrote:
>>>
>>> On Tue, Jan 22, 2013 at 8:18 PM, Luke Welling WMF <
>>
>> lwelling(a)wikimedia.org
>>>
>>> wrote:
>>>
>>>> That was not the end of the problem I was referring to. We know our
>>>> specific captcha is broken at turning away machines. As far as I am
>>
>> aware
>>>>
>>>> we do not know how many humans are being turned away by the difficulty
>>
>> of
>>>>
>>>> it.
>>>
>>>
>>> It's at least impossible for blind users to solve the captcha, without an
>>> audio captcha. (unless they manage to find the toolserver account
>>
>> creation
>>>
>>> thing and enough motivated to do that)
>>>
>>> I am not convinced of the benefits of captcha versus other spam filtering
>>> techniques.
>>>
>>> Cheers,
>>> Katie
>>>
>>>
>>>
>> Someone should write a browser addon to automatically decode and fill in
>> captchas for blind users. (Only half joking)
>>
>> -bawolff
>> ______________________________**_________________
>>>>>
>>>>> Wikitech-l mailing list
>>>>> Wikitech-l(a)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(a)lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>>>
>>>
>>>
>>> --
>>> @wikimediadc / @wikidata
>>> _______________________________________________
>>> Wikitech-l mailing list
>>> Wikitech-l(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
--
John Vandenberg
There's a useful blog post on code review at Mozilla by Mozilla developer David Humphrey on his blog: <http://vocamus.net/dave/?p=1569>.
I like his breakdown of different types of code reviews. It seems like at Mozilla there is a lot of room for the patch submitter to indicate to reviewers what sort of review is needed for a particular patch, ranging from requests for manual testing and careful scrutiny all the way to what Humphrey calls "catechism reviews", in which the committer uses a review request to announce her intent and solicit a basic sanity-check.
Unofficially such reviews do not exist at the WMF because we are all infallibly meticulous and diligent about testing every branch of every code change. But unofficially they do, of course. It'd be nice if such reviews were formally sanctioned (with whatever qualifications). I'm interested to hear other people's thoughts.
--
Ori Livneh
All,
The switchover work is done.
The site was was available to readers throughout the migration work though
it was in read-only mode for about 32 minutes, when Asher and Mark had to
migrate the database masters over from Tampa to Ashburn.
We will cancel the reminding maintenance windows.
Thank you all for your patience and understanding.
Regards,
CT Woo
On Sat, Jan 19, 2013 at 10:57 AM, Ct Woo <ctwoo(a)wikimedia.org> wrote:
> All,
>
> We will be proceeding with the datacenter switchover plan this coming
> Tuesday (Jan 22, 2013), unless we discover some unexpected and
> insurmountable issues in our tests between now and then.
>
> During the 8-hour migration window on the 22nd, 23rd and 24th (from 17:00
> UTC to 01:00 UTC hours / 9am to 5pm PST), there would be times (lasting
> about 30 minutes) where the site would be set to "read-only" mode, to
> facilitate master database switchovers from one datacenter to another.
> While the site should be available to readers, no new contents could be
> created, edited or uploaded.
>
> We are aware of the inconvenience and we have put together plans to
> minimize such annoyances, e.g., automating much of the procedures,
> mitigating known risks, and performing tests to identify issues prior to
> deployment. Given the scale and complexity of this migration, we do realize
> not all operational impact is predictable. Some users could experience
> intermittent site unavailability and/or performance issues unfortunately.
>
> You can follow the migration on chat.freenode.net<http://irc.freenode.net>
> (and not irc.freenode.org as mentioned in previous email) in the
> #wikimedia-operations channel.
>
> Thanks,
> CT Woo
>
> ---------- Forwarded message ----------
> From: Ct Woo <ctwoo(a)wikimedia.org>
> Date: Fri, Jan 11, 2013 at 12:07 PM
> Subject: Update on Ashburn data center switchover / migration – target
> date is week of 1/22/13
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Development
> and Operations Engineers <engineering(a)lists.wikimedia.org>
>
>
> All,
>
> The Migration team is in the last lap on completing the remaining tasks to
> ready our software stack and Ashburn infrastructure for the big
> switchover day.
>
> Per my last update,<http://lists.wikimedia.org/pipermail/wikitech-l/2012-October/063668.html>
> with the Fundraising activity behind us now, the team has scheduled the *week
> of 22nd January*, 2013 to perform the switchover. We are going to block a
> 8-hour migration window on the *22nd, 23rd and 24**th*. During those
> periods, *17:00 UTC to 01:00 UTC hours (9am to 5pm PST*), there will be
> intermittent blackouts and they will be treated as 'planned' outages. You
> can follow the migration on irc.freenode.org in the #wikimedia-operations
> channel.
>
> The team is putting the finishing touches to the last few tasks and we
> will make the final Go/No decision on 18th Jan, 2013. An update will send
> out then. For those interested in tracking the progress, the meeting notes
> are captured on this wikitech page<http://wikitech.wikimedia.org/view/Eqiad_Migration_Planning#Improving_Switc…>
> .
>
> *Please note that we will be restricting code deployment during that
> week, allowing only emergency and critical ones only.*
>
> Thanks.
>
> CT Woo
>
>
>
>
>