public inbox for gentoo-lisp@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marijn <hkBst@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>,
	 gentoo-project@lists.gentoo.org
Cc: gentoo-lisp@lists.gentoo.org
Subject: [gentoo-lisp] Looking for (Common) Lisp shepherds
Date: Fri, 16 Mar 2012 15:09:55 +0100	[thread overview]
Message-ID: <4F6349B3.3060106@gentoo.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

the Gentoo Lisp project is having trouble maintaining Common Lisp
packages and to a lesser extent Scheme packages due to a lack of
time/interest of the people currently working on that. Most of those
packages are leaf packages, but some are not: mostly dev-scheme/guile
and dev-lisp/sbcl (Steel Bank Common Lisp compiler) I think. Many
Common Lisp packages have been maintained in our overlay (mostly
thanks to Stelian Ionescu (fe[nl]ix)) including SBCL but not much has
moved to main tree.
With this email I am hoping to achieve (in order of preference) that
either some people with an interest in the Lisp family of programming
languages join our team to help us out, or some people (without said
broader interest?) take over primary responsibility for non-leaf
packages that are suffering, with the Lisp team taking a back seat.

People interested in joining us can contact us on our mailing list
<gentoo-lisp@lists.gentoo.org> or on freenode in our channel #gentoo-lisp.

Marijn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9jSbMACgkQp/VmCx0OL2zuUACgp/Zg56jDxPwIIMGfmg8NJ7OD
/V0AmgIvcCIJ1+iBtJBkHoSgC/UIuK98
=Q5/8
-----END PGP SIGNATURE-----



                 reply	other threads:[~2012-03-16 15:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F6349B3.3060106@gentoo.org \
    --to=hkbst@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-lisp@lists.gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox