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 wrote: > > Date: Thu, 8 Jan 2015 18:59:09 +0100 > > From: Oleh Krehel > > > > 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. > >