Date: Fri, 25 Feb 2000 15:42:49 -0800
   From: Kevin Turner <[EMAIL PROTECTED]>

   On Fri, Feb 25, 2000 at 05:06:43PM +0100, Sven Neumann wrote:
   > There is a gimp-plugins project at SourceForge which you might be
   > interested in, since they can provide you with web, ftp and cvs resources:
   > PS: I don't know why people decided to use the SourceForge resources 
   >     since we have all we need at and But it
   >     turned out that people prefer SourceForge. Seems to be hip ATM.

   Basically because resources were not percieved as readily
   available, at least in comparison to SourceForge screaming "here, take
   it, please!"  We wanted to be able to pass out CVS and web write access
   to an as yet undetermined number of people without disturbing the core.
   Since plug-in development has a different centre that core development,
   it did not seem unreasonable to base the community at a seperate site.

Which I'd like to second.

Putting the print plugin on Sourceforge means that our team can decide
who gets what access; we don't need to get anyone else's permission to
give someone write access to our repository.  It also supports mailing
lists (fully automated), a bug tracking system, message boards, and a
whole lot else.  What's more, having a lot of projects on there means
that there's a lot of interplay.  For example, last night I noticed an
interesting project (someone's working on supporting Lexmark printers)
and I invited him to join our project.

I think it's great that plugin development is "fragmenting" in this
fashion.  It isn't going to weaken the Gimp; it's going to increase
the pool of people who want to write plugins for it, which is all to
the good.

Robert Krawitz <[EMAIL PROTECTED]>

Tall Clubs International  -- or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail [EMAIL PROTECTED]
Project lead for The Gimp Print --

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Reply via email to