Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[K. Peachey]

On Fri, Apr 19, 2013 at 8:54 AM, Rob Lanphier  wrote:
> We used to do that:
> https://www.mediawiki.org/wiki/Roadmap
>...

How about just something simple like
 * https://www.mediawiki.org/w/index.php?title=User:Peachey88/Sandbox/table2 or
 * https://www.mediawiki.org/w/index.php?title=User:Peachey88/Sandbox/table1

once they are tided up slightly, they have a similar layout as the
spreadsheet and not as confusing as the previous attempt (Which I
think may have been a little over worked for the end goal) although I
do admit they may be harder to edit (but that maybe fixed by some
template wizards)

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

Re: [Wikitech-l] Fwd: Deploying alpha of VisualEditor to non-English Wikipedias

[Raylton P. Sousa]

Ok, Thanks for the response!


2013/4/18 James Forrester 

> On 18 April 2013 17:44, Raylton P. Sousa  wrote:
> > You can add another language to the list?
>
> We'll hopefully be able to deploy to every Wikipedia in all our
> languages quite soon, but we should test it first on a selection so
> that if we find problems we don't have many dozens of users finding
> the same problem. :-)
>
> BTW, I notice that my message lost the important link for
> TranslateWiki.Net:
>
> https://translatewiki.net/w/i.php?title=Special%3AMessageGroupStats&x=D&group=ext-visualeditor#sortable:3=desc
> - very grateful for any who can help translate the VisualEditor
> interface!
>
> > or some of wikipedia sisters?
>
> We will hopefully be able to deploy to the sister projects in a little
> longer. Our focus to now has been on the core MediaWiki functionality
> and extensions that Wikipedias use, rather than on those for the
> sister projects, which means it may not be of as much use.
>
> > Btw, this is great!
>
> Thank you. :-)
>
> J.
> --
> James D. Forrester
> Product Manager, VisualEditor
> Wikimedia Foundation, Inc.
>
> jforres...@wikimedia.org | @jdforrester
>
> ___
> 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] Fwd: Deploying alpha of VisualEditor to non-English Wikipedias

[James Forrester]

On 18 April 2013 17:44, Raylton P. Sousa  wrote:
> You can add another language to the list?

We'll hopefully be able to deploy to every Wikipedia in all our
languages quite soon, but we should test it first on a selection so
that if we find problems we don't have many dozens of users finding
the same problem. :-)

BTW, I notice that my message lost the important link for
TranslateWiki.Net:
https://translatewiki.net/w/i.php?title=Special%3AMessageGroupStats&x=D&group=ext-visualeditor#sortable:3=desc
- very grateful for any who can help translate the VisualEditor
interface!

> or some of wikipedia sisters?

We will hopefully be able to deploy to the sister projects in a little
longer. Our focus to now has been on the core MediaWiki functionality
and extensions that Wikipedias use, rather than on those for the
sister projects, which means it may not be of as much use.

> Btw, this is great!

Thank you. :-)

J.
--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester

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

Re: [Wikitech-l] Fwd: Deploying alpha of VisualEditor to non-English Wikipedias

[Raylton P. Sousa]

Btw, this is great!


2013/4/18 Raylton P. Sousa 

> You can add another language to the list?
> or some of wikipedia sisters?
>
>
> 2013/4/18 James Forrester 
>
>> For info, given interest in the VisualEditor. :-)
>>
>>
>> -- Forwarded message --
>> From: James Forrester 
>> Date: 18 April 2013 17:32
>> Subject: Deploying alpha of VisualEditor to non-English Wikipedias
>> To: Coordination of technology deployments across languages/projects
>> 
>>
>>
>> All,
>>
>>
>> TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an
>> opt-in alpha. Your assitance is requested to inform your wikis about this
>> and help get the software translated.
>>
>>
>> Next week (on 25 April) we are going to deploy the alpha opt-in version of
>> the VisualEditor to some non-English Wikipedias in the same way that it
>> has been on the English Wikipedia since December 2012.
>>
>> This will let users get familiar with the VisualEditor, give us feedback
>> on what works and what is broken, and help us prioritise further work
>> ahead of the planned deployment as a 'default' editor for all users which
>> we intend to do in a few months' time.
>>
>> Due to a number of issues we have been unable to release VisualEditor to
>> non-English wikis until now, and we would very much like to get some great
>> feedback from as many wikis as possible - especially for extended Unicode
>> and RTL languages, but also other languages. Does the VisualEditor work in
>> your language? Does it gel with your wiki's workflow?
>>
>> The initial languages we want to target are the "top 10" Wikipedias by way
>> of scale - de, nl, fr, it, ru, es, sv, pl, ja - plus selected others to
>> help us discover issues we anticipate: ar, he, hi, ko, zh. These will let
>> us test most of the locales we are concerned about. If this goes well, we
>> hope to deploy the opt-in alpha to all Wikipedias.
>>
>> Please tell your wiki colleagues that this is coming, especially if your
>> wiki is in this list! Additionally, you can see how fully-translated the
>> software is into your language in the stats at TranslateWiki.Net[0] -
>> please encourage wiki colleagues to help translate the messages ahead of
>> the deployment!
>>
>>
>> As a note, we have just updated the VisualEditor integration so that the
>> "Edit" tab goes to VisualEditor, and there is an "Edit source" tab to go
>> to the wikitext editor.
>>
>> This change (which affects the English Wikipedia opt-in deployment and
>> MediaWiki.org as well as the new deployments mentioned above) moves the
>> way that VisualEditor integrates with the wiki's workflow to be closer to
>> how it will appear when it is the 'default' editor. It is still easy to
>> use the wikitext editor if that is what you want to do - the "Edit source"
>> tab (at least for now) will be "above the fold" and not in the drop-down
>> menu on Vector.
>>
>>
>> Happy to answer any questions you might have!
>>
>> Yours,
>> --
>> James D. Forrester
>> Product Manager, VisualEditor
>> Wikimedia Foundation, Inc.
>>
>> jforres...@wikimedia.org | @jdforrester
>>
>>
>> --
>> James D. Forrester
>> Product Manager, VisualEditor
>> Wikimedia Foundation, Inc.
>>
>> jforres...@wikimedia.org | @jdforrester
>>
>> ___
>> 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] Fwd: Deploying alpha of VisualEditor to non-English Wikipedias

[Raylton P. Sousa]

You can add another language to the list?
or some of wikipedia sisters?


2013/4/18 James Forrester 

> For info, given interest in the VisualEditor. :-)
>
>
> -- Forwarded message --
> From: James Forrester 
> Date: 18 April 2013 17:32
> Subject: Deploying alpha of VisualEditor to non-English Wikipedias
> To: Coordination of technology deployments across languages/projects
> 
>
>
> All,
>
>
> TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an
> opt-in alpha. Your assitance is requested to inform your wikis about this
> and help get the software translated.
>
>
> Next week (on 25 April) we are going to deploy the alpha opt-in version of
> the VisualEditor to some non-English Wikipedias in the same way that it
> has been on the English Wikipedia since December 2012.
>
> This will let users get familiar with the VisualEditor, give us feedback
> on what works and what is broken, and help us prioritise further work
> ahead of the planned deployment as a 'default' editor for all users which
> we intend to do in a few months' time.
>
> Due to a number of issues we have been unable to release VisualEditor to
> non-English wikis until now, and we would very much like to get some great
> feedback from as many wikis as possible - especially for extended Unicode
> and RTL languages, but also other languages. Does the VisualEditor work in
> your language? Does it gel with your wiki's workflow?
>
> The initial languages we want to target are the "top 10" Wikipedias by way
> of scale - de, nl, fr, it, ru, es, sv, pl, ja - plus selected others to
> help us discover issues we anticipate: ar, he, hi, ko, zh. These will let
> us test most of the locales we are concerned about. If this goes well, we
> hope to deploy the opt-in alpha to all Wikipedias.
>
> Please tell your wiki colleagues that this is coming, especially if your
> wiki is in this list! Additionally, you can see how fully-translated the
> software is into your language in the stats at TranslateWiki.Net[0] -
> please encourage wiki colleagues to help translate the messages ahead of
> the deployment!
>
>
> As a note, we have just updated the VisualEditor integration so that the
> "Edit" tab goes to VisualEditor, and there is an "Edit source" tab to go
> to the wikitext editor.
>
> This change (which affects the English Wikipedia opt-in deployment and
> MediaWiki.org as well as the new deployments mentioned above) moves the
> way that VisualEditor integrates with the wiki's workflow to be closer to
> how it will appear when it is the 'default' editor. It is still easy to
> use the wikitext editor if that is what you want to do - the "Edit source"
> tab (at least for now) will be "above the fold" and not in the drop-down
> menu on Vector.
>
>
> Happy to answer any questions you might have!
>
> Yours,
> --
> James D. Forrester
> Product Manager, VisualEditor
> Wikimedia Foundation, Inc.
>
> jforres...@wikimedia.org | @jdforrester
>
>
> --
> James D. Forrester
> Product Manager, VisualEditor
> Wikimedia Foundation, Inc.
>
> jforres...@wikimedia.org | @jdforrester
>
> ___
> 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] Fwd: Deploying alpha of VisualEditor to non-English Wikipedias

[James Forrester]

For info, given interest in the VisualEditor. :-)


-- Forwarded message --
From: James Forrester 
Date: 18 April 2013 17:32
Subject: Deploying alpha of VisualEditor to non-English Wikipedias
To: Coordination of technology deployments across languages/projects



All,


TL;DR: VisualEditor will be deployed on 14 new Wikipedias next week as an
opt-in alpha. Your assitance is requested to inform your wikis about this
and help get the software translated.


Next week (on 25 April) we are going to deploy the alpha opt-in version of
the VisualEditor to some non-English Wikipedias in the same way that it
has been on the English Wikipedia since December 2012.

This will let users get familiar with the VisualEditor, give us feedback
on what works and what is broken, and help us prioritise further work
ahead of the planned deployment as a 'default' editor for all users which
we intend to do in a few months' time.

Due to a number of issues we have been unable to release VisualEditor to
non-English wikis until now, and we would very much like to get some great
feedback from as many wikis as possible - especially for extended Unicode
and RTL languages, but also other languages. Does the VisualEditor work in
your language? Does it gel with your wiki's workflow?

The initial languages we want to target are the "top 10" Wikipedias by way
of scale - de, nl, fr, it, ru, es, sv, pl, ja - plus selected others to
help us discover issues we anticipate: ar, he, hi, ko, zh. These will let
us test most of the locales we are concerned about. If this goes well, we
hope to deploy the opt-in alpha to all Wikipedias.

Please tell your wiki colleagues that this is coming, especially if your
wiki is in this list! Additionally, you can see how fully-translated the
software is into your language in the stats at TranslateWiki.Net[0] -
please encourage wiki colleagues to help translate the messages ahead of
the deployment!


As a note, we have just updated the VisualEditor integration so that the
"Edit" tab goes to VisualEditor, and there is an "Edit source" tab to go
to the wikitext editor.

This change (which affects the English Wikipedia opt-in deployment and
MediaWiki.org as well as the new deployments mentioned above) moves the
way that VisualEditor integrates with the wiki's workflow to be closer to
how it will appear when it is the 'default' editor. It is still easy to
use the wikitext editor if that is what you want to do - the "Edit source"
tab (at least for now) will be "above the fold" and not in the drop-down
menu on Vector.


Happy to answer any questions you might have!

Yours,
--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester


--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester

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

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[Rob Lanphier]

On Thu, Apr 18, 2013 at 8:13 AM, K. Peachey  wrote:
> On Fri, Apr 19, 2013 at 1:10 AM, Mark A. Hershberger  
> wrote:
>> Wow, thank you for pointing to Framasoft.  Looks like they've got some
>> really useful stuff going on there.
>
> Could be done very easily and neatly in a MediaWiki page...

We used to do that:
https://www.mediawiki.org/wiki/Roadmap

After a year of maintaining, it was too much work for too little
value.  It's much easier for us to have a big picture view with the
spreadsheet format, which unfortunately, is too difficult to maintain
in a wiki page.  We do a lot of real-time collaborative editing of
this doc, which limits the amount of template voodoo we can get away
with.

As Greg mentioned, my weekend coding project is puttering around with
a script to export this data to wiki[1].  The nice thing about this
approach is that I can export whatever template/LST voodoo I want from
this without impacting our ability to edit it in groups in real-time.
That means, that instead of only having this information in a single
place, we can also incorporate the information into all of the
relevant activity pages.  I'll happily take some guidance now as to
whether I should endeavor to output a single page with lots of section
markers for LST, or if instead I should output a bunch of pages (e.g.
one "Foo/Roadmap" subpage per activity). that get transcluded into a
single "Roadmap" page.  Rather than bikeshed here about this, let's
have that discussion on-wiki at
https://www.mediawiki.org/wiki/Talk:Roadmap .

Rob

[1] Roadmap publisher script:  https://gist.github.com/robla/5416776
Very much a work in progress, so I almost didn't publish.  The only
useful bits as of this writing are the bit to pull the info from
Google Docs and push it to mediawiki.org...the conversion step is
practically non-existent.  I started off thinking I could deal with
csv, then dabbled with html, but my preferred approach now is to parse
ods from GDocs, but the code isn't really even started for that since
I'm just figuring out how to do that.

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

Re: [Wikitech-l] Heads up: small new feature in ConfirmEdit

[Matthew Flaschen]

On 04/18/2013 06:21 PM, Steven Walling wrote:
> Hi all,
> 
> This is a heads up that we've added a small new feature which hopefully
> will make things less painful for users across the projects: the ability to
> refresh the CAPTCHA you're presented without refreshing the entire page. It
> should work everywhere ConfirmEdit can throw the image CAPTCHA at someone:
> account creation, login, the edit form, etc. (It won't modify the simple
> math CAPTCHA, and so on.)

Specifically, this is a FancyCaptcha feature.

Matt Flaschen

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

[Wikitech-l] Heads up: small new feature in ConfirmEdit

[Steven Walling]

Hi all,

This is a heads up that we've added a small new feature which hopefully
will make things less painful for users across the projects: the ability to
refresh the CAPTCHA you're presented without refreshing the entire page. It
should work everywhere ConfirmEdit can throw the image CAPTCHA at someone:
account creation, login, the edit form, etc. (It won't modify the simple
math CAPTCHA, and so on.)

The original enhancement request for this (
https://bugzilla.wikimedia.org/show_bug.cgi?id=14230) goes back to 2008. A
patch was submitted back in January by lalei:
https://gerrit.wikimedia.org/r/#/c/44376/

If you want to test this out yourself before it's deployed, you can use
http://toro.wmflabs.org/wiki/Main_Page

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

Re: [Wikitech-l] Making inter-language links shorter

[Yuri Astrakhan]

There are a few things (IMO) that should be done to langlist ordering:

* Group by alphabet
People who understand latin alphabet should get a list of all latin-using
languages listed/sorted together. Cyrillic is a separate group, and so are
various asian and middle-eastern languages. I have seen other sites do this
(e.g. Google, but I can't quickly locate an example right now). Having all
languages bunched up together make going through them extremely painful -
one has to skip all the scripts not understood.

* Each wiki site has different ordering requirements - like Hebrew and
Hungarian wikis want English as the first link, or 'nn' uses 'no','sv','da'
before all others. See
pywiki-
interwiki_putfirst

* Lastly, but IMO - most importantly, we should honor user settings or
browser settings. If my browser sends *Accept Language:
en-US,en;q=0.8,ru;q=0.6*, it would be good to show english & russian at the
top, followed by others.

All this can (and should) be done in javascript, without affecting servers.

And for historical reasons: bug
2867...
i filed it in 2005, it has over 60 votes (highest count in bugzilla if i'm
not mistaken)...

--Yuri


On Thu, Apr 18, 2013 at 9:57 PM, Brion Vibber  wrote:

> I was traditionally in favor of keeping the full language list visible,
> but it's just too damn big in many cases and is hard to search through
> on any device. On touch devices it's difficult to pick a correct item from
> the list as all the links are adjacent (though if you zoom it's ok).
>
> Definitely we need something improved, and if we're going to improve it we
> need to do it for the default or we're failing to serve 99% of our
> readers...
>
> I'm not sure about the current demo; one thing that bugs me is that there's
> a very small tap/click target for getting the full language list call-out.
> Clicking on "Language" just hides/shows the short list, it doesn't do
> anything. Clicking the "settings" gear icon next to "Languages" brings up a
> call-out with language-related settings none of which help you get to
> another language version of the wiki.
>
>
> On the mobile site we've collapsed the whole thing to an "Other languages"
> section or button (depending on if you're in beta mode) at the bottom of
> the article, and this seems to have gotten good usability responses from
> mobile users.
>
>
>
> On Thu, Apr 18, 2013 at 12:47 PM, David Gerard  wrote:
>
> > On 18 April 2013 20:43, David Gerard  wrote:
> > > On 18 April 2013 17:50, Pau Giner  wrote:
> >
> > >> Please let me know if you see any possible concern with this approach.
> >
> > > My first thought is of how upset people were when the first version of
> > > Vector hid the language links by default. I would suggest being sure
> > > there will be little or no similar objection.
> >
> >
> > (hit send too soon, sorry)
> >
> > A simple solution that would avoid a similar reaction is: do not do
> > this by default - make it only for logged-in users who want it that
> > way.
> >
> > Possibly for default users, you could put the heuristically-calculated
> > likely preferred languages at the top. But keeping the rest of the
> > list below, right there on display, will (I predict) be favoured, as
> > advertising the many languages of Wikipedia is a strongly-held value
> > of many Wikimedians.
> >
> >
> > - d.
> >
> > ___
> > 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

Re: [Wikitech-l] Making inter-language links shorter

[Mathieu Stumpf]

Le jeudi 18 avril 2013 à 12:57 -0700, Brion Vibber a écrit :
> On the mobile site we've collapsed the whole thing to an "Other languages"
> section or button (depending on if you're in beta mode) at the bottom of
> the article, and this seems to have gotten good usability responses from
> mobile users.

Oh by the way, is there an access to discussion pages on the mobile
version now? Last time I checked it wasn't accessible directly, but at
the begining it wasn't possible to access other languages if I'm not
mistaken, so I thought that may also come with an update.

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

Re: [Wikitech-l] [Design] Making inter-language links shorter

[Mathieu Stumpf]

Le jeudi 18 avril 2013 à 18:50 +0200, Pau Giner a écrit :
> As multilingual content grows, interlanguage links become longer on
> Wikipedia articles. Articles such as "Barak Obama" or "Sun" have more
> than 200 links, and that becomes a problem for users that often
> switch 
> […]
> As part of the testing process for the ULS language settings, I
> included a task to test also the compact interlanguage designs. Users
> seem to understand their use (view recording), but I wanted to get
> some feedback for changes affecting such an important element.

Very nice job, congratulation. For the feedback:
- you may use a plain text label like "additional languages" instead of
a simple "…"
- when you start typing to filter then type backspace, you won't have a
less filtered list again, you have to hit the cross to clear the whole
entry.
- a totaly personal bias : I prefer broon icons like in Gnome instead of
cross, but cross I widely used so I guess it's not a usability issue

> 
> 
> Please let me know if you see any possible concern with this approach.
> 
> 
> 
> Thanks
> 
> 
> 
> 
> -- 
> Pau Giner
> Interaction Designer
> Wikimedia Foundation
> ___
> Design mailing list
> des...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/design


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

Re: [Wikitech-l] Moodle & Wikiversity - new Moodle plugin interfaces with MediaWiki

[Jan Luca]

Hi,

I have created the bug https://bugzilla.wikimedia.org/show_bug.cgi?id=47381 for 
this.

Best regards,
Jan

-Ursprüngliche Nachricht-
Von: wikitech-l-boun...@lists.wikimedia.org 
[mailto:wikitech-l-boun...@lists.wikimedia.org] Im Auftrag von Quim Gil
Gesendet: Donnerstag, 18. April 2013 17:34
An: wikitech-l@lists.wikimedia.org
Betreff: Re: [Wikitech-l] Moodle & Wikiversity - new Moodle plugin interfaces 
with MediaWiki

On 04/18/2013 07:14 AM, Jan Luca wrote:
> Hallo Sumana,
>
> I have created a section for creating a Moodle-extension for MW:
> https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#M
> ediaWiki-Moodle_extension
>
> It would be nice if somebody else would help with item 1 because I'm 
> not the best designer. There should be people with more experience than me.

Ok, at least with you there is enough technical expertise to get the project 
going if an interested student shows up.

Please create a related enhancement request in Bugzilla, under Mediawiki 
extensions >> Extension requests, and link it from the wiki entry.

Thank you for contributing your skills mentoring newcomers!

--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation 
http://www.mediawiki.org/wiki/User:Qgil

___
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] Making inter-language links shorter

[Brion Vibber]

I was traditionally in favor of keeping the full language list visible,
but it's just too damn big in many cases and is hard to search through
on any device. On touch devices it's difficult to pick a correct item from
the list as all the links are adjacent (though if you zoom it's ok).

Definitely we need something improved, and if we're going to improve it we
need to do it for the default or we're failing to serve 99% of our
readers...

I'm not sure about the current demo; one thing that bugs me is that there's
a very small tap/click target for getting the full language list call-out.
Clicking on "Language" just hides/shows the short list, it doesn't do
anything. Clicking the "settings" gear icon next to "Languages" brings up a
call-out with language-related settings none of which help you get to
another language version of the wiki.


On the mobile site we've collapsed the whole thing to an "Other languages"
section or button (depending on if you're in beta mode) at the bottom of
the article, and this seems to have gotten good usability responses from
mobile users.



On Thu, Apr 18, 2013 at 12:47 PM, David Gerard  wrote:

> On 18 April 2013 20:43, David Gerard  wrote:
> > On 18 April 2013 17:50, Pau Giner  wrote:
>
> >> Please let me know if you see any possible concern with this approach.
>
> > My first thought is of how upset people were when the first version of
> > Vector hid the language links by default. I would suggest being sure
> > there will be little or no similar objection.
>
>
> (hit send too soon, sorry)
>
> A simple solution that would avoid a similar reaction is: do not do
> this by default - make it only for logged-in users who want it that
> way.
>
> Possibly for default users, you could put the heuristically-calculated
> likely preferred languages at the top. But keeping the rest of the
> list below, right there on display, will (I predict) be favoured, as
> advertising the many languages of Wikipedia is a strongly-held value
> of many Wikimedians.
>
>
> - d.
>
> ___
> 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] Making inter-language links shorter

[David Gerard]

On 18 April 2013 20:43, David Gerard  wrote:
> On 18 April 2013 17:50, Pau Giner  wrote:

>> Please let me know if you see any possible concern with this approach.

> My first thought is of how upset people were when the first version of
> Vector hid the language links by default. I would suggest being sure
> there will be little or no similar objection.


(hit send too soon, sorry)

A simple solution that would avoid a similar reaction is: do not do
this by default - make it only for logged-in users who want it that
way.

Possibly for default users, you could put the heuristically-calculated
likely preferred languages at the top. But keeping the rest of the
list below, right there on display, will (I predict) be favoured, as
advertising the many languages of Wikipedia is a strongly-held value
of many Wikimedians.


- d.

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

Re: [Wikitech-l] Making inter-language links shorter

[David Gerard]

On 18 April 2013 17:50, Pau Giner  wrote:

> Please let me know if you see any possible concern with this approach.


My first thought is of how upset people were when the first version of
Vector hid the language links by default. I would suggest being sure
there will be little or no similar objection.


- d.

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

Re: [Wikitech-l] Making inter-language links shorter

[Petr Onderka]

There is a user script [1] that does a primitive version of this.
I have found it to be quite useful, so I think it's a good idea to do this
properly.

Petr Onderka
[[en:User:Svick]]

[1]: http://en.wikipedia.org/wiki/User:Lampak/MyLanguages


On Thu, Apr 18, 2013 at 6:50 PM, Pau Giner  wrote:

> As multilingual content grows, interlanguage links become longer on
> Wikipedia articles. Articles such as "Barak Obama" or "Sun" have more than
> 200 links, and that becomes a problem for users that often switch among
> several languages.
>
> As part of the future plans for the Universal Language Selector, we were
> considering to:
>
>- Show only a short list of the relevant languages for the user based on
>geo-IP, previous choices and browser settings of the current user. The
>language the users are looking for will be there most of the times.
>- Include a "more" option to access the rest of the languages for which
>the content exists with an indicator of the number of languages.
>- Provide a list of the rest of the languages that users can easily scan
>(grouped by script and region ao that alphabetical ordering is
> possible),
>and search (allowing users to search a language name in another
> language,
>using ISO codes or even making typos).
>
> I have created a prototype 
> to
> illustrate the idea. Since this is not connected to the MediaWiki backend,
> it lacks the advanced capabilities commented above but you can get the
> idea.
> If you are interested in the missing parts, you can check the flexible
> search and the list of likely languages ("common languages" section) on the
> language selector used at http://translatewiki.net/ which is connected to
> MediaWiki backend.
>
> As part of the testing process for the ULS language settings, I included a
> task to test also the compact interlanguage designs. Users seem to
> understand their use (view
> recording >),
> but I wanted to get some feedback for changes affecting such an important
> element.
>
> Please let me know if you see any possible concern with this approach.
>
> Thanks
>
>
> --
> Pau Giner
> Interaction Designer
> 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] Ideating on GSoC project : Mobilize Wikidata

[Jon Robson]

Pragun: It's still a work in progress.

I personally think it would be great to have different mobile skins as
all our projects have different needs and don't necessarily need
to/should look the same or behave the same.

I'd happily work closely to you (help with code review etc) to support
such a move.

If you were to take this approach you'd create an extension that
depends on MobileFrontend and extends SkinMobile / SkinMobileBase
class overriding certain functions. In a LocalSettings.php you'd be
able to configure it as the default mobile skin on your wiki.

You can check out the current state of the code/my mind here:
https://gerrit.wikimedia.org/r/#/c/58997/

On Thu, Apr 18, 2013 at 12:03 AM, Pragun Bhutani  wrote:
> I'll go ahead and request that Wikilabs account then. If I get stuck
> somewhere, I'll revert back to you.
>
> Also Jon, could you tell me a little more about your work on the skin? Is
> it possible for me to view the code?
>
> On Wed, Apr 17, 2013 at 9:43 PM, Jon Robson  wrote:
>
>> I've been doing some work on refactoring the mobile skin.
>>
>> In theory when I'm done doing this (I need some help code reviewing) you
>> would be able to write your own mobile skin with its own modules and own
>> scripts simply by extending some classes in MobileFrontend extension.
>>
>> Does this sound appealing at all?
>>  On 17 Apr 2013 08:02, "Brion Vibber"  wrote:
>>
>> > What you probably want to do is *integrate with* MobileFrontend, but keep
>> > your code within WikiBase extension and friends.
>> >
>> > There's provisions now for specifying desktop or mobile targets
>> separately
>> > in ResourceLoader, which will let you load either the same or different
>> CSS
>> > and JS for mobile views. You could also format your special pages
>> > differently, but I recommend doing the differences in CSS and JS if you
>> > can, to keep things clean.
>> >
>> > But you could also detect that mobile view is in use and change the
>> > formatting of a Special: page directly, for instance.
>> >
>> > From what I remember, the base HTML of the data editing forms is
>> relatively
>> > straightforward, but might not fit well on small screens, so definitely
>> > consider the user-interface needs of a ~320x480px screen when planning
>> what
>> > to do. :)
>> >
>> > -- brion
>> >
>> >
>> > On Wed, Apr 17, 2013 at 1:47 AM, Denny Vrandečić <
>> > denny.vrande...@wikimedia.de> wrote:
>> >
>> > > 2013/4/10 Pragun Bhutani 
>> > >
>> > > > Based on a discussion I had with YuviPanda and MaxSem on
>> > > #wikimedia-mobile,
>> > > > I've got a few things to add:
>> > > >
>> > > > - It might be a good idea to let Wikidata detect when it's being
>> > accessed
>> > > > through a mobile device and then have it adjust the widths and such
>> of
>> > > the
>> > > > box-structures accordingly and then pass them to MobileFrontend.
>> > > >
>> > > > Maybe we can set up a Wikilabs instance with MobileFrontend like Quim
>> > Gil
>> > > > suggested and then we can see how much work there is involved with
>> > trying
>> > > > to make WIkidata mobile-friendly.
>> > > >
>> > > > If we can get it to work with MobileFrontend, that'll be excellent
>> but
>> > if
>> > > > it turns out to be too complex or too dirty a solution, it would make
>> > > more
>> > > > sense to make a completely new extension for it.
>> > > >
>> > > >
>> > > I think that sounds like a good plan.
>> > >
>> > >
>> > > > Although the scope of the project is not very clear at the moment, I
>> > > think
>> > > > that a feasible implementation plan could be worked out with respect
>> to
>> > > the
>> > > > GSoC timeline and if it's required, I can continue to work on the
>> > project
>> > > > after GSoC ends.
>> > > >
>> > > >
>> > > I am glad to hear that. But I think it would be important to scope the
>> > > project so that it can be finished in GSoC time - but obviously,
>> further
>> > > work on it afterwards will be gladly appreciated.
>> > >
>> > > So, let's consider what should be working:
>> > > * create a mobile site for Wikidata
>> > > * displays the content in a layout that is more adequate for mobile
>> > devices
>> > > * retains different language versions
>> > > * Bonus: easy to edit
>> > >
>> > > First step would be to figure out the exact technology to use, i.e.
>> > whether
>> > > it would use the MobileFrontend or not, etc. We would help with setting
>> > it
>> > > up on labs.
>> > >
>> > > Cheers,
>> > > Denny
>> > >
>> > >
>> > > > On Tue, Apr 9, 2013 at 6:49 PM, Quim Gil  wrote:
>> > > >
>> > > > > On 04/09/2013 02:39 AM, Denny Vrandečić wrote:
>> > > > >
>> > > > >> I would hope
>> > > > >>
>> > > > >
>> > > > >  It would also be extremely good to look
>> > > > >>
>> > > > >
>> > > > > > I would assume
>> > > > >
>> > > > >  I don't think
>> > > > >>
>> > > > >
>> > > > > Can the Wikidata and Mobile teams please answer with the best of
>> your
>> > > > > knowledge to the questions at
>> > > > >
>> > > > > Bug 43065 - WikibaseRepo to be mobile friendly (t

Re: [Wikitech-l] Moodle & Wikiversity - new Moodle plugin interfaces with MediaWiki

[Scott MacLeod]

Hi Sumana, Jan, Quim and Wikimedia Developers,

I just wanted to let you know that:

MIT OCW-centric, free World University and School, in English, is
soft-launched ...
http://worlduniversityandschool.blogspot.com/2013/04/world-university-and-school-in-english.html...
for free (C.C.), online, MIT-centric, university degrees ...

and that WUaS has added and adds such "Moodle & Wikiversity - new Moodle
plugin interfaces with MediaWiki" ...  resources ... to 'Educational
Software' and http://worlduniversity.wikia.com/wiki/Educational_Softwareand
'Courses and Schools' ...
http://worlduniversity.wikia.com/wiki/Courses .

If you are a high school student actively interested in applying to free,
online, Creative Commons' licensed, MIT OCW-centric World University and
School in English, or know of one, this autumn 2013 - with complete
applications due by January 1, 2014, at 12 pm Pacific Time - please email
WUaS now at - worlduniversityandsch...@gmail.com - with a brief letter just
saying you're interested.

Here's the link to the developing Admissions office at WUaS page -
http://worlduniversity.wikia.com/wiki/Admissions_at_World_University_and_School
.

Best,
Scott





On Thu, Apr 18, 2013 at 8:33 AM, Quim Gil  wrote:

> On 04/18/2013 07:14 AM, Jan Luca wrote:
>
>> Hallo Sumana,
>>
>> I have created a section for creating a Moodle-extension for MW:
>> https://www.mediawiki.org/**wiki/Mentorship_programs/**
>> Possible_projects#MediaWiki-**Moodle_extension
>>
>> It would be nice if somebody else would help with item 1 because I'm not
>> the
>> best designer. There should be people with more experience than me.
>>
>
> Ok, at least with you there is enough technical expertise to get the
> project going if an interested student shows up.
>
> Please create a related enhancement request in Bugzilla, under Mediawiki
> extensions >> Extension requests, and link it from the wiki entry.
>
> Thank you for contributing your skills mentoring newcomers!
>
> --
> Quim Gil
> Technical Contributor Coordinator @ Wikimedia Foundation
> http://www.mediawiki.org/wiki/**User:Qgil
>
>
> __**_
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/**mailman/listinfo/wikitech-l
>



-- 
http://scottmacleod.com/worlduniversityandschool.htm

This email is intended only for the use of the individual or entity to
which it is addressed and may contain information that is privileged and
confidential. If the reader of this email message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication is prohibited. If you have received this
email in error, please notify the sender and destroy/delete all copies of
the transmittal. Thank you.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New labs project request -- Wikivoyage

[Andrew Bogott]

Roger --

On 4/18/13 12:26 PM, rogerchris...@gmail.com wrote:

Could a labs admin please add me, 'rogerhc', to the Bastion[1] labs project?

I need Bastion membership in order to access the Wikivoyage[2] labs
project I am a member of.


You are already a member of both projects;  users are automatically 
added to bastion when they get shell rights.


If you're having trouble with access, best to start here 
https://wikitech.wikimedia.org/wiki/Help:Access  and then look for help 
in the #wikimedia-labs channel on IRC.


-Andrew


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

Re: [Wikitech-l] New labs project request -- Wikivoyage

[rogerchrisman]

Could a labs admin please add me, 'rogerhc', to the Bastion[1] labs project?

I need Bastion membership in order to access the Wikivoyage[2] labs
project I am a member of.

1. https://wikitech.wikimedia.org/wiki/Nova_Resource:Bastion
2. https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikivoyage

Thanks,

Roger
https://wikitech.wikimedia.org/wiki/User:Rogerhc

On Wed, Apr 17, 2013 at 8:57 PM,   wrote:
> Andrew, also could you add me, 'rogerhc', to the Bastion labs project?
>
> Thanks,
>
> Roger
> https://wikitech.wikimedia.org/wiki/User:Rogerhc
>
> On Wed, Apr 17, 2013 at 5:14 PM,   wrote:
>> Andrew, where can I locate the new Wikivoyage labs project? I don't see it 
>> here:
>>
>> https://wikitech.wikimedia.org/wiki/Special:Ask/-5B-5BResource-20Type::project-5D-5D/-3F/-3FMember/-3FDescription/mainlabel%3D-2D
>>
>> Also, https://wikitech.wikimedia.org/wiki/New_Project_Request/Wikivoyage
>> still says:
>>"Has this request been completed by an admin? No"
>>
>> Perhaps this is not "Done" done?
>>
>> Roger
>>
>> On Wed, Apr 17, 2013 at 5:01 PM,   wrote:
>>> Labs project Wikivoyage is experimental, for prototyping, testing and
>>> showcasing feature ideas to the Wikivoyage community. Only after
>>> community approval of a particular showcased feature would that
>>> feature progress to Deployment-prep. Right?
>>>
>>> We Wikivoyagers are new to this Labs resource; please do help clue us in.
>>>
>>> Roger
>>>
>>> On Wed, Apr 17, 2013 at 1:22 PM, Max Semenik  wrote:
 On 17.04.2013, 23:55 Roger wrote:

> Hi,

> Could someone with approval authority please process this new labs
> project request:

> https://wikitech.wikimedia.org/wiki/New_Project_Request/Wikivoyage

 How is it different from deployment-prep?


 --
 Best regards,
   Max Semenik ([[User:MaxSem]])


 ___
 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] MediaWiki for 3rd parties: two useful projects

[Mark A. Hershberger]

On 04/18/2013 12:24 PM, Quim Gil wrote:
>> 2) http://wikiapiary.com A wiki with various statistics about MediaWiki
>> installations and statistics about extensions. I see the huge
>> potential in
>> this project although it's only several months old. Template:Extension on
>> mediawiki.org have finally turned to something useful when the link to
>> wikiapiary had been added there.
> 
> I'm also impressed about this project. It's so good that I wondered who
> made it, why and with which resources.  :)

I contacted the creator of the project yesterday and got an initial
response.  I have some ideas that could really use a site like
WikiApiary -- hopefully, I'll have something more concrete by the time
we get to Amsterdam.

> For instance, it would be great to get
> mwusers.com involved in activities around improving QA or documentation.
> This would save them some users posting questions about the same
> problems originated by some problem in MediaWiki or mediawiki.org.

I've started a thread on mwusers about this.

Here's to a better MediaWiki community!


-- 
http://hexmode.com/

Imagination does not breed insanity. Exactly what does breed insanity
is reason. Poets do not go mad; but chess-players do.
-- G.K. Chesterson

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

[Wikitech-l] Making inter-language links shorter

[Pau Giner]

As multilingual content grows, interlanguage links become longer on
Wikipedia articles. Articles such as "Barak Obama" or "Sun" have more than
200 links, and that becomes a problem for users that often switch among
several languages.

As part of the future plans for the Universal Language Selector, we were
considering to:

   - Show only a short list of the relevant languages for the user based on
   geo-IP, previous choices and browser settings of the current user. The
   language the users are looking for will be there most of the times.
   - Include a "more" option to access the rest of the languages for which
   the content exists with an indicator of the number of languages.
   - Provide a list of the rest of the languages that users can easily scan
   (grouped by script and region ao that alphabetical ordering is possible),
   and search (allowing users to search a language name in another language,
   using ISO codes or even making typos).

I have created a prototype  to
illustrate the idea. Since this is not connected to the MediaWiki backend,
it lacks the advanced capabilities commented above but you can get the idea.
If you are interested in the missing parts, you can check the flexible
search and the list of likely languages ("common languages" section) on the
language selector used at http://translatewiki.net/ which is connected to
MediaWiki backend.

As part of the testing process for the ULS language settings, I included a
task to test also the compact interlanguage designs. Users seem to
understand their use (view
recording),
but I wanted to get some feedback for changes affecting such an important
element.

Please let me know if you see any possible concern with this approach.

Thanks


-- 
Pau Giner
Interaction Designer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[Mono]

When will commons.wikimedia get Echo?


On Thu, Apr 18, 2013 at 9:33 AM, Greg Grossmeier  wrote:

> As always, a correction:
>
> 
> > * Echo will be rolling out on en, de, and fr wiki next week on Thursday
> >   (the 25th)
>
> Notifications (formally "Echo") will only be deployed to English
> Wikipedia, not German nor French, next week on April 25th.
>
> My apologies,
>
> Greg
>
> --
> | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
> | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D |
>
> ___
> 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] WMF Engineering Roadmap Update - 20130417

[Greg Grossmeier]

As always, a correction:


> * Echo will be rolling out on en, de, and fr wiki next week on Thursday
>   (the 25th)

Notifications (formally "Echo") will only be deployed to English
Wikipedia, not German nor French, next week on April 25th.

My apologies,

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @gregA18D 1138 8E47 FAC8 1C7D |

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

Re: [Wikitech-l] MediaWiki for 3rd parties: two useful projects

[Quim Gil]

Hi Yuri, thank you for bringing up this.

On 04/17/2013 09:25 AM, Yury Katkov wrote:

Hi everyone!
So we've had some discussions that are summarized here:
http://www.mediawiki.org/wiki/Third-party_MediaWiki_users_discussion/Summary

In this letter I want to point out to two projects that haven't been
organized by Wikimedias, but are still very useful for the people who think
about MW as of open source product:
1) http://www.mwusers.com - MediaWiki forum. Many people prefer forums to
mailing lists and wikipages like Support desk. Moreover, MWusers is now a
good Q&A database.


Yes, a very useful community that solved promptly all my problems as a 
3rd party MediaWiki superamateur sysadmin.


They are referenced in many pages. If you have other ideas just propose, 
or edit directly.


http://www.mediawiki.org/w/index.php?search=mwusers&title=Special%3ASearch


2) http://wikiapiary.com A wiki with various statistics about MediaWiki
installations and statistics about extensions. I see the huge potential in
this project although it's only several months old. Template:Extension on
mediawiki.org have finally turned to something useful when the link to
wikiapiary had been added there.


I'm also impressed about this project. It's so good that I wondered who 
made it, why and with which resources.  :)


http://www.mediawiki.org/wiki/Template:Extension has a field for it, and 
therefore plenty of extensions link to it through "Check usage and 
version matrix".



If WMF/Wikimedias interested in promoting MediaWiki not as WMF project but
as a piece of open source software, it can be beneficial to help those
projects with information support (i.e links from MediaWiki.org), funding
and cooperation.


Content and links in mediawiki.org: just do it, right? The WMF as such 
doesn't play a big role deciding here and each of us documents whatever 
is related with our work and whatever we still have some time to improve 
- just like anybody else.


Funding: the same doors are just as open for these initiatives as for 
anybody else. https://meta.wikimedia.org/wiki/Grants:Start


Cooperation: any ideas? For instance, it would be great to get 
mwusers.com involved in activities around improving QA or documentation. 
This would save them some users posting questions about the same 
problems originated by some problem in MediaWiki or mediawiki.org.


--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil

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

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[Greg Grossmeier]

Hello Mathieu,


> Le 2013-04-17 20:06, Greg Grossmeier a écrit :
> >* Echo will be rolling out on en, de, and fr wiki next week on
> >Thursday
> >  (the 25th)
> 
> On all Mediawiki projects, or just on some of them like Wikipedia?

Just the English, German, and French Wikipedias.

The Notifications (formerly "Echo") project team does a pretty good job
of keeping this etherpad up to date with their planned deployments:
http://etherpad.wikimedia.org/echo-release

> >Full roadmap at:
> >
> >https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Aoizbfxc5g6KdEkza0xkQnJlM0o0TXlwQXhDOUFvYnc#gid=0
> 
> Would it be possible to use free software solutions, which is not
> the case of the google spreadsheet as far as I know.

We (myself plus the Engineering Managers) were just talking about this
yesterday during the Roadmap Update Meeting (the meeting that happens
right before I send out this email).

Robla has a very very rough script that will (hopefully, someday)
convert the GDoc into a MediaWiki table that lives on mediawiki.org.
He's only working at it sporadically, unfortunately.

So, yes, we completely agree. From my understanding, the home of this
information was previously a mediawiki.org table, but that became too
unruly when the size of it and the number of people simultaneously
editing it caused usability problems. I can safely say that we aren't
happy with the non-Freeness of GDocs and we wish we didn't use it in
this case, but it was a stop-gap solution, and we fully intend on
something else (big F Free) replacing it when we know what will meet our
needs.

> Depending on
> the feature needed, EtherCalc may be used instead of the current
> solution. Other free/libre culture advocates, like the French
> framasoft[2] network are already using it, see [3].

Wow! Thanks! I have to admit, I haven't put in any real time searching
for a replacement, but these might be able to do it.

I'll work on copying over the current version of the Roadmap to
ethercalc today/tomorrow.

Actually, if anyone wants to help:
https://ethercalc.org/WMF_Engineering_Roadmap

I *think* all of the content is copied over, but the formatting needs
some work ;-).  I didn't see an "import from CSV/xsl" function, but if I
missed that, it might be worth a shot.

No promises from our end, yet (as I don't know if we tried this already
and decided against it for some reason), but this is a great option,
thank you Mathieu!

Greg

-- 
| Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @gregA18D 1138 8E47 FAC8 1C7D |

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

Re: [Wikitech-l] Moodle & Wikiversity - new Moodle plugin interfaces with MediaWiki

[Quim Gil]

On 04/18/2013 07:14 AM, Jan Luca wrote:

Hallo Sumana,

I have created a section for creating a Moodle-extension for MW:
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#MediaWiki-Moodle_extension

It would be nice if somebody else would help with item 1 because I'm not the
best designer. There should be people with more experience than me.


Ok, at least with you there is enough technical expertise to get the 
project going if an interested student shows up.


Please create a related enhancement request in Bugzilla, under Mediawiki 
extensions >> Extension requests, and link it from the wiki entry.


Thank you for contributing your skills mentoring newcomers!

--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil

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

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[K. Peachey]

On Fri, Apr 19, 2013 at 1:10 AM, Mark A. Hershberger  wrote:
> Wow, thank you for pointing to Framasoft.  Looks like they've got some
> really useful stuff going on there.

Could be done very easily and neatly in a MediaWiki page...

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

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[Mark A. Hershberger]

On 04/18/2013 04:26 AM, Mathieu Stumpf wrote:
> Would it be possible to use free software solutions, which is not the
> case of the google spreadsheet as far as I know. Depending on the
> feature needed, EtherCalc may be used instead of the current solution.
> Other free/libre culture advocates, like the French framasoft[2] network
> are already using it, see [3].
> 
> [1] https://ethercalc.org/
> [2] https://fr.wikipedia.org/wiki/Framasoft (Sorry, no English
> translation yet)
> [3] http://framacalc.org/_start

Wow, thank you for pointing to Framasoft.  Looks like they've got some
really useful stuff going on there.

-- 
http://hexmode.com/

Imagination does not breed insanity. Exactly what does breed insanity
is reason. Poets do not go mad; but chess-players do.
-- G.K. Chesterson

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

Re: [Wikitech-l] Article on API Characteristics

[Brian Wolff]

On 2013-04-18 1:13 AM, "Petr Kadlec"  wrote:
>
> On 17 April 2013 22:33, Brian Wolff  wrote:
>
> > My understanding is its not really possible to do this in php in a way
> > that would actually be of use to anyone. See
> > https://bugzilla.wikimedia.org/show_bug.cgi?id=26631#c1
> >
>
> Still, supporting this in a way “that wouldn’t be of use”, i.e. send the
> 100 status immediately instead of 417 would probably make it a tiny bit
> easier for clients. However, this is not a bug/problem/feature-request for
> MediaWiki, but for Squid. It seems Apache&PHP would handle this correctly,
> but Squid rejects such requests. There is a configuration variable doing
> exactly what Svick is proposing <
> http://www.squid-cache.org/Doc/config/ignore_expect_100/>, but I agree
> turning it on would not be a good idea. And FYI: Squid 3.2 seems to
support
> 100-continue somehow, but not sure how much. <
> http://wiki.squid-cache.org/Features/HTTP11>
>
> -- [[cs:User:Mormegil | Petr Kadlec]]
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l

I disagree. If we supported it, people will expect it to actually work, and
add the extra complexity to support 100 continue to their bots. This would
be bad since it would essentially be a no-op and just slow things down.

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

Re: [Wikitech-l] 1.21.0rc3 -- more bug fixes and testing

[Mark A. Hershberger]

On 04/18/2013 12:16 AM, MZMcBride wrote:
> Sorry to add to the pile, but  must
> be fixed before MediaWiki 1.21 is released, as far as I'm concerned.

No problem.  [[User:PleaseStand]] has been on top of that and already
submitted the necessary reversion: https://gerrit.wikimedia.org/r/59624/

-- 
http://hexmode.com/

Imagination does not breed insanity. Exactly what does breed insanity
is reason. Poets do not go mad; but chess-players do.
-- G.K. Chesterson

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

Re: [Wikitech-l] Moodle & Wikiversity - new Moodle plugin interfaces with MediaWiki

[Jan Luca]

Hallo Sumana,

I have created a section for creating a Moodle-extension for MW:
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#MediaWi
ki-Moodle_extension

It would be nice if somebody else would help with item 1 because I'm not the
best designer. There should be people with more experience than me.

Best regards,
Jan 

-Ursprüngliche Nachricht-
Von: Sumana Harihareswara [mailto:suma...@wikimedia.org] 
Gesendet: Mittwoch, 17. April 2013 23:47
An: Jan Luca Naumann
Cc: Wikimedia developers; 'w vk'
Betreff: Re: AW: Moodle & Wikiversity - new Moodle plugin interfaces with
MediaWiki

Jan, thank you for working on this!  If you are willing to mentor a student
or new contributor in working on items 1 or 2, maybe you could add some
details about what would be desired and add them to
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects .

Thanks,
Sumana

On 04/17/2013 02:01 AM, Jan Luca wrote:
> Hallo Sumana,
> 
> thank you for your support. I have added Wvk in CC so he will get the 
> messages, too.
> 
> The main part of the Moodle-plugin is ready but I have thought about 
> some others things that we could do:
> 
> 1. Create a Wikiversity Moodle-theme
> 2. Create a MW-extension which shows some information about a 
> Moodle-course in a wiki page 3. Add another admin for Moodle and the 
> Labs project (wikiversity-sandbox)
> 
> About localisation: I already planned to contact the people from 
> translatewiki.net to ask if they could add my plugin
> 
> About testing: http://sandbox.wikiversity.wmflabs.org/moodle is open 
> for everybody to use and test it. I would be happy when as many as 
> possible would test the plugin and report bugs to me.
> 
> Best regards,
> Jan
> 
> -Ursprüngliche Nachricht-
> Von: Sumana Harihareswara [mailto:suma...@wikimedia.org]
> Gesendet: Dienstag, 16. April 2013 22:09
> An: Wikimedia developers; Jan Luca Naumann
> Betreff: Moodle & Wikiversity - new Moodle plugin interfaces with 
> MediaWiki
> 
> https://outreach.wikimedia.org/wiki/Education_Portal/Newsletter/April_
> 2013/W
> ikiversity_and_Moodle
> 
> "Moodle is a free and open source learning management system (LMS).
> James Neill has made some valuable contributions about how Moodle can 
> be used in conjunction with Wikiversity as a platform for open education.
> To minimise the need for exporting/importing content from one learning 
> management system (LMS) class site to another and then to another 
> institution Wikiversity may be used as an open educational content 
> repository.
> 
> A moodle-plugin has been developed by Jan Luca (German Wikiversity) to 
> include content into Moodle hosted on Wikiversity by using a simple tag:
> [Include-WV][/Include-WV]. The plug-in can be tested on 
> http://sandbox.wikiversity.wmflabs.org/moodle. For further information 
> contact Jan Luca or Wvk. This move is part of an initiative to restart 
> German Wikiversity that seeks to invite new contributors to the project."
> 
> Thanks for working on this, Jan Luca and Wyk! I see the code is at 
> https://github.com/JanLuca/Moodle_Wikiversity_plugin .  Are you 
> looking for help of any sort -- design, testing, localisation, etc.?
> --
> Sumana Harihareswara
> Engineering Community Manager
> Wikimedia Foundation
> 



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

[Wikitech-l] Looking for a GsoC mentor (Wikisource, Djvu)

[David Cuenca]

Hi!

I'm looking for a co-mentor for this project:
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Merge_proofread_text_back_into_Djvu_files

There is already someone that would be giving guidance on Tesseract OCR,
now I'm looking for a second mentor to advise on Mediawiki issues.
A student has shown interest in this project already.

Anyone up to mentoring? :-)

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

Re: [Wikitech-l] Bugzilla Weekly Report

[Željko Filipin]

On Wed, Apr 17, 2013 at 8:23 PM, Andre Klapper wrote:

> https://gerrit.wikimedia.org/r/#/c/59656/


Hi Andre,

I have white belt in SQL-fu so I am really not the right person to review
the code. Also, Quim was the one requesting the change, he will know more
about what changes to output are required.

Could you provide the output that the new SQL script would generate?

Thanks,

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

Re: [Wikitech-l] WMF Engineering Roadmap Update - 20130417

[Mathieu Stumpf]

Le 2013-04-17 20:06, Greg Grossmeier a écrit :
Hello and welcome to the latest edition of the WMF Engineering 
Roadmap

Update.


Highlights include:
* Mobile resubmitted to AppStore yesterday, still waiting on the 
Apple

  Geniuses to approve ;)

* QA is turning all the tests running against betalabs green (they 
were

  red from unexpected config differences); they're close.

* Echo will be rolling out on en, de, and fr wiki next week on 
Thursday

  (the 25th)


On all Mediawiki projects, or just on some of them like Wikipedia?



Full roadmap at:

https://docs.google.com/a/wikimedia.org/spreadsheet/ccc?key=0Aoizbfxc5g6KdEkza0xkQnJlM0o0TXlwQXhDOUFvYnc#gid=0


Would it be possible to use free software solutions, which is not the 
case of the google spreadsheet as far as I know. Depending on the 
feature needed, EtherCalc may be used instead of the current solution. 
Other free/libre culture advocates, like the French framasoft[2] network 
are already using it, see [3].


[1] https://ethercalc.org/
[2] https://fr.wikipedia.org/wiki/Framasoft (Sorry, no English 
translation yet)

[3] http://framacalc.org/_start


--
Association Culture-Libre
http://www.culture-libre.org/

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

Re: [Wikitech-l] Article on API Characteristics

[Petr Kadlec]

On 17 April 2013 22:33, Brian Wolff  wrote:

> My understanding is its not really possible to do this in php in a way
> that would actually be of use to anyone. See
> https://bugzilla.wikimedia.org/show_bug.cgi?id=26631#c1
>

Still, supporting this in a way “that wouldn’t be of use”, i.e. send the
100 status immediately instead of 417 would probably make it a tiny bit
easier for clients. However, this is not a bug/problem/feature-request for
MediaWiki, but for Squid. It seems Apache&PHP would handle this correctly,
but Squid rejects such requests. There is a configuration variable doing
exactly what Svick is proposing <
http://www.squid-cache.org/Doc/config/ignore_expect_100/>, but I agree
turning it on would not be a good idea. And FYI: Squid 3.2 seems to support
100-continue somehow, but not sure how much. <
http://wiki.squid-cache.org/Features/HTTP11>

-- [[cs:User:Mormegil | Petr Kadlec]]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Ideating on GSoC project : Mobilize Wikidata

[Pragun Bhutani]

I'll go ahead and request that Wikilabs account then. If I get stuck
somewhere, I'll revert back to you.

Also Jon, could you tell me a little more about your work on the skin? Is
it possible for me to view the code?

On Wed, Apr 17, 2013 at 9:43 PM, Jon Robson  wrote:

> I've been doing some work on refactoring the mobile skin.
>
> In theory when I'm done doing this (I need some help code reviewing) you
> would be able to write your own mobile skin with its own modules and own
> scripts simply by extending some classes in MobileFrontend extension.
>
> Does this sound appealing at all?
>  On 17 Apr 2013 08:02, "Brion Vibber"  wrote:
>
> > What you probably want to do is *integrate with* MobileFrontend, but keep
> > your code within WikiBase extension and friends.
> >
> > There's provisions now for specifying desktop or mobile targets
> separately
> > in ResourceLoader, which will let you load either the same or different
> CSS
> > and JS for mobile views. You could also format your special pages
> > differently, but I recommend doing the differences in CSS and JS if you
> > can, to keep things clean.
> >
> > But you could also detect that mobile view is in use and change the
> > formatting of a Special: page directly, for instance.
> >
> > From what I remember, the base HTML of the data editing forms is
> relatively
> > straightforward, but might not fit well on small screens, so definitely
> > consider the user-interface needs of a ~320x480px screen when planning
> what
> > to do. :)
> >
> > -- brion
> >
> >
> > On Wed, Apr 17, 2013 at 1:47 AM, Denny Vrandečić <
> > denny.vrande...@wikimedia.de> wrote:
> >
> > > 2013/4/10 Pragun Bhutani 
> > >
> > > > Based on a discussion I had with YuviPanda and MaxSem on
> > > #wikimedia-mobile,
> > > > I've got a few things to add:
> > > >
> > > > - It might be a good idea to let Wikidata detect when it's being
> > accessed
> > > > through a mobile device and then have it adjust the widths and such
> of
> > > the
> > > > box-structures accordingly and then pass them to MobileFrontend.
> > > >
> > > > Maybe we can set up a Wikilabs instance with MobileFrontend like Quim
> > Gil
> > > > suggested and then we can see how much work there is involved with
> > trying
> > > > to make WIkidata mobile-friendly.
> > > >
> > > > If we can get it to work with MobileFrontend, that'll be excellent
> but
> > if
> > > > it turns out to be too complex or too dirty a solution, it would make
> > > more
> > > > sense to make a completely new extension for it.
> > > >
> > > >
> > > I think that sounds like a good plan.
> > >
> > >
> > > > Although the scope of the project is not very clear at the moment, I
> > > think
> > > > that a feasible implementation plan could be worked out with respect
> to
> > > the
> > > > GSoC timeline and if it's required, I can continue to work on the
> > project
> > > > after GSoC ends.
> > > >
> > > >
> > > I am glad to hear that. But I think it would be important to scope the
> > > project so that it can be finished in GSoC time - but obviously,
> further
> > > work on it afterwards will be gladly appreciated.
> > >
> > > So, let's consider what should be working:
> > > * create a mobile site for Wikidata
> > > * displays the content in a layout that is more adequate for mobile
> > devices
> > > * retains different language versions
> > > * Bonus: easy to edit
> > >
> > > First step would be to figure out the exact technology to use, i.e.
> > whether
> > > it would use the MobileFrontend or not, etc. We would help with setting
> > it
> > > up on labs.
> > >
> > > Cheers,
> > > Denny
> > >
> > >
> > > > On Tue, Apr 9, 2013 at 6:49 PM, Quim Gil  wrote:
> > > >
> > > > > On 04/09/2013 02:39 AM, Denny Vrandečić wrote:
> > > > >
> > > > >> I would hope
> > > > >>
> > > > >
> > > > >  It would also be extremely good to look
> > > > >>
> > > > >
> > > > > > I would assume
> > > > >
> > > > >  I don't think
> > > > >>
> > > > >
> > > > > Can the Wikidata and Mobile teams please answer with the best of
> your
> > > > > knowledge to the questions at
> > > > >
> > > > > Bug 43065 - WikibaseRepo to be mobile friendly (tracking)
> > > > > https://bugzilla.wikimedia.**org/show_bug.cgi?id=43065<
> > > > https://bugzilla.wikimedia.org/show_bug.cgi?id=43065>
> > > > >
> > > > > Beyond hope and believe, the fact is that I couldn't get any answer
> > > more
> > > > > precise than "Interesting" when asking about this project to people
> > in
> > > > > those teams. And as for today I'm not confident to tell to a
> > candidate
> > > > like
> > > > > Pragun whether this project is too complex or too simple, and where
> > the
> > > > > complexity/simplicity relies.
> > > > >
> > > > > In case of doubt I'd prefer to play safe and actually not encourage
> > > GSOC
> > > > /
> > > > > OPW to apply for a project like this, before we regret around
> August.
> > > > >
> > > > > Is it possible to have a Wikidata / WikidataRepo test instance
> > > somewhere
> > > > > with MobileFront