the gerrit classes from nova and
define services according to that, currently it knows only apache
service, but I can of course insert more classes there. The source
code is located in trunk/tools/nparser. Thanks to Ryan Lane for the
semantic query in order to get a list.
If you would find any
But that is exactly the problem; you left in the *old* yellow against a much
mellower blue. If that blue was as bright as the old green, it would be much
less of a problem. I don't know how expert you are in CSS and web colors,
but there should really have been more attention to matching all
Why didn't you test the original blue/green? What were your findings on
that? You should have applied the colors as present in the patch, as these
were the colors agreen upon in the original commit, which were blue for
deleted content, and green for added content. Those had been tested by
This is awesome! Great work everyone!
On Wed, Dec 3, 2014 at 9:03 AM, Giuseppe Lavagetto glavage...@wikimedia.org
wrote:
Hi all,
it's been quite a journey since we started working on HHVM, and last
week (November 25th) HHVM was finally introduced to all users who didn't
opt-in to the beta
On Fri, Jan 16, 2015 at 4:29 AM, David Gerard dger...@gmail.com wrote:
On 16 January 2015 at 07:38, Chad innocentkil...@gmail.com wrote:
These days I'm not convinced it's our job to support every possible
scale of wiki install. There's several simpler and smaller wiki solutions
for people
On Fri, Jan 16, 2015 at 8:27 AM, David Gerard dger...@gmail.com wrote:
On 16 January 2015 at 16:09, Antoine Musso hashar+...@free.fr wrote:
So what we might end up with:
- Wikimedia using the SOA MediaWiki with split components maintained by
staff and the Wikimedia volunteers devs. Code
On Fri, Jan 16, 2015 at 10:21 AM, Ryan Schmidt skizz...@gmail.com wrote:
This sounds like a problem we need to fix, rather than making it worse.
I'd most wikis are not up to date then we should work on making it easier
to keep up to date, not making it harder. Any SOA approach is sadly DOA
On Fri, Jan 16, 2015 at 1:05 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Fri, Jan 16, 2015 at 12:27 PM, Ryan Lane rlan...@gmail.com wrote:
What you're forgetting is that WMF abandoned MediaWiki as an Open Source
project quite a while ago (at least 2 years ago).
{{citation
On Fri, Jan 16, 2015 at 1:20 PM, Erik Moeller e...@wikimedia.org wrote:
I think the confusion between third party support and an open
source project is unhelpful. We're obviously an open source project
with lots of contributors who aren't paid (and many of them are
motivated by Wikimedia's
On Fri, Jan 16, 2015 at 1:23 PM, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
So this was never publicly announced and has had no visible effect, to the
point that the latest version of all the code is still publicly available
under a free license and volunteers are still encouraged to
On Wed, Feb 11, 2015 at 9:55 AM, Tyler Romeo tylerro...@gmail.com wrote:
On February 11, 2015 at 11:49:15, Bryan Davis (bd...@wikimedia.org) wrote:
On Tue, Feb 10, 2015 at 8:48 PM, Tyler Romeo tylerro...@gmail.com wrote:
What is more important: allowing as many people to use our libraries as
On Mon, Feb 9, 2015 at 11:37 AM, Tyler Romeo tylerro...@gmail.com wrote:
This entire conversation is a bit disappointing, mainly because I am a
supporter of the free software movement, and like to believe that users
should have a right to see the source code of software they use. Obviously
On Mon, Mar 16, 2015 at 6:02 PM, Risker risker...@gmail.com wrote:
How about just converting those threads back to Wikitext, instead? That
script already exists, I've seen it used on Mediawiki. Will it mess up the
pages that have already been converted using that script?
Bottom line, it
On Thu, Mar 19, 2015 at 8:18 AM, Risker risker...@gmail.com wrote:
The dogfooding has been happening for a while on WMF's own office-wiki. We
haven't heard any results about that. Is the system being used more than
the wikitext system? (i.e., are there more talk page comments now than
On Sat, Apr 11, 2015 at 7:44 PM, Brian Wolff bawo...@gmail.com wrote:
On Apr 11, 2015 1:18 PM, Pine W wiki.p...@gmail.com wrote:
https://citizenlab.org/2015/04/chinas-great-cannon/
Pine
___
Wikitech-l mailing list
On Wed, Jul 22, 2015 at 2:14 PM, Gergo Tisza gti...@wikimedia.org wrote:
GitHub is focused on small projects; for a project with lots of patches and
committers it is problematic in many ways:
Some of the largest open source projects around are on github:
Is this simply to support hosted providers? npm is one of the worst package
managers around. This really seems like a case where thin docker images and
docker-compose really shines. It's easy to handle from the packer side,
it's incredibly simple from the user side, and it doesn't require
On Thu, Nov 5, 2015 at 5:38 PM, C. Scott Ananian
wrote:
> I view it as partly an effort to counteract the perceived complexity of
> running a forest full of separate services. It's fine to say they're all
> preinstalled in this VM image, but that's still a lot of
On Fri, Nov 6, 2015 at 11:13 AM, C. Scott Ananian
wrote:
> Let's not let this discussion sidetrack into "shared hosting vs VMs (vs
> docker?)" --- there's another phabricator ticket and summit topic for that
> (
> https://phabricator.wikimedia.org/T87774 and
>
On Thu, Oct 8, 2015 at 9:13 AM, Petr Bena wrote:
> As to why:
>
> AWS is more flexible and more reliable than wikimedia-labs, other than
> that it's basically the same. If they really need to use AWS it's
> probably because they don't like the restrictions that come with
>
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
>
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
I haven't been actively maintaining the LDAP extension for MediaWiki for
over two years. There's not really much that needs to change, but some
basic love and care is likely a good idea. The LDAP extension is one of the
most popular MediaWiki extensions, so it wouldn't be great if it was broken
On Wed, Sep 9, 2015 at 7:08 AM, Adam Wight wrote:
>
> Another misconception or oversight I want to bring up is that Fundraising
> is the team pioneering the 2/3-page or full-page banners. We're driving
> readers from the website to completely closed and somewhat evil
On Mon, Sep 21, 2015 at 8:41 AM, Chris Steipp wrote:
> On Sep 19, 2015 11:15 AM, "bawolff" wrote:
> >
> > maintain is an ambiguous word. WMF has some responsibility to all the
> > extensions deployed on cluster (imo). If Devunt (and any others who
>
On Sun, Nov 29, 2015 at 8:18 PM, Yeongjin Jang
wrote:
>
> I recall that I saw financial statement of WMF that states around $2.3M
> was spent for Internet Hosting. I am not sure whether it includes
> management cost for computing resources
> (server clusters such as
The best option here is:
https://www.mediawiki.org/wiki/Extension:LDAP_Authentication
I'm not sure why you think LDAP is a wart on Windows. Active Directory is
just LDAP with Kerberos.
Anyway, the LDAP Authentication extension has examples of how to do
auto-auth using kerberos. You still need
les.GetRolesForUser().Length;
> foreach (var role in Roles.GetRolesForUser())
> {
> context.Response.Write('"' + role + '"');
> if (++i != count) context.Response.Write(',');
> }
> context.Response.Write(']');
> context.Response.End();
> }
>
> - Françoi
s worth sharing with the community, if others would
> benefit from an LDAP-less SSO solution for MW hosted on IIS?
>
> -Original Message-
> From: Wikitech-l [mailto:wikitech-l-boun...@lists.wikimedia.org] On
> Behalf Of Ryan Lane
> Sent: Tuesday, February 09, 2016 17:41
>
The right question here is: is it more important for Wikimedia foundation
to use only open source than it is to focus on work that directly benefits
the movement? There's no reasonable open source to do this function. The
ones that exist are terrible, are less efficient, and have to have hardware
To be totally honest, I think this is a great idea, but it should use
emojis. Github added this for PRs and messages for instance, and it's
amazingly helpful:
https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments
Slack has the same thing. It's fun, people like it, and
/me marks this email with "anger"
On Fri, Apr 1, 2016 at 1:41 PM, Ricordisamoa
wrote:
> This sounds like something that some random WMF team would actually
> implement in the near future...
>
>
> Il 01/04/2016 21:24, Legoktm ha scritto:
>
>> Hi,
>>
>> It's well
Any chance that Wikimedia Foundation can actually do proper releases of
this extension, rather than sending people a link to a phabricator page
that has a link to a gerrit change buried in the comments?
This seems like a pretty poor way to do a security release to third parties
that may be
On Tue, Apr 26, 2016 at 12:01 PM, Alex Monk wrote:
> It's not an extension that gets bundled with MediaWiki releases.
>
>
That doesn't mean third parties aren't using it. When I say a release of
the extension, I mean give it a version number, increase the version
number, tag
On Mon, May 16, 2016 at 12:45 AM, Lukas Mezger
wrote:
> Yes, we're also looking into reducing the environmental impact of the rest
> of the activities in the Wikimedia movement. And I am very aware that many
> websites consume a lot more energy than Wikipedia does.
The most likely way for people to see codes of conduct is through
repositories, which lets them know they have some way to combat harassment
in the tool they're using to try to contribute to a particular repository.
It makes sense to have a CODE_OF_CONDUCT.md in the repos; however, if all
the
401 - 436 of 436 matches
Mail list logo