You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Martin Scharrer <ma...@madmarty.de> on 2007/01/02 21:40:48 UTC

Perl Dumpfilter Module, CPAN Namespace

Hi,

like I already posted on this list on 2006-06-12 I wrote a Perl module, named 
SVN::Dumpfilter to read and filter Subversion dumpfiles and was planning to 
publish it on CPAN. Because of the lack of time I just put it on my homepage 
( http://www.scharrer-online.de/svn/dumpfilter.shtml ).
In the meantime Philippe 'BooK' Bruhat wrote a similar module called 
SVN::Dump, which has a quite different user interface.

Now I planning to put it on CPAN any time soon. I would like to ask if 
anything speaks again the proposed name 'SVN::Dumpfiler' and if there is 
something I should do before publishing a module in the SVN namespace.

If anyone like to give suggestion what (additional) feature this module 
should have then he/she should not hesitate to write me.

Best,
Martin
 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Perl Dumpfilter Module, CPAN Namespace

Posted by Daniel Rall <dl...@collab.net>.
On Tue, 02 Jan 2007, Martin Scharrer wrote:

> On Tuesday 02 January 2007 23:05, Daniel Rall wrote:
> > It'd be nice if you licensed the module under a less restrictive
> > license than the GPL.  BSD or Apache-style licensing would fit the
> > bill.  Other than that, I don't have any problems with your use of the
> > "SVN" namespace.
>
> What exactly in to restrictive with GPL in this case? Would the LGPL or Perl 
> licence be good enough?

I'd prefer not to get into a license discussion, so only a quick
couple points about the GPL:

1) It's difficult to base traditional products around software which
is GPL'd because of the requirements that the source of the product
must also be freely available.

2) The GPL is viral, infecting any software which uses software
licensed under it.

OSI is a good starting point for more information
<http://www.opensource.org/>, but a Google search will provide a lot
more discussion.


> PS: Check your PC's time, your post reached me some minutes in the future.

Thanks Martin -- sync'd back up over NTP.

Re: Perl Dumpfilter Module, CPAN Namespace

Posted by Martin Scharrer <ma...@madmarty.de>.
On Tuesday 02 January 2007 23:05, Daniel Rall wrote:
> It'd be nice if you licensed the module under a less restrictive
> license than the GPL.  BSD or Apache-style licensing would fit the
> bill.  Other than that, I don't have any problems with your use of the
> "SVN" namespace.
What exactly in to restrictive with GPL in this case? Would the LGPL or Perl 
licence be good enough?

best,
Martin

PS: Check your PC's time, your post reached me some minutes in the future.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Perl Dumpfilter Module, CPAN Namespace

Posted by Daniel Rall <dl...@collab.net>.
On Tue, 02 Jan 2007, Martin Scharrer wrote:

> like I already posted on this list on 2006-06-12 I wrote a Perl module, named 
> SVN::Dumpfilter to read and filter Subversion dumpfiles and was planning to 
> publish it on CPAN. Because of the lack of time I just put it on my homepage 
> ( http://www.scharrer-online.de/svn/dumpfilter.shtml ).
> In the meantime Philippe 'BooK' Bruhat wrote a similar module called 
> SVN::Dump, which has a quite different user interface.
> 
> Now I planning to put it on CPAN any time soon. I would like to ask if 
> anything speaks again the proposed name 'SVN::Dumpfiler' and if there is 
> something I should do before publishing a module in the SVN namespace.

It'd be nice if you licensed the module under a less restrictive
license than the GPL.  BSD or Apache-style licensing would fit the
bill.  Other than that, I don't have any problems with your use of the
"SVN" namespace.

> If anyone like to give suggestion what (additional) feature this module 
> should have then he/she should not hesitate to write me.