[prev] [thread] [next] [lurker] [Date index for 2003/10/20]
Hiya, Fair enough, I'll see if we can register it on SourceForge. -Steve On Monday, October 20, 2003, at 11:25 am, James A. Duncan wrote: > Hmm, > > Pixie is released under the license terms that Perl itself is released=20= > under, and thats not going to change. As for placing a copy of the=20 > license in every file, well, TBH I'm not sure that having as copy of=20= > both the GPL and Artistic licenses in _every_ file is in any way=20 > practical or needed. > > We are in the process of moving our outside CVS server, and this sort=20= > of thing will be much easier soon, but at the moment we are stuck=20 > using she-ra for external projects, and this is likely to remain the=20= > case for the next little while. Sourceforge's CVS is painfully hosed=20= > but TBH, license discussions are rather dull and boring, and until we=20= > can bring it back under the Fotango umbrella I'd rather just import it=20= > into sourceforge, and then bring it back later once it is more=20 > practical. > > Regards, > James. > > On Monday, October 20, 2003, at 11:10 am, Steve Purkis wrote: > >> From: Steve Purkis <spurkis@xxx.xx> >> Date: Mon Oct 20, 2003 11:10:04 am Europe/London >> To: Pixie List <pixie@xxxxxx.xxxxxxxxx.xxx> >> Cc: James Duncan <jduncan@xxxxxxx.xxx> >> Subject: Fwd: submission of Pixie - The magic data pixie -=20 >> savannah.nongnu.org >> >> Hi all, >> >> Before Savannah agree to host Pixie they have some requests regarding=20= >> the GPL (see below). This decision is really up to Fotango as it=20 >> relates to licensing -- I can make the changes if need be (though=20 >> must admit I find copyright notices at the beginning of each file=20 >> annoying.. it's also more perl-ish to have them at the end). Fotango=20= >> should also consider including the Artistic license if we go down=20 >> this route. >> >> There are two other options: I can try bringing Pixie to Sourceforge,=20= >> or if Fotango grants me CVS access we can leave the repository where=20= >> it is for the moment. >> >> Let me know what the decision is. >> >> Regards, >> -Steve >> >> >> Begin forwarded message: >> >>> From: Mathieu Roy <yeupou@xxx.xxx> >>> Date: Sun Oct 19, 2003 3:36:38 pm Europe/London >>> To: spurkis@xxx.xx >>> Cc: savannah-hackers@xxx.xxx >>> Subject: Re: submission of Pixie - The magic data pixie -=20 >>> savannah.nongnu.org >>> >>> >>> Hi, >>> >>> I'm evaluating the project you submitted for approval in Savannah. >>> >>> >>> >>> spurkis@xxx.xx a tapot=E9 : >>> >>>> A package was submitted to savannah.nongnu.org >>>> This mail was sent to spurkis@xxx.xx, savannah-hackers@xxx.xxx >>>> >>>> Steve Purkis <spurkis@xxx.xx> described the package as follows: >>>> License: perl >>>> Other License: >>>> Package: Pixie - The magic data pixie >>>> System name: pixie >>>> Type: non-GNU >>>> >>>> Description: >>>> Pixie is yet another object persistence tool for Perl. The basic=20 >>>> goal of Pixie is that it should be possible to throw any object you=20= >>>> want at a data pixie and the pixie will just tuck it away in its=20 >>>> magic sack, giving you a cookie in exchange. Then, minutes, hours=20= >>>> or days later, you can show the pixie your cookie and get the=20 >>>> object back. >>>> >>>> Source code is available on CPAN: >>>> >>>> http://search.cpan.org/dist/Pixie/ >>> >>> To release your project under the GPL, you should put >>> copyright notices and copying permission statements >>> at the beginning of every source-code file, and >>> include a copy of the plain text version of the GPL >>> (http://www.gnu.org/licenses/gpl.txt). >>> Put it in a file named COPYING. >>> >>> Please follow the advice of=20 >>> http://www.gnu.org/licenses/gpl-howto.html. >>> >>> The GPL FAQ explain the reason behind these recommendations. For >>> example, there is an entry explaining why the GPL requires including=20= >>> a >>> copy of the GPL with every copy of the program: >>> http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude >>> >>> >>> Please register your project once more with the changes mentioned >>> above. The way we handle pending projects makes it difficult to = keep >>> track of projects that have been answered but have not been approved >>> yet, so we erase them and we ask you to register the project again=20= >>> every >>> time some change has to be done to the registration, and users might >>> have to register their projects several times. Thank you for your >>> understanding. >>> >>> Some users find it useful to use the big re-registration URL=20 >>> provided in >>> the acknowledgment e-mail you received after registration. >>> >>> Regards, >>> >>> >>> --=20 >>> Mathieu Roy=There's stuff above here
Generated at 13:56 on 01 Jul 2004 by mariachi 0.52