Re: [PHP-DEV] Low Hanging Fruit

[Thomas Hruska]

On 11/1/2016 11:08 PM, Michael Morris wrote:

What are some outstanding bugs that should be relatively easy to fix that
no one has gotten around to? Low hanging fruit as it were for beginning
devs.


Bug #72333 should be relatively easy and is most likely still a valid 
bug under the PHP 7 series.  I've been busy with other things but, while 
researching the issue, I came up with a one-liner that has a pretty good 
chance of fixing the problem and there is even a consistent test case to 
demonstrate the problem.  Bugfixes rarely get much more silver platter 
than that.


--
Thomas Hruska
CubicleSoft President

I've got great, time saving software that you will find useful.

http://cubiclesoft.com/

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

Re: [PHP-DEV] Low Hanging Fruit

[Yasuo Ohgaki]

Hi Michael,

On Wed, Nov 2, 2016 at 3:08 PM, Michael Morris  wrote:
> What are some outstanding bugs that should be relatively easy to fix that
> no one has gotten around to? Low hanging fruit as it were for beginning
> devs.

Easy is depends on what you know.
There are many. You can find them easily
https://bugs.php.net/

Just send pull request from github. We don't have much resource so
PR may take long time until merge.

Regards,

--
Yasuo Ohgaki
yohg...@ohgaki.net

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

[PHP-DEV] Low Hanging Fruit

[Michael Morris]

What are some outstanding bugs that should be relatively easy to fix that
no one has gotten around to? Low hanging fruit as it were for beginning
devs.

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

[Miah Gregory]

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

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

[Hannes Magnusson]

On Mon, May 14, 2012 at 1:27 PM, Miah Gregory m...@darksilence.net 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

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

[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

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