Arpi wrote: A> Hi, A> A> > I will add the code to the CVS and put a mark that is still beta code. A> A> where should i send the updates later?
We can add it to the spamassassin CVS tree and handle bugfixes/updates through bugzilla. We can give CVS write access to you for working on the code there if you like. It probably makes more sense to have this be a separate tree though, with a separate release cycle, etc. A> i mean i see no sense of having it in your cvs, while the developed version A> is here... I think I agree. A> > If someone is decided to hack it a bit more, then they will be welcome A> > to do it. A> do you plan to give cvs write access to them? Well, we could. Or we could use the submit-patch-through-bugzilla system which we use for the perl code now, with a limited number of authorized commiters. A> > BTW, what is the license of the code? GPL? A> same as spamassassin - dunno what :) A> i don't care of the liceses SA is Perl Artistic License. Which basically means the licensee can choose between GPL or a BSD-like license. Which is more or less equivalent to "i don't care". C _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
