I came across http://www.whatcanidoformozilla.org/ today, and
proceeded to register whatcanidoforwikipedia.org :)
Thoughts on what to put there? I cal already think of the following
languages to put up:
1. PHP
2. JS
3. Lua
4. Python
5. Java
6. Obj-C
7. 'Design'
I'll start a wiki page sometime to collect content, and then spend
some time writing the code - we can even fork the original site's code
and use it.
Thoughts?
P.S. Can we *please* not bikeshed on the domain name? Domain names are cheap
--
Yuvi Panda T
http://yuvi.in/blog
In case y'all missed this:
----- Forwarded Message -----
> From: "PRIVACY Forum mailing list" <privacy(a)vortex.com>
> To: privacy-list(a)vortex.com
> Sent: Saturday, April 6, 2013 3:10:01 PM
> Subject: [ PRIVACY Forum ] French homeland intelligence threatens a volunteer sysop to delete a Wikipedia Article
> French homeland intelligence threatens a volunteer sysop to delete a
> Wikipedia Article
>
> http://j.mp/16C8Cxn (Wikimedia France)
>
> "Unhappy with the Foundation's answer, the DCRI summoned a Wikipedia
> volunteer in their offices on April 4th. This volunteer, which was one
> of those having access to the tools that allow the deletion of pages,
> was forced to delete the article while in the DCRI offices, on the
> understanding that he would have been held in custody and prosecuted
> if he did not comply. Under pressure, he had no other choice than to
> delete the article, despite explaining to the DCRI this is not how
> Wikipedia works. He warned the other sysops that trying to undelete
> the article would engage their responsability before the law. This
> volunteer had no link with that article, having never edited it and
> not even knowing of its existence before entering the DCRI offices. He
> was chosen and summoned because he was easily identifiable, given his
> regular promotional actions of Wikipedia and Wikimedia projects in
> France."
>
> - - -
>
> The return of "Vichy France" mentalities, apparently.
>
> --Lauren--
> Lauren Weinstein (lauren(a)vortex.com): http://www.vortex.com/lauren
> Co-Founder: People For Internet Responsibility:
> http://www.pfir.org/pfir-info
> Founder:
> - Network Neutrality Squad: http://www.nnsquad.org
> - PRIVACY Forum: http://www.vortex.com/privacy-info
> - Data Wisdom Explorers League: http://www.dwel.org
> - Global Coalition for Transparent Internet Performance:
> http://www.gctip.org
> Member: ACM Committee on Computers and Public Policy
> Lauren's Blog: http://lauren.vortex.com
> Google+: http://vortex.com/g+lauren / Twitter:
> http://vortex.com/t-lauren
> Tel: +1 (818) 225-2800 / Skype: vortex.com
>
> _______________________________________________
> privacy mailing list
> http://lists.vortex.com/mailman/listinfo/privacy
--
Jay R. Ashworth Baylink jra(a)baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
<Tron>Greetings, Programs!</Tron>
So, not many updates for a while, as things have been progressing at a
fair clip in the "oh, my god boring gruntwork" front.
The biggest news is the addition of Petr Bena to the tools project
sysadmin team as its first volunteer. Petr has been very involved in
the setup and administration of the Tool Labs' predecessor projects, and
will continue to steer the bots project where the rules are a little
more relaxed to facilitate more experimental development.
He's also joining me on the tools project proper, to help provide
support to maintainers over a wider range of times, and to increase
availability of sysadmins. You can find him hanging around
#wikimedia-labs, often at times where I am not available.
There is some documentation-in-progress that give a lot of information
on how to set up your tools on the Labs architecture at:
https://www.mediawiki.org/wiki/Wikimedia_Labs/Tool_Labs/Help
Please don't hesitate to comment if you see missing information, or if
parts of it are less clear than idea.
On the other fronts, the wikitech management interface is now in place
for self-serve of tool account creation by Labs users; this requires
moving already-existing tool accounts to the new scheme, and a brief
outage for that purpose later this week (see note below)
Experiments with a bulletproof replacement for gluster are well on their
way; with NFS from a highly redundant server as the currently favored
option. With a bit of luck, I'll use the opportunity given by the
outage for the tool account switchover to move the shared tools
filesystem to NFS as a trial run.
The database replication is also well on its way; you can find the
current roadmap at:
https://wikitech.wikimedia.org/wiki/Tool_Labs/Database_plan
=== Planned outage ===
In order to move the extant tool accounts to the new, final scheme, and
(progress permitting) move the shared filesystems to a new storage
server, there will be a brief outage of the Tool Labs infrastructure
this Thursday April 11 starting at 16:00 UTC. The outage is expected to
last 20 minutes during which service will be intermittently unavailable.
Announcements will be sent by email, on IRC and on the servers 30
minutes before the start of maintenance, at its start, and upon completion.
Impact:
* Jobs running on the grid engine will be stopped then restarted
automatically at the end of the maintenance window. If you are running
a job that cannot or should not be restarted automatically without
intervention from its maintainers, please make certain that it has been
stopped before the start of the maintenance window;
* The login server will be restarted during the window, ending active
sessions;
* The web service will be intermittently unavailable; and
* Running processes not scheduled through the grid engine will be killed.
Recovery plan:
In case of unplanned failure during the maintenance window,
configuration will be rolled back to the current version and a new
window will be planned after postmortem. Disruption of services will
take place as noted and an announcement will be sent.
-- Marc
Hey,
I am looking for a way to obtain some information on the commits made to
some WMF hosted git repo within the last n seconds. My current solution is
using githubs since parameters as follows:
https://api.github.com/repos/wikimedia/mediawiki-extensions-Wikibase/commit…
This however does not really work for me since there is a lag of a minute
or two before the commit gets pushed to github. So if I ask for the commits
made in the last 30 seconds, I will never get anything back.
Is there a similar API in gitweb, gerrit or something else accessible over
http?
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
*I got the idea of this extension via the mailing list itself
*I plan on implementing a *pronunciation recording extension*
***More Details can be found out on
https://www.mediawiki.org/wiki/User:Rahul21/Gsoc
*You Could Contact me on the IRC(Rahul_21) or email me back.
Thank You
Rahul Maliakkal
On 04/05/2013 03:01 PM, Isabel Gancedo wrote:
> Everything seems to be working fine; jobs run a maximum warp and the queue
> is becoming tiny.
Excellent. I see this line in the "New features" list from the Release
notes:
The Job system was refactored to allow for different backing stores
for queues as well as cross-wiki access to queues, among other
things. The schema for the DB queue was changed to support better
concurrency and reduce deadlock errors.
Perhaps that deserves more attention?
> There is just one issue that I would like to mention: in my database
> (MySQL) pre-upgrade jobs have job_random set to 0 and do not seem to be
> picked up -not even when I use the option --type=replaceText.
>
> I can repeat the replace text operations, so this is not big problem for
> me. However, if this is the normal behaviour for an upgrade, maybe it
> should be mentioned in the notes somewhere.
This may be a bug that was introduced during the refactoring. Could you
file one?
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki&cc=mah@every…
Thank you for your helpful comments!
--
http://hexmode.com/
It is not the case that simple clear questions have simple clear
answers, not even in the world of pure ideas, and much less so in
the messy real world of everyday life.
-- Gregory Chaitin, “Paradoxes of Randomness”
Hey,
I'm curious what the list thinks of deprecating and eventually removing the
Hooks class. Some relevant info:
/**
* Hooks class.
*
* Used to supersede $wgHooks, because globals are EVIL.
*
* @since 1.18
*/
https://github.com/wikimedia/mediawiki-core/blob/master/includes/Hooks.php#…
I personally find the comment hilarious and hope you see why when looking
at the "class". Looks like usage in core and extensions is not to
extensive, so switching to something more sane seems quite feasible.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--