Closing choices on Book name - Take your Pick

[Chris Corbyn]

OK, we need to come up with the final name for our book. After much discussion and a quick general vote we seem to have closed into these choices.

Let's note the objectives of this book whilst we think of a title for it.

Objectives:

• WILL be welcoming and easy reading for newbie programmers
• Will therefore teach general progamming concepts such as logic
• Will NOT distill OOP as a completely alien and separate area of programming
• WILL teach good design from the outset, using OOP without even making the reader concious of it
• WILL teach the essentials/basics of related technologies but no more than the basics (except MySQL where we go into more depth)
• SHOULD appeal to advanced and knowledgable developers as well as newbies
• SHOULD encourage the reader to read further on advanced topics with a larger scope than the book itself
• The reader will be capable of writing a small but solid and well designed web application
• Will cover other advanced areas which make good programmers such as project planning and management

[feyd]

I like names to be short and simple: Unraveled for me.

[RobertGonzalez]

I am a fan of PHP for Anyone so I voted for it, but I would be satisfied with any of them.

[JayBird]

Shouldn't "The Developer Network's Guide to PHP" be "The Developer's Network Guide to PHP"

Or am i just rubbish at english?

[GM]

I think that technically it should be "Developer's Network's Guide", but it's a bit of a mouthful.

[Oren]

I wasn't sure whether to vote for 'PHP: Installation to Application' or to 'PHP Unraveled'. Eventually, I voted for 'PHP: Installation to Application'.

[RobertGonzalez]

I suppose, if it is a possessive form of the name, it would be the same as 'PHPDN's ...'. The question is then, is PHPDN translated to 'PHP Developers Network' (implying a network of developers) or is it 'PHP Developer's Network' (implying ownership of the network by PHP Developer)?

[Christopher]

I think that technically it should be "Developer's Network's Guide", but it's a bit of a mouthful.

I think probably "The Developer's Network Guide" is correct because "Developer's Network" is just being used as an adjective like "The blue Guide". There is some flexiblity with titles.

And "Developer's Network" could also be simplified to just "Developers Network" meaning "the network of developers" rather than "the network of the developers" -- it is splitting hairs and I am not sure one coveys any more meaning than the other.

PS - I was suprised that the simple "Community PHP" did not make the list.

[feyd]

Personally, "community" just felt weird. I can't place why, it just did.

[Christopher]

Personally, "community" just felt weird. I can't place why, it just did.

For me it felt the most like a brand, because the word seems the least commonly used with programming language books.

[GM]

24 hours have passed, and I'm rather worried by the lack of votes... does this mean that only 11 people come in here? Or... do only 11 people care?

We've got a hell of a lot of stuff to write.

[feyd]

I think it's fair to leave it in here for a little longer. Not everyone is as active as some of us.

[Oren]

A little bit off-topic, but what is going with the book?

1. When do we start to write?
2. Do we have a license?
3. Who does what? (Who are the editors, writers, etc)

[RobertGonzalez]

Check out the book forum, Oren. There is a lot that went on while you were away for those few days.

[Christopher]

How about:

series: Developer's Network Guides
title: PHP: Installation to Application

I was about to throw Unraveled on the end