i think i lose my individuality and that i have to make extra key
presses to set extra spaces near brackets and commas. currently tests
/ automatical reviews show in gerrit that my commit has such errors.
what if they are not (would not be? were not? ) blamed on commit
(patch set) uploads, but
FWIW, we do index the full text of (PDF and?) DjVu files on Commons
(because it's stored in img_metadata). It's probably the biggest
improvement CirrusSearch brought for Commons.
And we also index office documents via Tika (*.doc and similar).
And I think it should not be a feature of the
i do not see search form in
https://lists.wikimedia.org/mailman/listinfo/wikitech-l and google has
nothing for site:https://lists.wikimedia.org/pipermail/wikitech-l/ ,
because of robots.txt. see https://lists.wikimedia.org/robots.txt :
# robots.txt for lists.wikimedia.org
#
# Disabled crawling
i have seen a new message in this list and i have remembered about
mailing list archives
2015-10-14 19:10 GMT+03:00 dinar qurbanov :
> i do not see search form in
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l and google has
> nothing for
dinar qurbanov wrote:
> i think i lose my individuality and that i have to make extra key
> presses to set extra spaces near brackets and commas. currently tests
> / automatical reviews show in gerrit that my commit has such errors.
> what if they are not (would not be? were
Just FYI for those on Google-hosted email.
See: https://phabricator.wikimedia.org/T115416
TL;DR: Check your spam folder :)
Greg
--
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @gregA18D 1138 8E47 FAC8 1C7D |
> How would it help the reviewer if they constantly need to
> switch their mind from "prettified" code to "whatever" when
> they review your code?
it is possible to show prettified code in gerrit web pages, and send
prettified version to people if they get it via git fetch, but save
also their
FYI regarding updates to WMF production the rest of the week.
- Forwarded message from Greg Grossmeier -
> Date: Wed, 14 Oct 2015 11:46:17 -0700
> From: Greg Grossmeier
> To: Development and Operations engineers ,
FYI if you are talking about JavaScript you might want to explore
http://jsbeautifier.org/
All code standards are currently being enforced by jscs.
They recently closed an issue to add auto-formatting
https://github.com/jscs-dev/node-jscs/issues/516
In theory, you could create a script to
https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-10-24
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Apologies for the bluntness, but if you cannot conform to the coding standards
of a project in terms of minor things such as spacing, how can we know or trust
you that you are confirming to standards that are more meaningful, such as
those related to security?
Standards allow for a consistent
dinar qurbanov wrote:
>> How would it help the reviewer if they constantly need to
>> switch their mind from "prettified" code to "whatever" when
>> they review your code?
> it is possible to show prettified code in gerrit web pages, and send
> prettified version to people if
You can whitelist mails from wikimedia.org via gmail's web interface:
http://email.about.com/od/gmailtips/qt/et_whitelist.htm
Am 14.10.2015 um 19:35 schrieb Greg Grossmeier:
> Just FYI for those on Google-hosted email.
>
> See: https://phabricator.wikimedia.org/T115416
>
> TL;DR: Check your
>Apologies for the bluntness, but if you cannot conform to the coding standards
>of a project in terms of minor things such as spacing, how can we know or
>trust you that you are confirming to standards that are more meaningful, such
>as those related to security? ...
we are talking about
On Wed, Oct 14, 2015 at 10:42 AM, dinar qurbanov wrote:
> it is possible to show prettified code in gerrit web pages, and send
> prettified version to people if they get it via git fetch, but save
> also their original form .
>
It really isn't.
On Wed, Oct 14, 2015 at 11:57 AM dinar qurbanov wrote:
> >Apologies for the bluntness, but if you cannot conform to the coding
> standards of a project in terms of minor things such as spacing, how can we
> know or trust you that you are confirming to standards that are more
>
Hi everybody,
I just had a discussion with the GSoC program admin: Carols and
she said that the GSoC program for 2016 has been announced. Date of
announcement is: 13th Oct, 2015.
You can have a look at the news here for more information like the timeline
- Timeline:
On Wed, Oct 14, 2015 at 10:23 AM, Jon Robson wrote:
> All code standards are currently being enforced by jscs.
> They recently closed an issue to add auto-formatting
> https://github.com/jscs-dev/node-jscs/issues/516
There's also the --fix flag to jscs, which automatically
On Wed, Oct 14, 2015 at 12:07 PM, Gergo Tisza wrote:
> On Wed, Oct 14, 2015 at 10:42 AM, dinar qurbanov wrote:
>
> > it is possible to show prettified code in gerrit web pages, and send
> > prettified version to people if they get it via git fetch, but
>
> --
>
> Message: 6
> Date: Tue, 13 Oct 2015 19:41:08 -0400
> From: Pine W
> To: Wikimedia developers
> Subject: Re: [Wikitech-l] Tools repository
> Message-ID:
>
Hi,
On 09/26/2015 04:28 PM, Legoktm wrote:
> There are still a few code style rules that are disabled, [2] is
> tracking fixing those issues.
These have all been resolved, and all rules in the MediaWiki standard
are now passing and voting \o/
> [2] https://phabricator.wikimedia.org/T102609
--
Corrected link:
https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-10-14
On Wed, Oct 14, 2015 at 11:25 AM, Grace Gellerman
wrote:
> https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-10-24
>
___
Wikitech-l mailing list
I've written about my problem ~2 years ago:
http://wikitech-l.wikimedia.narkive.com/6G0YPmWQ/need-a-way-to-modify-text-before-indexing-was-searchupdate
It seems I've lost the latest message, so I want to answer to it now:
With lsearchd and Elasticsearch, we absolutely wouldn't want to munge
*yay* thanks for the work! :)
Gesendet mit meinem HTC
- Nachricht beantworten -
Von: "Legoktm"
An: "Wikimedia developers"
Betreff: [Wikitech-l] PHP CodeSniffer is now voting on MediaWiki core patches
Datum: Do., Okt. 15, 2015
FWIW, we do index the full text of (PDF and?) DjVu files on Commons
(because it's stored in img_metadata). It's probably the biggest
improvement CirrusSearch brought for Commons.
Nemo
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On 10/14/2015 10:53 PM, Jon Robson wrote:
> FYI if you are talking about JavaScript you might want to explore
> http://jsbeautifier.org/
Yes. And if you are using an IDE(Example: atom), there are extensions
that will beautify
your code as per a defined jsbeautify configuration on file save or
26 matches
Mail list logo