[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSoC projects

From: Flávio Cruz
Subject: Re: GSoC projects
Date: Sun, 3 Aug 2008 22:04:30 +0100

> Hello!

Hello! :-)

> The GSoC projects are making good progress, as I read from various IRC
> log lines.  Hence, we'd like to make this work available through the
> standard GNU Savannah Hurd group/repository.  I'm going to make the
> GSoCers members of that group.  Here are some rules:
> <http://www.bddebian.com/~wiki/rules/source_repositories/>
> So far, we'll grant you commit-after-approval permission, so please
> (continue to) post and discuss everything to bug-hurd that you'd like to
> have committed.  On your own tagged branches, you can do what you feel
> like (commit directly), but please also obey to the above rules.  Better
> to ask first, than trying to do something on your own.  (Remeber that
> whatever you do, it'll be part of the Hurd's permanent RCS history.)
> So, let me say this again: Thanks for your interest in the GNU Hurd and
> welcome on board!  :-)

Thanks! ;-)

> Now, I'd now like each of GSoCers post a follow-up to this message, and
> give a short overview of (a) what he's working on and (b) if this is
> rather a stand-alone thing or has to be included into the main Hurd
> repository.  If it's stand-alone I'd rather have it remain so and make up
> a separate module for it (might even use git or else for it instead of
> CVS, whatever people prefer).  If it has to be integrated into the main
> Hurd tree, then we have to make up some rules about how to do this.

a) I'm creating a translator library written in Common Lisp and
binding some Mach and Hurd libraries/API along the way. The library
uses generated MIG stubs and doesn't rely on libports (apart from
libmachuser & libhurduser, it only needs libfshelp), since the main
objective was to take advantage of the functionalities present in the
Common Lisp language. The library purpose is to allow the rapid
development of translators. It's specially suited to write "virtual"
translators (network based, proxies, simple translators, etc.).

b) People on IRC said it was a better idea to include it in the main
source tree. IMHO, it should be a standalone thing, because it has
dependencies in three external Lisp libraries and it's written in Lisp


Flávio Cruz.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]