I propose to split the topic and discuss the creation of ACL for MW in
I see three sub-tasks here:
0) Writing a good proposal of how ACL should work. Will it be based on
namespaces? or maybe categories (although it's hard to imagine)? or
maybe per-page access? I can help to describe this vision document.
1) coordination with WMF and including ACL into Roadmap. First we need
to be sure that the possible patches to the core:
- will not be rejected just because of philosofy of openness
- will not be removed after several versions
I've got no ideas how that can be done. Probably via RFC with
signatures of interested companies.
2) Searching for the developers and tester. There are many possible
developers that may be interested in this task: HalloWelt, Custis,
DIQA-PM, maybe even Wikia. Besides there are a lot of independent
3) Fundraising. For independent developer it's possible to ask for
individual engagement grant  but mostly it should be a crowdfunding
from MediaWiki-related companies.
For that task we need a person who has personal contact with many
MediaWiki-related companies and is ready to contact each of them
asking to take part in funding. I'm not sure who that can be (maybe
me, maybe someone from organizing comittee of Wikimania or Wikisym,
maybe someone from WMF) but it's going to be a god damn lot of dirty
work that needs funding.
Yury Katkov, WikiVote
On Sat, Aug 24, 2013 at 4:38 AM, Mark A. Hershberger <mah(a)nichework.com> wrote:
> On 08/23/2013 06:31 PM, Yury Katkov wrote:
>> Of course, after some time the extension will stop working because of
>> ugly hacks that will definetely appear in the code.
>> Another and more proper solution is not so fast, that is: to lobby the
>> proper ACL support in MediaWiki core before starting development.
> Markus Glaser and I have discussed precisely this as one of the biggest
> hurdles for Corporate adoption of MediaWiki. There are a lot of things
> to do in the MediaWiki space but, as you point out, this is one that we
> need developers outside the WMF for.
>> MediaWiki is used as an enterprise wiki and the impossibility of good
>> ACL should not be considered as not some kind of philosophy of the
>> software (as some people claims) but as a bug that needs fixing.
> +1 (again. That makes 2 points for Yury, so far.)
> So if -- as many of us on the -enterprise mailing list agree, I think --
> this is a bug that needs fixing, how are we going to fix it?
> That is, where is the money to pay for developer time going to come from?
> The release manager contractor that the WMF is funding this year is
> meant to be finding funds outside of the Foundation to sustain release
> management long term. One way to do that is to begin extending
> MediaWiki in ways that enterprises would be willing to fund -- say, for
> example. through developing ACLs.
> If we can find some MW developers interested in working on adding this
> to core, and the money to fund those developer's work, the problem then
> becomes coordinating their work and making sure it has real momentum.
> Mark A. Hershberger
> NicheWork LLC
According to the Version lifecycle, MediaWiki 1.22 is slated for
release on November 30th, at the very latest.
In that vein, we've come up with a timeline for the release. If we
use this timeline and shoot for the latest date, we'll need to start the
release process no later than October 19th. Please look over the
timeline and the "TBD" section and provide feedback.
Of course, if you see gaps or things that you can help clarify, please
feel free to mention them on the talk page.
Mark A. Hershberger
I've been hacking at this for a while and hoping someone has solved it.
I am trying to set up MediaWiki with LDAP so users from a remote network
must log in, but it's optional on the local network. I don't want users to
have to log in twice, so I set up Extension:AutomaticREMOTE_USER (htauth) which
works well for remote users, but I can't determine a good way to permit
login for local users in the same instance.
I've tried a variety of hacks, including setting a directory where the
local user must log in then directing them back, but Apache won't pass
REMOTE_USER in the MW directory for a local user, and other hacks are all
ugly in one way or another. Does anyone have any ideas?
Thanks to Mark Holmquist for maintaining http://etherpad.wmflabs.org for
the past long while. It is going down in 2 weeks, so please retrieve
I recommend that you:
* go into your browser history
* search it for etherpad.wmflabs.org
* go to each of those pads and copy-and-paste the content someplace,
preferably on a public wiki, even if it's just in your userspace
* replace the content of the Etherpad with a link to the wiki page
you've moved the text to
-------- Original Message --------
Subject: [Wikitech-l] Etherpad Lite labs instance going down in two
weeks - backup time
Date: Fri, 23 Aug 2013 13:02:13 -0700
From: Mark Holmquist <mtraceur(a)member.fsf.org>
Reply-To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
To: wikitech-l(a)lists.wikimedia.org, engineering(a)lists.wikimedia.org,
The day we have all equally hoped for and dreaded is come to pass: Etherpad
Lite has now replaced Etherpad "Classic" in production, and the labs
is on its way out.
This is my as-wide-as-possible email warning to say that everything on the
labs instance, as really should have been expected, is going to be gone
Not immediately - we intend to give you two weeks to get your important data
off the instance and onto the new one at https://etherpad.wikimedia.org/ -
but you should _absolutely_ be moving things as soon as possible. We will
also keep a data dump around, in case anything else needs to get pulled out
of the pads, but I would suggest not relying on that if you don't have to.
And in the future: If a URL has "wmflabs.org" in it...don't put anything,
ANYTHING, important there. The purpose of labs is to let us experiment with
new technology without having to worry about reliability.
Thanks so much for your help and understanding in the course of this
tl;dr: http://etherpad.wmflabs.org is going down in 2 weeks, get yer
stuff off it.
Software Engineer, Multimedia
Wikitech-l mailing list