unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: A problem with old bugs
Date: Wed, 01 Mar 2017 11:26:32 +0100	[thread overview]
Message-ID: <87efyhcmxz.fsf@zigzag.favinet> (raw)
In-Reply-To: <87r32h9zj4.fsf@jane> (Marcin Borkowski's message of "Wed, 01 Mar 2017 09:22:55 +0100")

[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]


() Marcin Borkowski <mbork@mbork.pl>
() Wed, 01 Mar 2017 09:22:55 +0100

   Unfortunately, I have to say that I got very little feedback.
   [...]  I do understand the main reason (too few developers,
   the bugs were not critical), but I have to say that the
   situation isn't exactly motivating for me.

   Is there anything that could be done to avoid turning off
   people wanting to help with Emacs development?  Did I choose
   wrong bugs to work on?  If so, should I close them as
   "wontfix", even though (in 2 cases) there are actual patches
   that seem to fix them?

Do you have write privs to the repo?

If so, perhaps you can find motivation from installing changes
directly and dealing w/ any discussion that ensues, rather than
From positive feedback in discussion pre-commit.  This is the
vaunted "better to ask forgiveness than ask permission" model.
Of course, it's not always so much fun discussing one's mistakes
in public but (take it from someone w/ lots of experience making
mistakes :-D), it does get easier w/ practice.  Sez Perlis:

 Dealing with failure is easy: Work hard to improve.
 Success is also easy to handle: You've solved the wrong
 problem.  Work hard to improve.

I take from this: Satisfaction (and thus motivation to continue)
comes from the hard work applied towards improvement.  What to
improve?  Emacs, yourself, Emacs and yourself, Emacs and others.

If not (no write privs), why not?  What are you waiting for?

-- 
Thien-Thi Nguyen -----------------------------------------------
 (defun responsep (query)
   (pcase (context query)
     (`(technical ,ml) (correctp ml))
     ...))                              748E A0E8 1CB8 A748 9BFA
--------------------------------------- 6CE4 6703 2224 4C80 7502


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2017-03-01 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-01  8:22 A problem with old bugs Marcin Borkowski
2017-03-01 10:26 ` Thien-Thi Nguyen [this message]
2017-03-01 13:28   ` Marcin Borkowski
2017-03-02  7:38     ` Thien-Thi Nguyen
2017-03-02 12:33       ` Noam Postavsky
2017-03-02 16:53         ` Richard Stallman
2017-03-07  6:17         ` Marcin Borkowski
2017-03-06 13:19     ` Phillip Lord
2017-03-07  6:16       ` Marcin Borkowski
2017-03-07 12:24         ` Phillip Lord
2017-03-01 16:16 ` Eli Zaretskii
2017-03-07  6:15   ` Marcin Borkowski
2017-03-07 16:51     ` Eli Zaretskii
2017-03-08  7:01       ` Marcin Borkowski
2017-03-08 16:08         ` Eli Zaretskii
2017-05-21 16:00 ` John Wiegley

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/emacs/

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

  git send-email \
    --in-reply-to=87efyhcmxz.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --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 public inbox

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

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