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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
