Re: Create/update Internals section

Hi Rowan, Thanks for the suggestions. I think that (in the long run) this section should give the bases so that the developer, at the least, understand what's going on under the hood. Or course, a developer can just go to the code and read it, but lower the learning curve will ease any contribution. Other point, I intend to document the preferred ways of doing things, using the e-mails already on the internals list, and any help that I can find. I'll use the Internals Book [1] as a base for the first drafts and from there we can adjust the things. In terms of content, the plan is to follow the natural way, from the basics to more advanced content. I intend to remove the old section, but after we have something useful to put on the place, which could be this basics content. I know it is a really tough job, and that it will not be accomplished in just a few days. Quite the opposite, it will be an ongoing effort, but it's needs to be done, and once the first version is in place, things will be easier. [1] http://www.phpinternalsbook.com/ Best Regards, *Adiel Cristo* Senior PHP Developer adielcristo@gmail.com LinkedIn <http://br.linkedin.com/in/adielcristo> | DevBlog <http://www.adielcristo.com/blog/pt> On Mon, Apr 9, 2018 at 10:03 AM, Rowan Collins <rowan.collins@gmail.com> wrote: > On 7 April 2018 15:32:55 BST, Adiel Cristo <adielcristo@gmail.com> wrote: > >Hi everybody, > > > >As stated at [1], the Hacker's Guide seems to be on its way to be > >deleted > >or replaced with a list of external references. > > > >I'm interested in update this section, although I know nothing about > >the > >internals. > >Is there anyone already doing something or interested in joining this > >work? > > > >[1] http://news.php.net/php.doc/969386904 > > I guess the first task is to define what the aims and scope of this > section should be. How will it differ from existing resources like > http://www.phpinternalsbook.com/ and how do we avoid > duplicating effort? > Who is the target audience - what are they expected to know already, and > what tasks should the guide help them understand? For instance, you could > focus on those parts needed for common types of third-party extension. > > Then you can think about whether to update the existing content one page > at a time, or remove it and start again with a more focused guide, which > would be easier to start, and easier to keep up to date as the engine > evolves. > > Regards, > > -- > Rowan Collins > [IMSoP] >