unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: guile-devel@gnu.org
Subject: Re: Guile project page garbage collection
Date: Fri, 09 Nov 2007 15:39:02 +0100	[thread overview]
Message-ID: <87640bxz3t.fsf@laas.fr> (raw)
In-Reply-To: <87hcjz6olr.fsf@ossau.uklinux.net> (Neil Jerram's message of "Tue\, 06 Nov 2007 21\:38\:56 +0000")

Hi,

Neil Jerram <neil@ossau.uklinux.net> writes:

> The tools for dealing with this format are available, though; see
> http://gnuvola.org/software/guile-projects/.

OK.

> But in any case, if they contain equivalent information, I guess one
> protocol (HTML) is as good as another (sexp).

Yep, that's what I thought, especially if the latter doesn't buy us much
practically, which I suspect.  After all, we're just talking about 20
entries or so I suppose, not hundreds.

> Do you have something in mind for implementing an automatic
> build/sanity check, or are you implying that project maintainers
> should confirm that their projects still build with 1.6/1.8 before
> resubmitting their entries?

I was thinking about something completely manual: send an email to
`guile-user' explaining the plan, then wait for submissions and
copy/paste them in the page.  We could also be kind enough to explicitly
email individuals when deemed appropriate, although it's not
unreasonable to expect them to hang around `guile-user' IMO.

Thanks,
Ludovic.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2007-11-09 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 14:34 Guile project page garbage collection Ludovic Courtès
2007-11-03 16:32 ` Neil Jerram
2007-11-03 17:45   ` Ludovic Courtès
2007-11-06 21:38     ` Neil Jerram
2007-11-09 14:39       ` Ludovic Courtès [this message]
2007-11-09 23:14         ` Neil Jerram

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=87640bxz3t.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --cc=guile-devel@gnu.org \
    --cc=neil@ossau.uklinux.net \
    /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).