[Wikitech-l] Avatars coming to gerrit

2018-10-05 Thread Paladox via Wikitech-l
Hi, with https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/464907/ being 
merged. We are a step closer to enabling avatars.
The only changes left to do is 
https://gerrit.wikimedia.org/r/#/c/operations/puppet/+/456437/ and also 
installing the plugin.
You can begin uploading your avatars to 
https://gerrit.wikimedia.org/r/#/admin/projects/All-Avatars
Note that we will only accept png images. Please do not upload any other format.
Note: Image formats are case sensitive so the image must match the username 
field at https://gerrit.wikimedia.org/r/#/settings/
So for example me (paladox) will be paladox.png.
We also have a license file for you to specify the license of your image at 
https://gerrit.wikimedia.org/r/plugins/gitiles/All-Avatars/+/refs/heads/master/LICENSE
If none is specified then it defaults to GPL 2.0+.
We are using "Trusted-Contributors" for this. So to be able to upload and merge 
your own change you will need to be in this group. If you would like to be 
added to this group please reply to this email saying you would like to be 
added to it.
Note all members in "mediawiki" will already be able to merge or add users to 
these groups, same for admins and ldap/ops (seeing as they are also admins).
See task https://phabricator.wikimedia.org/T191183


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] non-obvious uses of in your language

2018-10-05 Thread John Erling Blad
In my opinion we should try to first process the whole linked phrase by
inflection aka affix rules, and if that fails aka no link target can be
found – then and only then should regexps form prefix and linktrails be
applied. If applying prefix or linktrails creates a word that can be
inflected, and it links to the same target, then move the strings into the
linked phrase. If the link use the pipe-form, then move the strings into
the second part of the link, aka the link text.

Links using the pipe-form should not have the link target inflected. This
is important, as this is the natural escape route if inflection gives wrong
target for whatever reason.

Inflected links should go to the target with the smallest difference. This
is a non-trivial problem. We often link _phrases_ and those could be
processed by several rules, each with some kind of weight rules. An edit
distance would probably not be sufficient.

Perhaps most important; VisualEditor should not insert , if the
users needs this escape route then let them do it themselves in
WikitextEditor.


On Fri, Oct 5, 2018 at 6:17 PM Amir E. Aharoni 
wrote:

> ‫בתאריך יום ו׳, 5 באוק׳ 2018 ב-16:59 מאת ‪Dan Garry‬‏ <‪
> dga...@wikimedia.org
> ‬‏>:‬
> >
> > On Thu, 4 Oct 2018 at 23:29, John Erling Blad  wrote:
> >
> > > Usually it comes from user errors while using VE. This kind of errors
> are
> > > quite common, and I asked (several years ago) whether it could be fixed
> in
> > > VE, but was told "no".
> > >
> >
> > I'd really appreciate it if you could give me more information on this.
>
> This is very frequent. I know that in the Hebrew Wikipedia it happens up to
> 20 times a day (I actually counted this for many months), and this is never
> intentional or desirable. Never, ever. 100% of cases. The same must be true
> for many other languages, but probably not for all. In wikis bigger than
> the Hebrew Wikipedia it probably happens much more often than 20 times a
> day.
>
> It is possibly the most frequent reason for automatic insertion of 
> tags (although this may be different by language).
>
> How does it happen? Several ways:
> * People add a word ending to an existing link. English has very few word
> endings (-s, -ing, -ed, -able, and not much more), but many other languages
> have more.
> * People highlight only a part of a word when they add a link, even though
> they should have highlighted the whole word.
> * In particular, people highlight the part of the word without an ending.
> For example, "Dogs" is written, and people highlight "Dog".
> * People sometimes actually want to write two separate words and forget to
> write a space. (This may sound silly, but I saw this happening very often.)
> * People write a compound word and link a part of the word. Sometimes it's
> intentional, although as we can see in other emails in this thread not
> everybody agrees about the desirability of this. This works very
> differently in different languages. German has a lot of them, English has
> much less, Hebrew has almost zero.
>
> It's worth running proper user testing
>
> > Here's how the linking feature works right now for adding links to words
> > which presently have no links:
> >
> >- If you put your cursor inside a word without highlighting anything,
> >and add a link, the link is added to the entire word.
> >- If you highlight some text, and add a link, the link is added to the
> >highlighted text.
>
> I know this, and I like how it works, but the fact is that there are many
> other users who don't know this. Simply searching wikitext for
> "]]" will show how often does this happen.
>
> > How would you propose this feature be changed?
>
> One possibility is to not add  after a link. I proposed it, but it
> was declined: https://phabricator.wikimedia.org/T141689 . The declining
> comment links to T128060, which you mentioned in your email, and it's still
> not resolved.
>
> Other than fully stopping to do it, I cannot think of many other
> possibilities. Maybe we could show a warning, although I suspect that many
> users will ignore it or find it unnecessarily intrusive. I'm not a real
> designer, and it's possible that a real designer can come with something
> better.
>
> Another thing we could consider is to link the whole word *by default*, and
> to add another function that separates a link from the trail. I'd further
> suggest the separation be done internally not by "", but by some
> other syntax that looks more semantic, for example "{{#sep}}" (this should
> be a magic word and not a template!). My educated guess is that separating
> the word from the link is much less frequent than wanting to link the whole
> word. Part of my motivation for starting this thread was to understand how
> does this work in different languages.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Collecting UI feedback for PolyGerrit - Gerrit

2018-10-05 Thread Paladox via Wikitech-l
 I have filed it upstream at 
https://bugs.chromium.org/p/gerrit/issues/detail?id=9815
On Friday, 5 October 2018, 06:54:25 BST, Dalba  
wrote:  
 
 I have issues with copying the text of changed files:

`ctrl+a` does not work as it used to anymore: While using the
side-by-side diff view, go to a changed file, click on the old/new
revision, press `ctrl+a`. In the old UI only the text of the selected
file would have been selected, but now the whole page gets selected
which is not that useful.

Also, copying multiple lines results in extra whitespace being copied
in the middle of the lines. For example goto [1], select the text of
both lines and copy... It'll be copied as `# -*- coding: utf-8
-*-\n\t\n\t\n"""Package to hold all library tests."""` (note the
`\n\t\n\t\n` which should have been just a `\n`).

[1]: 
https://gerrit.wikimedia.org/r/c/pywikibot/core/+/463061/5/tests/library_tests/__init__.py#1

On Thu, Oct 4, 2018 at 12:39 AM Paladox via Wikitech-l
 wrote:
>
> Hi, i am collecting feedback for Gerrit's New UI called PolyGerrit. It's 
> possible to use PolyGerrit on gerrit.wikimedia.org since 2.14. The new UI has 
> recently been made the default upstream. The Old UI is going away in the next 
> release after 2.16. Upstream have given PolyGerrit another update that looks 
> different to the one on gerrit.wikimedia.org. PolyGerrit now includes a dark 
> ui.
>
> To switch to PolyGerrit either click the "New UI" button on the footer or put 
> ?polygerrit=1 in the url.
>
> To switch back to GWTUI either click "Switch back to old ui" on the footer or 
> put ?polygerrit=0 in the url.
>
> Non dark mode:
>
> Here's how it looks like:
>
> Dashboard:
>
> https://phabricator.wikimedia.org/F26296230
>
>
> Change list:
>
> https://phabricator.wikimedia.org/F26296240
>
> Change screen:
>
> https://phabricator.wikimedia.org/F26296242
>
>
> https://phabricator.wikimedia.org/F26296257
>
>
> Dark mode: https://phabricator.wikimedia.org/F26296282
>
>
> And many other UI improvements across the app.
>
> You can play around the the new ui from the master branch that will become 
> 2.16 here https://gerrit.git.wmflabs.org/r/
>
> Please give feedback so upstream can make PolyGerrit even better! You can 
> either file your reports at 
> https://phabricator.wikimedia.org/project/view/330/ or reply to the email 
> with your feedback.
>
>
>
>
> It has a dedicated team on the UI with a design researcher behind the scenes 
> redesigning polygerrit constantly based on feedback.
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l  
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] non-obvious uses of in your language

2018-10-05 Thread John Erling Blad
T129778

On Fri, Oct 5, 2018 at 3:59 PM Dan Garry  wrote:

> On Thu, 4 Oct 2018 at 23:29, John Erling Blad  wrote:
>
> > Usually it comes from user errors while using VE. This kind of errors are
> > quite common, and I asked (several years ago) whether it could be fixed
> in
> > VE, but was told "no".
> >
>
> I'd really appreciate it if you could give me more information on this.
> Could you link to the task for this request? There is T128060
>  from early 2016 ("VisualEditor
> makes it easy to create partially linked words, when the user expects a
> fully linked one") but I don't see you on there, and I want to make sure I
> understand your request.
>
> Here's how the linking feature works right now for adding links to words
> which presently have no links:
>
>- If you put your cursor inside a word without highlighting anything,
>and add a link, the link is added to the entire word.
>- If you highlight some text, and add a link, the link is added to the
>highlighted text.
>
> How would you propose this feature be changed?
>
> Thanks,
> Dan
>
> --
> Dan Garry
> Lead Product Manager, Editing
> Wikimedia Foundation
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] non-obvious uses of in your language

2018-10-05 Thread Amir E. Aharoni
‫בתאריך יום ו׳, 5 באוק׳ 2018 ב-16:59 מאת ‪Dan Garry‬‏ <‪dga...@wikimedia.org
‬‏>:‬
>
> On Thu, 4 Oct 2018 at 23:29, John Erling Blad  wrote:
>
> > Usually it comes from user errors while using VE. This kind of errors
are
> > quite common, and I asked (several years ago) whether it could be fixed
in
> > VE, but was told "no".
> >
>
> I'd really appreciate it if you could give me more information on this.

This is very frequent. I know that in the Hebrew Wikipedia it happens up to
20 times a day (I actually counted this for many months), and this is never
intentional or desirable. Never, ever. 100% of cases. The same must be true
for many other languages, but probably not for all. In wikis bigger than
the Hebrew Wikipedia it probably happens much more often than 20 times a
day.

It is possibly the most frequent reason for automatic insertion of 
tags (although this may be different by language).

How does it happen? Several ways:
* People add a word ending to an existing link. English has very few word
endings (-s, -ing, -ed, -able, and not much more), but many other languages
have more.
* People highlight only a part of a word when they add a link, even though
they should have highlighted the whole word.
* In particular, people highlight the part of the word without an ending.
For example, "Dogs" is written, and people highlight "Dog".
* People sometimes actually want to write two separate words and forget to
write a space. (This may sound silly, but I saw this happening very often.)
* People write a compound word and link a part of the word. Sometimes it's
intentional, although as we can see in other emails in this thread not
everybody agrees about the desirability of this. This works very
differently in different languages. German has a lot of them, English has
much less, Hebrew has almost zero.

It's worth running proper user testing

> Here's how the linking feature works right now for adding links to words
> which presently have no links:
>
>- If you put your cursor inside a word without highlighting anything,
>and add a link, the link is added to the entire word.
>- If you highlight some text, and add a link, the link is added to the
>highlighted text.

I know this, and I like how it works, but the fact is that there are many
other users who don't know this. Simply searching wikitext for
"]]" will show how often does this happen.

> How would you propose this feature be changed?

One possibility is to not add  after a link. I proposed it, but it
was declined: https://phabricator.wikimedia.org/T141689 . The declining
comment links to T128060, which you mentioned in your email, and it's still
not resolved.

Other than fully stopping to do it, I cannot think of many other
possibilities. Maybe we could show a warning, although I suspect that many
users will ignore it or find it unnecessarily intrusive. I'm not a real
designer, and it's possible that a real designer can come with something
better.

Another thing we could consider is to link the whole word *by default*, and
to add another function that separates a link from the trail. I'd further
suggest the separation be done internally not by "", but by some
other syntax that looks more semantic, for example "{{#sep}}" (this should
be a magic word and not a template!). My educated guess is that separating
the word from the link is much less frequent than wanting to link the whole
word. Part of my motivation for starting this thread was to understand how
does this work in different languages.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Datacenter switchover and switchback

2018-10-05 Thread Alexandros Kosiaris
I am sorry to hear that. It looks like something that we will have to
take into account for the next switchovers. That being said, we had
deliberations across the involved teams months ago to come up with
those exact dates and have been communicating them via at least SoS
since 2018-08-01.

I am curious about something though. How does the deployment train
(cause that's what we are talking about) impact the software release
exactly ?
On Wed, Oct 3, 2018 at 6:19 PM C. Scott Ananian  wrote:
>
> Oct 8 seems to be a particularly bad time to freeze the train given that we
> are forking for the MW 1.32 release on Oct 15, and a lot of folks have
> last-minute things they want to get into the release (eg deprecations, etc).
>   --scott
>
> On Thu, Aug 30, 2018 at 10:57 AM Pine W  wrote:
>
> > +1 to DJ's question about timing. Also, one might wish to be mindful of
> > the number of recent trains that were supposed to be boring but involved
> > interesting surprises; this makes me wonder whether trains that one thinks
> > will be boring are actually OK in this circumstance even if they turn out
> > to be "interesting".
> >
> > Pine
> > ( https://meta.wikimedia.org/wiki/User:Pine )
> >
> >
> >
> >  Original message From: Derk-Jan Hartman <
> > d.j.hartman+wmf...@gmail.com> Date: 8/30/18  2:54 AM  (GMT-08:00) To:
> > Wikimedia developers  Subject: Re:
> > [Wikitech-l] Datacenter switchover and switchback
> > While I think these regular switches are a very good idea, from an outside
> > perspective I do have to question a process that puts a significant plug in
> > the velocity of various teams working on major projects (esp. in a time of
> > year that could probably be seen as one of the most productive). What are
> > plans to reduce the disruption of this exercise in the future ?
> >
> > DJ
> >
> > On Thu, Aug 30, 2018 at 8:38 AM Jaime Crespo 
> > wrote:
> >
> > > Let me explain the rationale of the bellow request for clarification:
> > >
> > > On Wed, Aug 29, 2018 at 11:30 PM MA  wrote:
> > >
> > > > Hello:
> > > >
> > > > >For the duration of the switchover (1 month), deployers are kindly
> > > > >requested to refrain from large db schema changes and avoid deploying
> > > > >any kind of new feature that requires creation of tables.
> > > > >There will be a train freeze in the week of Sept 10th and Oct 8th.
> > >
> > >
> > > During the failover, some schema changes will be finalized on the current
> > > active datacenter (plus some major server and network maintenance may be
> > > done)- our request is mostly to refrain from quickly enabling those large
> > > new unlocked features (e.g. the ongoing comment refactoring, actor/user
> > > refactoring, Multi Content Revision, JADE, major wikidata or structured
> > > comons structure changes, new extensions not ever deployed to the
> > cluster,
> > > etc.) at the same time than the ongoing maintenance to reduce variables
> > of
> > > things that can go bad- enabling those features may be unblocked during
> > the
> > > switchover time, but we ask you to hold until being back on the current
> > > active datacenter. Basically, ask yourself if you are enabling a large
> > new
> > > core feature or want to start a heavy-write maintenance script and there
> > is
> > > a chance you will need DBA/system support. Sadly, we had some instances
> > of
> > > this happening last year and we want to explicitly discourage this during
> > > these 2 weeks.
> > >
> > > In own my opinion, enabling existing features on smaller projects (size
> > > here is in amount of server resources, not that they are less important)
> > is
> > > equivalent to a swat change, and I am not against it happening. I would
> > ask
> > > contributors to use their best judgement on every case, and ask people on
> > > the #DBA tag on phabricator or add me as reviewers on gerrit if in doubt.
> > > My plea is to not enable major structural changes during that time may
> > > affect thousands of edits per minute. Swat-like changes and "boring" :-)
> > > trains are ok.
> > >
> > > For new wiki creations I would prefer if those were delayed but CC #DBA s
> > > on the phabricator task to check with us.
> > > ___
> > > Wikitech-l mailing list
> > > Wikitech-l@lists.wikimedia.org
> > > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
> > ___
> > Wikitech-l mailing list
> > Wikitech-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
> --
> (http://cscott.net)
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l



-- 
Alexandros Kosiaris 

___

[Wikitech-l] MediaWiki 1.32 branch announcement

2018-10-05 Thread Greg Grossmeier
Greetings!

We are beginning the process of working on the 1.32 release of
MediaWiki. The release is currently scheduled for Nov. We plan to create
the REL1_32 branch on October 16 and to generate the first release
candidate, so we will be requesting "pencils down" on October 15.

In the meantime, if you have any open Phabricator tasks tagged with
mw-1.32-release [0], please check to see if they are indeed blockers for
the release. If not, please remove the mw-1.32-release tag from them.
Conversely, if there are any blockers that are not tagged with
mw-1.32.release, please tag them. Please feel free to reach out to me if
you have any questions about this.

We will be in the normal patch master + backport process from October 16
until the release in Nov.

Thanks,

Greg

[0] https://phabricator.wikimedia.org/tag/mw-1.32-release/

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team ManagerA18D 1138 8E47 FAC8 1C7D |


signature.asc
Description: PGP signature
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] non-obvious uses of in your language

2018-10-05 Thread Dan Garry
On Thu, 4 Oct 2018 at 23:29, John Erling Blad  wrote:

> Usually it comes from user errors while using VE. This kind of errors are
> quite common, and I asked (several years ago) whether it could be fixed in
> VE, but was told "no".
>

I'd really appreciate it if you could give me more information on this.
Could you link to the task for this request? There is T128060
 from early 2016 ("VisualEditor
makes it easy to create partially linked words, when the user expects a
fully linked one") but I don't see you on there, and I want to make sure I
understand your request.

Here's how the linking feature works right now for adding links to words
which presently have no links:

   - If you put your cursor inside a word without highlighting anything,
   and add a link, the link is added to the entire word.
   - If you highlight some text, and add a link, the link is added to the
   highlighted text.

How would you propose this feature be changed?

Thanks,
Dan

-- 
Dan Garry
Lead Product Manager, Editing
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l