unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Neil W. Van Dyke" <nwv@neilvandyke.org>
Cc: nwv@neilvandyke.org, guile-devel@gnu.org
Subject: Re: kudos and observation
Date: Wed, 3 Apr 2002 08:17:44 -0500	[thread overview]
Message-ID: <15531.248.122662.447359@winona.neilvandyke.org> (raw)
In-Reply-To: <E16shGd-0002fm-00@giblet>

Thien-Thi Nguyen <ttn@giblet.glug.org> writes at 01:41 03-Apr-2002 -0800:
>    Lack of say is a disempowerment of programmers, and, once
>    there is the inevitable disagreement on points that the
>    disempowered programmers care about, this creates morale
>    problems.  All of which seems antithetical to the spirit of
>    free software.
> 
> well, you're sliding from disproportionate to lack but i follow
> you.  what is the ideal proportion?  how do you determine this?

I don't think there is any simple rule, especially for a project like
Guile, which has some clear organizational hierarchy but a strong
volunteer flavor overall.

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.

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.

(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.)

-- 
                                                        Neil W. Van Dyke
                                             http://www.neilvandyke.org/

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-04-03 13:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-30  7:25 kudos and observation Neil W. Van Dyke
2002-04-03  9:41 ` Thien-Thi Nguyen
2002-04-03 13:17   ` Neil W. Van Dyke [this message]
2002-04-03 21:34     ` Thien-Thi Nguyen
2002-04-04  5:18       ` Neil W. Van Dyke
2002-04-04 22:04         ` Thien-Thi Nguyen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15531.248.122662.447359@winona.neilvandyke.org \
    --to=nwv@neilvandyke.org \
    --cc=guile-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).