how to contribute reports on many small issues?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

how to contribute reports on many small issues?

Oliver Koenig
This post has NOT been accepted by the mailing list yet.
Hi,

I'm a ZF2 newbie. In order to understand ZF2, I browse through the framework code a lot, often in a debugger session, but also by reading the code.
So I often come across some small issues in the code (for example, inconsistencies and inconveniences, e.g. EventManagerInterface::trigger() and triggerUntil() are inconsistent in the argv parameter, trigger() produces a fatal error when passing null as argv, it should better accept the null value and replace it internally with an empty array).
How and where can I report such things? There are just many small things, I certainly don't want to clutter a general-purpose forum with these, but I would very much like to see these many small things improve.
Can anyone hint me to the proper place and way to do so, please? :-)

Thanks,
Oliver
Reply | Threaded
Open this post in threaded view
|

Re: how to contribute reports on many small issues?

dennis-fedco
This post has NOT been accepted by the mailing list yet.
In no particular order:

1.  Convince Zend to hire you as a developer & fix up the framework.
2.  Fix them yourself and submit multitude of Pull Requests on GitHub, which reportedly may result in a lot of waiting, discussions, and some general pain, due to sheer number of them.  
3.  Convince Zend Community to create a subforum for these things, call it "Zend Framework Improvement" forum as to not to clutter the other ones.
4.  Live with it, and hope that some time, somebody will notice and get to some of them some time.
5.  Create & Keep a blog with each inconsistency documented and active links pointing to the git repository.  This may get noticed and generate enough interest to close out some of them.
6.  There must be a ZF2 Bug Tracking database somewhere.  Find out if it is open to the public and submit bug/feature requests.  Maybe GitHub "Issues" is it?

I'd say #6 may be most promising, with #2 followed closely if you have enough chutzpah to modify the code yourself.  The rest is probably not very likely.