[Wikitech-l] 1.20 RC Tarball

[Mark A. Hershberger]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

It is a week later than I originally said I would get to it, but I've
finally managed to get the time together to construct a beta tarball
to, as Rob said over a week ago, "help with pre-release practice".

I've used the make-release script that Sam Reed pointed me to before,
so I think I've done this using the same tools as he would have.  I
used the wmf1.2011 branch, so I think this is pretty sane.

And just to verify this, I did a brief sanity check by running the
installer.

Hopefully, we can use this to start getting a 1.20 tarball out at the
beginning of October.

Download:
http://mah.everybody.org/mediawiki-1.20.0beta0.tar.gz

Release Notes:
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob_plain;f=RELEASE-NOTES-1.20


GPG signatures:
http://mah.everybody.org/mediawiki-1.20.0beta0.tar.gz.sig

Public key:
http://mah.everybody.org/contact-info
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x7956EE477F901A30

(If there there is anyone with a PGP key in the Philadelphia/New York
City area who can sign my key, let me know.  I have to get some more
signatures.)

- -- 
http://hexmode.com/

Human evil is not a problem.  It is a mystery.  It cannot be solved.
  -- When Atheism Becomes a Religion, Chris Hedges
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iD8DBQFQVQtlc17xCi38v/URAnDvAJ9+yjY1AMntUzedWyzHyckSSc5C2gCggciH
KcKJuNP3yEHIAm8esqPnNbw=
=8g8S
-END PGP SIGNATURE-

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

Re: [Wikitech-l] Planet update is taking too long

[James Alexander]

Hey DJ,

I'm really sorry about that :( . We ran into some issues with the new
planet which stopped it from being fully deployed. At the moment I can't
actually update the old config at all (I tried) because the SVN repository
is locked down but I'll talk to mutante to see if we can at least unlock it
for now to try and get it up. The old planet is still having lots of issues
(for some reason languages are randomly not updating and then stopping
until a manual update) but it's better then nothing for now.

James

On Sat, Sep 15, 2012 at 2:46 AM, Derk-Jan Hartman <
d.j.hartman+wmf...@gmail.com> wrote:

> Planet was supposed to be switched to the new version about a month ago,
> but still isn't. In the mean time, no new blogs can be added to the old
> planet it seems, and that causes the WLM blogs to STILL not be present in
> the blog feed, half way into the event. If it keeps up like this, the event
> will be over before the blogs are in the planet feed.
>
> Can SOMEONE update the old config, or SOMEONE deploy the new planet
> services ?
>
> DJ
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>



-- 
James Alexander
Manager, Merchandise
Wikimedia Foundation
(415) 839-6885 x6716 @jamesofur
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Announcing initial version of gerrit-stats

[Dan Andreescu]

>
> do anything and it cannot be undone. After deleting and adding one
> metric I had two metrics with same color.
>

I tried to do this and wasn't successful, could you please provide the
steps that you took when you found the issue?  Thank you.

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

Re: [Wikitech-l] Announcing initial version of gerrit-stats

[Diederik van Liere]

>
>
> Is the slowness issue known?
>   -Niklas
>
Yes this is known and it is related to the fact that gerrit-stats is
currently hosted on a Labs instance. We are working on migrating it to
another server.
Best,
Diederik
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Announcing initial version of gerrit-stats

[Niklas Laxström]

On 14 September 2012 20:18, Diederik van Liere  wrote:
> To create a new chart yourself visit
> http://gerrit-stats.wmflabs.org/graphs/new
> This will launch the interface to create your own graph. Click on 'Data'
> and  Click on 'Add Metric' and a pull down menu with all the repositories
> will appear. Select the repository of your interest and select the metric
> that you want to visualize. Once you have selected all the metrics of your
> interest go back to 'Info' and enter a slug name. Then press 'Enter' and
> then click the 'Save' button.

I tried to create a new graph but clicking on most things seems to
freeze the browser for a good amount of time. It also seems to be
possible to select multiple metrics for one metric though it doesn't
do anything and it cannot be undone. After deleting and adding one
metric I had two metrics with same color.

Is the slowness issue known?
  -Niklas


-- 
Niklas Laxström

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

Re: [Wikitech-l] Notification bubble system

[Daniel Friesen]

On Sat, 15 Sep 2012 06:11:31 -0700, Krinkle  wrote:

On Sep 14, 2012, at 3:11 AM, Daniel Friesen   
wrote:


On Thu, 13 Sep 2012 15:03:04 -0700, Steven Walling  
 wrote:


On Wed, Sep 12, 2012 at 11:09 PM, Erik Moeller   
wrote:



Is the system documented somewhere already so gadget/script authors
can start using it?



+1 to docs for this, please. :)

My other question is similar to what Andrew asked earlier: what  
potential

is there for including something more than just strings?

My team just finished up a test where simple "your edit was saved"
confirmation messages lead to a significant bump in the editing  
activity of

newbies on English Wikipedia.[1] The only core differences between the
custom notification we built and bubble notifications are that it was
center-aligned and that it included a checkmark icon. I would prefer to
build on top of this if we're going to try and make an edit  
confirmation

message a part of MediaWiki.


mw.notify accepts DOM nodes and jQuery objects. So you can add in  
whatever html you want by parsing it into dom.
mw.notify also accepts mw.Message objects so you can use `mw.notify(  
mw.message( 'foo' ) );` and it'll be parsed.




... yes, but now that we're on the subject, lets try to aim for  
standardization here instead of encouraging arbitrary HTML for layout  
(I'd like to phase that out sooner rather than later). We can allow HTML  
inside the body (e.g. for hyperlinks which are allowed even in edit  
summaries), though we could call jQuery .text() on html and disallow  
HTML completely (while still keeping output clean of html characters).  
We'll see about that later. One step at a time.


I propose to implement the following content options (in addition to the  
configuration options we have like "autoHide" and "tag"). Inspired by  
API for Notification Center as found in OS X and iOS:


* icon (optional)
Must be square and transparent. Can potentially be displayed in  
different sizes. Important here to know that this icon is for source  
identification, not message type. I think it is good design to keep  
images out of notifications. No smilies, check marks or the like (unless  
the icon of a feature contains it).

w3-notifications uses iconUrl, but yeah we could shorten it to icon.


* title (optional)
Title of the message. If too long, will be auto-ellipsis-ified.

Already in the options.


* body (required)
Spans around up to 3 or 4 lines. If too long, will be  
auto-ellipsis-ified (in the case of a confirmation it would contain just  
one or two sentences, in case of a notification of en edit it might show  
(part of an) edit summary).
The body/content of the message is the most important part of the  
notification. Displaying it is the whole purpose of the notification. Why  
should it be truncated?


Also we already have the mw.notify(body, options) form, we don't need to  
go putting body into the options.


* buttons (optional, multi, recommendation is to use 2 buttons, not 1 or  
3+ )
Similar to jQuery UI dialog buttons): Label text and callback function.  
There can be be no two buttons with the same label. When a message has  
buttons it basically becomes what would be called an "Alert" (has  
buttons and doesn't autohide) in "Notification Center" lingo (as opposed  
to "Banner", which autohides and has no buttons). It makes sense to  
automatically enforce autoHide:false if buttons are set.


Applications / Features that send many notifications might abstract part  
of this internally, like:



var extPath = mw.config.get( 'wgExtensionAssetsPath' ) + '/Feature';
/**
 * @param {mw.Title} title
 * @param {Object} revision Information about revision as given by the  
API.

 */
Feature.prototype.editNotif = function( title, revision ) {
  return mw.notify({
content: {,
  icon: extPath + '/modules/ext.Feature.foo/images/notify.icon.png',
  title: title.getPrefixedText(),
  body: $.parseHTML(  revision.parsedcomment )
  },
  config: {
autoHide: true
  });
};


-- Krinkle



--
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name]

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

Re: [Wikitech-l] Planet update is taking too long

[MZMcBride]

Derk-Jan Hartman wrote:
> Planet was supposed to be switched to the new version about a month ago, but
> still isn't. In the mean time, no new blogs can be added to the old planet it
> seems, and that causes the WLM blogs to STILL not be present in the blog feed,
> half way into the event. If it keeps up like this, the event will be over
> before the blogs are in the planet feed.
> 
> Can SOMEONE update the old config, or SOMEONE deploy the new planet services ?

Is there a relevant bug in Bugzilla? I've found it much easier to get issues
such as this resolved when there's a Bugzilla bug (and sometimes an
accompanying RT ticket).

MZMcBride



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

Re: [Wikitech-l] Notification bubble system

[Krinkle]

On Sep 14, 2012, at 3:11 AM, Daniel Friesen  wrote:

> On Thu, 13 Sep 2012 15:03:04 -0700, Steven Walling  
> wrote:
> 
>> On Wed, Sep 12, 2012 at 11:09 PM, Erik Moeller  wrote:
>> 
>>> Is the system documented somewhere already so gadget/script authors
>>> can start using it?
>>> 
>> 
>> +1 to docs for this, please. :)
>> 
>> My other question is similar to what Andrew asked earlier: what potential
>> is there for including something more than just strings?
>> 
>> My team just finished up a test where simple "your edit was saved"
>> confirmation messages lead to a significant bump in the editing activity of
>> newbies on English Wikipedia.[1] The only core differences between the
>> custom notification we built and bubble notifications are that it was
>> center-aligned and that it included a checkmark icon. I would prefer to
>> build on top of this if we're going to try and make an edit confirmation
>> message a part of MediaWiki.
> 
> mw.notify accepts DOM nodes and jQuery objects. So you can add in whatever 
> html you want by parsing it into dom.
> mw.notify also accepts mw.Message objects so you can use `mw.notify( 
> mw.message( 'foo' ) );` and it'll be parsed.
> 

... yes, but now that we're on the subject, lets try to aim for standardization 
here instead of encouraging arbitrary HTML for layout (I'd like to phase that 
out sooner rather than later). We can allow HTML inside the body (e.g. for 
hyperlinks which are allowed even in edit summaries), though we could call 
jQuery .text() on html and disallow HTML completely (while still keeping output 
clean of html characters). We'll see about that later. One step at a time.

I propose to implement the following content options (in addition to the 
configuration options we have like "autoHide" and "tag"). Inspired by API for 
Notification Center as found in OS X and iOS:

* icon (optional)
Must be square and transparent. Can potentially be displayed in different 
sizes. Important here to know that this icon is for source identification, not 
message type. I think it is good design to keep images out of notifications. No 
smilies, check marks or the like (unless the icon of a feature contains it).

* title (optional)
Title of the message. If too long, will be auto-ellipsis-ified.

* body (required)
Spans around up to 3 or 4 lines. If too long, will be auto-ellipsis-ified (in 
the case of a confirmation it would contain just one or two sentences, in case 
of a notification of en edit it might show (part of an) edit summary).

* buttons (optional, multi, recommendation is to use 2 buttons, not 1 or 3+ )
Similar to jQuery UI dialog buttons): Label text and callback function. There 
can be be no two buttons with the same label. When a message has buttons it 
basically becomes what would be called an "Alert" (has buttons and doesn't 
autohide) in "Notification Center" lingo (as opposed to "Banner", which 
autohides and has no buttons). It makes sense to automatically enforce 
autoHide:false if buttons are set.

Applications / Features that send many notifications might abstract part of 
this internally, like:


var extPath = mw.config.get( 'wgExtensionAssetsPath' ) + '/Feature';
/**
 * @param {mw.Title} title
 * @param {Object} revision Information about revision as given by the API.
 */
Feature.prototype.editNotif = function( title, revision ) {
  return mw.notify({
content: {,
  icon: extPath + '/modules/ext.Feature.foo/images/notify.icon.png',
  title: title.getPrefixedText(),
  body: $.parseHTML(  revision.parsedcomment )
  },
  config: {
autoHide: true
  });
};


-- Krinkle


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

[Wikitech-l] git review updated

[Derk-Jan Hartman]

When using git review today, i was greeted with:

> A new version of git-review is availble on PyPI. Please
> update your copy with:
> 
> pip install -U git-review

Actually running that resulted in an error:

> pip install -U git-review
> Traceback (most recent call last):
> File "/usr/local/bin/pip", line 5, in 

The solution to this for me was:

> sudo easy_install --upgrade pip

Just in case others run into this problem.

DJ

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

[Wikitech-l] Planet update is taking too long

[Derk-Jan Hartman]

Planet was supposed to be switched to the new version about a month ago, but 
still isn't. In the mean time, no new blogs can be added to the old planet it 
seems, and that causes the WLM blogs to STILL not be present in the blog feed, 
half way into the event. If it keeps up like this, the event will be over 
before the blogs are in the planet feed.

Can SOMEONE update the old config, or SOMEONE deploy the new planet services ?

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

Re: [Wikitech-l] Article Feedback v4

[Yury Katkov]

The current development of Article Feedback is very strange: I'm from the
croudsourcing company and I can tell that the user comments are useless
most of the time since there are very little tools to analyze them (except
maybe for some topics in English language).

Maybe the goal of the new incarnation of AF is not to give the feedback but
to encourage people to write anything on Wikipedia and show the authors of
the page that somebody reads their articles thus motivating them?
-
Yury Katkov




On Sat, Sep 15, 2012 at 7:59 AM, MZMcBride  wrote:

> David Gerard wrote:
> > On 14 September 2012 18:05, Matthias Mullie 
> wrote:
> >> Technical issues are the reason for its slow ramp-up: the underlying
> >> architecture does not yet allow us to safely deploy to 100% of enwiki
> and
> >> we're currently working on resolving that.
> >
> > So is the AFTv4 data doing anything or being used for anything?
>
> Err, is the AFTv5 data doing anything or being used for anything? When I
> skim  >,
> the signal-to-noise ratio is so imbalanced that the tool is useless. This
> "comments section" of the site has quickly become filled with gibberish and
> a fair number of biographies of living persons violations. It hasn't yet
> reached the awfulness of a YouTube comments section, but it's certainly on
> its way. I've no idea why resources are being invested in this way.
>
> MZMcBride
>
>
>
> ___
> 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