Hi all,
I am a member of Wikimedia Hungary, which will have a stand at the Hungarian
Free Software Conference this weekend. I thought that would be a good
oppurtinity to raise awareness for MediaWiki. Do you know of leaflets or other
handout materials about SMW which I could translate to help with that? Or any
source material to compose something similar from? Testimonials, comparisons,
statistics, feature sets etc.
thanks
Gergő
Dear Sumana,
I'm going to remove my application from consideration, this whole
process has been demeaning and insulting and I've taken enough of a
beating over it.
While full of optimism and excitement in mid-September, while
constantly active in #mediawiki for over a month, the attitude of the
developers (who you do not name, where's the transparency in this
process?) and yourself have just leeched out any energy I have towards
the MediaWiki community.
When I arrived, extension in hand (which is still mark in beta, I
remind you, using your own template), people seemed friendly,
encouraging me immediately to apply for access, so that more eyes
could look at things and give feedback, which up to that point I was
actively soliciting in IRC. In that time I've started two more
extensions (each with multiple iterative releases, one in beta and
another experimental), which is very clear given the download page for
my Realnames extension which lists all three. The mere fact that here
you are asking me if I've done anything other then Realnames shows a
basic lack of interest in my application, my MW profile, my website
where my downloads are hosted and described, as well as an ignorance
to my daily presence and participation in IRC for most of September
and almost all of October (I've been away on a trip at the very end).
If developers have criticism about my code, I'm happy. I want to
actually receive it. I thought that was the whole point of asking for
access, so you can get into the code review queue and actually receive
that criticism and people can point you in the right direction.
Considering I have an extension (and two more now, one beta and one
experimental) that work, isn't slow even on large wikis (that I've
tested, despite them not being as optimized as they could be --
perhaps if I had a chance to learn the MW Framework better and get
feedback), shows that you "don't have to train me from scratch" as the
wiki pages about svn access say.
At no point was any attempt made to contact me in IRC (despite my high
level of participation there) to speed up this process in any manner,
to ask for clarification or voice concerns. Instead it's been 7 weeks
of silence with sudden burst of "produce this -- sorry no answer yet,
with heavy undertones of doesn't look good".
There seems to have been concern with my original license, a
BSD-2-Clause with copyright assignment so I don't lose the ability to
distribute my code, this isn't the GPL, you need a contributor
agreement with BSD (as I understand it). Yet absolutely no effort was
made to communicate these concerns to me, or to work out what those
issues were and how they could be resolved. I happen to have stumbled
upon another project that had a more elegant solution to the BSD
contribution problem (with a different type of contributor agreement)
and it seems like that may have cleared things up. But I'm guessing
here. From your emails it sounded like you were just ready to turn it
down with a "Sorry we don't agree with your license". During which
time no attempt was made to look at the code sample, just playing
cat-and-mouse for weeks on a licensing concern to now arrive at a
cat-and-mouse for weeks on code samples.
You've accused me in the past of not seeing you as a person, but just
another staff person part of a bureaucratic organization, and yet in
turn, no efforts have been made in this process to treat me like a
human being.
To make it clear, I've never asked for core access, I'm not trying to
mess up your project, all I wanted to do was be able to participate on
equal footing in the community with other extension developers, to
co-exist and grow and share knowledge. To take advantages of tools
like code-review, the familiarity people have with the MW repo (and
other who can contribute to it!) and distribution system.
You've made it painfully clear to me, and gauging from the message
left by Yaron, to others as well, that despite all the smiles and nice
words:
We're not welcome.
And to me, that's really sad.
Olivier Beaton
p.s. I'm cc'ing wikitech-l not just out of frustration, but because I
feel my feedback provides a meaningful contribution to the discussion
Yaron started weeks ago on this very topic of access -- one which has
seen near zero transparency in the community.
On Fri, Nov 4, 2011 at 10:21 PM, Commit access requests
<commit-access-requests(a)wikimedia.org> wrote:
> Olivier,
>
> One of the access-granting developers looked at the code sample,
> Extension:Realnames, and had some criticisms, as it tries to find and replace all
> username links in the page output HTML, and the User::newFromName( $m['username']
> ); query in the callback for each match is not batched.
>
> He and the other developers would very much like to see more code from you in
> order to grant commit access -- do you perhaps have some other code samples you've
> written, for another project, or possibly for MediaWiki or MediaWiki extensions in
> the sadly long time it's been since you originally submitted this request?
>
> Thank you.
>
> best,
> Sumana
>
> 11/02/2011 01:01 - Olivier Beaton wrote:
>
>> Thanks for the update.
>>
>> On Tue, Nov 1, 2011 at 8:48 PM, Commit access requests
>> <commit-access-requests(a)wikimedia.org> wrote:
>> > Olivier:
>> >
>> > Thank you, again, for requesting commit access and being part of the MediaWiki
>> > community. The developers reviewing your application are fine with your new plan
>> > (the BSD-2-Clause license) and are now reviewing your code samples, and I expect a
>> > decision based on that code review within the week. Thank you, and sorry for the
>> > delay.
>> >
>> > Sincerely,
>> > Sumana Harihareswara
Hi all,
So as should be known by now we're going with QUnit for writing and running
unit test of JavaScript and PHPUnit for writing and running unit test for
our PHP code base. One can manually run both of these locally without
problems (phpunit from CLI and QUnit test from the browser at
[mw]/tests/qunit/index.php [1]).
As automated continuous integration we're letting Jenkins update mediawiki,
run the tests and keep track of everything (including notification to IRC).
Although it's theoretically possible to let Jenkins run QUnit tests
(node.js from shell running synchronously), what we really want is
throwing all javascript unit tests onto our swarm of actual browsers. For
that we use TestSwarm, but it's downside is that it's not as cool as
Jenkins in providing statistics and insight into the state of our code.
The jQuery Testing team found a cool solution. Hooking up TestSwarm into
Jenkins.
See their instance at http://swarm.jquery.org:8080/#jenkins
Now one thing that might throw you off is the 'running build'. Jenkins is
not controlling the runs, as it shouldn't.
TestSwarm is controlling this through the swarm. Jenkins is merely
aggregating results, which, depending on the definition of "build ready"
can take a long time if one of the required browsers isn't connected to the
swarm. We will probably have to find a way to make this look better and
have statistics available even when not every browser is connected so that
we don't have to wait for "build ready", which has a different meaning when
working with multiple clients and 100s of asynchronous runs.
But overall it's very nice, I think we should take the same approach for
MediaWIki. Instead of trying to make TestSwarm do something it's not
designed for, let TestSwarm do what it's good at, and let Jenkins do what
it is good at.
More info:
* Project planning page by the jQuery Testing team:
http://jquerytesting.pbworks.com/w/page/43991777/TestSwarm-Jenkins-Integrat…
* Fork it on Github: https://github.com/appendto/jenkins-testswarm
* The jQuery Testing team
--
Krinkle
PS: Before we can use this though there are many things to do first on
integration.mediawiki.org; Such as installing TestSwarm, merging JSTesting
branch into trunk, setting up and testing the TestSwarmMwFetcher.. Just
wanted to get this idea out there before someone might waste time trying to
do the same.
[1] Soon to be /wiki/Special:JavaScriptTest/qunit :) (see
/branches/JSTesting/)
We're getting really close making a 1.18 tarball happen. My hope is to
have it released in two weeks at most. How realistic is that?
== Fixing the 1.18 milestone bugs ==
https://bugzilla.wikimedia.org/buglist.cgi?resolution=---&target_milestone=…http://hexm.de/97 (if the above URL wraps unusably).
There are three bugs here:
https://bugzilla.wikimedia.org/31060 -- [Regression] Sortable tables:
"unsortable" should also work for rows outside the table heading
https://bugzilla.wikimedia.org/31511 -- Unable to add/remove buttons
from (classic) toolbar from a gadget after MW update
https://bugzilla.wikimedia.org/31682 -- MW1.18 broke Edittools for
Special:Upload
That's down from 8 that were on the list last week. Now, granted, a
couple were removed from the from the milestone and are still open. But
in the meantime, we still fixed a few.
== Reviewing all outstanding revisions ==
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/tag/1.18?status=new
The above link currently points to 35 revisions that need to be reviewed
before we can ship a 1.18 tarball. If I can get 7 reviewers to review
one revision every day, we'll be done on Friday.
== Fixing the FIXMEs ==
http://www.mediawiki.org/wiki/MediaWiki_roadmap/1.18/Revision_report
There are two FIXME'd revisions left. The committers (Krinkle and
Happy-Melon) are aware of them, but anyone can fix the problems if they
are motivated.
I think getting a 1.18 tarball out in two weeks is completely do-able.
Let's make it happen!
Mark.
> Message: 10
> Date: Mon, 7 Nov 2011 15:40:58 +0000
> From: David Gerard <dgerard(a)gmail.com>
> Subject: Re: [Wikitech-l] License exceptions in Wikimedia's repo (was
> Re: SVN Extension Access)
> To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
> Message-ID:
> <CAJ0tu1EepsqjT41rRYY9gnkCVJ-BZ-6oe-oUgy3nt1XVtFFSrQ(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> On 7 November 2011 15:08, Olivier Beaton <olivier.beaton(a)gmail.com> wrote:
>
> > To make it clear, copyright assignments (what I had in my original
> > request) are common in the FOSS community, as you pointed out you
> > talked about them yourself on your blog and wmf talked about having
>
>
> Copyright assignments are inherently harmful, as their only use is so
> that the assigned-to body can defect on the implicit covenant of open
> source: that is, so it can take people's contributions private.
>
> The FSF continues to use them, on the theory that this gives greater
> legal protection. While the FSF is quite unlikely to defect (it's
> spent twenty-five years behaving as a consistent actor), its legal
> theory appears unnecessary (neither the Linux kernel nor BusyBox use
> copyright assignments, but both have been spectacularly successful in
> pursuing GPL violations) and its continued use makes people think
> they're a good idea.
>
> For an example of defection, see Oracle taking MySQL open-core.
>
> Copyright assignments are harmful. They are not some sort of standard
> thing in open source. They would be harmful to MediaWiki.
>
>
> - d.
You don't need to go for ideological reasons to go against copyright
assignments to individual extension authors. It's simply impractical
in the MW repo where many people make batch maintenance commits to
expect all of those people to assign you their copyright (imho).
My understanding is we allow people to commit extensions under
whatever OSI approved license strikes their fancy, and that if you
commit to someone else's extension, then you also release your commit
under that license. This always struck me as common sense...
-bawolff
This Saturday, November 12, Wikimedia DC is hosting an accessibility
hackathon 10am to 5:30pm. RSVP at
http://accessibilityhackathon.eventbrite.com/ .
If MediaWiki developers come, they can work on making MediaWiki more
accessible --
https://bugzilla.wikimedia.org/buglist.cgi?keywords=accessibility has
129 bugs right now, so there's a lot of work to be done! Katie Filbert
(aude), who's running the event, is aiming to get accessibility experts
to the event to help developers improve their apps' accessibility. She
writes that "at some point, we might do an "audit" of MediaWiki and
identify issues ... maybe on Saturday."
Enjoy!
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
Hi everyone,
I'm working on the Git migration project, and I need your help!
Unlike SVN which stores commits based on a username, Git stores
a commit attributed to a name + e-mail address. I've made a lot of
progress on figuring these out, but I've gotten the list narrowed down
and I'm getting a little stuck on some of the old accounts that aren't
active anymore.
So I thought I'd ask if people on the list could take a look at my
unknown committers list[0] and see which people they know and can
figure out. I'm finding that lots of people know about one or two of the
people on the list.
If you know the name or the e-mail address of any of the users that
we've got listed there, fill it in. Thanks for any help you can provide!
-Chad
[0] http://etherpad.wikimedia.org/Unknown-committers
Hi, I have noticed that on http://www.mediawiki.org/wiki/Git_conversion is
that
*Not done* Commits via IRC
I don't know if you want to use bots like CIA, but if you would like to use
more customized output of bot feed, I could volunteer here, I have some
years of experience with irc bots, even a place to host it (at least I have
own VPS, or I could use toolserver for that), may I ask what is current
status of this? Is someone working on that? I could at least help if it's
needed. I know that GIT repo is not yet being used but I could at least
prepare it.
I need to grab all the categories of a page as an array. This feels like a
noob question, but how would I obtain an array of categories solely from a
skin file?
Only category reference in the QuickTemplate skin class seems to
be QuickTemplate::data['catlinks'], which has a div containing links in it.
Any solutions?
- Hunter F.