IANAL, but you might want to take a look at how the vlc people handled this kind of problems - i remember a huge rewrite effort from their part, but no link on hand, sorry.
Strainu
"Mr. Donald J. Fortier II" <technical_13(a)yahoo.com> a scris:
>A little additional information on topic 1 -- The pull request including the changes that this contributor to the script made can be viewed at https://github.com/WPAFC/afch/pull/54/files if it is of any interest. Thanks.
>
>
>
>________________________________
> From: "wikitech-l-request(a)lists.wikimedia.org" <wikitech-l-request(a)lists.wikimedia.org>
>To: wikitech-l(a)lists.wikimedia.org
>Sent: Thursday, September 26, 2013 8:01 AM
>Subject: Wikitech-l Digest, Vol 122, Issue 65
>
>
>Send Wikitech-l mailing list submissions to
> wikitech-l(a)lists.wikimedia.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>or, via email, send a message with subject or body 'help' to
> wikitech-l-request(a)lists.wikimedia.org
>
>You can reach the person managing the list at
> wikitech-l-owner(a)lists.wikimedia.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Wikitech-l digest..."
>
>
>Today's Topics:
>
> 1. Fwd: afch licensing question (Steven Walling)
> 2. Re: Killing 1.XXwmfYY branches -- another idea? (Antoine Musso)
> 3. Re: MediaWiki-Vagrant: new features (Željko Filipin)
> 4. Re: Fwd: afch licensing question (Denny Vrandečić)
> 5. Job posting: frontend dev (JavaScript) at Wikimedia
> Deutschland (Lydia Pintscher)
> 6. Re: MediaWiki-Vagrant: new features (Ori Livneh)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Wed, 25 Sep 2013 20:36:43 -0700
>From: Steven Walling <swalling(a)wikimedia.org>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: [Wikitech-l] Fwd: afch licensing question
>Message-ID:
> <CAMryOMXWs7QYrtKCfMUUEVTzKsK-mrV1EijNBT=zxLB0Q6nv0Q(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>Forwarding, with permission.
>
>For background the "AFC Helper" script is one that assists English
>Wikipedians reviewing pages in the Articles for Creation queue, which
>currently is severely backlogged.
>
>Any thoughts on the licensing issue, from folks with experience on the
>question of gadget/userscript licensing?
>
>---------- Forwarded message ----------
>From: Mr. Donald J. Fortier II <technical_13(a)yahoo.com>
>Date: Wed, Sep 25, 2013 at 8:30 PM
>Subject: afch licensing question
>To: "swalling(a)wikimedia.org" <swalling(a)wikimedia.org>
>
>
>Per the discussion on https://github.com/WPAFC/afch/issues/61 one of the
>previous contributors to the project refuses to agree to relicense AFCH
>under the MIT license. Right now, the script is licensed under
>CC-BY-SA/GFDL, as it was originally coded on-wiki (per
>[[Wikipedia:Copyright]] -- all text-based contributions). This came about
>due to some confusion that can be seen
>https://github.com/WPAFC/afch/issues/60. So, we are unsure as to where to
>go from here. If we replace any code contributed to the project by the
>person that refuses to agree, can we dissolve any requirements to get him
>to agree? Is there enough contribution from him to actually worry about it
>as he hasn't actually written any functions, just converted some stuff from
>old school JavaScript to jQuery? Any advice/assistance on this would be
>appreciated.
>
>
>
>--
>Steven Walling,
>Product Manager
>https://wikimediafoundation.org/
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 26 Sep 2013 10:09:30 +0200
>From: Antoine Musso <hashar+wmf(a)free.fr>
>To: wikitech-l(a)lists.wikimedia.org
>Subject: Re: [Wikitech-l] Killing 1.XXwmfYY branches -- another idea?
>Message-ID: <l20q3g$55i$1(a)ger.gmane.org>
>Content-Type: text/plain; charset=UTF-8
>
>Le 26/09/13 00:46, Chad a écrit :
>>> >
>>> > What's actually the problem with expanding branches?
>>> >
>> To me at least, it makes it harder to see what's actually deployed at
>> a given time. Try `git branch -r` on core. We're at 86 branches now...that's
>> 172 if you've got two remotes. It's only going to get worse and it'll be
>> progressively harder to spot what's important.
>
>We could simply delete the old branches after a few deployment cycles.
>If we want to keep the reference for history purposes, would tagging the
>tip of it be enough ?
>
>If you find yourself struggling to find out the last 2 wmf branches, you
>can write a tiny script to sort and filter the branches, keeping only
>the last two.
>
>--
>Antoine "hashar" Musso
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Thu, 26 Sep 2013 10:52:38 +0200
>From: Željko Filipin <zfilipin(a)wikimedia.org>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] MediaWiki-Vagrant: new features
>Message-ID:
> <CABfBeAr+=eBUMSTfHEMJrHGVE77rBngryhQeoyPcoxZqDh589A(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>Hi Ori,
>
>Is there a reason for having Guest Additions Version 4.1.12 in the VM
>instead of 4.2?
>
>$ vagrant up
>(...)
>[default] VM booted and ready for use!
>[default] The guest additions on this VM do not match the installed version
>of
>VirtualBox! In most cases this is fine, but in rare cases it can
>cause things such as shared folders to not work properly. If you see
>shared folder errors, please update the guest additions within the
>virtual machine and reload your VM.
>
>Guest Additions Version: 4.1.12
>VirtualBox Version: 4.2
>[default] Setting hostname...
>(...)
>
>I will file a bug in Bugzilla if that is something you can fix.
>
>Željko
>
>
>------------------------------
>
>Message: 4
>Date: Thu, 26 Sep 2013 10:57:06 +0200
>From: Denny Vrandečić <denny.vrandecic(a)wikimedia.de>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] Fwd: afch licensing question
>Message-ID:
> <CANnnRRtO5dCNkPnQeVCEsob6pUU-RofazJP+z981DOj7BMiNYQ(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>CC-BY-SA/GFDL is in the same spirit as GPL, which is an obviously
>acceptable license for WMF (since MediaWiki is written in it).
>
>Can you explain the need to relicense it under MIT?
>
>
>2013/9/26 Steven Walling <swalling(a)wikimedia.org>
>
>> Forwarding, with permission.
>>
>> For background the "AFC Helper" script is one that assists English
>> Wikipedians reviewing pages in the Articles for Creation queue, which
>> currently is severely backlogged.
>>
>> Any thoughts on the licensing issue, from folks with experience on the
>> question of gadget/userscript licensing?
>>
>> ---------- Forwarded message ----------
>> From: Mr. Donald J. Fortier II <technical_13(a)yahoo.com>
>> Date: Wed, Sep 25, 2013 at 8:30 PM
>> Subject: afch licensing question
>> To: "swalling(a)wikimedia.org" <swalling(a)wikimedia.org>
>>
>>
>> Per the discussion on https://github.com/WPAFC/afch/issues/61 one of the
>> previous contributors to the project refuses to agree to relicense AFCH
>> under the MIT license. Right now, the script is licensed under
>> CC-BY-SA/GFDL, as it was originally coded on-wiki (per
>> [[Wikipedia:Copyright]] -- all text-based contributions). This came about
>> due to some confusion that can be seen
>> https://github.com/WPAFC/afch/issues/60. So, we are unsure as to where to
>> go from here. If we replace any code contributed to the project by the
>> person that refuses to agree, can we dissolve any requirements to get him
>> to agree? Is there enough contribution from him to actually worry about it
>> as he hasn't actually written any functions, just converted some stuff from
>> old school JavaScript to jQuery? Any advice/assistance on this would be
>> appreciated.
>>
>>
>>
>> --
>> Steven Walling,
>> Product Manager
>> https://wikimediafoundation.org/
>> _______________________________________________
>> Wikitech-l mailing list
>> Wikitech-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>
>
>--
>Project director Wikidata
>Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
>Tel. +49-30-219 158 26-0 | http://wikimedia.de
>
>Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
>Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
>der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
>Körperschaften I Berlin, Steuernummer 27/681/51985.
>
>
>------------------------------
>
>Message: 5
>Date: Thu, 26 Sep 2013 11:52:59 +0200
>From: Lydia Pintscher <lydia.pintscher(a)wikimedia.de>
>To: wikitech-l <wikitech-l(a)lists.wikimedia.org>,
> mediawiki-l(a)lists.wikimedia.org
>Subject: [Wikitech-l] Job posting: frontend dev (JavaScript) at
> Wikimedia Deutschland
>Message-ID:
> <CABfqUgJpiiM_W=Snszhpr+xaPqeQ5W3j-3+a9idk+6w__0Rk1g(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>Heya folks :)
>
>Wikimedia Deutschland is looking for a software developer to work on
>all kinds of frontend-related things on exciting projects like
>Wikidata in a very cool team. If you're currently looking for a job
>and have the necessary skills please apply. You can find details at
>https://wikimedia.de/wiki/Software_Developer_(f/m)_focus_on_Frontend_Develo…
>Please let me know if you have any questions.
>
>
>Cheers
>Lydia
>
>--
>Lydia Pintscher - http://about.me/lydia.pintscher
>Community Communications for Technical Projects
>
>Wikimedia Deutschland e.V.
>Obentrautstr. 72
>10963 Berlin
>www.wikimedia.de
>
>Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
>
>Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
>unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
>Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
>
>
>
>------------------------------
>
>Message: 6
>Date: Thu, 26 Sep 2013 03:26:55 -0700
>From: Ori Livneh <ori(a)wikimedia.org>
>To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
>Subject: Re: [Wikitech-l] MediaWiki-Vagrant: new features
>Message-ID:
> <CAHXK4BzssgamHU9fixo4aUV0JU+9PRZuHwMWz4vhESbgr9qg5Q(a)mail.gmail.com>
>Content-Type: text/plain; charset=UTF-8
>
>On Thu, Sep 26, 2013 at 1:52 AM, Željko Filipin <zfilipin(a)wikimedia.org>wrote:
>
>> Hi Ori,
>>
>> Is there a reason for having Guest Additions Version 4.1.12 in the VM
>> instead of 4.2?
>>
>
>It's what Canonical's Vagrant image provides, and it's because that's the
>version that is packaged for Precise. (Remember, guest additions run on the
>guest.) You can update to the latest version by running
>'update-guest-additions' in the VM.
>
>I'll take the opportunity to remind folks who use Vagrant to send some
>positive feedback to Canonical. The Vagrant image they provide is part of a
>beta program they have not yet committed to supporting permanently.
>
>Per http://blog.utlemming.org/2013/01/vagrant-cloud-images.html
>"For those who use Vagrant, your feedback is essential. Please feel free to
>send feedback via the ubuntu-cloud(a)lists.ubuntu.com mailing list."
>
>
>------------------------------
>
>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l(a)lists.wikimedia.org
>https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
>
>End of Wikitech-l Digest, Vol 122, Issue 65
>*******************************************
>_______________________________________________
>Wikitech-l mailing list
>Wikitech-l(a)lists.wikimedia.org
>https://lists.wikimedia.org/mailman/listinfo/wikitech-l
According to the Version lifecycle[1], MediaWiki 1.22 is slated for
release on November 30th, at the very latest.
In that vein, we've come up with a timeline for the release[2]. If we
use this timeline and shoot for the latest date, we'll need to start the
release process no later than October 19th. Please look over the
timeline and the "TBD" section and provide feedback.
Of course, if you see gaps or things that you can help clarify, please
feel free to mention them on the talk page.
Thanks,
Mark.
[1] https://www.mediawiki.org/wiki/Version_lifecycle
[2]
https://www.mediawiki.org/wiki/Project:Release_management/Release_timeline
--
Mark A. Hershberger
NicheWork LLC
717-271-1084
A little additional information on topic 1 -- The pull request including the changes that this contributor to the script made can be viewed at https://github.com/WPAFC/afch/pull/54/files if it is of any interest. Thanks.
________________________________
From: "wikitech-l-request(a)lists.wikimedia.org" <wikitech-l-request(a)lists.wikimedia.org>
To: wikitech-l(a)lists.wikimedia.org
Sent: Thursday, September 26, 2013 8:01 AM
Subject: Wikitech-l Digest, Vol 122, Issue 65
Send Wikitech-l mailing list submissions to
wikitech-l(a)lists.wikimedia.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
or, via email, send a message with subject or body 'help' to
wikitech-l-request(a)lists.wikimedia.org
You can reach the person managing the list at
wikitech-l-owner(a)lists.wikimedia.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Wikitech-l digest..."
Today's Topics:
1. Fwd: afch licensing question (Steven Walling)
2. Re: Killing 1.XXwmfYY branches -- another idea? (Antoine Musso)
3. Re: MediaWiki-Vagrant: new features (Željko Filipin)
4. Re: Fwd: afch licensing question (Denny Vrandečić)
5. Job posting: frontend dev (JavaScript) at Wikimedia
Deutschland (Lydia Pintscher)
6. Re: MediaWiki-Vagrant: new features (Ori Livneh)
----------------------------------------------------------------------
Message: 1
Date: Wed, 25 Sep 2013 20:36:43 -0700
From: Steven Walling <swalling(a)wikimedia.org>
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Subject: [Wikitech-l] Fwd: afch licensing question
Message-ID:
<CAMryOMXWs7QYrtKCfMUUEVTzKsK-mrV1EijNBT=zxLB0Q6nv0Q(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Forwarding, with permission.
For background the "AFC Helper" script is one that assists English
Wikipedians reviewing pages in the Articles for Creation queue, which
currently is severely backlogged.
Any thoughts on the licensing issue, from folks with experience on the
question of gadget/userscript licensing?
---------- Forwarded message ----------
From: Mr. Donald J. Fortier II <technical_13(a)yahoo.com>
Date: Wed, Sep 25, 2013 at 8:30 PM
Subject: afch licensing question
To: "swalling(a)wikimedia.org" <swalling(a)wikimedia.org>
Per the discussion on https://github.com/WPAFC/afch/issues/61 one of the
previous contributors to the project refuses to agree to relicense AFCH
under the MIT license. Right now, the script is licensed under
CC-BY-SA/GFDL, as it was originally coded on-wiki (per
[[Wikipedia:Copyright]] -- all text-based contributions). This came about
due to some confusion that can be seen
https://github.com/WPAFC/afch/issues/60. So, we are unsure as to where to
go from here. If we replace any code contributed to the project by the
person that refuses to agree, can we dissolve any requirements to get him
to agree? Is there enough contribution from him to actually worry about it
as he hasn't actually written any functions, just converted some stuff from
old school JavaScript to jQuery? Any advice/assistance on this would be
appreciated.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
------------------------------
Message: 2
Date: Thu, 26 Sep 2013 10:09:30 +0200
From: Antoine Musso <hashar+wmf(a)free.fr>
To: wikitech-l(a)lists.wikimedia.org
Subject: Re: [Wikitech-l] Killing 1.XXwmfYY branches -- another idea?
Message-ID: <l20q3g$55i$1(a)ger.gmane.org>
Content-Type: text/plain; charset=UTF-8
Le 26/09/13 00:46, Chad a écrit :
>> >
>> > What's actually the problem with expanding branches?
>> >
> To me at least, it makes it harder to see what's actually deployed at
> a given time. Try `git branch -r` on core. We're at 86 branches now...that's
> 172 if you've got two remotes. It's only going to get worse and it'll be
> progressively harder to spot what's important.
We could simply delete the old branches after a few deployment cycles.
If we want to keep the reference for history purposes, would tagging the
tip of it be enough ?
If you find yourself struggling to find out the last 2 wmf branches, you
can write a tiny script to sort and filter the branches, keeping only
the last two.
--
Antoine "hashar" Musso
------------------------------
Message: 3
Date: Thu, 26 Sep 2013 10:52:38 +0200
From: Željko Filipin <zfilipin(a)wikimedia.org>
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Subject: Re: [Wikitech-l] MediaWiki-Vagrant: new features
Message-ID:
<CABfBeAr+=eBUMSTfHEMJrHGVE77rBngryhQeoyPcoxZqDh589A(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi Ori,
Is there a reason for having Guest Additions Version 4.1.12 in the VM
instead of 4.2?
$ vagrant up
(...)
[default] VM booted and ready for use!
[default] The guest additions on this VM do not match the installed version
of
VirtualBox! In most cases this is fine, but in rare cases it can
cause things such as shared folders to not work properly. If you see
shared folder errors, please update the guest additions within the
virtual machine and reload your VM.
Guest Additions Version: 4.1.12
VirtualBox Version: 4.2
[default] Setting hostname...
(...)
I will file a bug in Bugzilla if that is something you can fix.
Željko
------------------------------
Message: 4
Date: Thu, 26 Sep 2013 10:57:06 +0200
From: Denny Vrandečić <denny.vrandecic(a)wikimedia.de>
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Subject: Re: [Wikitech-l] Fwd: afch licensing question
Message-ID:
<CANnnRRtO5dCNkPnQeVCEsob6pUU-RofazJP+z981DOj7BMiNYQ(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
CC-BY-SA/GFDL is in the same spirit as GPL, which is an obviously
acceptable license for WMF (since MediaWiki is written in it).
Can you explain the need to relicense it under MIT?
2013/9/26 Steven Walling <swalling(a)wikimedia.org>
> Forwarding, with permission.
>
> For background the "AFC Helper" script is one that assists English
> Wikipedians reviewing pages in the Articles for Creation queue, which
> currently is severely backlogged.
>
> Any thoughts on the licensing issue, from folks with experience on the
> question of gadget/userscript licensing?
>
> ---------- Forwarded message ----------
> From: Mr. Donald J. Fortier II <technical_13(a)yahoo.com>
> Date: Wed, Sep 25, 2013 at 8:30 PM
> Subject: afch licensing question
> To: "swalling(a)wikimedia.org" <swalling(a)wikimedia.org>
>
>
> Per the discussion on https://github.com/WPAFC/afch/issues/61 one of the
> previous contributors to the project refuses to agree to relicense AFCH
> under the MIT license. Right now, the script is licensed under
> CC-BY-SA/GFDL, as it was originally coded on-wiki (per
> [[Wikipedia:Copyright]] -- all text-based contributions). This came about
> due to some confusion that can be seen
> https://github.com/WPAFC/afch/issues/60. So, we are unsure as to where to
> go from here. If we replace any code contributed to the project by the
> person that refuses to agree, can we dissolve any requirements to get him
> to agree? Is there enough contribution from him to actually worry about it
> as he hasn't actually written any functions, just converted some stuff from
> old school JavaScript to jQuery? Any advice/assistance on this would be
> appreciated.
>
>
>
> --
> Steven Walling,
> Product Manager
> https://wikimediafoundation.org/
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 | http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
------------------------------
Message: 5
Date: Thu, 26 Sep 2013 11:52:59 +0200
From: Lydia Pintscher <lydia.pintscher(a)wikimedia.de>
To: wikitech-l <wikitech-l(a)lists.wikimedia.org>,
mediawiki-l(a)lists.wikimedia.org
Subject: [Wikitech-l] Job posting: frontend dev (JavaScript) at
Wikimedia Deutschland
Message-ID:
<CABfqUgJpiiM_W=Snszhpr+xaPqeQ5W3j-3+a9idk+6w__0Rk1g(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Heya folks :)
Wikimedia Deutschland is looking for a software developer to work on
all kinds of frontend-related things on exciting projects like
Wikidata in a very cool team. If you're currently looking for a job
and have the necessary skills please apply. You can find details at
https://wikimedia.de/wiki/Software_Developer_(f/m)_focus_on_Frontend_Develo…
Please let me know if you have any questions.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Technical Projects
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
------------------------------
Message: 6
Date: Thu, 26 Sep 2013 03:26:55 -0700
From: Ori Livneh <ori(a)wikimedia.org>
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Subject: Re: [Wikitech-l] MediaWiki-Vagrant: new features
Message-ID:
<CAHXK4BzssgamHU9fixo4aUV0JU+9PRZuHwMWz4vhESbgr9qg5Q(a)mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Thu, Sep 26, 2013 at 1:52 AM, Željko Filipin <zfilipin(a)wikimedia.org>wrote:
> Hi Ori,
>
> Is there a reason for having Guest Additions Version 4.1.12 in the VM
> instead of 4.2?
>
It's what Canonical's Vagrant image provides, and it's because that's the
version that is packaged for Precise. (Remember, guest additions run on the
guest.) You can update to the latest version by running
'update-guest-additions' in the VM.
I'll take the opportunity to remind folks who use Vagrant to send some
positive feedback to Canonical. The Vagrant image they provide is part of a
beta program they have not yet committed to supporting permanently.
Per http://blog.utlemming.org/2013/01/vagrant-cloud-images.html
"For those who use Vagrant, your feedback is essential. Please feel free to
send feedback via the ubuntu-cloud(a)lists.ubuntu.com mailing list."
------------------------------
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
End of Wikitech-l Digest, Vol 122, Issue 65
*******************************************
Hello,
I'm writing to tell you about some cool new MediaWiki-Vagrant features.
MediaWiki-Vagrant now ships with a custom Vagrant plug-in that augments the
default 'vagrant' command-line tool with some additional sub-commands that
are specifically designed to make MediaWiki development more productive and
fun.
The most important addition is a set of four sub-commands for managing
roles. (Roles, you'll recall, are optional software stacks that
MediaWiki-Vagrant can configure automatically. There's a VisualEditor role,
a Scribunto role, a qa/browsertests role, etc.) The new commands are:
$ vagrant list-roles
Lists available roles. Currently enabled roles are marked with a '*'.
$ vagrant enable-role
Enables a role. Example: 'vagrant enable-role visualeditor'.
$ vagrant disable-role <name>
Disables a role.
$ vagrant reset-roles
Disable all roles.
There's a short, 1-minute screencast up at
http://ascii.io/a/4428demonstrating usage. Check it out. I'll wait.
The other cool sub-command that was recently added is 'vagrant run-tests'.
Any command-line arguments following 'run-tests' are passed through to
PHPUnit running on the VM, so it's possible to run (for example) 'vagrant
run-tests extensions/EventLogging'. Finally, there's 'vagrant
puppet-paste'. This uploads the log of your most recent Puppet run to <
dpaste.de> and prints out a URL. This is primarily intended as a debugging
aid.
Additional documentation, including installation help, is up at <
https://www.mediawiki.org/wiki/MediaWiki-Vagrant>.
Please report any bugs you encounter at <
https://bugzilla.wikimedia.org/enter_bug.cgi?product=Tools&component=Vagrant
>.
Ori
Heya folks :)
Wikimedia Deutschland is looking for a software developer to work on
all kinds of frontend-related things on exciting projects like
Wikidata in a very cool team. If you're currently looking for a job
and have the necessary skills please apply. You can find details at
https://wikimedia.de/wiki/Software_Developer_(f/m)_focus_on_Frontend_Develo…
Please let me know if you have any questions.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Technical Projects
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Forwarding, with permission.
For background the "AFC Helper" script is one that assists English
Wikipedians reviewing pages in the Articles for Creation queue, which
currently is severely backlogged.
Any thoughts on the licensing issue, from folks with experience on the
question of gadget/userscript licensing?
---------- Forwarded message ----------
From: Mr. Donald J. Fortier II <technical_13(a)yahoo.com>
Date: Wed, Sep 25, 2013 at 8:30 PM
Subject: afch licensing question
To: "swalling(a)wikimedia.org" <swalling(a)wikimedia.org>
Per the discussion on https://github.com/WPAFC/afch/issues/61 one of the
previous contributors to the project refuses to agree to relicense AFCH
under the MIT license. Right now, the script is licensed under
CC-BY-SA/GFDL, as it was originally coded on-wiki (per
[[Wikipedia:Copyright]] -- all text-based contributions). This came about
due to some confusion that can be seen
https://github.com/WPAFC/afch/issues/60. So, we are unsure as to where to
go from here. If we replace any code contributed to the project by the
person that refuses to agree, can we dissolve any requirements to get him
to agree? Is there enough contribution from him to actually worry about it
as he hasn't actually written any functions, just converted some stuff from
old school JavaScript to jQuery? Any advice/assistance on this would be
appreciated.
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/
Hi,
When the ResourceLoader was deployed (or even before it) to production,
there were migration development guides for gadget/extension developers:
-
http://www.mediawiki.org/wiki/ResourceLoader/Migration_guide_for_extension_…
-
http://www.mediawiki.org/wiki/ResourceLoader/Developing_with_ResourceLoader
Such guides allowed easier adoption of ResourceLoader. We need something
similar for the visual editor:
- Migration - What are the recommended steps to make gadget/extension
VE adapted? [with answers to questions such as: how to get the underlying
model - instead of $('#wpTextbox1').val() and what is this model [and what
modifications to the underlying model are supported/to be avoided by
gadgets/user scripts ] ]
- Development with the VE: guides with explanation for common editor UI
customization, and what is recommended API for it (for example: add custom
toolbar buttons).
Eran
Hey all,
I'm pleased to announce the 1.1 release of the ParserHooks
library.ParserHooksis a small library that adds an object orientated
and declarative parser
hook interface on top of MediaWiki.
https://github.com/wikimedia/mediawiki-extensions-ParserHooks/blob/master/R…
This new version simplifies the API a little and adds support for
registering hook handlers as tag extensions. This library is now also used
by the SubPageList extension.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil. ~=[,,_,,]:3
--
On Wed, Sep 25, 2013 at 7:11 PM, Luca Martinelli
<martinelliluca(a)gmail.com>wrote:
> May I just ask why all names have been changed?
>
wikipedia is redundant, because you can run this framework in any
mediawiki-based wiki, and It's simpler and shorter, We used this name in
git, nightly distributor, bugzilla, etc. but It was not official
> And why all those new nested folders? Just curiosity.
>
Sorry but I can't understand what you are saying
> L.
> Il giorno 25/set/2013 17:27, "Amir Ladsgroup" <ladsgroup(a)gmail.com> ha
> scritto:
>
>> Hello folks!
>> *Name of pywikipedia or pywikipediabot is officially changed to
>> "pywikibot", please update local documentation
>> *Bug tracker of pywikibot is changed from sf.net to bugzilla. Open bugs
>> was imported from there by a bot that legoktm has written [1], So don't
>> file new bugs in sf.net anymore and keep tracking your reports (if you
>> has reported something) in bugzilla,
>>
>> If you like you can hack some of the bugs and make it fixed! [2] and
>> please update local documentation
>>
>> [1] https://git.wikimedia.org/summary/pywikibot%2Fsf-export.git
>> [2]
>> https://bugzilla.wikimedia.org/buglist.cgi?list_id=236065&short_desc=.&reso…
>>
>> Cheers
>> --
>> Amir
>>
>>
>> _______________________________________________
>> Wikitech-ambassadors mailing list
>> Wikitech-ambassadors(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>>
>>
> _______________________________________________
> Wikitech-ambassadors mailing list
> Wikitech-ambassadors(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
>
>
best
--
Amir
Hello folks!
*Name of pywikipedia or pywikipediabot is officially changed to
"pywikibot", please update local documentation
*Bug tracker of pywikibot is changed from sf.net to bugzilla. Open bugs was
imported from there by a bot that legoktm has written [1], So don't file
new bugs in sf.net anymore and keep tracking your reports (if you has
reported something) in bugzilla,
If you like you can hack some of the bugs and make it fixed! [2] and please
update local documentation
[1] https://git.wikimedia.org/summary/pywikibot%2Fsf-export.git
[2]
https://bugzilla.wikimedia.org/buglist.cgi?list_id=236065&short_desc=.&reso…
Cheers
--
Amir