Hi,
I have a simple question
What is the average size of a wikipedia article in Spanish?
I need this to calculate the amount of articles that can be included
on a CD. Subsequently, this size will be compressed by LZMA2 (OpenZIM
format)
http://en.wikipedia.org/wiki/Wikipedia:Size_comparisons => is updated?
--
Lcdo. Wilfredo Rafael Rodríguez Hernández
msn,googletalk = wilfredor(a)gmail.com
blog = http://wilfredor.blogspot.com
"Imagine a world in which every single person on the planet is given
free access to the sum of all human knowledge. That's what we're
doing."
Looks like this may be something many on this list would like to know asap.
I think the mail is in the moderation queue because Danese may not be
subscribed.
Siebrand
From: Danese Cooper <danese(a)gmail.com>
Date: Thu, 2 Jun 2011 09:23:35 -0700
To: <wikitech-l(a)lists.wikimedia.org>,
<WikimediaAnnounce-l(a)lists.wikimedia.org>
Subject: [Wikimedia Announcements] CTO Leaving Wikimedia Foundation end of
July
Hello,
It is with considerable regret that I inform you of my planned departure
from the Wikimedia Foundation at the end of July. I¹ve really enjoyed my
time here, and I¹m proud of what Wikimedia Engineering has accomplished
together.
While I tremendously enjoyed helping to build the engineering organization,
at this point in the development of the organization and the role, Sue, Erik
and I have agreed that there¹s no longer a fit between the identified near
term needs and goals of the organization, and my own interests. I¹ve
therefore decided to leave WMF as CTO, but I remain a friend of the
organization and the mission, and Sue, Erik and I talked about some ways to
work together in coming months.
To allow for an orderly transition, I will stay on as Wikimedia¹s CTO
through July. I'll be representing the Foundation and recruiting talent at
several tech conferences, as well as engaging in transition activites within
the Foundation. Erik will assume the title of Interim VP of Engineering and
Product Development, and we¹ll immediately start the transition of personnel
and reporting lines.
Erik will send a note about the transition shortly.
Danese
Hey,
The getSkin method of the User class has been deprecated in MW 1.18, but is
still in use on a lot of places. I want to take care of this in the
extensions I maintain, but it's not clear to me what to replace it with in
parser functions and tag extensions. The deprecation notice states you
should use the most relevant RequestContext. How can this be obtained from
inside a parser function or tag extension? I did several searches through
trunk and the extensions I've checked out, but did not find any parser hooks
using this yet.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
> The problem isn't reverting commits that are bad, it's reverting
> commits solely because they haven't been reviewed. In a pre-commit
> review system, the equivalent to the proposed 72-hour rule would be
> letting unreviewed code languish without comment. Both of these are
> bad things.
>
> The point is, people's code should only be rejected with some specific
> reason that either a) lets them fix it and resubmit, or b) tells them
> definitively that it's not wanted and they shouldn't waste further
> effort or hope on the project. Whether you're using
> review-then-commit or commit-then-review, one of the most demoralizing
> things you can do to a volunteer's contributions is say "nobody cares
> enough to provide any feedback on your code, so we're just going to
> reject it by default".
+1
As a volunteer person, I'm fine if code I commit is reverted based on
it sucking, being too complicated, being too ugly, etc provided there
is actually some objection to the code. However, I'd be rather
offended if it was reverted on the basis of no one got around to
looking at in the last 3 days, since that is something essentially out
of my control.
As it stands, trivial one line changes aren't even reviewed in 72 hours.
-bawolff
[Forking thread "Code review process"]
On 01/06/11 09:58, Max Semenik wrote:
> To make this reasonable, we would also need to run tests for branches
> on the central server, too - CruiseControl doesn't look flexible enough
> for this.
Hello,
I am planning to add the REL1_18 branch to the CruiseControl system as a
new project The prerequisite being to make it works for trunk :-)
REL1_17 does not have the test suite. I think it was broken beyond
repair at the point we branched.
--
Ashar Voultoiz
Hi developers,
for streamlining (my) support (to users), I created a kind of
first aid checklist [1]
which I ask users coming with questions to read and answer first. If
possible.
- adapted to my needs
- comprises most of the questions and "have you already done this and
that" I needed to ask them over and over again
- currently not a template (I don't think that this is necessary or
useful at the moment)
You may also find it useful for integrating, adapting to your needs, on
your extension or whatever page/s.
[1] http://www.mediawiki.org/wiki/Extension_talk:OpenID#First_aid_checklist
Changed status of this extension to:
stable,
because since January 2011, I discovered _not a single problem._
For legacy MediaWiki versions, I have working OpenID extensions as
"tarballs" for MediaWiki 1.15.1, 1.16.1.
Changes were not committed to the branches (no experience, how to do
this; no requests to do this; no time to do this).
Tom