[PHP-DEV] Low hanging fruit / entry point for new developers to the core

Hi there,

The recent suhosin 'discussions' and subsequent browsing of various
mailing lists prompted me into looking at doing some core
development/bug fixing/whatever, since I have a vested interest as a
user.

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.

Would also be of use to know what automated (or otherwise) testing
procedures are available for pre-commit checking?

--
Regards,

Miah




--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

On Mon, May 14, 2012 at 1:27 PM, Miah Gregory <[email protected]> wrote:
> Hi there,
>
> The recent suhosin 'discussions' and subsequent browsing of various
> mailing lists prompted me into looking at doing some core
> development/bug fixing/whatever, since I have a vested interest as a
> user.
>
> 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.


It really depends on what you are looking for. Maintaining such list
is just to much work as most things do get fixed fairly quickly.
We do however have bunch of bug reports, of various quality and complexity..


All I can think of is:
https://wiki.php.net/ideas
https://bugs.php.net/random (and keep hitting the random link until
you find something you consider interesting)


> Would also be of use to know what automated (or otherwise) testing
> procedures are available for pre-commit checking?


compiling and running the tests with/without
--enable-maintainer-zts
--enable-debug
and running run-tests.php under valgrind (-m)

-Hannes

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

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