Development

/doc/branches/1.2/jobeet/en/ack.txt

You must first sign up to be able to contribute.

root/doc/branches/1.2/jobeet/en/ack.txt

Revision 19427, 3.4 kB (checked in by Russ, 4 years ago)

Replace skeptical - thought it was a typo but it's just the US English spelling
(US English is used a lot more widely in the symfony docs so best to be consistent - much as it hurts my Queen's English pride!)

Line 
1 Acknowledgments
2 ===============
3
4 Writing a book is both exciting and exhausting. Writing a technical book is
5 even more intense. You spend hour after hour trying to figure out how to
6 convey your message, how to explain concepts, and how to provide simple but
7 meaningful and reusable examples.
8
9 Writing a book is just impossible to do without people around supporting you
10 along the process.
11
12 The biggest support you can have is your **family**. And I must say I have one
13 of the most comprehensive and supporting family. As an entrepreneur, I already
14 spend most of my time at work. As the lead developer of symfony, I spend most
15 of my free time on hacking the next version of the framework. And then, I
16 decided to write another book. But without the continuous encouragements of my
17 wife, **Hélène**, and my two wonderful children, **Thomas** and **Lucas**,
18 this book would not have been written in such a small amount of time.
19
20 You cannot write a book all by yourself, especially a technical one. For this
21 one, I had the chance to benefit from top notch reviewers. They are all part
22 of the symfony adventure and I want to thank them all for the time they spent
23 on the project.
24
25 **Kris Wallsmith**, our community manager and symfony 1.3 release manager,
26 took the time to proof-read my far-from-perfect English prose. As this book
27 was published on a day-to-day basis on the symfony website, and because I live
28 in France, and he lives in the US, he got up very early every single morning
29 during a month, including weekends, to read and fix each chapter.
30
31 **Stefan Koopmanschap**, one of the most active symfony evangelists, took the
32 responsibility to run the Subversion repository for this book. Thanks to his
33 work, you can checkout the code and start reading the book from any chapter.
34
35 **Fabian Lange**, the symfony 1.2 release manager, and the symfony "Windows
36 guy", read the book with a Windows perspective and tried to be our newbie
37 reader. On a side note, he recently bought a Mac so we need someone else to
38 take on the "Windows guy" responsibility.
39
40 **Jonathan Wage**, the Doctrine lead developer, took the time to create a
41 Doctrine edition of the book. Thanks to his great efforts, you can choose
42 between Propel or Doctrine as your main ORM for symfony, and still enjoy the
43 same book.
44
45 **Pascal Borreli**, an online barfly on the symfony french IRC channel, and
46 the most friendly symfony community member, read the book chapter after
47 chapter at the speed of light. His continuous support and his kind words kept
48 me in a good mood to write this book from start to finish.
49
50 As the CEO of Sensio, I have a lot of responsibilities. And without the
51 support of the whole **Sensio team**, writing this book would not have been
52 possible. Special thanks go to **Grégory Pascal**, my 10 year partner, who was
53 quite skeptical about the Open-Source business model at the start but now
54 embraces it. I also want to thank **Laurent Vaquette**, my "aide de camp", who
55 simplifies my life on an every day basis, and agrees to come with me from time
56 to time to eat a *döner kebab*.
57
58 I also want to thank all the **online readers** for the feedback they gave me
59 early on. They have spotted a lot of small and not so small typos,
60 inconsistencies, and not-so-well explained concepts.
61
62 By buying an Open-Source book, you, the "**offline reader**" are my hero.
63 Buying a book that you can read online for free is a testament that you want
64 to actively support the symfony Open-Source project.
65
66 *Merci à tous !*
Note: See TracBrowser for help on using the browser.