Hi, is there a policy / recommendation about Wikimedia employees using
wikimedia.org addesses when contributing code and participating in
community activities as part of their paid work? Or has this topic been
discussed in the past?
--
Quim
I believe I was told that, for the purposes of (say) Gerrit, contractors
(and potentially full employees) were advised to use personal email
addresses in order to provide continuity of their account once they had
ceased to be contractors/employees. It did of course make my code review
analysis -- which required users to be labelled either as staff or
non-staff -- a little tricky.
Harry
--
Harry Burt
User:Jarry1250
Is there any easy way (via extension) to modify the "src" attribute of images on wiki pages?
I see hooks for modifying href values - LinkBegin and LinkEnd. But I don't see something similar for images, whose URLs seem to be produced via File::getUrl().
Purpose: I want to add a querystring parameter onto the ends of the URLs, turning <img src="foo.jpg"/> into <img src="foo.jpg?timestamp=xxxxxxxxxxx"/> to aid with caching.
Thanks,
DanB
I'm trying to test a parser tag extension with phpunit and have run into a
strange problem. Whenever my extension calls $parser->recursiveTagParse(), the unit
test blows up in Parser.php, complaining that $parser->mOptions is a non-object.
The tag callback looks pretty normal:
static function render($input, $argv, $parser, $frame) {
// ...
$parser->recursiveTagParse("something");
// ...
}
and I have unit tests that call render()directly:
public function testMyTag() {
global $wgParser;
$this->assertEqual(MyTag::render("some text", array(), $wgParser, false));
}
(I don't like using $wgParser here, and maybe that's the root of my problems?)
The tag works perfectly in the browser. Just not when unit-testing on the command
line.
The blowup occurs in Parser.php::replaceVariables, when it calls
$this->mOptions->getMaxIncludeSize().
Any advice appreciated!!
Thanks,
DanB
We've finished replicating all core and extensions to Github
now, as I announced yesterday. Per discussion, we're now
replicating everything to the Wikimedia account to avoid
confusion and duplication. The mediawiki organization was
closed to avoid this confusion.
All mediawiki/* repos are now being replicated, and have the
same name as in Gerrit (with the caveat that slashes "/" are
changed to dashes "-" due to Github naming conventions).
Please let me know if you have any problems with the
replicated repositories.
https://github.com/organizations/wikimedia
Next step: finding a way to get pull requests back into Gerrit :)
-Chad
Hi everyone,
I was wondering what people thought of marking /trunk/extensions
in SVN as read only. Pretty much every active extension (as far as
I can tell) has been moved out already. It doesn't preclude us from
migrating any of these extensions to Git at a later date, and nothing
is being deleted.
Thoughts?
-Chad
Hi, what about having Wikimedia features as organization in Ohloh?
The proposal is interesting considering the current state of things:
MediaWiki seems to be stalled with the SVN to Git migration, and it is
close impossible to find out what other projects come from this community.
This would help or quest on community metrics, so here goes my humble
+1. I also volunteer with some work, basically following the steps of
https://github.com/wikimedia and pinging Sumana / here for anything else.
-------- Original Message --------
Subject: Seeking feedback on new "Organizations" feature on Ohloh
Date: Tue, 16 Oct 2012 18:22:54 +0000
From: Rich Sands <rsands(a)blackducksoftware.com>
To: metrics-wg(a)theopensourceway.org <metrics-wg(a)theopensourceway.org>
Hi all,
As I mentioned here recently, we're rolling out a new feature on Ohloh
next week I thought might be interesting to this list. We're adding
rollups of projects into "Organizations", so project contributors and
others could see for example all the projects in the FooBar Foundation,
which ones are most active, the most active contributors, year over year
summary statistics, etc. I know many of you or folks in your
organizations have rolled your own metrics for watching your
foundation's projects and their activity. This feature isn't intended to
replace any of that, but rather to provide a view into how organizations
are contributing to and influencing FOSS. We've spoken with a number of
you who've expressed a need for this, and hope this new feature can be a
valuable resource.
We're rolling this out as a Beta feature and would love to get your
feedback. There are two aspects we're looking at: which organizations
steward which projects, and also which organizations contribute to which
projects through developers affiliated with those organizations, whether
they're for-profit, non-profit, governmental, or educational. Initially
we're concentrating on the first aspect - projects in organizations. In
a near-term iteration we'll add in the contribution bit, but for now
we're not showing stats on which projects an organization contributes to.
If you would like a preview of this feature before it is released, let
me know and I'll send you a URL and a name/password combo so you can
check it out. And if you'd like your organization to be one of the
featured ones when we open this up, I'd be thrilled to add you. All I
need is an organization name, a short description, a logo (if
available), a homepage URL for the organization, and a list of projects
to include. If your projects aren't already on Ohloh, I can help you add
them as well.
We're keen to make this useful, and we're rolling it out in a fairly raw
state, so that the FOSS community can help it evolve. Also, please don't
post about or publicize this new feature before it comes out next week.
Looking forward to hearing from you!
-- rms
Rich Sands
Director of Developer Communities
Black Duck Software, Inc.
rsands(a)blackducksoftware.com <mailto:rsands@blackducksoftware.com>
Cell: +1 617-283-0027
www.ohloh.net <http://www.ohloh.net>