Re: A problem with old bugs

[Marcin Borkowski <mbork@mbork.pl>]

On 2017-03-01, at 11:26, Thien-Thi Nguyen <ttn@gnu.org> wrote:

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

Nope.  What do I do to get them?

> 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?

Nobody gave them to me.

What should be the workflow once I have them?  I assume that I branch
off fresh master, push my branch and write here - correct?

Best,

-- 
Marcin Borkowski