From: Andy Wingo <wingo@pobox.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Guile User <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Collecting suggestions of Guildhall
Date: Tue, 22 Jan 2013 16:55:22 +0100 [thread overview]
Message-ID: <87pq0xqkk5.fsf@pobox.com> (raw)
In-Reply-To: <CAPjoZodaC8W5Np=PgVaEN3hmajEhevHrAcQy_3O7x_9SvMhEDw@mail.gmail.com> (Nala Ginrut's message of "Tue, 22 Jan 2013 23:24:55 +0800")
On Tue 22 Jan 2013 16:24, Nala Ginrut <nalaginrut@gmail.com> writes:
> Yes, but do we have some kind of spec standard for guildhall packages?
The zip bundles, no? The guild tool should create the bundles.
I had another thought. When someone submits a bundle, they should HTTP
POST it to a URL on guildhall.gnu.org. The POST will create a new URL
for the incoming package. That way review can proceed around the one
copy of the bundle, and it's a place to do automated tests on the
bundle. We can add a "guild upload" command or so to upload a new
bundle. Maybe "guild upload" can sign the bundle as well.
> And another related question bothered me for a long time: which is
> guildhall's upstream
> repo now? ijp's? or andy's?
> I think ijp's repo is newer now, maybe do a merge work is better.
Probably ijp's, dunno; surely we should get this onto Savannah though?
> 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.
>
>
> Mark and me both have GNU account, is it enough? Or we'll have an extra
> one?
Dunno, I was thinking guildhall-uploads@gnu.org or something --
something like ftpuploads (see maintain.texi).
> We should also write a
> web application that lists recent updates to the guildhall.
>
> We may write a simple one for just working, and after my Glow(Guile
> Lauch on Web) done, we may write a brand new site for a whole guildhall
> in a Ruby on rails like way.
> God knows when it's done...but in a long term, such a thing would be
> expected by any folks.
:-)
Cheers,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-01-22 15:55 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
2013-01-22 15:24 ` Nala Ginrut
2013-01-22 15:55 ` Andy Wingo [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=87pq0xqkk5.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).