On Sun, 10 Aug 2014, at 04:04, Andre Klapper wrote:
programming should be a hobby, like editing articles
Free Software definitions don't imply that you shall not take money for
your work, or eventually even make a living on it. It's part of the
personal freedom that everybody has. However,
For very small abandoned projects, nobody is around to do anything, even to
review a patch.
For a slightly bigger project, someone is around to review a patch and explain
you how to write one, and where to get started. The process of you writing it
is slow, and the process of them reviewing it
In honor of bug 1's 10th birthday today, take the time to fix some out
of date documentation or write some missing ones :)
https://bugzilla.wikimedia.org/show_bug.cgi?id=1
-- Legoktm
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On Sat, Aug 9, 2014 at 5:22 PM, dan-nl dan.entous.wikime...@gmail.com
wrote:
this is an excellent idea and i don't think it needs to be focused only on
large corporations or only on corporate individuals who want to volunteer.
i would suggest opening the idea to any developer with a skill set
On 10 August 2014 13:57, Chris McMahon cmcma...@wikimedia.org wrote:
Actually, I think we should consider serious limits to any such proposal,
such as (as Gilles suggested) working only with reputable employees (or
ex-employees, like Aaron Arcos) of reputable companies. Otherwise I
suspect
Lets all welcome the new overlord Erik.
Add a new protection level called superprotect
Assigned to nobody by default. Requested by Erik Möller for the purposes
of protecting pages such that sysop permissions are not sufficient to
edit them.
Change-Id: Idfa211257dbacc7623d42393257de1525ff01e9e
Hi folks,
Admins are currently given broad leeway to customize the user
experience for all users, including addition of site-wide JS, CSS,
etc. These are important capabilities of the wiki that have been used
for many clearly beneficial purposes. In the long run, we will want to
apply a code
On Sun, Aug 10, 2014 at 9:27 AM, svetlana svetl...@fastmail.com.au wrote:
I feel that having development carried out by employees hinders programming
the same software as a hobby: for instance, they work in a single language,
and don't need localised documentation
Good localized software is
On Sun, 10 Aug 2014, at 23:19, K. Peachey wrote:
Lets all welcome the new overlord Erik.
Add a new protection level called superprotect
Assigned to nobody by default. Requested by Erik Möller for the purposes
of protecting pages such that sysop permissions are not sufficient to
edit them.
Le 10 août 2014 15:35, svetlana svetl...@fastmail.com.au a écrit :
On Sun, 10 Aug 2014, at 23:19, K. Peachey wrote:
Lets all welcome the new overlord Erik.
Add a new protection level called superprotect
Assigned to nobody by default. Requested by Erik Möller for the purposes
of
personally i really liked your comparison, when we were chatting the other
day, to an artist in residence -- imo, programmers are the artists of our
time and this matches well.
Absolutely, I also like that idea of doing something similar to artist
residencies. This could take many forms. The
On 10 aug. 2014, at 14:27, Erik Moeller e...@wikimedia.org wrote:
However, we've clarified in a number of venues that use of the
MediaWiki: namespace to disable site features is unacceptable. If such
a conflict arises, we're prepared to revoke permissions if required.
This protection level
Hi!
I made a XML dump with --current option, then replaced some of external
domain links [http://somedomain.org] in it. When I import the dump back,
these pages aren't updated. I think that's because text processors /
editors do not update sha1 / timestamp fields. Why doesn't
Wiadomość napisana przez Nicolas Vervelle nverve...@gmail.com w dniu 10 sie
2014, o godz. 15:45:
I hope it's not an other step from WMF to prevent the application of
community decisions when they not agree with it. I fear that they will use
this to bypass community decisions. For example like
Totally agree with that, dirty common.js hacks aren't really beneficial
for anyone.
Cheers,
Marius
On Sun, 2014-08-10 at 14:56 +0100, Derk-Jan Hartman wrote:
On 10 aug. 2014, at 14:27, Erik Moeller e...@wikimedia.org wrote:
However, we've clarified in a number of venues that use of the
Hi Erik,
I understand you reasoning, but you couldn't have communicated and timed
this in a worse way. You might be doing the right thing, but because of
this ill communication and timing, this will be completely overshadowed.
That saddens me. Good luck with the shit storm :-(
On Sun, Aug 10, 2014 at 9:00 PM, Michał Łazowik mlazo...@me.com wrote:
Wiadomość napisana przez Nicolas Vervelle nverve...@gmail.com w dniu 10 sie
2014, o godz. 15:45:
I hope it's not an other step from WMF to prevent the application of
community decisions when they not agree with it. I fear
Hi,
It could mean that, but of course it is actually introduced to prevent
the German community from deactivating the Media Viewer.
User JEissfeldt, removed `mw.config.set(wgMediaViewerOnClick,
false);` from Common.js [0] and is the same person who sets
`protect-level-superprotect`.
I have no
Le 10 août 2014 17:06, James HK jamesin.hongkon...@gmail.com a écrit :
Hi,
It could mean that, but of course it is actually introduced to prevent
the German community from deactivating the Media Viewer.
User JEissfeldt, removed `mw.config.set(wgMediaViewerOnClick,
false);` from Common.js
On 08/08/14 14:24, Jon Robson wrote:
On 8 Aug 2014 04:23, Antoine Musso hashar+...@free.fr wrote:
Le 07/08/2014 22:05, Erwin Dokter a écrit :
I now have to submit two patches and hope they both get merged at the
exact same time.
The world we should be working towards is one where you'd only
On Sun, Aug 10, 2014 at 2:47 PM, Gilles Dubuc gil...@wikimedia.org wrote:
personally i really liked your comparison, when we were chatting the
other
day, to an artist in residence -- imo, programmers are the artists of our
time and this matches well.
To me the point
is to have our
+1 Scott
As a new hire at WMF, I consider it to be a privilege to be doing work that
supports the efforts of the community and the movement, but I am also proud of
the fact that what I am doing allows me to support my family without
compromising my personal values. Doing good and making a
Dear All,
I need some help tracking down a DB deadlock on a single-server,
private Wiki installation running latest MediaWiki download
from http://www.mediawiki.org/wiki/Download
I have been referred to this mailing list from #mediawiki at
irc.freenode.org, thanks for the pointer!
Il 10/08/2014 15:27, Erik Moeller ha scritto:
Hi folks,
Admins are currently given broad leeway to customize the user
experience for all users, including addition of site-wide JS, CSS,
etc. These are important capabilities of the wiki that have been used
for many clearly beneficial purposes. In
On 10-08-2014 15:35, svetlana wrote:
This change solves a problem that does not exist.
We either trust sysops, or we don't.
I concur. There are enough admins available to revert bad code
additions. Also, this measure is completely without effect.
*Suppose* I were a rogue admin wanting to
This seems like an unfortunate escalation on the WMF's part. Both sides
have a responsibility to try to work together, but as a practical matter,
the community does not answer to a single person, and the WMF staff do:
it's likely that the first olive branch is going to need to come from the
WMF
Erwin Dokter wrote:
On 10-08-2014 15:35, svetlana wrote:
This change solves a problem that does not exist.
We either trust sysops, or we don't.
I concur. There are enough admins available to revert bad code
additions. Also, this measure is completely without effect.
*Suppose* I were a rogue
On 08/10/2014 04:10 PM, Bjoern Kahl wrote:
What could cause this behavior and how should I configure my system to
prevent the deadlocks? If this is a Bug in either MediWiki or the
VisualEditor or Parsoid, how to further investigate and fix it?
In case this is a private wiki:
Did you set
hopelessI'd really like to hear Jimbo's opinion on the matter/hopeless
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Superprotect is a feature, the way it will be used must be determined by
consensus, on a theoretical basis there are different possible good uses.
But, anyway, anyone using this feature should be accountable to the
community, like anyone holding any advanced rights.
Vito
Inviato con AquaMail
Op 10 aug. 2014 om 20:12 heeft Ricordisamoa ricordisa...@openmailbox.org
het volgende geschreven:
hopelessI'd really like to hear Jimbo's opinion on the matter/hopeless
You should really watch Jimmy's speech at the Wikimania closing session. You
might be surprised.
Cheers!
--
Siebrand
Wow this is pretty depressing, although in today's age I cannot say I'm
surprised. Corporations have always been about controlling their consumers,
and it was really only a matter of time before the WMF fell into that as
well. I wonder whether there's any legitimate justification for all of
this,
After VE fiasco I would had expected to see a less full of itself
Wikimedia. I was wrong.
The Roman Empire strength was its ability to make Romans out of other peoples.
The wiki strenght is making editors and develepers out of netizens.
Rome felt before losing its ability.
Is wiki losing its
Am 10.08.14 um 20:52 schrieb Gabriel Wicke:
On 08/10/2014 04:10 PM, Bjoern Kahl wrote:
What could cause this behavior and how should I configure my system to
prevent the deadlocks? If this is a Bug in either MediWiki or the
VisualEditor or Parsoid, how to further investigate and fix it?
On Mon, 11 Aug 2014, at 04:07, Tomasz W. Kozłowski wrote:
Philippe,
the patch is not for the MediaWiki software but for the configuration
of Wikimedia wikis (it's in the operations/mediawiki-config repository
on Gerrit).
It has been merged and deployed on the production cluster. The user
Hi,
etc. These are important capabilities of the wiki that have been used
for many clearly beneficial purposes. In the long run, we will want to
apply a code review process to these changes as with any other
deployed code, but for now the system works as it is and we have no
intent to remove
If you simply remove the timestamp from a revision in a dump, the importer
appears to happily insert it with the current time as the timestamp. This
may also cause cancer, summon Cthulhu, etc.
In addition to pywikibot, there's the Replace Text extension[0], which
ought to be able to handle what
MediaWiki Bugzilla Report for August 04, 2014 - August 11, 2014
Status changes this week
Reports changed/set to UNCONFIRMED: 1
Reports changed/set to NEW: 23
Reports changed/set to ASSIGNED : 10
What seems like a deadlock may in fact be parsoid timing out while
trying to connect to your local wiki's API end point. We have had
some users report problems of this sort which were caused by their
firewall or access control setup. You might want to verify that the
API end point for your local
Hi,
Following up on a conversation on the gendergap email list, I am discussing
with Freenode the possibility of changing the default web client to one
that is friendlier and has a less technical feel, primarily for the benefit
of new users who access #wikipedia-en-help by clicking on a link. The
40 matches
Mail list logo
