Re: (L)GPLv3

2010-07-15 Thread Alan Cox
> Not true! For example, when you assign to the FSF, the papers you sign
> contain a number of guarantees. From an old version of the assignment
> papers (you should contact the FSF if you are considering using this
> language, as it might have been updated):
> 
> 4. FSF agrees that all distribution of the Works, or of any work
> "based on the Works", or the Program as enhanced by the Works, that
> takes place under the control of FSF or its agents or successors,
> shall be on terms that explicitly and perpetually permit anyone
> possessing a copy of the work to which the terms apply, and
> possessing accurate notice of these terms, to redistribute copies of
> the work to anyone on the same terms.  These terms shall not
> restrict which members of the public copies may be distributed to.
> These terms shall not require a member of the public to pay any
> royalty to FSF or to anyone else for any permitted use of the work
> they apply to, or to communicate with FSF or its agents or assignees
> in any way either when redistribution is performed or on any other
> occasion.

And ask your lawyer what happens if the FSF goes bankrupt. Also btw in
many countries check copyright assignment is actually possible !


___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: (L)GPLv3

2010-07-15 Thread Andy Wingo
Greets :)

A couple points of clarification:

On Wed 14 Jul 2010 21:45, Christian Persch  writes:

> [In] copyright assignment, you don't have *any* guarantees about the
> terms the new 'owner' may choose to distribute your work under.

Not true! For example, when you assign to the FSF, the papers you sign
contain a number of guarantees. From an old version of the assignment
papers (you should contact the FSF if you are considering using this
language, as it might have been updated):

4. FSF agrees that all distribution of the Works, or of any work
"based on the Works", or the Program as enhanced by the Works, that
takes place under the control of FSF or its agents or successors,
shall be on terms that explicitly and perpetually permit anyone
possessing a copy of the work to which the terms apply, and
possessing accurate notice of these terms, to redistribute copies of
the work to anyone on the same terms.  These terms shall not
restrict which members of the public copies may be distributed to.
These terms shall not require a member of the public to pay any
royalty to FSF or to anyone else for any permitted use of the work
they apply to, or to communicate with FSF or its agents or assignees
in any way either when redistribution is performed or on any other
occasion.

> Also, even if you do consider "or later versions" a significant
> risk, you should note that you've *already taken* this risk by using
> LGPL2.1-only, since LGPL2.1 allows using the work under GPL2 or any
> later version of the GPL.

Interesting, I was not aware of this. From the LGPLv2.1:

 3. You may opt to apply the terms of the ordinary GNU General Public
   License instead of this License to a given copy of the Library.  To do
   this, you must alter all the notices that refer to this License, so
   that they refer to the ordinary GNU General Public License, version 2,
   instead of to this License.  (If a newer version than version 2 of the
   ordinary GNU General Public License has appeared, then you can specify
   that version instead if you wish.)  Do not make any other change in
   these notices.

The LGPLv3 does not have that parenthetical statement. I don't know if
that changes things.

Josselin mentions the risks that might arise in specifying an "or later"
license. They are real, but can be mitigated via the proxy clause in the
(L)GPLv3.

 If the Program specifies that a proxy can decide which future
   versions of the GNU General Public License can be used, that proxy's
   public statement of acceptance of a version permanently authorizes you
   to choose that version for the Program.

Happy hacking,

Andy
-- 
http://wingolog.org/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


New external dependencies for Rygel: GUPnP DLNA

2010-07-15 Thread Zeeshan Ali (Khattak)
Hi everyone,
   I would like to start using (and therefore depending on) a new
library called GUPnP DLNA[1].  GUPnP DLNA is a small utility library
that aims to ease the DLNA-related tasks such as media profile
guessing, transcoding to a given profile, etc. This library was
originally aimed to be part of gupnp-av but a hard dependency on
gstreamer was not acceptable for all existing gupnp-av users and hence
it was put in a separate package/library.

   For more information, please read the relevant thread (especially
the first email) on gupnp mailing-list and first release announcement:

http://lists.o-hand.com/gupnp/0915.html
http://lists.o-hand.com/gupnp/0975.html

-- 
Regards,

Zeeshan Ali (Khattak)
FSF member#5124

[1] http://gupnp.org/sources/gupnp-dlna/
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


Re: Bump min vala version to 0.9.3

2010-07-15 Thread Zeeshan Ali (Khattak)
Hi,
   I realized later that this is a micro version bump and I can change
it myself so went and did that (jhbuild and wiki).

On Thu, Jul 15, 2010 at 3:30 PM, Maciej Piechotka  wrote:
> On 15/07/10 01:18, Zeeshan Ali (Khattak) wrote:
>> Hi,
>>    The new vala release contains some improvements to glib API that
>> breaks rygel's build so I would like to use vala 0.9.3 in the next
>> release.
>>
>
> libgee 0.5.2 will and current master do require that version.

   Yes but the minimum version of libgee is at 0.5.0 and recommended
at 0.5.1. Feel free to change that. :)

-- 
Regards,

Zeeshan Ali (Khattak)
FSF member#5124
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Bump min vala version to 0.9.3

2010-07-15 Thread Maciej Piechotka
On 15/07/10 01:18, Zeeshan Ali (Khattak) wrote:
> Hi,
>The new vala release contains some improvements to glib API that
> breaks rygel's build so I would like to use vala 0.9.3 in the next
> release.
> 

libgee 0.5.2 will and current master do require that version.

Regards



signature.asc
Description: OpenPGP digital signature
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list

Re: Bump min vala version to 0.9.3

2010-07-15 Thread Guillaume Desmottes
Le jeudi 15 juillet 2010 à 02:18 +0300, Zeeshan Ali (Khattak) a écrit :
> Hi,
>The new vala release contains some improvements to glib API that
> breaks rygel's build so I would like to use vala 0.9.3 in the next
> release.

libfolks which will be used by Empathy needs this version as well.


G.


-- 
Guillaume Desmottes 
Jabber 
GPG 1024D/711E31B1 | 1B5A 1BA8 11AA F0F1 2169  E28A AC55 8671 711E 31B1

___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list