From: Andy Wingo <wingo@pobox.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Collecting suggestions of Guildhall
Date: Tue, 22 Jan 2013 12:30:49 +0100 [thread overview]
Message-ID: <874ni9wj2u.fsf@pobox.com> (raw)
In-Reply-To: <1358004081.23443.110.camel@Renee-desktop.suse> (Nala Ginrut's message of "Sat, 12 Jan 2013 23:21:21 +0800")
On Sat 12 Jan 2013 16:21, Nala Ginrut <nalaginrut@gmail.com> writes:
> We'd like to start up guildhall.gnu.org, which is a guilers community
> MAYBE based on savannah to let you guys share/fetch Guile packages. Just
> like rubygems.org does. ;-)
FWIW we do have access to a guildhall.gnu.org and are in the process of
setting it up.
> 1. Package verify policy (PVP)
> 2. Package evaluate policy (PEP)
Sounds sensible to me. Would you like to start working on software to
do this?
WDYT about this workflow: we work via the GNU bug tracker that we
already have in Guile. When someone has a new package, they mail
bug-guile@gnu.org with the information, creating a ticket.
We will have a GPG keyring for guildhall maintainers. We can rig up
some special email account, perhaps at gnu.org, to queue jobs for the
guildhall. Guildhall maintainers can then queue the addition or update
of a package via mail, verified with their key. We should also write a
web application that lists recent updates to the guildhall.
WDYT?
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-22 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 15:21 Collecting suggestions of Guildhall Nala Ginrut
2013-01-22 11:30 ` Andy Wingo [this message]
2013-01-22 15:24 ` Nala Ginrut
2013-01-22 15:55 ` Andy Wingo
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=874ni9wj2u.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=nalaginrut@gmail.com \
/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).