Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60584 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13181 invoked from network); 14 May 2012 18:35:55 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 May 2012 18:35:55 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.143 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.143 smtp143.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.143] ([67.192.241.143:44796] helo=smtp143.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BB/31-03088-98051BF4 for ; Mon, 14 May 2012 14:35:54 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp14.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 3CA2929B196; Mon, 14 May 2012 14:35:50 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp14.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id CDCD529B17D; Mon, 14 May 2012 14:35:49 -0400 (EDT) Message-ID: <4FB15085.5000704@sugarcrm.com> Date: Mon, 14 May 2012 11:35:49 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Miah Gregory CC: "internals@lists.php.net" References: <1336994836.5381.9.camel@thinkpad3.darksilence.net> In-Reply-To: <1336994836.5381.9.camel@thinkpad3.darksilence.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Low hanging fruit / entry point for new developers to the core From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I had a look around the various php.net sites but didn't really find > much in the way of guidelines to get involved, code wise, or suggestions > as to low hanging fruit that wouldn't be too painful to start on. If > someone could point me in the right direction it would be much > appreciated. I would suggest looking through bugs.php.net either looking for bugs in mainstream extensions or ones that you may be familiar with underlying library, or looking into XFAILs on the tests maybe (see below how to run them). You could also do http://bugs.php.net/random and see random bugs - after a few tries you usually can find some with good reproducing case - though not all of them will be easy to deal with :) > Would also be of use to know what automated (or otherwise) testing > procedures are available for pre-commit checking? make test runs all the unit tests (be warned, there's 10K+ of them, more depending on enabled extensions, so some patience is required). run-test.php script will run any specific test or group of tests in given directory (tests are in tests/ usually and called .phpt) -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227