From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nala Ginrut Newsgroups: gmane.lisp.guile.user,gmane.lisp.guile.devel Subject: Re: Collecting suggestions of Guildhall Date: Tue, 22 Jan 2013 23:24:55 +0800 Message-ID: References: <1358004081.23443.110.camel@Renee-desktop.suse> <874ni9wj2u.fsf@pobox.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b66f6c3157ecc04d3e22e18 X-Trace: ger.gmane.org 1358868325 32526 80.91.229.3 (22 Jan 2013 15:25:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Jan 2013 15:25:25 +0000 (UTC) Cc: Guile User , guile-devel To: Andy Wingo Original-X-From: guile-user-bounces+guile-user=m.gmane.org@gnu.org Tue Jan 22 16:25:41 2013 Return-path: Envelope-to: guile-user@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TxfjC-0001uU-OV for guile-user@m.gmane.org; Tue, 22 Jan 2013 16:25:34 +0100 Original-Received: from localhost ([::1]:39607 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Txfiv-0004RO-Is for guile-user@m.gmane.org; Tue, 22 Jan 2013 10:25:17 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:41305) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Txfik-0004Ni-72 for guile-user@gnu.org; Tue, 22 Jan 2013 10:25:13 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Txfib-00007W-BM for guile-user@gnu.org; Tue, 22 Jan 2013 10:25:06 -0500 Original-Received: from mail-ea0-f171.google.com ([209.85.215.171]:64058) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Txfib-00007F-1e; Tue, 22 Jan 2013 10:24:57 -0500 Original-Received: by mail-ea0-f171.google.com with SMTP id c13so2391021eaa.16 for ; Tue, 22 Jan 2013 07:24:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=//wZzWNtu+CseOBnI/xQZx9hWU0XcDjhCgM7pvh3K8g=; b=gmIgn6dEgKK1yVKs9B9UJEUw7YHGrxW7OQyPymbhTUSnjJdIwdIZT/zl7rYhp6hBrs 8Df0st1mJm7TD9i3eejDgAGSJNsx5oqjzC1DUHXR5qt0tyn7WSiFQHdmnb6du2X9lC2c Fav3Nn9lkE+r2n8pz42BlYqEDpGSHN3OG66+H030RZx6gvW7BsbFuEHV4Myzc9XhIQgk i70VNFi9E+kOEWrhB3qp2SfLvj/0qzy6woxowXkxhwLWvjf4PJUiQdVAHCsbnLo+lPwW AI7ZPjR+hgL7wjsbtX6jJ4XCWhVX7cych9EB9Ew05j3uAU0K4tRsZsAeGQF8KRs0DZ3n D/wA== X-Received: by 10.14.2.5 with SMTP id 5mr36115674eee.30.1358868296072; Tue, 22 Jan 2013 07:24:56 -0800 (PST) Original-Received: by 10.223.102.131 with HTTP; Tue, 22 Jan 2013 07:24:55 -0800 (PST) In-Reply-To: <874ni9wj2u.fsf@pobox.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 209.85.215.171 X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Original-Sender: guile-user-bounces+guile-user=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.user:9905 gmane.lisp.guile.devel:15543 Archived-At: --047d7b66f6c3157ecc04d3e22e18 Content-Type: text/plain; charset=UTF-8 On Tue, Jan 22, 2013 at 7:30 PM, Andy Wingo wrote: > On Sat 12 Jan 2013 16:21, Nala Ginrut 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? > > Yes, but do we have some kind of spec standard for guildhall packages? If answer is no, I'll do some post-work before the policy discussion. 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. > 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. > > It's fine to take advantage of the bug tracker, except for 'bug' ;-P Isn't there any other way for the transaction with GNU things? I'll throw it into my TODO list. (error TODO "your list is overflow!") > 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? > 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. Thanks! > WDYT? > > Andy > -- > http://wingolog.org/ > --047d7b66f6c3157ecc04d3e22e18 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable



On Tue, Jan 22, 2013 at 7:30 PM, Andy Wingo <<= a href=3D"mailto:wingo@pobox.com" target=3D"_blank">wingo@pobox.com>= wrote:
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. Ju= st
> 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. =C2=A0Would you like to start working on softw= are to
do this?


Yes, but do we have some kind of spec = standard for guildhall packages?
If answer is no, I'll do som= e post-work before the policy discussion.
And another related que= stion bothered me for a long time: which is guildhall's upstream
repo now? ijp's? or andy's?
I think ijp's repo i= s newer now, maybe do a merge work is better.
=C2=A0
WDYT about this workflow: we work via the GNU bug tracker that we
already have in Guile. =C2=A0When someone has a new package, they mail
bug-guile@gnu.org with the informa= tion, creating a ticket.


It's fine to take advantage of the= bug tracker, except for 'bug' ;-P
Isn't there any ot= her way for the transaction with GNU things?
I'll throw it in= to my TODO list.
(error TODO "your list is overflow!")=C2=A0
=C2=A0=
We will have a GPG keyring for guildhall maintainers. =C2=A0We can rig up some special email account, perhaps at gnu.org, to queue jobs for the
guildhall. =C2=A0Guildhall maintainers can then queue the addition or updat= e
of a package via mail, verified with their key. =C2=A0
Mark and me both have GNU account, is it enough? Or we'll h= ave an extra one?
=C2=A0
We should also write a
web application that lists recent updates to the guildhall.


We may write a simple one for just wor= king, 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.=C2=A0
God= knows when it's done...but in a long term, such a thing would be expec= ted by any folks.

Thanks!
=C2=A0
WDYT?

Andy
--
http://wingolog.org/=

--047d7b66f6c3157ecc04d3e22e18--