On Sun, May 4, 2008 at 3:57 PM, Gary King <gwking@metabang.com> wrote:

Hi Elliott,

We'd be happy to set you up; however the signature you sent doesn't look right to me. Is this from

gpg --export -a <your name here>

No, it was generated using puttygen. Do you need a key created with gpg? -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

Gary W. King writes:

Hi Elliot,

...

No, it was generated using puttygen. Do you need a key created with gpg?

I don't know about puttygen and whether or not its keys are interoperable with gpg. The site is designed with gpg in mind so it would be best / easiest if you could use that.

PuTTYgen, as far as I am aware, generates SSH keys and they're, in general, not interchangeable with GPG/PGP keys. //Ingvar

Ok then, here is my GPG key: -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.9 (MingW32) mQGiBEgfaOcRBACQxySqGWmUdZTVspLZ4IFHRUXyptJnjIfMYpZs2kogWtns29OZ +rVRo4qz58hxXAGeJ9h4RxK8UBoCMZAz6dj1q2k/O4n3IQrmqtiuUCymllxSYBT2 19aBaT9ok45k1b5IA2n8WlzzE+SbEkxogLc/HiXDCXmDbNyUrysU9rrYxwCg4/uL GlGcaj3d5pWZGIAJB2tILKsD/30HzJM2xtogUmshr2pxeh1IrCcqn0cNldobIhIH wRq4RfGVqJdRRLhw8ZBhIlyXmCqqk20GVjYlItSFwHSQlaoQTOu7a1qC+DVZL0hi 8los3/E2adZo8o6juR8Au6WQ0V588/unkOnGXFxOAgs1+Nj8ucwiT1/pJYF6v1vK EML1A/wIoQ2Yh07VKYKFa+MMC/En/9dQUeS8JYgnGGGfd7pRH3UDFhtkQYNEz8tw uwlG8S2ip9fOC64EOYCujo/DaltkBIvESFnqOE3UCCbQcfytGotMrEhQ7+V8ktfs lhWhwF8WGXraJb5TVFIx67tFsMt06Sd4EqgVY9F6LQbPxIxhtLRARWxsaW90dCBT bGF1Z2h0ZXIgKGNvbW1vbi1saXNwLm5ldCkgPGVsbGlvdHRzbGF1Z2h0ZXJAZ21h aWwuY29tPohgBBMRAgAgBQJIH2jnAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AA CgkQNM7D5Dzlr5UAlACbBj0cjTiR4r8mJid0/V3MZYKwsSYAoJCGLAFk2pSDavtv ypZ1acYXJkq0uQIMBEgfaOcQCACbAsIp+oT/Vbi1FR1Np5hkWdQagvbEGi1zAzQg GgEVRc/8Cmx5Qa/kGhU4P5MNA0sNe2mR/3ks12EcqMJoOv4cf4KHwXDol/5DdyqH ubxyORgHBO9O9DoNXqBDmYB6YdQP0vHdLMWdBtE/Vvk1cEo+pLhg6ubw1gUc5V6P 4xVMhvzzG8bCXxoTPcqs1EBYxK5pvKX1nJiJV6DXOVqb1/kYWIAvplC/S/m6Wd/2 +7olzapIAJImOSJzZFm1QIfW0VNO855iLEgA6F41mhq8sXDik/+oEgbjk2PJ/jBl hokb/xpRFDeQmEjRAzOryOPq+wd0BCfiMkzO63Xqg+1si0NzAAMGB/itcqFLBoqu lmGR1271M+y8lhDXaCC2K0T8f+/5u3Yfp4ygM6Pg4wOGmDCeCR0ZT1tLSb19auVh vcbM9IuP97xmF3QgrWTED5wGwL4BZJIiVgVif4vaw0w0qFoOr3wF6XfKSJkyEjPU QHZHIx3oJxzOcLEvSZCiWIISoSexFbC4PqZDijFQwJ6CAHosYRmXn79JN1emchFi M5VlX3M7hyCPsOkhsizAyCFREMogPRNasxzQLarsKnBIYtZZ6k2lVHm7y1eQAz/I b3AYSBpOlaLyWoi34o6xsrJ90OD3PVqUPKMcGYRRy0N5OXVfhPfvK5zpfU2SDCRF 56iARtNePJ2ISQQYEQIACQUCSB9o5wIbDAAKCRA0zsPkPOWvlUQcAKC/THkqEJ4q Nv+HZaBgz6OV66RHLgCdF6u04oJwItTAu3wVs+ibwF7oNOA= =A00U -----END PGP PUBLIC KEY BLOCK----- On Mon, May 5, 2008 at 6:33 AM, Gary King <gwking@metabang.com> wrote:

Hi Elliot,

...

No, it was generated using puttygen. Do you need a key created with gpg?

I don't know about puttygen and whether or not its keys are interoperable with gpg. The site is designed with gpg in mind so it would be best / easiest if you could use that.

thanks,

-- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

-- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

Thanks. Could you explain to me how I can set up personal repositories on common-lisp.net? On Wed, May 7, 2008 at 9:27 AM, Gary King <gwking@metabang.com> wrote:

Hi Elliot, You should be ready to roll.

On May 2, 2008, at 11:16 PM, Elliott Slaughter wrote:

Hi,

My name is Elliott Slaughter, and I would like a account on common-lisp.net for the purpose of working on SBCL Windows threading for Google's Summer of Code.

I don't believe I require project hosting, because for the most part, I intend to use existing SBCL resources. However, I would like personal repository for my work on SBCL. My understanding is that I don't need actual project hosting, that a user account will be sufficient to get hosting for a repository.

Thank you for your time.

Other information you may want:

Full name: Elliott Slaughter.

Public key: ---- BEGIN SSH2 PUBLIC KEY ---- Comment: "rsa-key-20080502" AAAAB3NzaC1yc2EAAAABJQAAAIByGWa4cxUcKXAC/1rlS4LlW/KrkrI7JZx/RY/d jRN+s3Sozeqy8r/unhbONPXikL6Frq2aqtEOLk2JrLzf0VznC4vAksKahF4VMj33 KinySulYURLO/Z+7uAzK546jbVPnSUWN+QPNSYEzAG2zQ7x6/uOX1QpvmzId0a/0 dlyTBQ== ---- END SSH2 PUBLIC KEY ----

Description of project: An abstract for the project can be found at http://code.google.com/soc/2008/lispnyc/appinfo.html?csaid=E2FD52402672134E .

-- Elliott Slaughter

"Any road followed precisely to its end leads precisely nowhere." - Frank Herbert _______________________________________________ admin mailing list admin@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/admin

-- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

-- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

On Sun, Jul 27, 2008 at 2:39 PM, Gary King <gwking@metabang.com> wrote:

You have ssh access to your account so your should be able to do "anything" (within some definition of reason) that you need to do. We support cvs, svn, git, darcs and maybe other stuff too!

Let me know if you have more questions

Thanks! Also, I'm wondering what licensing requirements common-lisp.net puts on projects its hosts. If I create a repository with my account, will that be public to the internet? If it is, then I assume I need some sort of license (even if I don't think my project is far enough along that anyone else would want to contribute)... so what would you recommend? Since I happen know you work for Franz as well, could you tell me if there are any additional licensing constraints when working on a project which happens to only run on ACL? That is, the current iteration of my project uses AllegroCache and thus can't run on any other Lisp system. Does this influence what licenses I can use with my project? Thanks again. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

On Tue, Jul 29, 2008 at 1:23 AM, Nikodemus Siivola <nikodemus@random-state.net> wrote:

On Mon, Jul 28, 2008 at 7:27 PM, Elliott Slaughter <elliottslaughter@gmail.com> wrote:

Huh, it seems licence requirements have vanished from the clnet website -- or maybe they never ended up there in the first place, not sure.

At any rate, Common-Lisp.net has since it's inception been open to all open source / free software projects building on Common Lisp. No implemention specific restrictions. That said, clnet is for *public* code. If you use clnet to store your personal code without releasing it into the open, that's not in the spirit of the service provided.

Thought so, just making sure :-)

My *biased* recommendation is the MIT licence <http://www.opensource.org/licenses/mit-license.php>, but whatever suits *your* needs is fine: in the absence of a public notice on the clnet site, assume that any license which fulfills DFSG <http://www.debian.org/social_contract#guidelines> is fine.

Thanks for the advice. Any particular reason you like the MIT license? (I know MIT is less restrictive than the GPL, but I really don't know much more than that.) -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

On Wed, Jul 30, 2008 at 9:33 AM, Nikodemus Siivola <nikodemus@random-state.net> wrote:

Itent of LGPL is nice: don't steal this code, but it won't contaminate anything. Unfortunately LGPL has plenty of language that doesn't make sense for Lisp. If you want LGPL like effect, use GPL plus the classpath exception (or something like that), and hope your and your users lawyers agree.

Doesn't the LLGPL (http://opensource.franz.com/preamble.html) deal with this (at least to some extent)? -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

Hi Eliot, (Thanks to Nikodemus for answering your questions while I've been swamped). To summarize. 1. cl.net is for hosting open-source software -- any reasonable license is fine 2. I also like the MIT license. It's simple! 3. for simpler ssh access, look for ssh-agent (on the Mac, I use sshKeyChain) 4. I don't think that using AllegroCache adds any additional licensing problems (aside from the fact that anyone without ACL won't be able to use your software). If I missed anything, please ask again. thanks, On Jul 29, 2008, at 7:50 PM, Elliott Slaughter wrote:

On Tue, Jul 29, 2008 at 1:23 AM, Nikodemus Siivola <nikodemus@random-state.net> wrote:

...

On Mon, Jul 28, 2008 at 7:27 PM, Elliott Slaughter <elliottslaughter@gmail.com> wrote:

Huh, it seems licence requirements have vanished from the clnet website -- or maybe they never ended up there in the first place, not sure.

At any rate, Common-Lisp.net has since it's inception been open to all open source / free software projects building on Common Lisp. No implemention specific restrictions. That said, clnet is for *public* code. If you use clnet to store your personal code without releasing it into the open, that's not in the spirit of the service provided.

Thought so, just making sure :-)

...

My *biased* recommendation is the MIT licence <http://www.opensource.org/licenses/mit-license.php>, but whatever suits *your* needs is fine: in the absence of a public notice on the clnet site, assume that any license which fulfills DFSG <http://www.debian.org/social_contract#guidelines> is fine.

Thanks for the advice. Any particular reason you like the MIT license? (I know MIT is less restrictive than the GPL, but I really don't know much more than that.)

-- Elliott Slaughter

"Any road followed precisely to its end leads precisely nowhere." - Frank Herbert _______________________________________________ admin mailing list admin@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/admin

-- Gary Warren King, metabang.com Cell: (413) 559 8738 Fax: (206) 338-4052 gwkkwg on Skype * garethsan on AIM

Elliott Slaughter wrote:

On Sun, Jul 27, 2008 at 2:39 PM, Gary King <gwking@metabang.com> wrote:

...

You have ssh access to your account so your should be able to do "anything" (within some definition of reason) that you need to do. We support cvs, svn, git, darcs and maybe other stuff too!

How do I make ssh work with gpg keys? The server keeps using keyboard-interactive authentication and I assume that isn't how it is supposed to work.

And for that matter, what is my user name? (I don't remember either specifying or being told what it was.)

Once the account is set up, you should receive a PGP-encrypted email, stating what the name of your account is (probably "eslaughter") and the password. Once that's done, you should be able to add any and all SSH keys you need to ~/.ssh/authorized_keys and go from there. Checking, I can see that your account has been created, so there should be an email for you, somewhere. //Ingvar

Hi, I'm just resending this request since it has been more than a week since I asked. On Sat, Aug 9, 2008 at 9:01 PM, Elliott Slaughter <elliottslaughter@gmail.com> wrote:

On Sat, Aug 2, 2008 at 2:26 PM, Ingvar <ingvar@hexapodia.net> wrote:

...

Checking, I can see that your account has been created, so there should be an email for you, somewhere.

Hmmm... can't seem to find that email (it probably got caught in my spam folder and deleted a long time ago). Would it be possible to have it resent?

Or is there any other way I can get my password again? Thanks. -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert

Hi Gary, On Sat, Aug 23, 2008 at 3:55 PM, Gary King <gwking@metabang.com> wrote:

Hi Eliot,

My apologies for the delay; I've just reset your password.

Thanks, I managed to log in. (The message didn't include my username, but I managed to guess what it was in a couple of tries.) Now, I'm not sure how to actually upload my project to common-lisp.net. I thought it would be enough to tar and upload my local darcs repository, but darcs on common-lisp.net complains that it is not a repository when I try darcs changes or darcs show files, and complains that it is when I try darcs init. Is there a better way to do this? And once I have my repository up, how do I make it publicly available? Thanks again! -- Elliott Slaughter "Any road followed precisely to its end leads precisely nowhere." - Frank Herbert