From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.user Subject: Re: top-down design + nevermind Date: Mon, 22 Apr 2002 00:34:51 -0700 Sender: guile-user-admin@gnu.org Message-ID: References: <87u1ql94an.fsf@lackawana.kippona.com> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1019461379 24416 127.0.0.1 (22 Apr 2002 07:42:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 22 Apr 2002 07:42:59 +0000 (UTC) Cc: guile-user@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16zYTT-0006La-00 for ; Mon, 22 Apr 2002 09:42:59 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zYSg-0004e7-00; Mon, 22 Apr 2002 03:42:10 -0400 Original-Received: from ca-crlsbd-u4-c4c-174.crlsca.adelphia.net ([68.66.186.174] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zYPv-0004WS-00 for ; Mon, 22 Apr 2002 03:39:19 -0400 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16zYLb-0000E1-00; Mon, 22 Apr 2002 00:34:51 -0700 Original-To: chrisb@kippona.com In-Reply-To: <87u1ql94an.fsf@lackawana.kippona.com> (news@kippona.com) Errors-To: guile-user-admin@gnu.org X-BeenThere: guile-user@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General Guile related discussions List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.user:241 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.user:241 From: (Chris Beggy ) news@kippona.com Date: Mon, 08 Apr 2002 19:08:48 -0400 What do you think [re guile direction]? i think guile is moving towards a federated development model. whatever people's inclinations and abilities are, they can band together and fork a "guile design instance" (and code, presumably) that is candidate for integration using due process. basically, SIGs like for python, but recognizing plurality. the goal remains to please the users, but the users have to take responsibility to communicate precisely what pleases them, and work the system to get their desired results. incompatible branches are somewhat frowned upon, but should not be denied berth. emacs/xemacs watchers wag their fingers but maybe they can help prevent similar long-term pain. "due process" sounds heavy but the hint here is to get one of your SIG members write privs early on (to get write privs you have to follow some slackful methods so presumably your repo insider can find the balance points for your SIG on the tightrope across the chaos). the overall effect is that specific designs will be implemented for their proponents' benefit, and maybe busy bees will cross-pollinate the good bits into the common base, as is their style. all guile users are programmers and all programmers who use guile are encouraged to expand their usage of guile to include changing guile and telling others about it. (guile is not an application -- it is a framework for ("extensive" :-) experimentation in language and runtime implementation -- how's that for an ad blurb?) "but what if i just want to use (the standard) Guile?". well, figure out what is "standard" and form a Standard Interest Group. :-> btw, perhaps there are other interesting grouping terms besides BOF and SIG -- be creative! thi _______________________________________________ Guile-user mailing list Guile-user@gnu.org http://mail.gnu.org/mailman/listinfo/guile-user