In the last few weeks I have been updating documentation on Selenium tests.
You can find it here:
https://www.mediawiki.org/wiki/Selenium
Please notice that there is documentation on how to write Selenium tests in
Node.js:
https://www.mediawiki.org/wiki/Selenium/Node.js
There is still a lot of things I would like to do, but I think the
documentation is now in a good enough shape to announce it.
I am still working on it and I really need your feedback. Feel free to
reply here, at IRC (zeljkof at #wikimedia-releng) or at Phabricator:
https://phabricator.wikimedia.org/T108108
I was not working on the documentation alone. I would like to say thank you
to Antoine Musso (hashar), Dan Duvall and Greg Grossmeier, among others.
Željko
The 'phabricator model' is far from perfectly fitting our needs though:
https://secure.phabricator.com/maniphest/query/qWbzSK1NVwb0/
On 17 Nov 2016 1:07 pm, "Vi to" <vituzzu.wiki(a)gmail.com> wrote:
That's obvious, anybody knows only bag inspectors are allowed to inspect
wallets.
Coming back to be serious, imho, Wikimedia should apply the "phabricator
model" to a 2FA open source app: collaborating in development and making it
perfectly fit with our needs
Vito
2016-11-17 13:06 GMT+01:00 Dmitry Brant <dbrant(a)wikimedia.org>:
> Don't give your wallet to anyone claiming to be a Wallet Inspector.
>
> On Nov 17, 2016 4:48 AM, "Vi to" <vituzzu.wiki(a)gmail.com> wrote:
>
> So are you telling me that tool "test if your credit card was cloned" is a
> fraud? But its test included my ccv2 too! :p
>
> Vito
>
> 2016-11-17 9:33 GMT+01:00 Chad <innocentkiller(a)gmail.com>:
>
> > On Thu, Nov 17, 2016 at 12:18 AM Antoine Musso <hashar+wmf(a)free.fr>
> wrote:
> >
> > > Le 16/11/2016 à 19:19, Pine W a écrit :
> > > >
> > > > (0) Consider testing your password strength with a tool like
> > > > http://www.testyourpassword.com/; be sure that the tool you use does
> > not
> > > > send your chosen password over the Internet and instead tests it
> > locally.
> > >
> > > By using an online testing tool, you are effectively breaking the very
> > > first rule:
> > >
> > > DO NOT GIVE OUT YOUR PASSWORD. EVER.
> > >
> > > Using that site is exactly like sharing your password with a random
> > > stranger in the world. Even if you trusted that website, and audited
> > > the code at a given point in time, you have no guarantee the site
> hasn't
> > > changed or that it is not collecting passwords.
> > >
> > >
> > Not to mention, it's plain-old-insecure HTTP, so of course anyone and
> > their mother's uncle could be sniffing the traffic ;-)
> >
> > Same rule goes for a "generate a random password" site. Don't use
> > them.
> >
> > -Chad
> > _______________________________________________
> > 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
>
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Don't give your wallet to anyone claiming to be a Wallet Inspector.
On Nov 17, 2016 4:48 AM, "Vi to" <vituzzu.wiki(a)gmail.com> wrote:
So are you telling me that tool "test if your credit card was cloned" is a
fraud? But its test included my ccv2 too! :p
Vito
2016-11-17 9:33 GMT+01:00 Chad <innocentkiller(a)gmail.com>:
> On Thu, Nov 17, 2016 at 12:18 AM Antoine Musso <hashar+wmf(a)free.fr> wrote:
>
> > Le 16/11/2016 à 19:19, Pine W a écrit :
> > >
> > > (0) Consider testing your password strength with a tool like
> > > http://www.testyourpassword.com/; be sure that the tool you use does
> not
> > > send your chosen password over the Internet and instead tests it
> locally.
> >
> > By using an online testing tool, you are effectively breaking the very
> > first rule:
> >
> > DO NOT GIVE OUT YOUR PASSWORD. EVER.
> >
> > Using that site is exactly like sharing your password with a random
> > stranger in the world. Even if you trusted that website, and audited
> > the code at a given point in time, you have no guarantee the site hasn't
> > changed or that it is not collecting passwords.
> >
> >
> Not to mention, it's plain-old-insecure HTTP, so of course anyone and
> their mother's uncle could be sniffing the traffic ;-)
>
> Same rule goes for a "generate a random password" site. Don't use
> them.
>
> -Chad
> _______________________________________________
> 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
Hi, the second role mentioned in the email below is technical, and maybe
someone in this list is interested.
---------- Forwarded message ----------
From: Maria Cruz <mcruz(a)wikimedia.org>
Date: Thu, Nov 17, 2016 at 12:17 AM
Subject: [Wikimedia-l] Two internships in the Community Engagement
department
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Hello all,
As some of you may have seen there are two open positions (both paid) in
the Community Engagement department for internships on the Learning &
Evaluation team:
-
Communications Intern:. (6 months, up to 30 hours/week) We are looking
for a candidate who works and / or studies in the field of
communications,
has excellent verbal and written English communications skills and the
ability to excel in a fast-paced, multitasking environment. Knowledge
and/or experience with Wikimedia Projects a plus!
The Communications Iintern will primarily support conference communications
for the Community Engagement Team (including event planning and materials
preparation), help plan workshops and community events for program leaders
(as well as document the outcome of those events), and assist with the
coordination of technology supports for communications and events. You can
find the complete job description here:
https://boards.greenhouse.io/wikimedia/jobs/488571#.WCHxXOErKRs
-
Technical Intern (3 months up to 20 hours/week) We are looking for a
candidate that has experience in Mediawiki mark-up and technical
communications experience in designing for web content curation and user
flow, has proficiency in at least three of the following programming
languages: Javascript, Lua, Python, MySQL, has experience developing or
administrating MediaWiki websites. The candidate should have a strong
interest in archival systems, searchability and usable portals on wiki,
and
technical skills for designing Wikimedia templates and pages.
The Technical Design Intern will work closely with the Communications and
Outreach Coordinator (that would be me!) on the Wikimedia Resource Center,
the redesign of the Evaluation Portal on Meta Wikimedia, and migration and
archiving of L&E portal pages from existing namespaces to new namespace,
among other tasks. You can find the complete job description here:
<https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs>
https://boards.greenhouse.io/wikimedia/jobs/488570#.WBE6X-ErKRs
If you are interested, please apply. If you know someone who might fit this
position, please forward the email to them!
Cheers,
María
_______________________________________________
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines
New messages to: Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
In Gerrit change 321406[1] and related patches,[2] I've proposed code to
allow the MediaWiki action API to return errors and warnings in languages
other than English. Feedback and code review would be appreciated.
A detailed description of the proposed changes is posted at
https://www.mediawiki.org/wiki/API/Architecture_work/i18n#Warnings_and_erro….
Summary:
- For clients of the API, some error codes will change, particularly
from query submodules. If you're trying to parse the human-readable error
and warning text, these also are likely to change. A few modules that
returned error or warning text in a non-standard manner have been changed.
For the most part, though, client code should not need updating since the
default is backwards-compatible.
- For extension authors, several ApiBase methods are deprecated and
should be replaced. The existing patches[2] may serve as examples.
[1]: https://gerrit.wikimedia.org/r/#/c/321406/
[2]: https://gerrit.wikimedia.org/r/#/q/topic:api-error-i18n/T47843
--
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
Hi Mathieu,
I came across this on-line conference I thought it might be interesting
stuff for other engineers. I find all conferences worth checking as they
usually cover newest technologies/trends in engineering. This mailing list
seemed to be the most appropriate to share such information.
But in the future I think a better list would be the engineering list.
Thanks for the feedback.
Piotr
On 15.11.2016 16:24, mathieu stumpf guntz wrote:
> Hi Piotr,
>
> Despite the fact that this is a list with many developer, how is this
> information relevant on a Wikimedia mailing list? Is their any focus on
> how this products may useful in the Wikimedia environment? Will the
> their be free pedagogical material we may include on Wikibooks,
> Wikiversity or Commons as an outcome from this session?
>
> If such is not the case, that's not an information I whish to receive
> through this canal. Other might have a different opinion, and they are
> welcome to bring feedback, but hopefully this won't make to much noise
> on this ml, and any flamewar will be contained somewhere else.
>
> Kind regards,
> mathieu
>
>
> Le 15/11/2016 à 14:37, Piotr Miazga a écrit :
>> Hi all,
>>
>> At November 16th - 18th Microsoft hosts Connect - Developer virtual
>> event.
>> This event is streamed live and it's for free.
>>
>> Link to event: https://connectevent.microsoft.com/
>>
>> Speakers will share latest innovations from Microsoft software. There
>> will
>> be many interactive Q&A sessions with Microsoft engineering teams,
>> customers and partners. Third day is an online full-day courses on
>> developing and deploying web and data applications or cross-platform
>> mobile
>> apps.
>>
>>
>> Piotr
>> _______________________________________________
>> 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
Hello all,
A quick note that next week is Thanksgiving in the US. As such the week
is shorter (only 3 days) and we will NOT be rolling out a new version of
MediaWiki.
We will have the normal SWAT windows on Monday and Tuesday (but not
Wednesday, as that is effectively a "Friday"). Those SWATs are only for
important fixes; don't even think about using them as a way of getting
around the lack of a train.
Details:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_November_21st
Best,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
https://www.mediawiki.org/wiki/Scrum_of_scrums/2016-11-16
2016-11-16 =
== Product ==
=== Reading ===
==== iOS native app ====
https://phabricator.wikimedia.org/project/view/2220/
* Last week:
- * Fixed more remaining issues from persistance layer update,
investigated better long term solution
- * Sped up testing & build chain, began consolidating to buildmini &
Jenkins
* This week:
* More 5.3.0 beta feedback & fixes (and release Friday or Monday)
* Add announcement card to the news feed
* Initial dynamic type implementation & assessment of scope
==== Android native app ====
* Last week:
* Continuing Q2 goals for Wikidata descriptions
* Moving to kanban-ish workflow
* Next week:
* More Q2 goals for Wikidata descriptions (mostly polish)
==== Mobile Content Service (MCS) ====
* Adding announcements feed endpoint
==== Reading Web ====
* Current sprint: https://phabricator.wikimedia.org/project/board/2336/
* Continuing work from the last week
* Next sprint: https://phabricator.wikimedia.org/project/view/2342/
* Stopping Hovercards A/B tests in multiple wikis
* More work on PageImagesAPI (returning images in lead section only)
==== Reading Infrastructure ====
* We're disappointed in the fact that T150454 wasn't caught by grepping for
the removed function before merging into core.
https://phabricator.wikimedia.org/T150454
* API error/warning i18n patches are up!
** *https://gerrit.wikimedia.org/r/#/c/321406/*
<https://gerrit.wikimedia.org/r/#/c/321406/> (and its parent patches) could
use review, both codewise and for the output resulting when non-bc
errorformat is used.
** The patches depended on by that change are next in importance. These are
for OAuth, TitleBlacklist, GlobalBlocking, Translate, and ConfirmEdit.
** All other WMF-deployed extensions affected by this change have patches
too, see *https://gerrit.wikimedia.org/r/#/q/topic:api-error-i18n/T47843*
<https://gerrit.wikimedia.org/r/#/q/topic:api-error-i18n/T47843>.
Non-WMF-deployed extensions are (mostly) not touched at this time, the
worst that should happen to them is wfDeprecated warnings eventually.
=== Community Tech ===
* No blockers, not blocking
* RFC for changing default category collation to uca with numeric:
https://meta.wikimedia.org/wiki/Requests_for_comment/Switch_default_categor…
* Pageviews Analysis 2.0 out: https://tools.wmflabs.org/pageviews/ (Improved
UI)
* Script for populating fields in localuser table in CA due to run next
week: https://phabricator.wikimedia.org/T148242
** Long-running script - estimated 4-5 days
** Note: Global user account renaming will be disabled during the script
run to prevent conflicts
* Work continues on Programs Dashboard
=== Editing ===
==== Collaboration ====
* Updates
** RecentChanges new filtering work (ERI)
** Flow exception fixes
** Echo Notifications special page improvements
** Flow caching rewrite for multiple data centers has been deployed. Keep
an eye out on Flow issues, and let us know if you have any problems.
* Blocked - None
* Blocking - None
==== Language ====
==== Parsing ==== (Arlo / Scott will show up instead of Subbu)
* Parsoid: Released debian 0.6.1 and npm 0.6.1 packages -- last release to
support node 0.1x.
* Parsoid: Deprecated support for node 0.1x, dropping all support March
31st 2017 (see wikitech-l announcement).
* Working with Community Engagment to communicate Tidy replacement changes,
prepare FAQs, what this means for editors, what kind of fixups would be
needed, tools available, etc.
* Work ongoing to get the Linter extension ready for deployment on the
Wikimedia cluster -- could launch in the Dec 2016 - Jan 2017 timeframe.
=== UI Standardization ===
Still working on:
* Align Minerva (Mobile Frontend) to overhauled color palette (T146799)
* Review and integrate messages, alerts, warnings as WikimediaUI
component (T127405, continued)
* Changing visual language of styleguide
Working on:
* Improve form layouts in OOUI MW core forms for better user experience
(T136790)
* Align CX to overhauled WikimediaUI color palette (T150731)
* Align blog primary colors to WikimediaUI color palette (T150057)
Finished:
* Variable naming in WikimediaUI Base (T147612)
== Technology ==
=== Analytics ===
Blockers or blocking: None
Updates:
* Waiting for nodes to double storage capacity for Pageview API
* Computing the first standard metrics with reconstructed edit history
* Testing ClickHouse as a very fast serving layer of the edit data
* Public Event Streams is on its way of being productionized
Upcoming:
* We'll meet with Editing team to give some examples on edit data use
=== Architecture / ArchCom ===
=== Release Engineering ===
Updates:
* 1.28 rc.1 this week (for realz)
* scap 3.3.1 to go out (already on Beta Cluster)
* Phabricator update this week (Wednesday) with Calendar improvements (in
support of DevSummit)
Blocked:
* labs: Request for CI staging project
https://phabricator.wikimedia.org/T150772
=== Security ===
* All projects and and security reviews have been suspended while team
focuses on incident handling
=== Discovery ===
- You can now search for file properties such as file size and and file
type on Commons.
- https://www.mediawiki.org/wiki/Help:CirrusSearch#File_properties_search
- The Interactive Team's roadmap can be viewed here; it was finalized in
Nov 2016 for FY 2016/2017.
- https://www.mediawiki.org/wiki/File:Interactive_Roadmap_2016-2017.pdf
- Tabular & map data on Commons announced
-
https://commons.wikimedia.org/wiki/Commons:Village_pump#Launching_shared_ma…
=== Services ===
* Blockers: none
* Updates
** Node 6 update planning: https://phabricator.wikimedia.org/T149331
- *** All services ready and tested, kartotherian is on it's way
- *** Planned order: RESTBase -> Parsoid -> SCB -> Others
- *** Q for Ops: is node 6 rollout considered a deployment and is under
deployment freeze next week? Alex: Yes. It is under the freeze
** Thumb API discussion, please participate:
https://phabricator.wikimedia.org/T66214
** Scap3 config deployments:
- *** Parsoid: done
- *** CXServer: https://phabricator.wikimedia.org/T147634
- **** Patches done. Ready to proceed Thurstay EU morning, no objections?
- *** MCS - Marko ready to proceed Thursday EU morning, no objections?
=== Technical Operations ===
* '''Blocked''':
** none
* '''Blocking'''
** none
* Updates
** kubernetes goal ongoing. working with packaging kubernetes and calico
** labsdbs10{09,10,11} provisioned, work ongoing
** varnish 4 text cluster upgraded finally! Achievement unlocked!
** working with performance on thumbor 100% deployment
** deprecation of precise ongoing, down to 7 boxes
=== Performance ===
* Blocked
** Consensus to unlock further work on active/active DC project (etcd,
session storage, varnish, etc.). I encourage representatives of
Operations/Traffic and Services to attend the next active/active meeting on
Nov 23. That meeting can be moved later if it's too early for some.
* Blocking
** none
* Updates
** ?action=markpatrolled is now POST-based
** Live traffic investigation confirmed that a non-trivial amount of
pageviews start off as hidden tabs (>8%, mobile included).
** Parser report format reverted, the new format introduced for
PerformanceInspector was breaking a commong workflow (i.e. checking the
parser report when previewing an edit)
** Comparing HTTP status codes from production image scalers and Thumbor
revealed a dozen edge cases. We'll need to discuss with Operations at the
next Thumbor meeting which ones are blockers for the launch.
== Wikidata ==
* Being a WMDE employee I again was not able to join the Hangout, without
being manually added every time.
* RevisionSlider is out of beta.
* Final touches on Cognate extension (automatic interwiki links for all
Wiktionaries).
* Waiting for security review of the Cognate
https://gerrit.wikimedia.org/r/320743 and InterwikiSorting extensions.
* German Technical Wishlist team is working on a UI for the 2 PDF
renderers. Would like to track/gather feedback for a while. But:
https://phabricator.wikimedia.org/T150871
== Fundraising Tech ==
* Two weeks till Big English
** please tread very softly in core, especially anything that could affect
CentralNotice (messages, caching, ResourceLoader)
** FR-tech would appreciate a heads up if there are significant changes
* Improving signal to noise ratio in fundraising system logging and alerts
* Tweaking mailing list export and offline donation import
* Still looking at CentralNotice issues
** https://gerrit.wikimedia.org/r/320317 should have gotten us logging for
client-side issue, but we're not seeing those in logstash (search for
message key centralnotice, and you only get the server-side messages)
Hi, it seems that there is many people struggling with following
Phabricator notifications. Being overwhelmed by notifications defeats the
purpose of notifications. :)
This is an invitation to share some thoughts.
The main trick is of course to pay attention to what you
subscribe/unsubscribe to. Sometimes I ask myself: why am I receiving this
notification, and after a quick investigation it turns out that I am still
watching some project that I am not really interested anymore, or at least
not at the extent that it would impede me to follow better the projects
that I really want to follow.
I actually unsubscribe from many tasks, and that keeps the signal high vs
noise ratio high.
Email preferences can also help a lot reducing the amount of (what for you
constitutes) noise. Also, many people seem to struggle with volume of
emails received and haven't really tried the alternative of web
notifications, which (at least for me) allow for quicker scanning + the
fabulous button "Mark all as read".
I also set many types of notifications to "ignore", because for me at least
the information they bring doesn't compensate for the noise they create. I
have copied my Maniphest email preferences at
https://www.mediawiki.org/wiki/User:Qgil-WMF/Sandbox just in case someone
finds them useful.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil