From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile project page garbage collection
Date: Tue, 06 Nov 2007 21:38:56 +0000 [thread overview]
Message-ID: <87hcjz6olr.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <871wb7nry9.fsf@chbouib.org> (Ludovic Courtès's message of "Sat, 03 Nov 2007 18:45:34 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> One immediate worry: for the projects that are up to date, I am
>> concerned that we would be asking the authors to jump through a new
>> set of hoops, when they've already jumped nicely through the hoops
>> that we specified before.
>
> OTOH, it's been a while since somebody submitted something, I think, so
> maybe it's probably not unreasonable to expect authors to be re-submit a
> thing; or they could just say "keep the previous entry for my project".
>
>> Can we not do something using the existing format (assuming that the
>> records in that format are available somewhere), so as not to require
>> resubmission of equivalent information?
>
> You mean the s-exp-based format? I don't know whether the information
> was kept in this format somewhere and actually, I don't know what tools
> are available to deal with it. I think we could work with raw HTML,
> given that entries are fairly simple.
Yes. I had a quick look for the saved project submissions. I thought
they might be somewhere in Savannah CVS, or else in one of ttn's
websites. But I couldn't find them.
The tools for dealing with this format are available, though; see
http://gnuvola.org/software/guile-projects/.
But in any case, if they contain equivalent information, I guess one
protocol (HTML) is as good as another (sexp).
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?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-11-06 21:38 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 [this message]
2007-11-09 14:39 ` Ludovic Courtès
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=87hcjz6olr.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@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).