Re: [Bf-committers] Visibility of attribution

[Ton Roosendaal]

Hi Alex,

Dalai's reply is excellent, hope you can follow this for now.

For Blender we really should resolve this topic now indeed; there's a  
strong (legal) lobby in the OS world to make projects use developer  
agreements, whith good clarity about copryright origins of  
contributions and an agreement by contributors to accept on the GPL  
(or other) license.

Another relevant topic is to clearly define in which cases (c) goes to  
BF. There's sensitive development areas that can easily picked up by  
legal lizards to start IP or patent violation investigations. This is  
a reason why FSF advices to migrate rights to them. Blender has a  
fortunate legal base in the EU, giving it a bit more stable grounds  
for IP/patent attacks than in USA.

A developer agreement can also cover up for future adjustments in the  
covered license, worded in a way developers feel confident in (like  
keep it gpl compliant) but with sufficient open ends to upgrade a  
license or give out minor but relevant exceptions for extensions via  
Py or plugins.

I've mailed a while ago about this initiative: http://harmonyagreements.org/

Proposal: I'll check on this during the next 2 weeks in more detail,  
and come with a proposal for it. Will get at least feedback/ 
endorsement from the current project admins (brecht, campbell, matt e,  
martin p) on this too! We then can have the topic for public review  
here.

-Ton-


Ton Roosendaal  Blender Foundation   t...@blender.orgwww.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

On 21 Jun, 2011, at 4:52, Alex Fraser wrote:

> Hi all,
>
> When doing some work for a client recently, I developed a patch for  
> Blender. The client is happy to contribute the code back to Blender,  
> however they are concerned about attribution.
>
> Currently it seems there are no clear guidelines about how  
> attribution is given for contributions. My preference, and that of  
> my client, is that detailed copyright notices should be visible both  
> in the code and in Blender's GUI. This is not unusual: consider the  
> Linux kernel (e.g. [1]) and the GIMP (e.g. [2-4]), and the About  
> dialog boxes of gedit[5] and Firefox[6].
>
> Apart from giving contributors credit, detailed copyright notices in  
> the code would better satisfy the GPL, which states in section 2.a:
>
>a) You must cause the modified files to carry prominent notices
>stating that you changed the files and the date of any change.
>
>
> I propose that:
>
> 1. All future contributions be attributed in modified source files  
> as "Copyright  ", or at the  
> contributor's option, in another form that conveys the same  
> information.
>
> 2. The same copyright information be collected in a place accessible  
> from the GUI, either in the splash screen itself (perhaps in a tab)  
> or on a web page linked to from the splash screen.
>
> What do you think?
>
> Cheers,
> Alex
>
> -- 
> Alex Fraser
> Software Engineer
> The Victorian Partnership for Advanced Computing
>
> [1] 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=kernel/cgroup.c
> [2] http://git.gnome.org/browse/gimp/plain/plug-ins/common/polar-coords.c
> [3] http://git.gnome.org/browse/gimp/tree/plug-ins/twain/twain.h
> [4] http://git.gnome.org/browse/gimp/tree/libgimp/gimpitemcombobox.c
> [5] http://www.pasteall.org/pic/13959
> [6] http://www.pasteall.org/pic/13961
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] release ahoy soon, last chance for tests!

[Ton Roosendaal]

Hi,

Linux/OSX/Windows Platform builders have reported in too. Pete is  
around for freebsd?

The splash committee is still searching :) Final commits + tag will  
follow this evening or tomorrow morning (EU timezone). You can already  
prepare builds and just svn-up though!

Regression files seem to survive OK. :) But tests are welcome,  
especially scripts.

Laters,

-Ton-


Ton Roosendaal  Blender Foundation   t...@blender.orgwww.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

[Bf-committers] Blender 2.58 release AHOY!

[Ton Roosendaal]

Hi all,

That went smooth today :)

Splash commit had r37699, tag is being done now (r37700 most likely,  
Nathan will confirm!)
Let them build machines run then! Put builds on the usual places and  
notify me.

During tomorrow (wednesday) logs/docs will be updated too, and all  
goes life when the builds are in.

Thanks a lot everyone for the great work!

-Ton-


Ton Roosendaal  Blender Foundation   t...@blender.orgwww.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] release ahoy soon, last chance for tests!

[pete larabell]

Yeah I'm still alive :)

On Tue, Jun 21, 2011 at 11:19 AM, Ton Roosendaal  wrote:
> Hi,
>
> Linux/OSX/Windows Platform builders have reported in too. Pete is
> around for freebsd?
>
> The splash committee is still searching :) Final commits + tag will
> follow this evening or tomorrow morning (EU timezone). You can already
> prepare builds and just svn-up though!
>
> Regression files seem to survive OK. :) But tests are welcome,
> especially scripts.
>
> Laters,
>
> -Ton-
>
> 
> Ton Roosendaal  Blender Foundation   t...@blender.org    www.blender.org
> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.58 release AHOY!

[Nathan Letwory]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 21.6.2011 19:59, Ton Roosendaal wrote:
> Hi all,
> 
> That went smooth today :)
> 
> Splash commit had r37699, tag is being done now (r37700 most likely,  
> Nathan will confirm!)

Almost r37700 (I did get the revision on my name, but) r37702 became the
correct revision. So release builders, check out
https://svn.blender.org/svnroot/bf-blender/tags/blender-2.58-release
with revision r37702 and do your thing.

/Nathan

- -- 
Nathan Letwory
Blender Foundation | Letwory Interactive
http://www.blender.org | http://www.letworyinteractive.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOANPRAAoJEKtfN7KsE0Ttg7IH/26bJ4KQaYgAvgJ7/BjTIj4y
kVsrPhLXqAGTZNBbTgzFcKITSXB0HzYjYZGc0BAqBpfn39Frer5Ta0f5w0ke+GGn
yOW4fzqIg2U4fk4l2M/GizhXHtF/HZwlBBKGUA/uzk12ZV+f6q2jMBu+FNkiViYJ
tG34PYpDaAxI4qRYbDzKYKf0d10wrgrrztv4WQxOXKQDoJs9YJ9nyWQw0ZvBPvUN
asANTC7rSIKhxFncRfOfeX1dyZAoVwAVk+dJU64xQ2Nu1w2LcKeljijkfNKkyNHE
AVrgGYHQk/VEDbBRh+CYZ7KkK+bbbr3+/CeyetPocqd7QhKjxdWM0grxp8Ur3t4=
=nB2L
-END PGP SIGNATURE-
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.58 release AHOY!

[pete larabell]

FreeBSD 32 and 64 bit are up.

On Tue, Jun 21, 2011 at 12:24 PM, Nathan Letwory  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 21.6.2011 19:59, Ton Roosendaal wrote:
>> Hi all,
>>
>> That went smooth today :)
>>
>> Splash commit had r37699, tag is being done now (r37700 most likely,
>> Nathan will confirm!)
>
> Almost r37700 (I did get the revision on my name, but) r37702 became the
> correct revision. So release builders, check out
> https://svn.blender.org/svnroot/bf-blender/tags/blender-2.58-release
> with revision r37702 and do your thing.
>
> /Nathan
>
> - --
> Nathan Letwory
> Blender Foundation | Letwory Interactive
> http://www.blender.org | http://www.letworyinteractive.com
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQEcBAEBAgAGBQJOANPRAAoJEKtfN7KsE0Ttg7IH/26bJ4KQaYgAvgJ7/BjTIj4y
> kVsrPhLXqAGTZNBbTgzFcKITSXB0HzYjYZGc0BAqBpfn39Frer5Ta0f5w0ke+GGn
> yOW4fzqIg2U4fk4l2M/GizhXHtF/HZwlBBKGUA/uzk12ZV+f6q2jMBu+FNkiViYJ
> tG34PYpDaAxI4qRYbDzKYKf0d10wrgrrztv4WQxOXKQDoJs9YJ9nyWQw0ZvBPvUN
> asANTC7rSIKhxFncRfOfeX1dyZAoVwAVk+dJU64xQ2Nu1w2LcKeljijkfNKkyNHE
> AVrgGYHQk/VEDbBRh+CYZ7KkK+bbbr3+/CeyetPocqd7QhKjxdWM0grxp8Ur3t4=
> =nB2L
> -END PGP SIGNATURE-
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.58 release AHOY!

[Sergey I. Sharybin]

  Hi all,

I've uploaded linux 32/64 bit builds to 
http://download.blender.org/ftp/incoming/

It'll be cool if somebody else would check this archives. This week is 
neurous for me so i could forgot something.

P.S. Thx everyone and congrats with release!

pete larabell wrote:
> FreeBSD 32 and 64 bit are up.
>
> On Tue, Jun 21, 2011 at 12:24 PM, Nathan Letwory  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 21.6.2011 19:59, Ton Roosendaal wrote:
>>> Hi all,
>>>
>>> That went smooth today :)
>>>
>>> Splash commit had r37699, tag is being done now (r37700 most likely,
>>> Nathan will confirm!)
>> Almost r37700 (I did get the revision on my name, but) r37702 became the
>> correct revision. So release builders, check out
>> https://svn.blender.org/svnroot/bf-blender/tags/blender-2.58-release
>> with revision r37702 and do your thing.
>>
>> /Nathan
>>
>> - --
>> Nathan Letwory
>> Blender Foundation | Letwory Interactive
>> http://www.blender.org | http://www.letworyinteractive.com
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.10 (MingW32)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iQEcBAEBAgAGBQJOANPRAAoJEKtfN7KsE0Ttg7IH/26bJ4KQaYgAvgJ7/BjTIj4y
>> kVsrPhLXqAGTZNBbTgzFcKITSXB0HzYjYZGc0BAqBpfn39Frer5Ta0f5w0ke+GGn
>> yOW4fzqIg2U4fk4l2M/GizhXHtF/HZwlBBKGUA/uzk12ZV+f6q2jMBu+FNkiViYJ
>> tG34PYpDaAxI4qRYbDzKYKf0d10wrgrrztv4WQxOXKQDoJs9YJ9nyWQw0ZvBPvUN
>> asANTC7rSIKhxFncRfOfeX1dyZAoVwAVk+dJU64xQ2Nu1w2LcKeljijkfNKkyNHE
>> AVrgGYHQk/VEDbBRh+CYZ7KkK+bbbr3+/CeyetPocqd7QhKjxdWM0grxp8Ur3t4=
>> =nB2L
>> -END PGP SIGNATURE-
>> ___
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>


-- 
With best regards, Sergey I. Sharybin

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.58 release AHOY!

[Campbell Barton]

On Tue, Jun 21, 2011 at 4:59 PM, Ton Roosendaal  wrote:
> Hi all,
>
> That went smooth today :)
>
> Splash commit had r37699, tag is being done now (r37700 most likely,
> Nathan will confirm!)
> Let them build machines run then! Put builds on the usual places and
> notify me.
>
> During tomorrow (wednesday) logs/docs will be updated too, and all
> goes life when the builds are in.
>
> Thanks a lot everyone for the great work!
>
> -Ton-

finished editing the changelog before heading off to bed.
I've tried to make the first section more readable for users.

http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/changelog_258

Feel free to add anything you think is worth a special mention to the
'Prominent features' section, or expand on the descriptions.

Also, the addons svn still needs to be added into the changelog.
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.58 release AHOY!

[Jass]

please note that #27666 
 is 
still not fixed for Windows-32,
so maybe it should be removed from the changelog ?
I tried to find the cause of the problem on a 32-bit build of Blender
but i had no luck. Domino has added a comment this morning.
Maybe that helps to at least define a workaround ?

-Gaia-

Am 21.06.2011 20:42, schrieb Campbell Barton:
> On Tue, Jun 21, 2011 at 4:59 PM, Ton Roosendaal  wrote:
>> Hi all,
>>
>> That went smooth today :)
>>
>> Splash commit had r37699, tag is being done now (r37700 most likely,
>> Nathan will confirm!)
>> Let them build machines run then! Put builds on the usual places and
>> notify me.
>>
>> During tomorrow (wednesday) logs/docs will be updated too, and all
>> goes life when the builds are in.
>>
>> Thanks a lot everyone for the great work!
>>
>> -Ton-
> finished editing the changelog before heading off to bed.
> I've tried to make the first section more readable for users.
>
> http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/changelog_258
>
> Feel free to add anything you think is worth a special mention to the
> 'Prominent features' section, or expand on the descriptions.
>
> Also, the addons svn still needs to be added into the changelog.
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Blender 2.58 release AHOY!

[Sergey I. Sharybin]

  Hi,

I could remember OpenCOLLADA was recently updated for Win32/64. But I 
can't remember update of OSX libraries and I haven't updated OpenCOLLADA 
in my buildbot environment.

I'd prefer to keep libraries versions in sync. So, please do not use my 
linux builds as builds avalaible for downloading from b.o -- I'll 
upgrade them in 9hrs (I'll be ~10 a-dam time). And I also want OSX build 
also use the same OpenCOLLADA version.

Ton Roosendaal wrote:
> Hi all,
>
> That went smooth today :)
>
> Splash commit had r37699, tag is being done now (r37700 most likely,
> Nathan will confirm!)
> Let them build machines run then! Put builds on the usual places and
> notify me.
>
> During tomorrow (wednesday) logs/docs will be updated too, and all
> goes life when the builds are in.
>
> Thanks a lot everyone for the great work!
>
> -Ton-
>
> 
> Ton Roosendaal  Blender Foundation   t...@blender.orgwww.blender.org
> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands
>
> ___
> Bf-committers mailing list
> Bf-committers@blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>


-- 
With best regards, Sergey I. Sharybin

___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers

Re: [Bf-committers] Visibility of attribution

[Alex Fraser]

Hi Ton,

- Original Message -
> From: "Ton Roosendaal" 
> Dalai's reply is excellent, hope you can follow this for now.
> 
> For Blender we really should resolve this topic now indeed; there's a
> strong (legal) lobby in the OS world to make projects use developer
> agreements, whith good clarity about copryright origins of
> contributions and an agreement by contributors to accept on the GPL
> (or other) license.

Dalai's reply is great. However if you think the contributor agreement will be 
drawn up soon, I would rather wait for that. I would feel more comfortable if 
there was a formal agreement in place.

> Another relevant topic is to clearly define in which cases (c) goes to
> BF. There's sensitive development areas that can easily picked up by
> legal lizards to start IP or patent violation investigations. This is
> a reason why FSF advices to migrate rights to them. Blender has a
> fortunate legal base in the EU, giving it a bit more stable grounds
> for IP/patent attacks than in USA.

My personal opinion is that a requirement for copyright assignment would hinder 
contributions. But maybe it can be decided on a case-by-case basis.

> [...]
> Proposal: I'll check on this during the next 2 weeks in more detail,
> and come with a proposal for it. Will get at least feedback/
> endorsement from the current project admins (brecht, campbell, matt e,
> martin p) on this too! We then can have the topic for public review
> here.

That sounds good! Please consider my proposals (below) for the format and 
location of the attribution.

Cheers,
Alex

-- 
Alex Fraser
Software Engineer
The Victorian Partnership for Advanced Computing



> On 21 Jun, 2011, at 4:52, Alex Fraser wrote:
> 
> > [...]
> > I propose that:
> >
> > 1. All future contributions be attributed in modified source files
> > as "Copyright  ", or at the
> > contributor's option, in another form that conveys the same
> > information.
> >
> > 2. The same copyright information be collected in a place accessible
> > from the GUI, either in the splash screen itself (perhaps in a tab)
> > or on a web page linked to from the splash screen.
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers