From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Simon Haines Newsgroups: gmane.lisp.guile.devel Subject: Guildhall Date: Wed, 16 Nov 2011 09:52:17 +1100 Message-ID: Reply-To: simon.haines@con-amalgamate.net NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0015175cb6b811ebbc04b1cdd805 X-Trace: dough.gmane.org 1321397578 24236 80.91.229.12 (15 Nov 2011 22:52:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 15 Nov 2011 22:52:58 +0000 (UTC) To: guile-devel@gnu.org Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Tue Nov 15 23:52:54 2011 Return-path: Envelope-to: guile-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RQRs4-0007vQ-LZ for guile-devel@m.gmane.org; Tue, 15 Nov 2011 23:52:52 +0100 Original-Received: from localhost ([::1]:52603 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQRs3-0005gV-PG for guile-devel@m.gmane.org; Tue, 15 Nov 2011 17:52:51 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:56152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQRry-0005fG-JO for guile-devel@gnu.org; Tue, 15 Nov 2011 17:52:50 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQRru-00037L-Ki for guile-devel@gnu.org; Tue, 15 Nov 2011 17:52:46 -0500 Original-Received: from caiajhbdcagg.dreamhost.com ([208.97.132.66]:52179 helo=homiemail-a35.g.dreamhost.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQRru-000376-D2 for guile-devel@gnu.org; Tue, 15 Nov 2011 17:52:42 -0500 Original-Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id 3145D54058 for ; Tue, 15 Nov 2011 14:52:40 -0800 (PST) Original-Received: from mail-bw0-f41.google.com (mail-bw0-f41.google.com [209.85.214.41]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: simon.haines@con-amalgamate.net) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id C4C9F54057 for ; Tue, 15 Nov 2011 14:52:39 -0800 (PST) Original-Received: by bke17 with SMTP id 17so7938638bke.0 for ; Tue, 15 Nov 2011 14:52:38 -0800 (PST) Original-Received: by 10.204.154.201 with SMTP id p9mr13691765bkw.33.1321397558306; Tue, 15 Nov 2011 14:52:38 -0800 (PST) Original-Received: by 10.223.156.136 with HTTP; Tue, 15 Nov 2011 14:52:17 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 208.97.132.66 X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Developers list for Guile, the GNU extensibility library" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Original-Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.devel:12897 Archived-At: --0015175cb6b811ebbc04b1cdd805 Content-Type: text/plain; charset=ISO-8859-1 I'd like to start looking into getting some of my libraries ready for the guildhall, and have a few quick questions. How are library namespaces going to be determined? I can see a couple of approaches: a) authoritative (contributors apply to a central authority for a namespace upon library contribution), or b) federated (contributors have a namespace, perhaps based on a login name, under which all their libraries live) I guess it's a matter of taste: (import (guildhall db nosql mongodb (1))) vs (import (guildhall simonhaines mongodb (1))). Perhaps this is mere bikeshedding and the best approach is 'anything goes'. What's the contribution process going to look like? I assume a 'contribute' form on a web page somewhere, similar to PLaneT or CPAN. Some infrastructure may be required to support this: repository hosting and an announce mailing list. On the latter points, the last I heard guildhall.gnu.org was being sought for hosting, and I guess guile-user would be a good announce list. I think the guildhall would be a fantastic development for guile, and I'd like to do all I can to get the ball rolling, from paper-chasing to helping out with the dorodango integration. Just let me know how I can help. Simon. --0015175cb6b811ebbc04b1cdd805 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'd like to start looking into getting some of my libraries ready for t= he guildhall, and have a few quick questions.

How are li= brary namespaces going to be determined? I can see a couple of approaches:<= /div>
a) authoritative (contributors=A0apply to a central authority for a na= mespace upon library contribution), or
b) federated (contributors= have a namespace, perhaps based on a login name, under which all their lib= raries live)
I guess it's a matter of taste: (import (guildhall db nosql mongod= b (1))) vs (import (guildhall simonhaines mongodb (1))). Perhaps this is me= re bikeshedding and the best approach is 'anything goes'.

What's the contribution process going to look like?= I assume a 'contribute' form on a web page somewhere, similar to P= LaneT or CPAN. Some infrastructure may be required to support this: reposit= ory hosting and an announce mailing list. On the latter points, the last I = heard guildhall.gnu.org was being = sought for hosting, and I guess guile-user would be a good announce list.

I think the guildhall would be a fantastic development = for guile, and I'd like to do all I can to get the ball rolling, from p= aper-chasing to helping out with the dorodango integration. Just let me kno= w how I can help.
Simon.


--0015175cb6b811ebbc04b1cdd805--