From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: guildhall status
Date: Mon, 18 Jul 2011 15:06:16 +0200 [thread overview]
Message-ID: <878vrvu4af.fsf@gnu.org> (raw)
In-Reply-To: 877h7jlpw7.fsf@pobox.com
Hi!
Andy Wingo <wingo@pobox.com> skribis:
> So, the status:
>
> 1) Builds.
> 2) Passes make check.
> 3) Can update the available list.
> 4) Everything else is untested :-)
Sounds like great news!
> I will see if I can get work to sponsor a server that we can use, and
> see if we can get it aliased to guildhall.gnu.org -- unless someone else
> would like to provide the server. It would be nice to have root on that
> server, FWIW. It could be a VM.
I believe FSF could lend us a server or VM, which would thus be
“independent”, but we’d need to check.
> As far as relation with dorodango goes, we should do our best to keep
> the guildhall compatible with dorodango archives on the net. We should
> also try hard to share code, but that is secondary. Farther along I
> would like to rename (dorodango ...) in our source to (guildhall ...) or
> something so that we don't conflict with upstream. I would also like to
> reduce the number of bundled dependencies, and for the ones that are
> left, include them under the (guildhall ...) namespace, making them
> effectively private. That way you can also install dorodango on your
> machine, if you wish, and also install the wak- packages, industria,
> ocelotl, etc.
Sounds cool.
Since the project may become quite central, it would be nice if it could
be FSF-copyrighted. That’s obviously something to discuss with Andreas,
but the sooner the better.
Thanks for the fast & efficient work!
Ludo’.
next prev parent reply other threads:[~2011-07-18 13:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 11:55 guildhall status Andy Wingo
2011-07-15 19:10 ` dsmich
2011-07-15 19:21 ` dsmich
2011-07-18 8:39 ` Andy Wingo
2011-07-18 13:06 ` Ludovic Courtès [this message]
2011-07-18 14:57 ` Andy Wingo
2011-07-18 16:05 ` Ludovic Courtès
2011-07-18 16:06 ` Ludovic Courtès
2011-07-23 10:37 ` Andreas Rottmann
2011-07-25 9:21 ` Andy Wingo
2011-07-25 9:48 ` Andy Wingo
2011-07-25 18:53 ` Andreas Rottmann
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vrvu4af.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).