From: rm@fabula.de
Cc: rm@fabula.de
Subject: Re: Guile and the Free Software Directory
Date: Tue, 4 Mar 2003 15:58:42 +0100 [thread overview]
Message-ID: <20030304145842.GC27537@www> (raw)
In-Reply-To: <ljvfz05mij.fsf@burns.dt.e-technik.uni-dortmund.de>
On Mon, Mar 03, 2003 at 07:32:36PM +0100, Marius Vollmer wrote:
>
> We would make sure for each entry in our database, there is a
> corresponding entry in the Free Software Directory. The entry would
> be deleted from our database. Hopefully our databse is empty after
> that and can be 'decommissioned'.
>
> > While think it migh be a nice idea for the projects to also show up
> > on the FSD site (but the projects maintainer should decide) i think
> > there really should be a well- maintained list of Guile-related
> > software on the Guile website as well.
>
> I would like to avoid the double maintainance. We don't need to
> duplicate something that is already there and useful. When the FSD
> has shortcomings, we should try to improve the FSD itself instead of
> rejecting it.
Ok, double maintainance _is_ a problem (but that could be left to
a script ;-)
> > This is the place people will look at to see the current state of
> > Guile. I'd hate to have to dig through the FSD to find out about
> > some Guile bindings to a library
>
> We can link to the FSD in general and to a pre-frabricated query so
> that only Guile relevant entries are listed.
Sound reasonable ...
> > (not only is the UI suboptimal, there's no way to apply a filter to
> > only see 'Guile projects').
>
> We might make a new category (with subcategories) and put the Guile
> related packages in it.
If this is a possibility i'd say to go for it.
> > What, actually, _is_ the problem with the current setup? From Thi's
> > comment i grok it's rather a political than a technical, or did i
> > get something wrong?
>
> Technically, I think it is wrong to maintain a projects database when
> there is already one that can do the job. There is nothing
> politically wrong about our current database, it is only unfortunate
> that the person willing to maintain it can not have write access to
> the repository (since I decided back then that I didn't trust him
> enough and I haven't reconsidered yet).
I see the technical reasons. As for the current maintainer: i think
this situation needs to be resolved. The current setup only seems to
create problems and frustration -- a maintainer without write access
has a hard time doing his job ...
> > > (The task of actually moving the entries can probably not be fully
> > > automated, so it would be great if we can find some people to help
> > > with it.)
> >
> > I'm happy to help keeping the current site up to date ...
>
> Would you also be willing to help find an arrangement where we use the
> FSD as our 'backend'?
Shure.
Ralf Mattes
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2003-03-04 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 13:12 Guile and the Free Software Directory Marius Vollmer
2003-03-03 15:00 ` Robert Uhl <ruhl@4dv.net>
2003-03-22 23:37 ` Marius Vollmer
2003-03-03 15:37 ` rm
2003-03-03 16:59 ` Thien-Thi Nguyen
2003-03-03 18:32 ` Marius Vollmer
2003-03-04 14:58 ` rm [this message]
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=20030304145842.GC27537@www \
--to=rm@fabula.de \
/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).