X-Received: by 10.182.213.166 with SMTP id nt6mr38527481obc.3.1437451763364; Mon, 20 Jul 2015 21:09:23 -0700 (PDT) X-Received: by 10.182.44.163 with SMTP id f3mr272832obm.7.1437451763314; Mon, 20 Jul 2015 21:09:23 -0700 (PDT) Path: csiph.com!optima2.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!pg9no2617258igb.0!news-out.google.com!t2ni16868igk.0!nntp.google.com!f3no672355igg.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.python Date: Mon, 20 Jul 2015 21:09:23 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=70.196.73.94; posting-account=h3aEwQoAAACiuqX-oR3gvCVFm8lLHoWj NNTP-Posting-Host: 70.196.73.94 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <3a6dccbf-4518-4fae-8dc9-e27cfd73cd00@googlegroups.com> Subject: Re: Should non-security 2.7 bugs be fixed? From: Rick Johnson Injection-Date: Tue, 21 Jul 2015 04:09:23 +0000 Content-Type: text/plain; charset=ISO-8859-1 Xref: csiph.com comp.lang.python:94266 On Monday, July 20, 2015 at 1:30:03 AM UTC-5, dieter wrote: > Experience like this (in another project) causes me to be > very reluctant to become a core contributor (in the sense > of actively fixing things in the core). You need a lot of > knowledge (coding conventions, test setup, change > workflow, ...) whichs goes far beyond the functionality of > the fix -- and you must be resilient, patient and maybe > even fighting to get the work accepted. Thanks for sharing your experiences. I hope many more will come forward and do the same. We are obviously ignoring some talented people out there, and as i stressed before, we need to prevent further hemorrhaging of this talent. I know there are tons of folks who will get involved if we can remove the onerous barriers.