Thank you for clarification. I'm agree with all points. But I think in this
particular case (1 file, <20 lines of code) simple review could be enough.
I'm new in php development and may be I am missing some workflow steps. If
RFC is absolutely necessary I will be happy to create it but I have no
enough wiki karma.


On 21 July 2014 14:52, Pierre Joye <pierre....@gmail.com> wrote:

> On Mon, Jul 21, 2014 at 11:50 AM, Dmitry Saprykin
> <saprykin.dmi...@gmail.com> wrote:
> > Ok, I will NOT ))
> > God saves us from bureaucracy
>
> Well, Michael's view is known.
>
> However let me explain what RFCs bring, besides bureaucracy.
>
> - clear identification of use cases, incl. edge cases
> - better design and design reviews
> - documentation, ready to be used by the doc team
>
> I do not know how big such changes will be but I can already see a
> couple of things that may require more than "works for me on my fav
> linux distros" edge cases. :)
>
> >> Yes, please do NOT create a RFC for each and every tiny feature. Just
> find
> >> someone to review and eventually merge your patch!
> >>
>
>
>
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
>

Reply via email to