From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Andy Wingo Newsgroups: gmane.lisp.guile.devel Subject: Re: Guildhall Date: Fri, 06 Jan 2012 18:04:12 +0100 Message-ID: <877h14n4oj.fsf@pobox.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1325869480 13097 80.91.229.12 (6 Jan 2012 17:04:40 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 6 Jan 2012 17:04:40 +0000 (UTC) Cc: guile-devel@gnu.org To: simon.haines@con-amalgamate.net Original-X-From: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Fri Jan 06 18:04:36 2012 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 1RjDDX-0003ZL-Ul for guile-devel@m.gmane.org; Fri, 06 Jan 2012 18:04:36 +0100 Original-Received: from localhost ([::1]:43927 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RjDDX-0002fN-9k for guile-devel@m.gmane.org; Fri, 06 Jan 2012 12:04:35 -0500 Original-Received: from eggs.gnu.org ([140.186.70.92]:44642) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RjDDL-0002Bc-Vc for guile-devel@gnu.org; Fri, 06 Jan 2012 12:04:32 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RjDDG-0003Zl-NT for guile-devel@gnu.org; Fri, 06 Jan 2012 12:04:23 -0500 Original-Received: from a-pb-sasl-sd.pobox.com ([74.115.168.62]:46297 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RjDDG-0003YG-Gf for guile-devel@gnu.org; Fri, 06 Jan 2012 12:04:18 -0500 Original-Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id 0FC7B8A28; Fri, 6 Jan 2012 12:04:17 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; s=sasl; bh=/2WufSc2U/QT m4tOZ4C9RCedXig=; b=r9B5Z3c+uvfJmMH08WGVo/RCbFYokQ27yEGpKdDGDokR 5mV18lMN574v99lKtzRjLMFi58GyOVl4PsvI4ipiToGC/ui7fvClNRyPmVZvUA/n rux8y+u9zF5aZMaOf0movoJXCUXJocH04oDfI982d9cA3mJv+O0DDd0lAfE2O/s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=V3dTA8 sRvSfb7Ad7n/XPUG8eHCk0lInMMCUDhsl8efV7XIf+p3xL+5o95jznuuUGTaN/H5 sDBj1mOqwNarBqGzSJ6KAxjJxotkBBLNyNP2YAWOHKSnpnz6M5yVLHur4dAg5uQs qtKlfLel08TfUxqRLglR6IfvLEdB8WSY6Ph4M= Original-Received: from a-pb-sasl-sd.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTP id F36B98A27; Fri, 6 Jan 2012 12:04:16 -0500 (EST) Original-Received: from badger (unknown [90.164.198.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by a-pb-sasl-sd.pobox.com (Postfix) with ESMTPSA id 3416E8A26; Fri, 6 Jan 2012 12:04:16 -0500 (EST) In-Reply-To: (Simon Haines's message of "Wed, 16 Nov 2011 09:52:17 +1100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) X-Pobox-Relay-ID: 77272AD4-3888-11E1-A2D2-65B1DE995924-02397024!a-pb-sasl-sd.pobox.com X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta) X-Received-From: 74.115.168.62 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:13357 Archived-At: Hi Simon, On Tue 15 Nov 2011 23:52, Simon Haines wr= ites: > 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=C2=A0apply 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'. MHO: * The names integrate with the global module namespace -- no (guildhall ) prefix, as you might want to provide a package both in the guildhall and via some other means (tarball, distro package, etc) * In hierarchies, prefer flat over deep: (statprof) over (system performance profiling statistical) * For names, consider the needs of the system - If you really have the right answer to a problem, use the Right Name -- e.g. (postgres) - Try to avoid conflicts with modules that already exist - For experimental modules for which you expect lots of API churn or changes in solution/problem fit, use a more unique name, for example (chbouib postgres) > 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. We did get guildhall.gnu.org, but haven't done anything with it yet. You can host elsewhere with no agreement. MHO is that we should not require copyright assignment for guildhall.gnu.org packages. Instead the requirement should just be that it have a free software license compatible with Guile, and GPLv3+ preferred. > 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. Sorry it's taken a couple months to get back to you! As you can see I'm a little swamped. But for the record, the process I have been using has been: * Examine the state of things * Remind myself where we want to go * Figure out the next step * Do the next step I don't need to be a blocker on any of this, though. The first three steps can be done on mailing lists. The last sometimes involves mail, sometimes code, and in the future will involve some sysadmin things -- for code, I am very, very happy to accept merge requests on the guildhall project on gitorious, or patches on this mailing list. Collaboration on sysadmin things is also possible: send me the code and I'll put it up on guildhall.gnu.org. Happy hacking :-) Andy --=20 http://wingolog.org/