date:20150918

The point of the intro is not to advise them of ALL their rights in one
paragraph. That's what the GNU license page is for, and also the FOSS link.
Those are complete references to all their rights under the GPL, and they
are included as links in this intro. So filling in the gaps with quick
information solves immediate (question) problems in a way that dumping an
entire page of legal jargon doesn't. :) We want our new users to feel safe
using the software, and companies asking to use GIMP need to be told that
they can do so clearly, and it will not affect their business in a negative
way. You would be surprised how skittish companies are with licensing
concerns. If it even LOOKS like it will cost them in terms of potential
lawsuits, they will gladly go back to buying industry-trusted software
packages. Strangely, we need to fill a gap in trust that is created by
people not having to buy the software. The reason for this is we are
conditioned to expect to have to buy everything, and if it's free, there's
always some catch. It's odd and strange to walk into FOSS world form the
corporate one. I want to get these companies (and professional users) up
and going quickly with GIMP as fast and easily as possible, because it
helps GIMP will become an industry standard tools. What we have gives them
just enough information to get them going fast. That's the information you
want on an intro page. Once they decide the software fits their needs, they
will  be more willing to explore the other advantages of the software in
terms of modifying it, etc. Even this is mentioned in the intro, so it's
not as if it's left out. :)

-C

On Fri, Sep 18, 2015 at 8:08 PM, Nikola M  wrote:

> On 09/18/15 08:38 PM, C R wrote:
>
>>   what they want to know (use case) is not covered by
>> the license in the first place.
>>
> It is not enough to just give them use case and a binary license.
> They must be informed on their rights and have option to display also
> source license.
> It is requirement for distribution under GPL.
>
>
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

I have also changed the spelling of licence to license since that's how it
is all over the gnu website. lol Guess the Americans win this round. ;)

On Fri, Sep 18, 2015 at 7:40 PM, C R  wrote:

> I included a reminder about the warranty it because it's included in big
> bold letters in the about information for GIMP. I have no basis for judging
> whether that's necessary or not, other than someone thought it was worth
> shouting digitally about. :)
>
> -C
>
> On Fri, Sep 18, 2015 at 7:13 PM, Gez  wrote:
>
>> El vie, 18-09-2015 a las 14:10 -0300, Gez escribió:
>>
>> > "The program itself is governed by the terms of the GNU General
>> > Public
>> > License (GPL) which ensures that users have freedom to use the
>> > program
>> > with any purpose, study and modify its source code and share
>> > modifications to the community. You are allowed and encouraged to
>> > share
>> > the program with your friends and colleagues, install it in your
>> > school
>> > or organization and use it for any purpose.
>> > If you're planning to modify the program and re-distribute it with
>> > your
>> > modifications, make sure that you make the source code available too.
>> > That's the only obligation required by the license.
>> > Follow [this link] if you need more information abut the GNU General
>> > Public License."
>>
>> I missed the "no warranty" bit. Is it really necessary? If yes, why?
>> Is it some required legal waiver or just a kind way of saying "don't
>> blame us if something went wrong and you lose your work"?
>>
>> Personally I find that kind of stuff really unnecessary. It's like
>> making an excuse in advance: "look, it may fail, don't blame us".
>> If someone wants to sue you I don't think the "no warranty" claim will
>> make any difference. But seriously, who would do that?
>>
>> I've been working with software for 20 years, I've lost count of the
>> times I've lost work because software failed, crashed or froze.
>> I may or may not cursed the software and its makers when that happened,
>> but never thought about suing the makers for the half hour of work I
>> lost because I forgot to hit CTRL+S (or CTRL+E :-p)
>>
>> That being said, GIMP is probably the most stable software I use, which
>> makes that remark even more unnecessary.
>>
>> Gez.
>> ___
>> gimp-developer-list mailing list
>> List address:gimp-developer-list@gnome.org
>> List membership:
>> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
>> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>>
>
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

El vie, 18-09-2015 a las 20:15 +0200, Nikola M escribió:
> On 09/18/15 07:10 PM, Gez wrote:
> > I wonder if saying that the only license pertains to the source
> > code.
> > I'd say that the binaries are also covered by the license, since
> > you
> > are obligued to make the source code available when you distribute
> > the
> > binaries.
> 
> Source code is covered and source changes, if binaries are
> distributed.
> But binaries itself can have whatever licence one wants, if source
> and 
> source changes are available.
> That is exactly what this thread is about - there is the difference.

No, you're wrong.
You're misinterpreting one the GPL terms that says that you're not
obligued to publish your changes if you're not going to redistribute
the modified program.
That means: If you change the code, you may use the software without
publishing the modifications *IF* you're going to keep the program for
yourself and nobody else.
But if you're going to give the modified program to someone else, you
have to give them the modified sources as well.
It has NOTHING to do with the license. The license for GPL licensed
work is and will be always GPL unless you're the only person who wrote
the original code and therefor you keep the right of re-licensing it to
whatever license you want.
But you can't relicense somebody else's code which is under the GPL.

Gez.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

El vie, 18-09-2015 a las 21:23 -0300, Gez escribió:

> It has NOTHING to do with the license. The license for GPL licensed
> work is and will be always GPL unless you're the only person who
> wrote
> the original code and therefor you keep the right of re-licensing it
> to
> whatever license you want.

I stand myself corrected. In the above paragraph I made a mistake:
If you're the rights holder of the original code you're free to
distribute it with a different license. That's not the same than saying
that you're free to re-license the GPL code.
Once you freed it under the GPL terms, others are free to use it and
you can't forbid them to do what the GPL allows.
You can, however, use the same code in a program distributed with a
different license, but that's because you hold the original rights, the
GPL-licensed code stays GPL.

Gez.

___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Michael Schumacher



On 09/18/2015 11:52 AM, Nikolam wrote:
> On 9/17/15, srikanth  wrote:
>> Dear All,
>>
>>
>>
>> Thank You very Much for the information.
> 
> Of course GPL license is about source code and Binaries can have
> another license,

No.


-- 
Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Nikola M


On 09/18/15 07:10 PM, Gez wrote:

I wonder if saying that the only license pertains to the source code.
I'd say that the binaries are also covered by the license, since you
are obligued to make the source code available when you distribute the
binaries.


Source code is covered and source changes, if binaries are distributed.
But binaries itself can have whatever licence one wants, if source and 
source changes are available.

That is exactly what this thread is about - there is the difference.

If one wants to change binary license of it's own build, one can change 
brending and release changed source.

Every user has same power to release binaries if wants to learn building it.
That is why there is so much different Linux distros with all builded 
packages around.


But centralised development and binary releasing has it's reasons for 
sanity checks, per-patch audit, chain of trust and keeping brending 
together with the quality control in one place, to be used by many with 
confidence.


GPL requires that user of binaries be informed about their rights as 
user and rights to source and changes. So it is not enough to just 
display binary license to user.
That is because per license there are no users and developers, everyone 
has same rights. That difference is imposed by the need for centralizing 
projects and personal abilities.


___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Crash with Print simulation


On 09/18/2015 01:59 PM, Gez wrote:

El vie, 18-09-2015 a las 13:56 -0400, Elle Stone escribió:


Hmm, hopefully it was implied by the post topic, but in
"Edit/Preferences/Color Management" pick "Print simulation" as the
"Mode
of operation".


Yes, it was clear. But now that you mention it, does the "color proof"
display filter produce the same crash?


The "color proof" display filter doesn't have the option to enable the 
LCMS gamut check to show which colors are out of gamut. So one of the 
three items in the combination isn't met, so the crash isn't triggered.


As an aside for anyone who doesn't already know this, when using the 
color proof display filter, in Preferences/Color Management the "Mode of 
operation" should be set to "Color Managed" or else you are double soft 
proofing, that is, chaining on the effects of additional soft proofing 
profiles. At least that's what it looks like is happening. And yes, if 
you use the color proof display filter AND enable "Print simulation" in 
Preferences, including the gamut check, then GIMP crashes.


___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Alexandre Prokoudine

18 сент. 2015 г. 21:15 пользователь "Nikola M" написал:
>
> On 09/18/15 07:10 PM, Gez wrote:
>>
>> I wonder if saying that the only license pertains to the source code.
>> I'd say that the binaries are also covered by the license, since you
>> are obligued to make the source code available when you distribute the
>> binaries.
>
>
> Source code is covered and source changes, if binaries are distributed.
> But binaries itself can have whatever licence one wants, if source and
source changes are available.

Where did you even get this idea from? :)

Alex
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Michael Schumacher



On 09/18/2015 08:15 PM, Nikola M wrote:
> On 09/18/15 07:10 PM, Gez wrote:
>> I wonder if saying that the only license pertains to the source code.
>> I'd say that the binaries are also covered by the license, since you
>> are obligued to make the source code available when you distribute the
>> binaries.
> 
> Source code is covered and source changes, if binaries are distributed.
> But binaries itself can have whatever licence one wants, if source and
> source changes are available.

You have yet to provide proof for this claim.

In case you missed it, your previous attempt at that is waiting for
answers to Alexandre's reply.


-- 
Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

I included a reminder about the warranty it because it's included in big
bold letters in the about information for GIMP. I have no basis for judging
whether that's necessary or not, other than someone thought it was worth
shouting digitally about. :)

-C

On Fri, Sep 18, 2015 at 7:13 PM, Gez  wrote:

> El vie, 18-09-2015 a las 14:10 -0300, Gez escribió:
>
> > "The program itself is governed by the terms of the GNU General
> > Public
> > License (GPL) which ensures that users have freedom to use the
> > program
> > with any purpose, study and modify its source code and share
> > modifications to the community. You are allowed and encouraged to
> > share
> > the program with your friends and colleagues, install it in your
> > school
> > or organization and use it for any purpose.
> > If you're planning to modify the program and re-distribute it with
> > your
> > modifications, make sure that you make the source code available too.
> > That's the only obligation required by the license.
> > Follow [this link] if you need more information abut the GNU General
> > Public License."
>
> I missed the "no warranty" bit. Is it really necessary? If yes, why?
> Is it some required legal waiver or just a kind way of saying "don't
> blame us if something went wrong and you lose your work"?
>
> Personally I find that kind of stuff really unnecessary. It's like
> making an excuse in advance: "look, it may fail, don't blame us".
> If someone wants to sue you I don't think the "no warranty" claim will
> make any difference. But seriously, who would do that?
>
> I've been working with software for 20 years, I've lost count of the
> times I've lost work because software failed, crashed or froze.
> I may or may not cursed the software and its makers when that happened,
> but never thought about suing the makers for the half hour of work I
> lost because I forgot to hit CTRL+S (or CTRL+E :-p)
>
> That being said, GIMP is probably the most stable software I use, which
> makes that remark even more unnecessary.
>
> Gez.
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Crash with Print simulation

El vie, 18-09-2015 a las 13:56 -0400, Elle Stone escribió:

> Hmm, hopefully it was implied by the post topic, but in 
> "Edit/Preferences/Color Management" pick "Print simulation" as the
> "Mode 
> of operation".

Yes, it was clear. But now that you mention it, does the "color proof"
display filter produce the same crash?

___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Gimp-developer] Python Interpreter on Windows

2015-09-18 Thread Partha Bagchi

I am little puzzled with how the Python interpreter is well
interpreted with GIMP. For instance, when I build GIMP from git, it's
all good and the interpreter I specify in pygimp.interp works fine.

Now I create an installer from my build and install it in Program
Files for example (location very different from my build location on a
removable SSD) and I modify pygimp.interp to point to a different
interpreter and it works fine.

However, If I make a copy of my original install and put it in another
location, I get the dreaded: "GIMP-Warning: Bad interpreter referenced
in interpreter file"

Also, this happens sometimes. It happens with current git pull. My
last build a month ago, it didn't happen.

Can anyone tell me how exactly GIMP decides on Bad interpreter? Note
that I know that GIMP checks to see if the interpreter is executable
and it is as specified above. What else am I missing to fix this
problem for me once and for all?

Thanks in advance,
Partha
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Crash with Print simulation


On 09/18/2015 12:01 PM, Elle Stone wrote:

The Color Management Preferences combination that sometimes causes a
crash seems to be:

1. Open or make a floating point sRGB image with out of gamut RGB values.
  As an aside, out of gamut RGB values generate screenfuls of
terminal messages like the following:
(gimp-2.9:23822): GLib-GObject-WARNING **: value "((GimpRGB*)
0x3664030)" of type 'GimpRGB' is invalid or out of range for property
'color' of type 'GimpRGB'. These terminal messages are not usually
accompanied by GIMP crashing.

2. Under "Edit/Preferences/Color Management/Print simulation profile"
choose an RGB profile that is of the "LUT" type rather than a simple
matrix RGB profile. The "Softproof rendering intent"  doesn't matter,
and it doesn't matter whether using or not using black point compensation.

3. Select "Mark out of gamut colors". This is what triggers the crash,
but only when combined with 1. and 2., and even then, not always.


Hmm, hopefully it was implied by the post topic, but in 
"Edit/Preferences/Color Management" pick "Print simulation" as the "Mode 
of operation".

___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Crash with Print simulation

The crash with Print simulation might be related to LCMS 2.8 from git. I 
can trigger a crash with LCMS 2.8 from git installed, and so far haven't 
managed to trigger a crash with LCMS 2.7 or 2.6 installed. The slowness 
is another issue, but that also is triggered somewhat sporadically.


___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Nikolam

Yes, Oracle Solaris and RedHat are examples where binaries are licensed as
company that is distributing binaries seems fit.But source is available
that other users can make binaries if they use their own bending (CentOS,
Fedora).
Not to mention forks like LibreOffice from OpenOffice etc. or example of
Java under GPL, that have Oracle-distributed binaries but also OpenJDK.
It is just important that branding is not the same, binraires are
distributed as distributor seems fit.

On Fri, Sep 18, 2015 at 12:12 PM, Michael Schumacher 
wrote:

>
>
> On 09/18/2015 11:52 AM, Nikolam wrote:
> > On 9/17/15, srikanth  wrote:
> >> Dear All,
> >>
> >>
> >>
> >> Thank You very Much for the information.
> >
> > Of course GPL license is about source code and Binaries can have
> > another license,
>
> No.
>
>
> --
> Regards,
> Michael
> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread srikanth

Dear All,

 

Thank You very Much for the information.

 

Thanks & Regard’s

Srikanth Kavarthapu

Executive IT

Kobelco Cranes India (P) Ltd.

  www. kobelco-cranes.com/India

P Before printing this email or any attachments, think about your 
responsibility and commitment to the ENVIRONMENT



Disclaimer Clause:

This e-mail is from Kobelco Cranes India Pvt. Ltd. The information in this 
e-mail (including attachment) is confidential and is only intended for use by 
the addressee. If you have received this e-mail and are not the intended 
recipient, please contact the sender immediately and delete this e-mail from 
your computer. Any unauthorized disclosure of the information, use or 
dissemination either in whole or in part is prohibited. Computer viruses can be 
transmitted by e-mail. The recipient should check this e-mail (including 
attachment) for the presence of viruses. Kobelco Cranes India Pvt. Ltd. accepts 
no liability for any damage caused by any virus transmitted by this e-mail.


 

 

From: C R [mailto:caj...@gmail.com] 
Sent: Thursday, September 17, 2015 1:42 AM
To: srikanth-kavarth...@kobelconet.com
Cc: gimp-developer
Subject: Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

 

There is no license to use the software. The only license for the GIMP pertains 
to the code it's self (altering it, etc). You are free to install and use the 
GIMP on as many machines as you want, free of charge, for any purpose you like. 
Please keep in mind that there is no warranty.

You retain all rights to the graphics produced with GIMP in accordance with the 
laws of your region. Usage of the GIMP does not alter your rights to your own 
work, or others rights to theirs.

 

From the Help menu in GIMP choose "About", then click the "License" button. It 
will show you this:

 

---

GIMP is free software: you can redistribute it and/or modify it under the terms 
of the GNU General Public Licence as published by the Free Software Foundation; 
either version 3 of the Licence, or (at your option) any later version.

 

GIMP is distributed in the hope that it will be useful, but WITHOUT ANY 
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.  See the GNU General Public Licence for more details.

 

You should have received a copy of the GNU General Public Licence along with 
GIMP.  If not, see http://www.gnu.org/licenses/.

---

 

 

Hope it helps. :)

 

On Wed, Sep 16, 2015 at 4:57 AM, srikanth  
wrote:

Dear All,



I am Planning to install the GIMP software for the users in my Organization.

Now I want to know is there any special license required to use the
software. If so, please share all the details for the purchase of the
software.





Thanks & Regard's

Srikanth Kavarthapu

Executive IT

Kobelco Cranes India (P) Ltd.

  www. kobelco-cranes.com/India



P Before printing this email or any attachments, think about your
responsibility and commitment to the ENVIRONMENT





Disclaimer Clause:

This e-mail is from Kobelco Cranes India Pvt. Ltd. The information in this
e-mail (including attachment) is confidential and is only intended for use
by the addressee. If you have received this e-mail and are not the intended
recipient, please contact the sender immediately and delete this e-mail from
your computer. Any unauthorized disclosure of the information, use or
dissemination either in whole or in part is prohibited. Computer viruses can
be transmitted by e-mail. The recipient should check this e-mail (including
attachment) for the presence of viruses. Kobelco Cranes India Pvt. Ltd.
accepts no liability for any damage caused by any virus transmitted by this
e-mail.







___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

 



Email secured by Check Point 

=

___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Nikolam

On 9/17/15, srikanth  wrote:
> Dear All,
>
>
>
> Thank You very Much for the information.

Of course GPL license is about source code and Binaries can have
another license,
In this case, binaries are also leaved freely to use and distribute.

This are my thoughts based on free software source license:
Binaries (running program) can be made by anyone using source code
license rights,
and distributed under terms and conditions of whatever one likes.

Source code and ability to change, compile and produce product yourself,
gives you the ability to treat both source and binary program as it
_is_ truly yours:
If you compile and make binaries by yourself, it IS yours.
That is the power that free software on source level license gives
you. (GNU GPL)

If you distribute (with changing source code) binary product to other
organizations,
you are obliged by the source license to also relay them changed
source code, too,
so the program continues to live.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Michael Schumacher

On 09/18/2015 04:33 PM, C R wrote:
> I'd patch the new website code thusly:
> http://opendesignstudio.org/gimp/about/
> 
> My thought is the majority of people coming to the site are not going to be
> interested in altering the code, but rather using it.

> Thoughts?

Please check that your text covers all the freedoms of the Free Software
definition and does not contradict any of the statements mentioned there:

https://www.gnu.org/philosophy/free-sw.html

P.S.
Deployment of Free Software within an organization, as it was the
initial question in this thread, quickly advances beyond mere usage.

-- 
Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

Does not contradict. It however, does not mention the four freedoms
verbatim however (neither did the previous text that was there).
Maybe it should?

On Fri, Sep 18, 2015 at 3:44 PM, Michael Schumacher  wrote:

>
>
> On 09/18/2015 04:33 PM, C R wrote:
> > I'd patch the new website code thusly:
> > http://opendesignstudio.org/gimp/about/
> >
> > My thought is the majority of people coming to the site are not going to
> be
> > interested in altering the code, but rather using it.
>
> > Thoughts?
>
> Please check that your text covers all the freedoms of the Free Software
> definition and does not contradict any of the statements mentioned there:
>
> https://www.gnu.org/philosophy/free-sw.html
>
>
> P.S.
> Deployment of Free Software within an organization, as it was the
> initial question in this thread, quickly advances beyond mere usage.
>
>
> --
> Regards,
> Michael
> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

I have added a hyperlink to "Free and Open Source Software", that links to
https://www.gnu.org/philosophy/free-sw.html

My thought is the gnu.org page explains the freedoms of all open source
software well enough. I've only filled in the direct implications of the
four freedoms for GIMP software users in regards to the questions we keep
getting regarding licensing, and usage of GIMP for professional
purposes/companies.

Changes welcome as always.
-C

On Fri, Sep 18, 2015 at 3:49 PM, C R  wrote:

> Does not contradict. It however, does not mention the four freedoms
> verbatim however (neither did the previous text that was there).
> Maybe it should?
>
> On Fri, Sep 18, 2015 at 3:44 PM, Michael Schumacher 
> wrote:
>
>>
>>
>> On 09/18/2015 04:33 PM, C R wrote:
>> > I'd patch the new website code thusly:
>> > http://opendesignstudio.org/gimp/about/
>> >
>> > My thought is the majority of people coming to the site are not going
>> to be
>> > interested in altering the code, but rather using it.
>>
>> > Thoughts?
>>
>> Please check that your text covers all the freedoms of the Free Software
>> definition and does not contradict any of the statements mentioned there:
>>
>> https://www.gnu.org/philosophy/free-sw.html
>>
>>
>> P.S.
>> Deployment of Free Software within an organization, as it was the
>> initial question in this thread, quickly advances beyond mere usage.
>>
>>
>> --
>> Regards,
>> Michael
>> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
>> ___
>> gimp-developer-list mailing list
>> List address:gimp-developer-list@gnome.org
>> List membership:
>> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
>> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>>
>
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

I'd patch the new website code thusly:
http://opendesignstudio.org/gimp/about/

My thought is the majority of people coming to the site are not going to be
interested in altering the code, but rather using it.
When most users think of software licences for graphics programs, it
generally has less to do with the code, and more to do with the content
they are producing with the code.
People coming with the intent to alter and distribute the code likely
already know what FOSS software is, so a secondary mention of the GNU
license seems adequate.

I have thusly altered the first paragraph slightly and added a separate
paragraph directly below with headline for licenses. I think this is clear
enough to keep most people from bugging us about professional
use/installation of the compiled GIMP.

Thoughts?

On Fri, Sep 18, 2015 at 2:24 PM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> On Fri, Sep 18, 2015 at 4:11 PM, C R wrote:
> > Feel free to use my description on the website.
>
> Where would you like it to show up? Just in case, we already have a
> new FAQ on the new website, and it answers this question in layman's
> terms.
>
> Alex
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Alexandre Prokoudine

On Fri, Sep 18, 2015 at 4:11 PM, C R wrote:
> Feel free to use my description on the website.

Where would you like it to show up? Just in case, we already have a
new FAQ on the new website, and it answers this question in layman's
terms.

Alex
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

2015-09-18 Thread Alexandre Prokoudine

On Fri, Sep 18, 2015 at 3:24 PM, Nikolam wrote:
> Yes, Oracle Solaris and RedHat are examples where binaries are licensed as
> company that is distributing binaries seems fit.

Please name an example of GPL software binaries relicensed by Red Hat.

> Not to mention forks like LibreOffice from OpenOffice etc.

Oh my goodness... Both OpenOffice and LibreOffice are licensed under
LGPL. Do some facts checking pretty please.

Alex
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

Feel free to use my description on the website. I can submit a patch for it
also if that's desirable.
On 18 Sep 2015 2:04 pm, "Alexandre Prokoudine" <
alexandre.prokoud...@gmail.com> wrote:

> On Fri, Sep 18, 2015 at 3:24 PM, Nikolam wrote:
> > Yes, Oracle Solaris and RedHat are examples where binaries are licensed
> as
> > company that is distributing binaries seems fit.
>
> Please name an example of GPL software binaries relicensed by Red Hat.
>
> > Not to mention forks like LibreOffice from OpenOffice etc.
>
> Oh my goodness... Both OpenOffice and LibreOffice are licensed under
> LGPL. Do some facts checking pretty please.
>
> Alex
> ___
> gimp-developer-list mailing list
> List address:gimp-developer-list@gnome.org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization

El vie, 18-09-2015 a las 14:10 -0300, Gez escribió:

> "The program itself is governed by the terms of the GNU General
> Public
> License (GPL) which ensures that users have freedom to use the
> program
> with any purpose, study and modify its source code and share
> modifications to the community. You are allowed and encouraged to
> share
> the program with your friends and colleagues, install it in your
> school
> or organization and use it for any purpose.
> If you're planning to modify the program and re-distribute it with
> your
> modifications, make sure that you make the source code available too.
> That's the only obligation required by the license.
> Follow [this link] if you need more information abut the GNU General
> Public License."

I missed the "no warranty" bit. Is it really necessary? If yes, why?
Is it some required legal waiver or just a kind way of saying "don't
blame us if something went wrong and you lose your work"?

Personally I find that kind of stuff really unnecessary. It's like
making an excuse in advance: "look, it may fail, don't blame us".
If someone wants to sue you I don't think the "no warranty" claim will
make any difference. But seriously, who would do that?

I've been working with software for 20 years, I've lost count of the
times I've lost work because software failed, crashed or froze.
I may or may not cursed the software and its makers when that happened,
but never thought about suing the makers for the half hour of work I
lost because I forgot to hit CTRL+S (or CTRL+E :-p)

That being said, GIMP is probably the most stable software I use, which
makes that remark even more unnecessary.

Gez.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Gimp-developer] WGO Redesign Update

2015-09-18 Thread Pat David

Just a small update.

I've been busy IRL, and haven't had a chance to work on some things these
past weeks.  I'll be ramping back up shortly.

I incorporated some changes per Jakub from a couple of weeks ago (mostly
the navigation header font and styling).  I am still trying to sort out
some font styling issues that is happening with some fonts, on some DE, in
some browsers... .  Thank you to everyone who took the time to look
and report the problems to me! (ankh, drc, akk, and more).

## Tutorials
The site is still not 100% transferred to the new infrastructure.  The
biggest slow-down at the moment is walking through each of the tutorials
and translating them to Markdown with a few updates to various components
(images now existing in the context of a  element, captions, adding
missing alt tags, etc).  If anyone wants to stand up the environment and
translate tutorials, I'm taking all patches! :)

## README
Jakub also pointed out the need for a README file in the root of the site,
which we don't have at the moment.  I will take a stab at writing one
shortly so others can now what the heck to do to get a build setup.

## Responsive/Mobile Styling
I am in the process of styling the smaller screens navigation.  I am
thinking of something similar to what I did with https://pixls.us - that
is, a floating icon to expand out a menu when requested on mobile only (I
think the header navigation is fine for larger views).  I am, of course,
open to feedback or suggestions on this idea.

## Downloads Page / OS detection
I have the platform detection working (I think?) on the downloads page
right now.  All that's left is to style the sections appropriately based on
the detected OS.  I am aiming for a similar response to what the current
download page does, show appropriate download section, plus options for
viewing others.  If no js is available, default to showing all of the
options.

## RSS Feeds
I haven't tested this yet at all.  I have no reason to suspect that they
_won't_ work, but won't know for sure until I sit down and get started
working on it.

## OpenGraph/Schema.org
I also have not modified the templates to contain opengraph/schema.org
microdata formats for parsing by those fancy-schmancy social websites and
others.  This is also something that I don't expect will be a problem (and
is not something visible to normal site consumers anyway).  It's also low
on my priority list, atm.

That's about where we are at.  We do have William Green who has offered to
help out, and I think that we could be ready to go before too long.

Is there any thoughts on a go-live/release schedule?  Is this something
that everyone wants to coincide with a bigger event?  If someone is
thinking of anything along these lines that may constrain the schedule, let
me know and I'll try to devote more resources (or find and bribe them) to
it.
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

[Gimp-developer] Crash with Print simulation

With current GIMP from git (last updated yesterday), "Preferences/Color
Management/Print simulation" is sometimes very slow to refresh the
screen, even with small (900x600px) images, and will sometimes crash GIMP.

The last time I used GIMP 2.9's Print simulation was in April 2015,
using LCMS 2.7, on a ten-year-old AMD Opteron computer, running Gentoo,
with opencl disabled, at which point the Print simulation was "a bit"
slow but very useable on images roughly 2000px by 3000px. I'm still
running Gentoo, but using LCMS 2.8 from git updated about a month ago,
on a new Intel i7 computer, with opencl enabled. So I'm not sure whether
this is a GIMP bug, an LCMS bug, an "incompatible with current hardware"
bug, a dependencies version problem, or etc.

The Color Management Preferences combination that sometimes causes a
crash seems to be:

1. Open or make a floating point sRGB image with out of gamut RGB values.
As an aside, out of gamut RGB values generate screenfuls of
terminal messages like the following:
(gimp-2.9:23822): GLib-GObject-WARNING **: value "((GimpRGB*)
0x3664030)" of type 'GimpRGB' is invalid or out of range for property
'color' of type 'GimpRGB'. These terminal messages are not usually
accompanied by GIMP crashing.

2. Under "Edit/Preferences/Color Management/Print simulation profile"
choose an RGB profile that is of the "LUT" type rather than a simple
matrix RGB profile. The "Softproof rendering intent" doesn't matter,
and it doesn't matter whether using or not using black point compensation.

3. Select "Mark out of gamut colors". This is what triggers the crash,
but only when combined with 1. and 2., and even then, not always.

Here is an XCF file that triggers the crash. In the bottom layer all the
colors in gamut with respect to the sRGB color gamut; in the second
layer some of the colors are out of gamut:
http://ninedegreesbelow.com/bug-reports/gimp29/red-green-blue-glass.xcf

I don't have any LUT RGB profiles that permit redistribution, so here
are links to web pages where such profiles can be downloaded:

http://www.drycreekphoto.com/icc/Profiles/IccFiles/NewYork/MPL-Chromira-Matte.icc
http://media.ephotopros.com/fromex/Fromex_Fuji_Pearl.icc
http://www.color.org/srgbprofiles.xalter#v4pref - choose the "sRGB v4
Preference" profile, which despite the glowing verbiage makes a truly
terrible RGB working space profile, as it is a LUT profile that isn't
color-balanced.

Oddly enough, this much older LUT profile doesn't seem to cause a crash:
http://rpm.pbone.net/index.php3/stat/26/dist/46/size/113654/name/PhotoGamutRGB-1.0-15.3.src.rpm
(extract the src, then extract the profile).

Can anyone confirm the crash and/or have any idea why GIMP is crashing?

Best regards,
Elle
--
http://ninedegreesbelow.com
Color management and free/libre photography
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

Re: [Gimp-developer] Reg:Usuage of the Gimp for my Organization