Re: License of the XCF loader in Imlib2
Hi, I would at first try to be a bit more friendly. I think, it is sufficient if one of the original authors writes an E-mail mentioning that Carsten forgot something and explaining what. What he did was definitely wrong but he should be given a chance to get out of the issue without losing his face. I guess it was a mistake (though a nasty one). I agree with this opinion and would be happy if we could set up a short email that we send to the Imlib2 people signed by some of the people owning the copyright of the affected code. Since it seems not necessary to involve Peter and Spencer at this point, some of the people who have made changes to the code should be ok as senders. I'm short in time right now. Who wants to set up an apropriate email ?? Salut, Sven
Re: License of the XCF loader in Imlib2
On 25 Jun, Sven Neumann wrote: I agree with this opinion and would be happy if we could set up a short email that we send to the Imlib2 people signed by some of the people owning the copyright of the affected code. Since it seems not necessary to involve Peter and Spencer at this point, some of the people who have made changes to the code should be ok as senders. I'm short in time right now. Who wants to set up an apropriate email ?? I'm waiting for an answer of the person who checked in the code. Maybe we should wait for his mail before considering further steps? -- Servus, Daniel
Re: License of the XCF loader in Imlib2
On 25 Jun, Nick Lamb wrote: It "appeared" courtesy of someone identified only as "cK", hopefully those working on Imlib2 will know that handle (though who knows, it doesn't look like an expertly managed project to me, maybe anyone can get CVS write privs) and remove their write privs. This code has been checked in by Christian Kreibich. Maybe we should contact him first... -- Servus, Daniel
Re: License of the XCF loader in Imlib2
On Sat, Jun 24, 2000 at 01:14:02PM +0200, Sven Neumann wrote: yesterday night on #gimp someone pointed out that an XCF loader appeared in the Imlib2 CVS tree. I was curious, checked out the source and had a closer look. It "appeared" courtesy of someone identified only as "cK", hopefully those working on Imlib2 will know that handle (though who knows, it doesn't look like an expertly managed project to me, maybe anyone can get CVS write privs) and remove their write privs. I await Raster's misspelled commentary on this problem, hopefully accompanied by the removal of the offending code from CVS. Nick.
