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.devel Subject: Re: kudos and observation Date: Wed, 03 Apr 2002 13:34:33 -0800 Sender: guile-devel-admin@gnu.org Message-ID: References: <15525.26721.978797.441772@winona.neilvandyke.org> <15531.248.122662.447359@winona.neilvandyke.org> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1017873683 27240 127.0.0.1 (3 Apr 2002 22:41:23 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 3 Apr 2002 22:41:23 +0000 (UTC) Cc: guile-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16stRS-00075F-00 for ; Thu, 04 Apr 2002 00:41:22 +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 16ssTH-0003IX-00; Wed, 03 Apr 2002 16:39:11 -0500 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 16ssRo-000341-00 for ; Wed, 03 Apr 2002 16:37:40 -0500 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 16ssOn-0003S5-00; Wed, 03 Apr 2002 13:34:33 -0800 Original-To: nwv@neilvandyke.org In-Reply-To: <15531.248.122662.447359@winona.neilvandyke.org> (nwv@neilvandyke.org) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:300 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:300 From: "Neil W. Van Dyke" Date: Wed, 3 Apr 2002 08:17:44 -0500 When making decisions in a group like this, I think people in general tend to negotiate the proportions subtly for each situation. More a collective art than a science. this kind of constant negotiation is difficult to scale, and some (actually most) people really aren't comfortable w/ negotiation at all. in the job context where there are processes already in place to alleviate these issues, negotiation is best done up front (at interview time). is guile maintenance (or more generally any free software project collaboration) a job? that's hard to say. i know that i put in lots of hours for some tenuous future benefit (being able to compile THUD modules), which is kind of like a job... There's few enough core Guile developers that there should be little need for edicts. The team is small enough for everyone to be heard in a discussion. Also, in those cases in which consensus on an issue is not quickly reached based on the merits of the issue alone, everyone on the team recognizes that compromise is sometimes necessary to move forward and to maintain a cooperative tone. the TODO list is pretty daunting for a small team, and i imagine doubly daunting for a large team that's unorganized. personally, i'm trying to encourage documentation of our current processes so that we attain the minimal self-awareness necessary to be able to teach that process to the new blood (and improve the process in the process!). (Just an opinion. I really hesitated to say anything at all, since I'm not a core Guile developer myself. But I hated to see unresolved team dynamics glitches that probably require only the slightest prodding to fix.) well the ancients say a good doctor cures your illness and the best doctor prevents illness in the first place, so a little fixing w/ a little forward-fixing seems "indicated" here. somewhat related, you sent `when' and `unless' and have contributed other useful patches. do you have any interest in guile repo write privs? (this is not an offer per se, just a feeler.) thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel