Re: [gentoo-dev] packages up for grabs
Raúl Porcel wrote: Since i don't have too much time nor motivation to fix packages(i prefer doing arch work), i'm asking someone to take the following packages, i'm dumping them to net-p2p atm, but its just Betelgeuse and me, so feel free to maintain them. net-p2p/deluge net-p2p/qbittorrent net-libs/rb_libtorrent I was planning to work on btg and dependencies (so rb_libtorrent) when I will have some time. Probably after my GSOC. Mounir
Re: [gentoo-dev] Gentoo Council 2009/2010 - Nominations are now open
Thanks again for the nomination, but i won't run for council. cheers, Wernfried -- Wernfried Haas (amne) - amne (at) gentoo.org Gentoo Forums - http://forums.gentoo.org forum-mods (at) gentoo.org #gentoo-forums (freenode) pgpOx0i3PV8aj.pgp Description: PGP signature
Re: [gentoo-dev] Gentoo Council 2009/2010 - Nominations are now open
On E, 2009-06-01 at 10:48 +0200, Patrick Lauer wrote: People I nominate: * leio / mraudsepp, because he's done a really good job protecting the distro's interests I accept -- Mart Raudsepp Gentoo Developer Mail: l...@gentoo.org Weblog: http://planet.gentoo.org/developers/leio signature.asc Description: This is a digitally signed message part
[gentoo-dev] Adding Nipper license to the tree
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya guys, One of the packages I maintain (nipper) has recently undergone a change of license, from being GPLed to a new license that whilst mostly being commercial features a non-commercial/personal use element. Due to the new license (and the no redistribution of any kind bits) the package will need mirror/fetch restrictions, which is fine. My concern is with the copyright clause which states: Any patches or updates that the Licensee may develop for NIPPER must be immediately submitted to the Licensor. In addition, the Licensee will forthwith transfer without charge all current and future rights including copyrights and other intellectual property rights relating to such updates to the Licensor. I'm wondering how this might affect any in-tree patching, because whilst I'm aware of this clause and happy to send any patches upstream and/or not patch at all, I can't say the same for every Gentoo dev that might want to fix a problem. I know the upstream author personally, and he's providing the source-code primarily for Gentoo users (we can always use the existing binary RPMs if patching is an issue), but I thought I should ask what the best course of action would be here? Thanks, Mike 5:) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAko1XWYACgkQu7rWomwgFXpWYACfaJO7c77PVD4kuEsPrLOG7Qsx Sw0An1JswTwSB0Asa2BEUQZyS4OBGbeE =rinb -END PGP SIGNATURE- LICENCE AGREEMENT FOR NIPPER This is a binding, legal agreement between you the end user (the Licensee) and Titania Limited (Company Number 06870498) whose registered office is at 46 Cormorant Rise, Worcester, WR2 4BA, United Kingdom (the Licensor) for the use of the Nipper software products (NIPPER) and electronic documentation (including the Nipper SDK). By installing, copying, downloading, accessing or otherwise using NIPPER you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this agreement you may not download, install or use NIPPER. 1. Definitions Computer shall mean a device that NIPPER is installed on/run from. Device shall mean a device for which NIPPER is used to produce a report. Commercial Use shall mean any use of Nipper for profit whether by or for the Licensee or for any person, organisation, government or government department. For the avoidance of doubt Commercial Use includes the use by the Licensee in the course of research funded by a commercial organisation. Non-Commercial Use shall mean any use of NIPPER (by an individual) which is not for profit. Subscription Fee shall mean the fee payable for a Commercial Use Licence. Subscription Period is the period renewable every 1, 2 or 3 years (as defined by the subscription) from the date the Subscription Fee is paid for which the Licensee may use NIPPER on a specified number of individual Devices. 2. Licensed Software 2.1 This Licence relates to all versions of NIPPER developed by the Licensor. The Licensor reserves all rights. 3. Grant Of Licence 3.1 End User Commercial Use Licence 3.1.1 The Licensee may only use NIPPER after paying the Subscription Fee. The Subscription Fee shall be determined in accordance with the Licensor's (or the Licensor's reseller's) price list which shall be available from the Licensor (or the Licensor's reseller's) on request. 3.1.2 The Licensor grants the Licensee a non-exclusive, non-transferable licence to use NIPPER during the Subscription Period. 3.1.3 The Licensee may only use NIPPER for the number of licensed Devices during the Subscription Period. Any additional use will require the payment of an additional Subscription Fee. 3.1.4 The Licensee may only install NIPPER on Computers owned by the Licensee. The Licensee may install NIPPER on any number of Computers owned by the Licensee. An exclusion is made where the Licensee provides a managed service, then the Licensee may additionally install NIPPER on devices managed by the Licensee. 3.1.5 The Licensee may not sell or re-sell NIPPER or otherwise share, exploit or allow it to be transferred to any person for value or for Commercial Use. 3.1.6 The Licensee may not rent, lease, hire out or lend NIPPER. 3.2 System Integrator Commercial Use Licence 3.2.1 The Licensee may only use NIPPER after paying the Subscription Fee. The Subscription Fee shall be determined in accordance with the Licensor's (or the Licensor's reseller's) price list which shall be available from the Licensor (or the Licensor's reseller's) on request. 3.2.2 The Licensor licenses NIPPER for use in commercial products developed by the Licensee where NIPPER comprises not more than 50% of the product's functionality (the Licensed Product). 3.2.3 The Licensor grants the Licensee the right to integrate NIPPER using only the NIPPER API, library and executables developed by the Licensor. 3.2.4 The Licensor grants the Licensee a
Re: [gentoo-dev] Adding Nipper license to the tree
On Sun, 2009-06-14 at 21:28 +0100, Mike Auty wrote: but I thought I should ask what the best course of action would be here? If it were my ebuild, I would not add the updates under the new, draconic license and either fork the GPL'd code or mask the package for removal. You can not in any way guarantee that a Gentoo user is non-commercial. Especially the patch clause would make ebuilds unsustainable. As you say the author personally, perhaps there is a sense of reason that you could appeal to. Thanks, Mike 5:) Regards. Tony V. signature.asc Description: This is a digitally signed message part
[gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2009-06-14 23h59 UTC
The attached list notes all of the packages that were added or removed from the tree, for the week ending 2009-06-14 23h59 UTC. Removals: x11-misc/xinput 2009-06-08 13:25:11 remi x11-misc/xkbdata2009-06-08 13:53:03 remi sys-cluster/mpich 2009-06-13 16:35:49 jsbronder dev-ruby/ruby-config2009-06-14 10:49:06 a3li Additions: x11-apps/xinput 2009-06-08 12:02:34 remi media-sound/qpitch 2009-06-08 13:33:47 hwoarang app-emulation/qtemu 2009-06-08 15:58:04 hwoarang app-pda/libplist2009-06-08 22:57:56 chainsaw app-pda/libiphone 2009-06-08 23:16:11 chainsaw app-pda/ifuse 2009-06-08 23:26:57 chainsaw dev-perl/POE-Test-Loops 2009-06-09 02:56:41 robbat2 dev-perl/POE-XS-Loop-EPoll 2009-06-09 02:56:59 robbat2 dev-perl/POE-XS-Loop-Poll 2009-06-09 02:57:17 robbat2 dev-perl/POE-XS-Queue-Array 2009-06-09 02:57:35 robbat2 dev-perl/XML-CompactTree-XS 2009-06-09 02:57:53 robbat2 dev-ruby/autotest-rails 2009-06-09 18:24:16 graaff dev-perl/Set-Infinite 2009-06-09 20:03:28 tove dev-perl/DateTime-Set 2009-06-09 20:06:44 tove dev-perl/Test-Most 2009-06-09 20:09:23 tove dev-perl/boolean2009-06-09 20:10:57 tove dev-perl/Time-Duration-Parse2009-06-09 20:16:47 tove dev-perl/Test-MockTime 2009-06-09 20:23:17 tove dev-perl/MooseX-AttributeHelpers2009-06-09 20:29:46 tove dev-perl/MooseX-ClassAttribute 2009-06-09 20:34:01 tove dev-perl/Olson-Abbreviations2009-06-09 20:38:38 tove dev-perl/DateTime-Format-Natural2009-06-09 20:45:54 tove dev-perl/DateTime-Event-Recurrence 2009-06-09 20:49:24 tove dev-perl/DateTime-Event-ICal2009-06-09 20:54:18 tove dev-perl/DateTime-Format-DateManip 2009-06-09 20:57:20 tove dev-perl/DateTime-Format-DateParse 2009-06-09 21:00:54 tove dev-perl/DateTime-Format-Flexible 2009-06-09 21:04:54 tove dev-perl/DateTime-Format-ICal 2009-06-09 21:06:41 tove dev-perl/DateTimeX-Easy 2009-06-09 21:10:56 tove dev-perl/MooseX-Types 2009-06-09 21:15:34 tove dev-perl/MooseX-Types-DateTime-ButMaintained2009-06-09 21:20:21 tove dev-perl/MooseX-Types-DateTimeX 2009-06-09 21:22:24 tove media-video/minitube2009-06-09 23:13:09 hwoarang app-editors/qxmledit2009-06-09 23:29:28 hwoarang dev-perl/Regexp-IPv62009-06-09 23:43:51 robbat2 dev-perl/NetAddr-IP 2009-06-10 01:26:08 robbat2 dev-perl/Net-DNS-Resolver-Programmable 2009-06-10 01:26:28 robbat2 dev-perl/Mail-SPF 2009-06-10 01:26:49 robbat2 sci-misc/vitables 2009-06-11 20:44:13 spock x11-themes/skulpture2009-06-12 11:42:12 scarabeus dev-libs/json-glib 2009-06-13 08:09:05 voyageur app-misc/activylircd2009-06-13 10:15:27 zzam dev-perl/Sane 2009-06-14 18:41:21 tove dev-perl/Gtk2-ImageView 2009-06-14 19:50:15 tove -- Robin Hugh Johnson Gentoo Linux Developer E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 Removed Packages: x11-misc/xinput,removed,remi,2009-06-08 13:25:11 x11-misc/xkbdata,removed,remi,2009-06-08 13:53:03 sys-cluster/mpich,removed,jsbronder,2009-06-13 16:35:49 dev-ruby/ruby-config,removed,a3li,2009-06-14 10:49:06 Added Packages: x11-apps/xinput,added,remi,2009-06-08 12:02:34 media-sound/qpitch,added,hwoarang,2009-06-08 13:33:47 app-emulation/qtemu,added,hwoarang,2009-06-08 15:58:04 app-pda/libplist,added,chainsaw,2009-06-08 22:57:56 app-pda/libiphone,added,chainsaw,2009-06-08 23:16:11 app-pda/ifuse,added,chainsaw,2009-06-08 23:26:57 dev-perl/POE-Test-Loops,added,robbat2,2009-06-09 02:56:41 dev-perl/POE-XS-Loop-EPoll,added,robbat2,2009-06-09 02:56:59 dev-perl/POE-XS-Loop-Poll,added,robbat2,2009-06-09 02:57:17 dev-perl/POE-XS-Queue-Array,added,robbat2,2009-06-09 02:57:35 dev-perl/XML-CompactTree-XS,added,robbat2,2009-06-09 02:57:53 dev-ruby/autotest-rails,added,graaff,2009-06-09 18:24:16
Re: [gentoo-dev] Adding Nipper license to the tree
On Sun, Jun 14, 2009 at 09:28:24PM +0100, Mike Auty wrote: One of the packages I maintain (nipper) has recently undergone a change of license, from being GPLed to a new license that whilst mostly being commercial features a non-commercial/personal use element. The website stills says GPL v3: http://nipper.titania.co.uk/licensing.php Reading the license, I'm really wondering why the change was made. It feels like it was written by a lawyer with little to no understanding of open source licensing - with the sole purpose of producing revenue, without regards as to the rights of the user. Additionally, the lawyer is not cognizant of some issues in the jurisdiction of the contract. Due to the new license (and the no redistribution of any kind bits) the package will need mirror/fetch restrictions, which is fine. My concern is with the copyright clause which states: ... I'm wondering how this might affect any in-tree patching, because whilst I'm aware of this clause and happy to send any patches upstream and/or not patch at all, I can't say the same for every Gentoo dev that might want to fix a problem. I'm answering this further down. I know the upstream author personally, and he's providing the source-code primarily for Gentoo users (we can always use the existing binary RPMs if patching is an issue), but I thought I should ask what the best course of action would be here? Try hard to persuade him not to pursue this license. Alternatively, dual-license instead of applying this license only. If his userbase cares enough about the product, they're going to fork after seeing this new license. Similar to the TrueCrypt issue, I'd say do NOT commit any ebuild covered by this license until the matter is resolved. IANAL, but I do follow lots of open-source licensing, and occasionally help organizations in compliance with open-source licensing, so here are my comments on various portions of the license. At least two clauses are unenforceable or outright illegal in some parts of the world. Several more are at the very least questionable. LICENCE AGREEMENT FOR NIPPER ... By installing, copying, downloading, accessing or otherwise using NIPPER you agree to be bound by the terms of this Agreement. If you do not agree to the terms of this agreement you may not download, install or use NIPPER. Click-through licenses are invalid in many jurisdictions. Additionally, there's no provision in the license, for anybody to be bound by the license simply for downloading it and NOT unpacking it. 2.1 This Licence relates to all versions of NIPPER developed by the Licensor. The Licensor reserves all rights. Nope, if previous versions were under GPL, they remain under it. They may be additionally licensed under new terms, but the GPL remains in effect AS well. 3.1 End User Commercial Use Licence ... 3.2 System Integrator Commercial Use Licence (I'd say Gentoo might fit under System Integrator, but certainly not Commercial). 3.3.3 The Licensee may only use NIPPER for up to five (5) Devices. Any additional use will require a Commercial Use license. This is bizarre. So a Not-for-profit organization or university couldn't use it for their IT infrastructure. 4.2 The Licensor reserves the right to revise the Licence at any time without notice. The current licence terms are available from the Licensors web site. This clause is invalid is many jurisdictions. http://www.out-law.com/page-8328 (covers UK and US) http://www.techdirt.com/articles/20090508/0212134792.shtml (US) Specifically, all parties MUST agree to a change for it to be valid. Additionally since the license granted in 3.3.1 does not expire, you can continue to use it forever without agree to the change. 5. Technical Support 5.1 Unless otherwise arranged, technical support for NIPPER is provided through the Licensor's web site http://www.titania.co.uk Some lawyers would say that due to this clause can't offer support for the packaging of Nipper on Bugzilla? Any patches or updates that the Licensee may develop for NIPPER must be immediately submitted to the Licensor. In addition, the Licensee will forthwith transfer without charge all current and future rights including copyrights and other intellectual property rights relating to such updates to the Licensor. Gentoo is NOT a licensee under any of the classes of use listed in the license. We don't use it, and we're not a commercial integrator. Ergo there is a loophole that allows us to patch it without losing our rights to the patches. HOWEVER, I'd be concerned that the context (non-modified) portions of the path are still bound by the original license, and would violate non-distribution. -- Robin Hugh Johnson Gentoo Linux Developer Infra Guy E-Mail : robb...@gentoo.org GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 pgpAlQdpaBmXp.pgp Description: PGP signature
Re: [gentoo-dev] Gentoo Council 2009/2010 - Nominations are now open
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jorge Manuel B. S. Vicetto wrote: Hello fellow developers and users. Nominations for the Gentoo Council 2009/2010 are now open for the next two weeks (until 23:59 UTC, 14/06/2009). Nominations are now closed. An email with further details about the election will be sent tomorrow. All nominations must be sent to the gentoo-dev mailing list. If you were nominated and want to run, you have to accept your nomination on the same mailing list. Here are the rules: * Council elections generally happen once a year * The council is composed of seven elected members * Nominations are allowed from June 1st 00H00 UTC to June 14th 23H59 UTC * Only Gentoo developers may be nominated * Anyone can nominate (nominating yourself is OK) * Nominees must accept their nomination before voting begins * Voting is opened from June 16th 00H00 UTC to June 30th 23H59 UTC (there is one day of break between nominations and voting so the infra team has time to set up everything) * Only Gentoo developers may vote * Gentoo uses the Condorcet method of voting The page listing all nominations is here: http://www.gentoo.org/proj/en/elections/council-200906-nominees.xml If you don't know what the Gentoo Council is, you can read about it here: http://www.gentoo.org/proj/en/council/ If you want to ask a question or share your thoughts, contact any of the election officials: Jorge Manuel B. S. Vicetto (jmbsvicetto) Łukasz Damentko (rane) Roy Bamford (neddyseagoon) Shyam Mani (fox2mike) will be doing infra magic. You can send us an e-mail (gentoo-elections at gentoo dot org) or find us on Freenode (#gentoo-elections, #gentoo-dev, so on). For the elections team, - -- Regards, Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org Gentoo- forums / Userrel / Devrel / SPARC / KDE -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAko10eIACgkQcAWygvVEyAJjPgCgkh5bZDMFnpx6lbQ8cYNHQml4 xT8AmwXVUzX3JIOBDYvjeyJcGYQW+rBU =lwbo -END PGP SIGNATURE-
[gentoo-dev] [Fwd: 2009 council nominations]
Hi. I'm forwarding Ned's (solar) mail accepting his nomination for the council. -- Regards, Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org Gentoo- forums / Userrel / Devrel / SPARC / KDE ---BeginMessage--- As I'm not subscribed to the getnoo-dev mailing list but rather make use of the archives. I can't send a mail there to officially accept the council nomination. So I was told to send my acceptance of the nomination it here. Hopefully this is ok. ---End Message--- signature.asc Description: OpenPGP digital signature
