Re: How to get access to the new bug database?

2001-02-07 Thread Martin Baulig

This was forwarded to me from gimp-devel on Feb 7:

 Since the GIMP/GNOME bug database has moved to bugzilla.gnome.org, the
 administrative options have changed.  On the old bugs.gnome.org, it
 was possible for me to change the status of some bugs easily, but now
 I cannot change the status, affected OS, priority and other features
 of the bugs.
 
 I have been through the list of GIMP bugs and I know that some of them
 could be changed from UNCONFIRMED to NEW or NEEDSINFO.  I also spotted
 several of them that could be set to "All OSes" instead of "Linux".
 Or some suggestions for enhancements (including some that I originally
 reported) that could be set to "Low" priority.  I would like to help
 and keep the bug database up-to-date, but unfortunately Bugzilla does
 not let me change these options.
 
 Since the Bugzilla home page does not mention any contact address, I
 am sending this slightly off-topic request to this list.  If anyone
 know who to ask, please tell me.  Thanks.

Hi guys,

now you get the official answer from me, the current bugzilla.gnome.org
maintainer :-)

Doing such changes is by default only allowed for the submitter of a
bug report and the person to which it is assigned.

To to other changes, you must have special privileges in Bugzilla. For
obvious reasons we don't want to automatically grant these privileges to
newly created accounts. This is just to get a little protection against
script-kiddies closing all open bug reports or doing stuff like this.

I was told that automatically granting this privilege to all *@gimp.org
email addresses is a bad idea either, so if you need this privilege
"caneditbugs", I need to do it manually.

All you need to do is to send me a short mail to [EMAIL PROTECTED] (I'll be
away Fri-Sat this week and Mon-Tue next week) and I'll do it asap.

I'll add a contact address ([EMAIL PROTECTED]) to Bugzilla as well.

-- 
Martin Baulig
[EMAIL PROTECTED] (private)
[EMAIL PROTECTED] (work)



Re: XCF loader for gdk-pixbuf

2000-05-30 Thread Martin Baulig

Havoc Pennington [EMAIL PROTECTED] writes:

 Federico Mena Quintero [EMAIL PROTECTED] writes: 
  However, there is the issue of licensing.  Gdk-pixbuf is released
  under the LGPL, and the XCF loader uses big chunks of GPLed code from
  the GIMP.  I am not sure what is the best way to proceed.
  
 
 Well, there are not many options.
 
  a) You find all the authors of that GPL code and get the license
changed (avoiding this mess is the advantage of copyright
assignment...)
 
  b) You don't include the code in gdk-pixbuf
  
  c) You do a clean-room reimplementation of the code

What's wrong with

  d) Keep the XCF loaded GPL

if I understand that correctly, the loaders are shared libraries which
dnyamically loaded so they can theoretically have different licenses
or do I miss something ?

Sure, I'd prefer a) - but IMO d) is much better than b) or even c).

-- 
Martin Baulig
[EMAIL PROTECTED] (private)
[EMAIL PROTECTED] (work)



Re: XCF loader for gdk-pixbuf

2000-05-30 Thread Martin Baulig

Havoc Pennington [EMAIL PROTECTED] writes:

 Martin Baulig [EMAIL PROTECTED] writes: 
  Well, then I think you misunderstood me.
  
  What I suggested was added XCF as a nice add-on to gdk-pixbuf for
  the situation where gdk-pixbuf is used under the GPL.
  
  Of cause, this means that you can't use XCF loading in a proprietary
  app where you use gdk-pixbuf under the LGPL.
 
 Maybe. It's a big can of worms though - can Red Hat and SuSE ship the
 XCF add-on, for example? Probably not.

Hmm, yes.

-- 
Martin Baulig
[EMAIL PROTECTED] (private)
[EMAIL PROTECTED] (work)