svetlana | 1 Sep 15:20 2014
Picon

Is simplicity is the key to success of Echo and Watchlist?

Hi all.

I'm including some thoughts on Echo below.
- *it* *doesn't* *scale* (constantly seeing a "(3)" or new emails pop up if you're active in ~6 discussions
is a pain)
- _nothing_ on-wiki ever warrants an urgent reaction ever
- distracting, especially as I'm getting more active with talking
- this last point caused me to switch it off entirely everywhere
- I'm reading an article to get more information and this piece of software drags me back into editing while
I'm merely reading something and intend to return to the watchlist in the evening
- Echo a consequence of newcomers being insufficiently communicated to (i.e. too few helpers involved
talking with newcomers at big wikis, let's automate that - NO! THAT's STUPID! have it semi-automated --
the entire wiki software should be centered around a big edit box and a less prominent, but comfortable,
box for leaving custom messages to articles and users talk pages)
- Echo is a consequence of a watchlist page which many people find insufficiently informative, intuitive,
or easy to control.
- special:watchlist and special:notifications overlap in functionality
- the 'notifications' tab lacks a 'watchlist' column so that I can choose where events go (email, echo's
nagging, or watchlist passively)
- the extra term ('notifications') is clutter
- please consider improving usability of the watchlist and integrating any echo fields into it
- and make watchlist easier to manage
- integrate these two tools together
- echo is really conceptually merely a new channel where to pipe watchlist items
- simplicity is the key to success

svetlana

--
(original rant attached for reference)
(Continue reading)

reporter | 1 Sep 05:00 2014
Picon

Bugzilla Weekly Report

MediaWiki Bugzilla Report for August 25, 2014 - September 01, 2014

Status changes this week

Reports changed/set to UNCONFIRMED:  9                             
Reports changed/set to NEW        :  24                            
Reports changed/set to ASSIGNED   :  29                            
Reports changed/set to REOPENED   :  16                            
Reports changed/set to PATCH_TO_RE:  82                            
Reports changed/set to RESOLVED   :  280                           
Reports changed/set to VERIFIED   :  1                             

Total reports still open              : 15607                         
Total bugs still open                 : 9472                          
Total non-lowest prio. bugs still open: 9143                          
Total enhancements still open         : 6135                          

Reports created this week: 275                           

Resolutions for the week:

Reports marked FIXED     :  178                           
Reports marked DUPLICATE :  25                            
Reports marked INVALID   :  24                            
Reports marked WORKSFORME:  23                            
Reports marked WONTFIX   :  25                            

Specific Product/Component Resolutions & User Metrics 

Created reports per component
(Continue reading)

Andre Klapper | 31 Aug 21:33 2014
Picon

UploadWizard bug triage on Sep 09, 17:00UTC

Heja everybody,

you are invited to join us on the next Bugday:

 Tuesday, September 09, 2014, 17:00 to 19:00UTC [1]
    in #wikimedia-multimedia on Freenode IRC [2]

We will take a look at open Bugzilla tickets for UploadWizard.

Everyone is welcome to join. No technical knowledge needed! 
It's an easy way to get involved or to give something back.

More information can be found here:
  https://www.mediawiki.org/wiki/Bug_management/Triage/20140909

For more information on triaging in general, check out 
  https://www.mediawiki.org/wiki/Bug_management/Triage

See you there?

andre

[1] Timezone converter:
    http://www.timeanddate.com/worldclock/converter.html
[2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC
--

-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/

_______________________________________________
(Continue reading)

Thomas Mulhall | 31 Aug 15:51 2014
Picon

Updating jQuery Choosen to 1.1.0

Hi I would like to ask those who use jquery.choosen to start updating there extensions that use it because
the change will deprecate some functions, or remove them it also changes the css code. 

Main thing about the update is a speed increase.

please review change here

gerrit.wikimedia.org/r/#/c/139699/
_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Bartosz Dziewoński | 30 Aug 17:13 2014
Picon

Code review in mediawiki/skins/Vector and friends

Hi all,

I'd like to remind everyone that we now have WMF-deployed code in the  
mediawiki/skins/* repository group, most importantly in  
mediawiki/skins/Vector (but also MonoBook, Modern, CologneBlue). It seems  
that patches proposed and merged there are getting a lot less review (and  
fewer reviewers) than they used to while the skins were in core.

Please update your review subscriptions :) There are at least two ways to  
subscribe to incoming changes:

* Publicly at https://www.mediawiki.org/wiki/Git/Reviewers
* Sneakily at https://gerrit.wikimedia.org/r/#/settings/projects

--

-- 
Matma Rex

_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
svetlana | 30 Aug 12:26 2014
Picon

Watchlist and Echo

Hi all.

I've noticed Echo has a separate special page, Special:Notifications. Would we like to rewrite the
extension so that it adds entries to the watchlist instead? (And add 'Edits' tab into echo itself - put the
watchlist items there).

There is a lot of Special: pages already and adding new ones doesn't - immediately - appear to help usability.

svetlana

_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Ori Livneh | 30 Aug 03:53 2014
Picon

+2 in mediawiki/core for Kevin Israel

Kevin Israel (User:PleaseStand) now has +2 in mediawiki/core, following a
successful nomination by MZMcBride[1]. Congratulations! :)

[1]:
https://www.mediawiki.org/w/index.php?title=Gerrit/Project_ownership&oldid=1072656
_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Seb35 | 29 Aug 20:25 2014
Picon

Static functions usable in LocalSettings.php

Hello,

Sometimes in LocalSettings.php or in extensions settings one want to do simple computations on the
namespaces or related to the Git branch in a development environment. Unfortunately this is not (resp. no
more) really possible, because LocalSettings.php is loaded before GlobalFunctions.php and Setup.php.

Is it a good practice to do that? If yes, is it possible to either:
* "tag" some static functions in some classes to avoid these to include hooks and other global functions and
variables (loaded later), and/or
* move before (in loading order) some global functions and variables to make them usable (e.g. wfDebugLog,
wfRunHooks, $wgCanonicalNamespaceNames)
?

Details for namespaces: $wgCanonicalNamespaceNames is defined in Setup.php, making
MWNamespace::getCanonicalNamespaces() and MWNamespace::getValidNamespaces() unusable in
LocalSettings.php to e.g. compute namespaces where an extension could be enabled <https://github.com/mementoweb/mediawiki/pull/2>.

Details for Git version: until two months it worked, but some wfDebugLog was introduced (defined in
GlobalFunctions.php), making it unusable in LocalSettings.php.

~ Seb35 [^_^]

_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Thomas Mulhall | 29 Aug 13:48 2014
Picon

Upgrading jQuery UI to 1.11.1

Hi should we upgrade jQuery UI to 1.11.1 since mediawiki droped support for javascript for internet
explorer 6 and might drop javascript for internet explorer 7.
_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Aran | 28 Aug 23:29 2014
Picon

Re: Parsoid

Thanks I was able to use the equivs package to get parsoid to run
properly - I also then found the following link in some fine print on MW
Parsoid/Setup page which works too:
https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager

On 28/08/14 12:46, Brad Jorsch (Anomie) wrote:
> On Thu, Aug 28, 2014 at 11:25 AM, Aran <aran <at> organicdesign.co.nz> wrote:
>
>> I'm trying to install parsoid on Ubuntu 12. I installed nodejs from
>> source, but when I try and install parsoid via apt-get it fails saying
>> that it depends on nodejs (>= 0.8.0) even though node --version returns
>> v0.10.31!
>>
>> Anyone have any ideas what could be wrong?
>>
> The package manager doesn't know anything about software you manually
> installed.
>
> The ideal thing to do would be to just install the nodejs package: I see
> Ubuntu trusty has 0.10.25, and Debian has 0.10.29 in both testing and
> unstable. You may be able to just download the source package and rebuild
> it for precise.
>
> Or you could try using the "equivs" package to fake out the package manager.
>
>

_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
(Continue reading)

Gabriel Wicke | 28 Aug 18:23 2014
Picon

Re: Parsoid

On 08/28/2014 08:46 AM, Brad Jorsch (Anomie) wrote:
> On Thu, Aug 28, 2014 at 11:25 AM, Aran <aran <at> organicdesign.co.nz> wrote:
> 
>> I'm trying to install parsoid on Ubuntu 12. I installed nodejs from
>> source, but when I try and install parsoid via apt-get it fails saying
>> that it depends on nodejs (>= 0.8.0) even though node --version returns
>> v0.10.31!
>>
>> Anyone have any ideas what could be wrong?
>>
> 
> The package manager doesn't know anything about software you manually
> installed.
> 
> The ideal thing to do would be to just install the nodejs package: I see
> Ubuntu trusty has 0.10.25, and Debian has 0.10.29 in both testing and
> unstable.

+1 for using the regular package rather than a manual install from source.
Normally the right nodejs package should be automatically pulled in when you
install parsoid from the repository as described in [1]. What happens when
you just do a 'apt-get install nodejs' ?

Gabriel

[1]: https://www.mediawiki.org/wiki/Parsoid/Setup#Ubuntu_.2F_Debian_on_amd64

_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
(Continue reading)


Gmane