From: Samer Masterson <nosefrog@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Oleh Krehel <o.krehel@tue.nl>, emacs-devel@gnu.org
Subject: Re: [PATCH] What's the quickest way to contribute?
Date: Thu, 8 Jan 2015 11:04:41 -0800 [thread overview]
Message-ID: <CAP6_t8iuGFWaLXeZDNm_r6H69b0FTG+fGg0XOOC49mekBXjRkg@mail.gmail.com> (raw)
In-Reply-To: <83mw5t5cs7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2136 bytes --]
On the topic of new developers, does anybody know how long the copyright
assignment process is supposed to take? I signed the copyright assignment
papers three weeks ago, and I have a couple patches
sitting in debbugs that are waiting for my copyright assignment to be fully
processed. And it took me a week to receive the copyright assignment form
after I sent my application, which means that I've waited an entire month
for my patch to be accepted into Emacs.
I know encouraging new developers has been a popular topic on the list for
the past couple months. But we probably shouldn't get ahead of ourselves if
it takes weeks for a new contributor to get anything merged in :)
Best,
Samer
On Thu, Jan 8, 2015 at 10:48 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Thu, 8 Jan 2015 18:59:09 +0100
> > From: Oleh Krehel <o.krehel@tue.nl>
> >
> > I like Emacs a lot and I'd like to contribute to the development. I
> > have assigned the FSF Copyright and made some small contributions in
> > the past, but so far my contributions have been moving slower than
> > molasses.
>
> Thanks for your contributions, and sorry for being so slow in reacting
> on them.
>
> > A few questions/ possible answers follow on why this is:
> >
> > 1. My patches / bug reports are lame. Then I'd appreciate at least
> > some feedback pointing out the faults. I learn quickly.
> >
> > 2. I'm submitting to the wrong place, e.g. to the bug tracker instead
> > of the devel list or vice versa. I'd like to know the proper and
> > approved way to do this.
> >
> > 3. My patches / bug reports are low priority and are not worth
> > applying / responding to. Then please let me know the priority areas
> > in which contributions are more actively accepted.
> >
> > 4. The devs are swamped with bug reports and I should just wait a few
> > months more until my turn.
>
> I wouldn't say "swamped", but definitely busy. So:
>
> 5. Please ping after a week that you didn't see any replies for your
> report, and keep pinging until things move.
>
> > I could then help with the review of other people's one-liners.
>
> Please do, and thanks in advance.
>
>
[-- Attachment #2: Type: text/html, Size: 2978 bytes --]
next prev parent reply other threads:[~2015-01-08 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 17:59 [PATCH] What's the quickest way to contribute? Oleh Krehel
2015-01-08 18:48 ` Eli Zaretskii
2015-01-08 19:04 ` Samer Masterson [this message]
2015-01-08 19:13 ` Dmitry Gutov
2015-01-09 0:01 ` Richard Stallman
2015-01-13 2:57 ` Dmitry Gutov
2015-01-13 5:10 ` Stefan Monnier
2015-01-13 11:15 ` Dmitry Gutov
2015-01-13 19:24 ` Stefan Monnier
2015-01-13 13:46 ` Oleh Krehel
2015-01-13 19:32 ` 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=CAP6_t8iuGFWaLXeZDNm_r6H69b0FTG+fGg0XOOC49mekBXjRkg@mail.gmail.com \
--to=nosefrog@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=o.krehel@tue.nl \
/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.