Am 05.04.2016 um 21:47 schrieb Siebrand Mazeland:
> We just had April fools. Please don't. A single test variant is fine, but
> we don't need more.
I realize that this was probably a joke. But i do think it would be useful. I'd
be fine with making this an extension though, instead of baking it
We just had April fools. Please don't. A single test variant is fine, but
we don't need more.
On Tue, Apr 5, 2016 at 4:48 PM, Purodha Blissenbach wrote:
> Yes, plase!
> (I shall add the German semi-equivalent "Hühnersprache" [1] as soon as I
> am able)
> Purodha
>
>
Yes, plase!
(I shall add the German semi-equivalent "Hühnersprache" [1] as soon as
I am able)
Purodha
[1] https://de.wikipedia.org/wiki/Spielsprache#H.C3.BChnersprache
On 05.04.2016 16:00, Daniel Kinzler wrote:
Am 01.04.2016 um 19:08 schrieb C. Scott Ananian:
On a somewhat serious note, I'm
The Release Engineering team's goal for the April-June 2016 quarter is
to move everything that is currently deployed with Trebuchet over to
Scap. With the release of Scap 3.1.0, everything that is deployed via
Trebuchet can be ported to Scap—it supports git-fat, restarting
services, and there is
I suppose you've figured out that I don't know how to write citations.
Subtract -1 from N for all [N] in the body. :-) -S.
On 04/05/2016 11:41 AM, Subramanya Sastry wrote:
Hi everyone,
We would like to let you know that Kunal (User:Legoktm for those who
don’t already know) is moving inside
Hi everyone,
We would like to let you know that Kunal (User:Legoktm for those who
don’t already know) is moving inside the Editing Department from the
Collaboration Team to the Parsing Team.
The Collaboration team is grateful for Kunal’s great work over the past
year, especially on the
On 2016-04-05 17:37, Jon Robson wrote:
> On Tue, Apr 5, 2016 at 5:00 PM, Daniel Kinzler
wrote:
>> Yes, please! I have been using a patch that Liangent wrote a few
years ago, but
>> which never got merged, for exactly this purpose. Piglatin may just
be a fun
>> easter egg
2. Identifying document fragments for translation is another instance of the
same problem of associating metadata with document fragments *across edits*.
Citations, content-translation, comments-as-documentation, authorship
information, maintaining-association-between-translated-fragments, etc.
+1. Where can I +2 this?
On Tue, Apr 5, 2016 at 5:00 PM, Daniel Kinzler wrote:
> Am 01.04.2016 um 19:08 schrieb C. Scott Ananian:
>> On a somewhat serious note, I'm a big fan of enabling pig Latin as a
>> language variant in enwiki.
>
> Yes, please! I have been using a
Am 01.04.2016 um 19:08 schrieb C. Scott Ananian:
> On a somewhat serious note, I'm a big fan of enabling pig Latin as a
> language variant in enwiki.
Yes, please! I have been using a patch that Liangent wrote a few years ago, but
which never got merged, for exactly this purpose. Piglatin may
I personally reserve -2 for "this is a fundamentally bad idea" or "this requires
community consensus before being implemented". Anything that is fixable in the
code should get a -1 or 0.
Btw, I personally prefer to get -1 reviews over 0 reviews, simply because it's
easier to spot them as "todo"
I think a review is valuable no matter what the score... with the
possible exception of -2 which I fear is probably a bit too aggressive
and unnecessary in our ecosystem for which reason the reading web team
agreed to avoid the use of -2 except to stop merges in progress that
were not ready. I
> I, for example, value better good -1 code reviews
Same here. There are statistics for -1 too, two clicks away from the
link I provided in the previous message.
https://www.mediawiki.org/wiki/Gerrit/Reports/Code_review_activity
Nemo
___
Wikitech-l
Hi, back from the Hackathon in Jerusalem, where technical collaboration
worked at its best. :)
I have been asking hackathon participants about their opinions on the Code
of Conduct, especially among volunteers that haven't participated in the
draft. The replies could be mainly classified in two
On Tue, Apr 5, 2016 at 9:12 AM, Ryan Kaldari wrote:
> On Fri, Apr 1, 2016 at 10:49 AM, Brion Vibber
> wrote:
>
> > 2) Some/many pages use ... incorrectly: spanning
> > paragraphs, markup level boundaries, etc.
> >
>
> The documentation says to do
On Mon, Apr 4, 2016 at 5:21 PM, Niklas Laxström
wrote:
> The use case for CX is very different from Translate's page
> translation. Former supports one-time "free form" translation from one
> language to one language. The latter supports maintaining
>
On Fri, Apr 1, 2016 at 10:49 AM, Brion Vibber wrote:
> 2) Some/many pages use ... incorrectly: spanning
> paragraphs, markup level boundaries, etc.
>
The documentation says to do it that way:
https://www.mediawiki.org/wiki/Help:Extension:Translate/Page_translation_example
17 matches
Mail list logo