On Sun, Apr 24, 2016 at 02:57:09AM +0100, Richard Russon wrote: > I want to help. > I offer code. No, not interested. > I offer help. No, not interested.
Really? https://dev.mutt.org/hg/mutt/rev/80926cec6d41 https://dev.mutt.org/hg/mutt/rev/1fb2a924a7c0 https://dev.mutt.org/hg/mutt/rev/cbf073e5e0d7 changeset: b8240918eded "Thanks to Richard Russon for the bug report and initial patch" changeset: 62e478a3f1c "This patch is based on the one Richard Russon found in the Fedora package." changeset: 789500dae762 "Thanks to Richard Russon for finding this patch in the Fedora package." changeset: c8c76a6a1e61 "Thanks to Richard Russon for bringing this patch to our attention." Now, let's review your history here: 1. Date: Sat, 21 Nov 2015 01:24:51 +0000 <20151121012451.ga20...@flatcap.org> You: Hi Everyone, I'm brand new, and you don't know me at all, but I want to touch the entire codebase. Please let me. Response: Uh, no. We don't know you. Please start small, or maybe work on some kind of tool to reformat the code that we can audit and run. You: disappear 2. Beginning of March: You: Hi Everyone, I've forked mutt, and I've chosen the name "neomutt" which is completely coincidental and has nothing to do with "neovim", the hostile fork of vim. Oh, but umm... it's not a fork. It has every rejected patch in the history of mutt and you all should come look at them all. Response: Some people look at the patches. While, some patches look interesting, but nothing looks immediately commitable. We'll see. 3. Middle of March, two weeks before 1.6.0 release: You: I've decided to run clang and coverity on the codebase and fix every single warning. Here it comes! patch broken patch broken patch huge patch patch useless patch useless patch huge patch broken patch Response: Stop it! We're trying to get a release out and this is not helping. Send patches that fix actual problems, please. 4. Mid-March through April: Two more postings about neomutt to mutt-dev and one to mutt-users, just to make sure everyone knows it's the new hotness. > What development will you consider? > Make a list. I told you in <20151122185830.ge2...@zaogao.lan> that if you want to become a contributor, you should start small. You ignored me, just left, and forked mutt. Then you started your ticket spree. Although you found a few patches that were helpful, the patches you've written along with your judgment and general attitude have not gained my trust. And I (grumpily) said as much in ticket 3824. The past week, as a way to hopefully find common ground, I worked on a fairly "grunt work" set of patches to perhaps work toward the sidebar getting in, which you pushed for in ticket 3829. While I did appreciate your slang fixes and reflow suggestion, when I finish and post to the list, your response is a condescending email about how much of a pain it is for you to deal with the revised patches and how things would be so much better if I just listened to you. As you said in the past, we're all volunteers. But you don't seem to want to work your way up within our community and culture: you want to go big and do everything your way, right now. You're very welcome to your fork, but I'm just about done with you. I'd rather have less contributors than deal with this kind of "help". -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA http://www.8t8.us/configs/gpg-key-transition-statement.txt
signature.asc
Description: PGP signature
