Derk-Jan Hartman wrote:
> I fully agree with Dan on that. I'd be much more interested in +/- votes on
> feedback statements.
AFv5 already had this feature IIRC, but I think it lacked some way to
categorise and structurise messages, and to identify users who have a habit of
posting rubbish feedb
Quim Gil wrote:
> On Tuesday, August 19, 2014, Jon Robson wrote:
>
> >
> > I was curious to how generic the rating system is. For example would
> > it be possible to use such a thing on something like BetaFeatures or
> > was it specifically designed for extension rating?
> >
>
> I'm not sure how
Yeah just noticed this as well. An awesome change indeed; much easier to read
and interpret. Thanks!
--
Tyler Romeo
0x405D34A7C86B42DF
From: James Forrester
Reply: Wikimedia developers >
Date: August 20, 2014 at 17:22:42
To: QA (software quality assurance) for Wikimedia projects.
>
Cc: Wikimed
On 20 August 2014 13:02, Antoine Musso wrote:
> Hello,
>
> The tests results being reported to Gerrit are now much nicer. The
> first ever example is https://gerrit.wikimedia.org/r/#/c/155341/
>
>
> James E. Blair from Openstack found a nice trick to inject HTML in
> Gerrit comment. Christian Ai
As a MediaWiki tarball user, I'd *love* something to rate extensions -
even to show if anyone actually uses it and cares.
On 20 August 2014 19:14, Derk-Jan Hartman wrote:
> I fully agree with Dan on that. I'd be much more interested in +/- votes on
> feedback statements. I think that might be a
I believe Flow is going to or could be changed to solve this issue of
upvoting comments.
I was more interested in hypothetically if it was possible, I hadn't
really thought too much about whether it would be useful or not.
On Wed, Aug 20, 2014 at 11:14 AM, Derk-Jan Hartman
wrote:
> I fully agree
On 8/20/14, 9:04 AM, Quim Gil wrote:
> In order to move forward, we can discuss at different levels:
>
> * At a general level, which should be the priorities for mediawiki.org's
> gallery of extensions? This will allow us to define more tasks and projects
> for potential developers. https://www.me
I fully agree with Dan on that. I'd be much more interested in +/- votes on
feedback statements. I think that might be a direction worth exploring. A low
barrier like that might help bring a more complete picture of sentiment on
problems and ideas.
DJ
On 20 aug. 2014, at 19:08, Dan Garry wrot
On 20 August 2014 09:16, Quim Gil wrote:
>
> I'm not sure how related is this, but Article Feedback allowed user rating
> + comment, and it was deployed in Wikimedia servers. Editors didn't find it
> that useful for regular articles (too much extra work processing too little
> value feedback on to
On Wed, Aug 20, 2014 at 7:58 AM, Antoine Musso wrote:
> Hello,
>
> We have a mediawiki/vendor repository that holds third party libraries.
> Since MediaWiki core is going to eventually rely on them I have crafted
> a new Jenkins job (mediawiki-vendor-integration) which clones both
> repositories,
On Tuesday, August 19, 2014, Jon Robson wrote:
>
> I was curious to how generic the rating system is. For example would
> it be possible to use such a thing on something like BetaFeatures or
> was it specifically designed for extension rating?
>
I'm not sure how related is this, but Article Feed
On Wednesday, August 20, 2014, Isarra Yos > wrote:
>
> When someone creates a product specifically for a certain group of users
> (in this case folks installing extensions) without actually knowing what is
> useful to them (never even mind 'important' at this stage), there is
> something seriously
Hello everyone,
next week on August, 27th, there will be another set of maintenance releases
for MediaWiki. There are still some unresolved bugs and changes that are wating
to be +2'ed. So if you feel like improving MediaWiki tarball releases in the
upcoming days, you could have a look at the
> When someone creates a product specifically for a certain group of users
> (in this case folks installing extensions) without actually knowing what
> is useful to them (never even mind 'important' at this stage), there is
> something seriously wrong with that process.
Though I might only be a
On 20/08/14 11:48, Quim Gil wrote:
For those interested in the process of proposing and accepting internship
projects, here you have a post mortem of this specific case:
On Tuesday, August 19, 2014, Strainu wrote:
This sounds like a serious miscommunication before the GSoC project
begun. Som
Hello,
We have a mediawiki/vendor repository that holds third party libraries.
Since MediaWiki core is going to eventually rely on them I have crafted
a new Jenkins job (mediawiki-vendor-integration) which clones both
repositories, checkout the appropriate patch / branch and run the whole
MediaWi
2014-08-20 14:48 GMT+03:00 Quim Gil :
> Hi,
>
> One thing is clear, Aditya has a thick skin, which sadly still seems to be
> a quality required in many open source projects including ours.
And will remain so for the foreseeable future.
> On Tuesday, August 19, 2014, Strainu wrote:
>
>>
>> This s
Hi,
One thing is clear, Aditya has a thick skin, which sadly still seems to be
a quality required in many open source projects including ours. I wonder of
many old-timers would enjoy the kind of reception he got here after
introducing himself as a GSoC student -- even by people that know well what
There is now a fourth pending patch: https://gerrit.wikimedia.org/r/155241
…and I would still like to know WHY these can not be done. We've had a
couple dozen done before with no problems at all, what is the holdup now?
--
Matma Rex
___
Wikitech-l
19 matches
Mail list logo
