Thanks. So now we'll have two unmaintained extensions, LQT and Flow. Can
we reverse the Flow conversion on mediawiki.org now, so that the wiki
stays on the luckiest side i.e. the extension which has most users and
is most likely to survive in the future?
(LQT is maintained by its non-Wikimedia
Ok, that is maybe correct, but what does "maintained" and "supported" mean
here? There are a lot of Feature requests for Flow to make Flow at least as
productive as some LQT boards, e.g. on mediawiki.org (think about the different
places for support, e.g. Support desk and extension talk pages,
On 1 September 2015 at 23:21, Federico Leva (Nemo)
wrote:
> Thanks. So now we'll have two unmaintained extensions, LQT and Flow.
To quote Danny's email directly, "Flow will be maintained and supported".
Your supposition that the extension will be unmaintained is not
On 2 September 2015 at 14:51, Risker wrote:
> I want to thank the Collaboration team for taking this brave step - and
> yes, it's a brave step. The natural trajectory of large projects that don't
> quite seem to meet their promise is to keep going and going until everyone
>
On Tue, Sep 1, 2015 at 8:10 PM, Oliver Keyes wrote:
>
> What was the publicising of the campaign prior to its launch?
>
> It should be pretty apparent to people with experience within the
> movement that this would be both entirely novel and pretty
> controversial.
As
> On Sep 2, 2015, at 11:17 AM, Gergo Tisza wrote:
>
> On Wed, Sep 2, 2015 at 6:19 AM, Oliver Keyes wrote:
>
>> For what it's worth, the line " For one thing, they can turn out
>> negative, in which case we will have been spared a philosophical
>>
Hi,
We have scheduled an upgrade of mailman (https://lists.wikimedia.org) for:
Wednesday, September 9, 2015 at 2:00:00 PM UTC ( 7:00 AM PDT, 16:00 CEST)
The scheduled mainteance window is 4 hours (or less).
During this time please expect all the mailing lists (web interface
and email) to be
I don't know if this is correct place to bring this idea, but
[[Extension:PageTriage]] is good example of a starting point. Is there any
plans to work on it by collaboration team?
Best
On Wed, Sep 2, 2015 at 10:50 PM Roan Kattouw wrote:
> On Wed, Sep 2, 2015 at 6:21 AM,
On Wed, Sep 2, 2015 at 12:13 PM, Oliver Keyes wrote:
>
> And without any answer to my question about whether this was an actual
> A/B test, and whether you're measuring overall user utility rather
> than 'did they download it', this is also highly subjective and costly
>
2015-09-02 1:53 GMT+02:00 MZMcBride :
> Ori Livneh wrote:
>>On Tue, Sep 1, 2015 at 8:43 AM, Jérémie Roquet
>>wrote:
>>> Has the RFC been abandonned because of lack of interest?
>>
>>Speaking for myself: at the time the RFC was written, I was skeptical
On 02/09/15 00:12, Quim Gil wrote:
Wikimedia Phabricator will be soon one year old!
On Tue, Sep 1, 2015 at 2:00 AM, wrote:
Number of accounts created in (2015-08): 288
Kind of surprised about the fact that we keep having almost ten new
Phabricator users
> On 3 Sep 2015, at 01:02, Jérémie Roquet wrote:
>
> 2015-09-02 1:53 GMT+02:00 MZMcBride :
>> [..] our code. As expected, we've encountered a number of bugs that
>> disappear when the debug=true URL parameter is specified.
>
> [..]
>
> As for bugs, I
I tried to get in a while ago but never heard back. I tried again when I
received your letter and was accepted. Looking forward to not missing
messages. Thanks!
--stephen
On Fri, Aug 28, 2015 at 9:00 AM, Jamison Lofthouse <
jamison.loftho...@gmail.com> wrote:
> Yep. Pretty good service. Been
On Wed, Sep 2, 2015 at 6:51 AM, Risker wrote:
> I am certain once the team has a chance to refocus, they may choose to
> examine workflows that are common across multiple Wikimedia projects that
> would benefit from improvement. Off the top of my head, creating a
>
On Wed, Sep 2, 2015 at 11:22 AM, Brandon Harris wrote:
>
>> On Sep 2, 2015, at 11:17 AM, Gergo Tisza wrote:
>>
>> On Wed, Sep 2, 2015 at 6:19 AM, Oliver Keyes
wrote:
>>
>>> For what it's worth, the line " For one thing, they can
Le 01/09/2015 17:30, Ori Livneh a écrit :
> We appear to be running a banner campaign on the mobile web site, driving
> people to download the mobile app:
>
> https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_2
> https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_1
>
> Campaign
On Wed, Sep 2, 2015 at 6:21 AM, David Gerard wrote:
> Did the stuff to port LQT threads/pages to Flow ever make it to
> production quality?
>
>
It was used to convert all LQT pages on mediawiki.org, including
[[mw:Support desk]] which is probably the largest LQT page that has
On 09/02/2015 12:35 PM, David Gerard wrote:
On 2 September 2015 at 14:51, Risker wrote:
I want to thank the Collaboration team for taking this brave step - and
yes, it's a brave step. The natural trajectory of large projects that don't
quite seem to meet their promise is
On 09/02/2015 02:21 AM, Federico Leva (Nemo) wrote:
Thanks. So now we'll have two unmaintained extensions, LQT and Flow.
As noted, Flow is not unmaintained.
Can we reverse the Flow conversion on mediawiki.org now, so that the wiki
stays on the luckiest side i.e. the extension which has most
https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-09-02
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Wed, Sep 2, 2015 at 11:20 AM, Roan Kattouw
wrote:
> I don't think we currently have good documentation on how you can convert
> your own wiki, but AFAIK "simply" running the convertAllLqtPages.php
> maintenance script on a wiki that has both LQT and Flow installed
On 09/02/2015 03:55 PM, Ryan Lane wrote:
Even ignoring the "is it right and ethical" debate, there's a pretty large
amount of research over the past 6 or so months that show this is a bad
idea.
[citation needed]
Matt Flaschen
___
Wikitech-l
On 09/02/2015 09:21 AM, David Gerard wrote:
On 2 September 2015 at 07:27, Dan Garry wrote:
On 1 September 2015 at 23:21, Federico Leva (Nemo)
wrote:
Thanks. So now we'll have two unmaintained extensions, LQT and Flow.
To quote Danny's email
1. Regarding Flow and LQT on mediawiki.org:
On Tue, Sep 1, 2015 at 11:21 PM, Federico Leva (Nemo)
wrote:
> Can we reverse the Flow conversion on mediawiki.org now,
Technically, I think that would be challenging. All LiquidThreads carefully
redirect to Flow topics, e.g.
On Tue, Sep 1, 2015 at 10:50 PM, Gergo Tisza wrote:
> On Tue, Sep 1, 2015 at 10:09 PM, Ori Livneh wrote:
>
> > Just in time!
> > http://techcrunch.com/2015/09/01/death-to-app-install-interstitials/
>
>
> Interstitials are full-page ads where you have to
On 2 September 2015 at 14:17, Gergo Tisza wrote:
> On Wed, Sep 2, 2015 at 6:19 AM, Oliver Keyes wrote:
>
>> For what it's worth, the line " For one thing, they can turn out
>> negative, in which case we will have been spared a philosophical
>> debate
Hi all --
I'm going to try to address as many of the issues mentioned in this thread
and the Phabricator ticket[1] as I can. I'm going to preface this by
explaining why we're doing this.
First of all, this is only a test in order to increase our understanding of
how our readers interact with our
Il 02/09/2015 22:26, Antoine Musso ha scritto:
Le 01/09/2015 17:30, Ori Livneh a écrit :
We appear to be running a banner campaign on the mobile web site, driving
people to download the mobile app:
https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_2
Hi!
This is just a heads-up to say that today we're deploying a significant
refactor of client-side CentralNotice code!
Please welcome ext.centralNotice.display, who will be taking over from
ext.centralNotice.bannerController. If all goes well, today will be
bannerController's last day on
2015. 9. 2. 오후 7:47에 "Andre Klapper" 님이 작성:
>
> On Wed, 2015-09-02 at 06:53 +0900, Yongmin Hong wrote:
> > 2015. 9. 1. 오후 7:18에 님이 작성:
> > > Needs Volunteer: 16678
> >
> > I thought this "Needs Volunteer" has been renamed to "Lowest" a while
I want to thank the Collaboration team for taking this brave step - and
yes, it's a brave step. The natural trajectory of large projects that don't
quite seem to meet their promise is to keep going and going until everyone
is burnt out, and it is courageous to say "this isn't going where we wanted
On Wed, 2015-09-02 at 06:53 +0900, Yongmin Hong wrote:
> 2015. 9. 1. 오후 7:18에 님이 작성:
> > Needs Volunteer: 16678
>
> I thought this "Needs Volunteer" has been renamed to "Lowest" a while
> ago?
It has been, but the string in the script [1] has not been updated.
For what it's worth, the line " For one thing, they can turn out
negative, in which case we will have been spared a philosophical
debate about openness." comes off as very snarky and also entirely the
wrong approach. Whether something is /within our ethos/ should not be
something we discuss after
On 2 September 2015 at 07:27, Dan Garry wrote:
> On 1 September 2015 at 23:21, Federico Leva (Nemo)
> wrote:
>> Thanks. So now we'll have two unmaintained extensions, LQT and Flow.
> To quote Danny's email directly, "Flow will be maintained and
On 2 September 2015 at 01:50, Gergo Tisza wrote:
> On Tue, Sep 1, 2015 at 10:09 PM, Ori Livneh wrote:
>
>> Just in time!
>> http://techcrunch.com/2015/09/01/death-to-app-install-interstitials/
>
>
> Interstitials are full-page ads where you have to click
35 matches
Mail list logo