all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail]
Date: Fri, 29 Nov 2013 16:37:19 -0800 (PST)	[thread overview]
Message-ID: <f527b11d-f842-4426-8e41-4991f9abe40c@default> (raw)
In-Reply-To: <CAH8Pv0h-7J-N-Drhc4vNw=26LtK4YShep0cuDXQeoPjLgqfvoQ@mail.gmail.com>

> 1. A user that provides feedback/bug reports is valuable, even if he
>    doesn't submit patches.
>
> 2. A user that also submit patches is even more valuable, even if he
>    doesn't commit them.
>
> 3. A user that also commit his patches is even (a little) more valuable.
> 
> Currently I'm at level 2.  It's better than nothing, isn't it?

+1, for drawing attention to the worth of #1 and #2.

But these are not *levels*.  And the "more" and "even (a little) more"
are inappropriate here.  All sincere effort can be helpful.

It makes no sense to quantify either the effort spent or the resulting
improvement, especially based only on the type of activity.

Spending 1/2 hour providing feedback + 1/2 hour committing code is
not necessarily more helpful than spending 1 hour providing feedback
(or 1 hour committing code).  All time spent is welcome.

And the result of the time spent, however long, likewise does not fit
into any useful value hierarchy.

Sometimes just posing a question can be worth an awful lot.  And good
feedback can sometimes prevent a lot of needless coding or committing.  Likewise, providing Emacs development snapshots that people can test
with - that's a great benefit that you provide, IMO.

You have N hours to spend.  You choose how to spend that time.  No
one should be trying to tell you how to spend your time, or thinking
that what they do with their time is more important than what you
choose to do with yours.

There are thousands of bugs reported, many (most) with good, careful
reports that lie dormant and die neglected.  Some people spend lots
of their volunteer time fixing Emacs bugs.  Others prefer to develop
new features and not fix bugs.  So what?  That's life.  It is not
constructive to berate volunteers for not doing this or that.

Don't let such bullying get you down, Dani.  I, for one, am very
appreciative of what you do.



  reply	other threads:[~2013-11-30  0:37 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 17:32 Latest changes with lisp/uni-*.el and leim/quail Eli Zaretskii
2013-11-28 20:36 ` Glenn Morris
2013-11-29  8:42   ` Eli Zaretskii
2013-11-29 13:46     ` Stefan Monnier
2013-11-29 14:25       ` Eli Zaretskii
2013-11-29 16:43         ` Stefan Monnier
2013-11-29  7:46 ` Dani Moncayo
2013-11-29  8:38   ` Eli Zaretskii
2013-11-29  9:03     ` Dani Moncayo
2013-11-29 20:10       ` Glenn Morris
2013-11-29 21:40         ` Dani Moncayo
2013-11-30  0:37           ` Drew Adams [this message]
2013-11-30  4:47             ` participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail] Jambunathan K
2013-11-30  8:36               ` Eli Zaretskii
2013-11-30  8:43                 ` Dani Moncayo
2013-11-30 11:04                   ` Eli Zaretskii
2013-11-30 11:11                   ` Jarek Czekalski
2013-11-30 23:05                     ` Drew Adams
2013-12-01  7:26                       ` Thien-Thi Nguyen
2013-12-01  7:27                         ` Jambunathan K
2013-12-02 13:29                         ` Rüdiger Sonderfeld
2013-12-02 13:37                           ` Jarek Czekalski
2013-12-03 10:51                           ` Thien-Thi Nguyen
2013-12-03 20:03                             ` Wolfgang Jenkner
2013-12-03 20:33                               ` Andreas Schwab
2013-12-03 20:55                                 ` Wolfgang Jenkner
2013-12-03 21:18                                   ` Andreas Schwab
2013-12-04  8:50                             ` Thien-Thi Nguyen
2013-12-04 10:05                               ` Andreas Schwab
2013-12-04 13:52                                 ` Stefan Monnier
2013-12-04 13:57                                   ` Andreas Schwab
2013-12-08 11:01                                 ` adventures w/ git-bzr Thien-Thi Nguyen
2013-12-01  7:50                       ` participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail] Thien-Thi Nguyen
2013-12-01  8:09                         ` Jambunathan K
2013-11-30  8:47                 ` Jambunathan K
2013-11-30 13:50                 ` Stefan Monnier
     [not found] <<83txew8m9v.fsf@gnu.org>
     [not found] ` <<CAH8Pv0hxmFCoEgd6Wag93LAuNy0JPPJ6UNjt3xcWjNdKAB=K5A@mail.gmail.com>
     [not found]   ` <<837gbr8uxa.fsf@gnu.org>
     [not found]     ` <<CAH8Pv0g0P7x=_KOmV2737AJpHgDEJu6_ecdmBseU6rVDuTzKQw@mail.gmail.com>
     [not found]       ` <<lubo13dl4n.fsf@fencepost.gnu.org>
     [not found]         ` <<CAH8Pv0h-7J-N-Drhc4vNw=26LtK4YShep0cuDXQeoPjLgqfvoQ@mail.gmail.com>
     [not found]           ` <<f527b11d-f842-4426-8e41-4991f9abe40c@default>
     [not found]             ` <<87wqjqts1b.fsf@gmail.com>
     [not found]               ` <<83zjom5ls5.fsf@gnu.org>
2013-11-30 18:41                 ` Drew Adams
2013-12-01  0:05                   ` Karl Fogel
2013-12-01 17:39                     ` Stephen J. Turnbull
2013-12-01 18:33                       ` Karl Fogel
2013-12-01 19:03                       ` Stefan Monnier

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

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

  git send-email \
    --in-reply-to=f527b11d-f842-4426-8e41-4991f9abe40c@default \
    --to=drew.adams@oracle.com \
    --cc=dmoncayo@gmail.com \
    --cc=emacs-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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.