Hello there!
I'd like to create a project at common-lisp.net (Mr. kire on #lisp advised me to do so). So, here are the details:
Full name: Janis Dzerins
Nickname (username): jdz
Project name: rfc2388
License: none at the moment, most probably BSD style; NO GPL. There's a single file, so I'll find the boilerplate and add it.
Description: Implements MIME parsing. I needed it to handle the multipart/form-data contents parsing to accept files posted through HTML forms. Works for me at the moment, but needs some improvements.
Did I miss something?
Best regards,
Janis Dzerins jdz@dir.lv writes:
I'd like to create a project at common-lisp.net (Mr. kire on #lisp advised me to do so). So, here are the details:
Looks good to me as long as the code has the license attached at the time you check it in. We'll have to get a "go" from the others which shouldn't take too long and when that happens I'll go ahead and set everything up for you.
Erik.
Erik Enge erik@nittin.net writes:
Janis Dzerins jdz@dir.lv writes:
I'd like to create a project at common-lisp.net (Mr. kire on #lisp advised me to do so). So, here are the details:
Looks good to me as long as the code has the license attached at the time you check it in. We'll have to get a "go" from the others which shouldn't take too long and when that happens I'll go ahead and set everything up for you.
I agree. This looks good, but the licence issue should be cleared up before the project is registered.
Regards, Mario.
On Tue, 26 Aug 2003 08:42:25 +0200, Mario Mommer <mommer@igpm.rwth- aachen.de> wrote:
Erik Enge erik@nittin.net writes:
Looks good to me as long as the code has the license attached at the time you check it in. We'll have to get a "go" from the others which shouldn't take too long and when that happens I'll go ahead and set everything up for you.
I agree. This looks good, but the licence issue should be cleared up before the project is registered.
The license is BSD -- Erik was so kind as to give me the text. I have put it in the file. Should I send the file by mail or wait for FTP to work and then upload it myself?
Janis Dzerins jonis@dir.lv writes:
On Tue, 26 Aug 2003 08:42:25 +0200, Mario Mommer <mommer@igpm.rwth-
This looks good, but the licence issue should be cleared up before the project is registered.
The license is BSD -- Erik was so kind as to give me the text. I have put it in the file.
Then, as far as I am concerned, wellcome on board :-)
(sorry for the delay. I though the discussion on naming was not over).
Should I send the file by mail or wait for FTP to work and then upload it myself?
Hm... Erik, what do you think?
I think that would make an entry to the FAQ, since it is a question people will have frequently.
Regards, Mario.
On Mon, Aug 25, 2003 at 10:25:25PM +0300, Janis Dzerins wrote:
Ok, here's my analysis: jdz seems to be mostly sane enough, and he seems to have working code, so the vitals are ok.
Then the bad.
name: rfc2388
Are we going to keep handing out RFC-numbers as project names?
Reasons why I think it *may* be a bad policy:
* It hints at being authorative, yet nwither the interface nor the implementation is.
* If we get more of them out announcements suddenly become quite unreadaable: "Huh? There's a new version of rfc-whazzanumber on common-lisp.net."
Cheers,
-- Nikodemus
Nikodemus Siivola nikodemus@random-state.net writes:
Are we going to keep handing out RFC-numbers as project names?
I don't think it is our job to do have any policy for project names. cCLan et al. seems to me to be the place to enforce that. Do you have an alternate strategy?
- If we get more of them out announcements suddenly become quite
unreadaable: "Huh? There's a new version of rfc-whazzanumber on common-lisp.net."
You mean like rfc2822-2 or rfc2388-theotherone? Yes, that will be slightly confusing. Do you have a suggestion for how we can do it better?
Erik.
Janis Dzerins jdz@dir.lv writes:
I'd like to create a project at common-lisp.net (Mr. kire on #lisp advised me to do so). So, here are the details:
Created! Password in a separate email.
Importing your code to the CVS repository is probably a better approach than copying it up via the FTP server.
Erik.