Definitive Dru Definitive Dru upal 8 upal 8 - China China Boz - PowerPoint PPT Presentation

Participa Participa ant Needs ant Needs  Make social connections o Make social connections o f Drupal mentorship status, f Drupal mentorship status, that can be used in the futu ure to get further involved 与 Drupal 专家有更多的社 与 Drupal 专家有更多的社 交互动，未来无限可能 交互动，未来无限可能  Build a network of these co onnections that will get us involved in major Drupal i involved in major Drupal i nitiatives module building nitiatives, module building and maintenance, even bui lding Core for Drupal 9  有了这个良好的关系，未 有了这个良好的关系 未来可以更方便地参与到模 未 未来可以更方便地参与到模 块维护，甚至如 D9 内核开 开发

duct Defined 品定义 ) ion 3 ion 3 5. DD8 Prod Secti Secti (DD8 产

5 The DD 5. The DD D8 Product D8 Product  1. Main Series  2. “Deep Dives” - Spon nsorship  3. MAJOR Website for  3. MAJOR Website for updates (not just errata) updates (not just errata) 1. 书的主体内容 2. 各种深入的内容，包含 含赞助 3 网站的更新等 3. 网站的更新等

5. The DD 5 The DD D8 Product D8 Product  4. Online Virtual Classe es with the Authors  5. Video interviews wit th Authors/Participants  6. Video podcasts of ex  6. Video podcasts of ex xercises being done xercises being done 4. 在线虚拟课程 5. 与作者、参与者们视频 频沟通 6. 视频播报等 6 视频播报等

5 The DD 5. The DD D8 Product D8 Product  7. Study Group organiz zation support  8 Free chapter updates  8. Free chapter updates and rewrites and rewrites  9. Killer module lists an nd documentation  10. Part of each topic do onated to Drupal.org 7. 学习小组的支持 7 学习小组的支持 8. 免费章节的更新 9. 杀手级模块列表及文档 档 10 与官网贡献的相关话 10. 与官网贡献的相关话 话题 话题

1 Main Series 1. Main Series Print Volumes Print Volumes  1. Beginner Volume  2 (?) Intermediate Volu  2. (?) Intermediate Volu ume ume  3. Advanced Volume  4. Theming (Soup to Nu uts) 1. 入门 1 入门 2. 中级 3. 高级 4. 主题 主题

1 Main Series 1. Main Series Print Volumes Print Volumes  5. Module Building  6 Application Develop  6. Application Develop ment and Integration ment and Integration  7. (?)Killer Modules  8. (?) Site Types 5 模块开发 5. 模块开发 6. 应用开发和集成 7. 杀手级模块 9 网站类型 9. 网站类型

1 Main Ser 1. Main Ser ries Strategy ries Strategy  1. Physical Presence an nd Brand Identification  2. Given hints at more m  2 Given hints at more m material material Cross Selling – All Allow Reader to p R d t plot their own course l t th i – 1. 实体发型，商业操作 2. 多样化的发售

Main Serie Main Serie es Strategy es Strategy  3. Drive reader toward t the Community 让读者走向社区 让读者走向社区  4. Uses the traditional r royalty model 传统的版权模式  5. Serves as a launchin  5 Serves as a launchin ng point for Deep Dives ng point for Deep Dives 更多开放的模式  6. Are tightly cohesive and use Git for examples 更多密切结合的方式 更多密切结合的方式，如 如 如 git 如 git

2 “Deep 2. Deep p Dives p Dives”  1. Open Content/ Sponsorship Pub blishing Model 开放的发布模式  2. About 50 different topics like Migrating sites from other CMS's or r versions – Dependency injection D d i j ti – User Experience and process topic cs – Contributing to core – 选取 50 个不同的话 话题 –

Deep Dives Deep Dives Brainstorm Brainstorm  Let's Brainstorm Ideas for Deep D Dives. What have you never seen in a book on Drupal that you would lik ke to see:  Drush Dr sh  Git for Drupal  Migration Mi i 头脑风暴，来深度挖掘。如一些你 你在其他 Drupal 书中还没有看到过 的话题。 的话题。

Secti Secti ion 4 ion 4 6 Topics 6. Topics - The The e Heart of DD8 e Heart of DD8 Con ntent (DD8 的各个 个核心话题 )

6 Topics 6. Topics s Defined s Defined  Topics are generally wh hat you would think they are in normal parlance are in normal parlance. For DD8, however, they For DD8 however they also take on additional m meaning. 我们讲的话题和一般的话 话题意义有点不同，书 本的章节会是话题，这 这个话题里会有团队成 员等 员等。  Topics are areas of stud p dy (Menus, Rules, etc.) y ( , , ) 话题也同时是各个具体的 的讨论。

6 Topics 6. Topics s Defined s Defined  Topics can also be multiple in natu ure, like Introduction to Views – Advanced Views – Specialty Views – Views and Git relations ship, Using Git with Views – Views Best Practices – 比如 views 可以有以上的话题 题

ainStorming ion 5 ion 5 题 ) 7. Topics Bra Secti Secti ( 话

6 Topics 6. Topics s Defined s Defined  I've bought 12 books on n Drupal 7  But since Topics are the  But since Topics are the e Heart of DD8 content, e Heart of DD8 content, do we really want them m to come from 12 people?  They should come from Th h ld f m the community th it  People that would buy t the book – You! 我们希望话题来源于社区 区，而不仅仅是 12 本书

6 Topics 6. Topics s Defined s Defined  In DD8, Topics will for rm the basis for organizing Chapters (1 organizing Chapters (1 per) and Topic Teams per) and Topic Teams 一个话题对应一个章节， ，一个团队  Since we are organizing g our community from the bottom up, this is co the bottom up, this is co onsistent with our onsistent with our philosophy 社区的参与会是本书的一 社区的参与会是本书的一 一个灵魂 一个灵魂

Sample Topic Sample Topic c Cover Page c Cover Page  Topic Name  By author name with m mentor name  Edited by SE Name wit  Edited by SE Name wit th Technical Editing by th Technical Editing by TE name  Quality assurance by Re Q lit b R eader/Testers names d /T t  Content Currency Engin neers: CCE names  Topic Volatility: High, , Medium, Low

rainstorm rainstorm Topics Br Topics Br

ned from DGD7 目的宝贵 ) 目的宝贵 ) ion 6 ion 6 (DD7 项目 (DD7 项目 3.Lessons Learn Secti Secti

3 Lessons Learn 3. Lessons Learn ned from DGD7 ned from DGD7  Just covering one today y. 今天只讲一个例子  Authors need help and t  Authors need help and t there are many benefits to there are many benefits to helping 每个作者需要很多的帮助 每个作者需要很多的帮助 助，在帮助过程中你也 助 在帮助过程中你也 能获益良多

3 Lessons Learn 3. Lessons Learn ned from DGD7 ned from DGD7  Michelle Lauer wrote the DGD7 h DGD7 chapter on Views t Vi Views 章节的作者  She wrote a great chapter

3 Lessons Lea 3. Lessons Lea rned – Views 3 rned Views 3  After Michelle submitte ed her chapter, and 3 days before the publishing de before the publishing de eadline Views 3 was eadline, Views 3 was announced  提交完内容的 3 天后， 提交完内容的 后 Views 3 发布了 发布了  Michelle had moved on Michelle had moved on n to other work projects n to other work projects and could not do a majo or revision. Not in 3 days. y  原作者因为项目而离开 开，无法继续更新

3 Lessons Lea 3. Lessons Lea rned rned – Views 3 Views 3  This is Michelle after the after the announcement of Views 3 and finding Views 3 and finding out that all her work had to be re done in had to be re-done in 3 days  表情的写照 表情的写照

3 Lessons Lea 3. Lessons Lea rned rned – Views 3 Views 3  Greg Stout, also from NH stepped from NH, stepped in and re-wrote major portions of major portions of the Chapter in 3 DAYS DAYS. 重新提升日程

3 Lessons Lea 3. Lessons Lea rned – Views 3 rned Views 3  This was a nearly impo ssible deadline. Although Greg worked day an nig Greg worked day an nig ght and finished ght and finished 无法完成的任务  The quality suffered. O One piece of information was left out, creating a R was left out, creating a R Relationship. And many Relationship. And many of the examples were ef ffected. 质量面临挑战 质量面临挑战

3 Lessons Lea 3. Lessons Learned rned – Views 3 Views 3  Also Greg was completely completely stressed out, by the impossible the impossible deadline.  And the one line mistake  This is how he looked.

Lessons Learn Lessons Learn ned – Views 3 ned Views 3  What if Michelle and G Greg had a team of people working with them taki working with them, taki ing care of specific small ing care of specific small jobs so that they could f focus on quality writing instead of the hundreds instead of the hundreds of other things that can of other things that can ruin your focus and crea ativity. What if they had desig gnated people to review  their work and make su ure it made sense? 我们需要有更好的团队架 架构

Lessons Learn Lessons Learn ned – Views 3 ned Views 3  A Content Currency En ngineer would have seen Views 3 coming and ale Views 3 coming and ale erted Michelle that her erted Michelle that her work would soon be ob solete. 一个内容校正工程师可 个内容校 程师 以提前发现这类问题 以提前发 这类问题  A Reader/Tester helpin A Reader/Tester helpin g Greg would have g Greg would have alerted him to the one m mistake that had such large consequences on q g q q quality. q y 一个阅读、测试者可以帮 帮助质量控制

Lessons Lessons Applied Applied  Let's give that kind of s upport to our Author's instead of letting them g instead of letting them g go it alone go it alone  Let's take some volunte eers from the community that would love to have the opportunity to work closely with high level D Drupalers and even pay them a percentage for th heir work  Let's create a whole team m not just to support the j pp Authors but to crowd so ource the whole book  有了这次经验，我们可 有了这次经验 我们可 可以把风险控制的更好 可以把风险控制的更好

Secti Secti ion 7 ion 7 7. Topic Teams a and Roles – How we get th t th hi d his done ( 围绕话题的 ( 围绕话题的 团队和角色 ) 团队和角色 )

Topic Topic Teams Teams  Each Topic Team will b be lead by a Main Author (MA) (MA)  The following chart sho ows how the teams are organized organized

Main Author MA M ?? / 主要作者 1 Topic Topic Teams Teams $ ￥ 赞助商 Team Sponsor TS T 1 Topic Mentor TM T ?? / 话题导师 1 Style Editor y SE S 5 hrs/ 样式编辑 1 1 Technical Editor Technical Editor T TE TE T 3 hrs/ 技术编辑 3 hrs/ 技术编辑 1 1 Reader/Tester Reader/Tester R R RT RT 3 hrs/ 测试 3 hrs/ 测试 3 3 Content Currency Engineer C CC 2 hrs/ 校正 3

Topic Tea Topic Tea am Roles am Roles  The following are short t descriptions of the duties for which each ro duties for which each ro ole is responsible ole is responsible  A more comprehensive description will be available soon, but for t available soon, but for t this presentation the short this presentation the short version is sufficient

Topic Tea Topic Tea am Roles am Roles  Main Author (MA)  Topic Knowledge: High  Availability: 10 to 20 hrs / w week for 3 months  Leader of the Topic Team an nd Chief Writer of the Chapter

Topic Tea Topic Tea am Roles am Roles  Communicates with team and d dependent authors  Provides outline of subjects P id tli f bj t  Commits work to Git (at leas st weekly)  Respond to reports from team m and dependent topic teams

Reader/Tester En Reader/Tester En ngineer Benefits ngineer Benefits  Highest recognition and repu utation enhancement of all the roles o es  High level of access to local and global mentors from English version of the book  Huge resume booster  Intimate knowledge of the pu Intimate kno ledge of the p ublishing process blishing process  Leads to speaking and other a acknowledged ninja status engagements engagements

Content Curre ency Engineer Comm mitment  Ultimately responsible for pr roducing the chapter and leading the team ead g t e tea  If you need to bail out, bailin ng out sooner rather than later is critical  Work with own team membe ers for internal accuracy  Work with leadership of othe Work ith leadership of othe er Topics to ensure volume er Topics to ens re ol me consistancy  Communicate issues to globa Communicate issues to globa al Topic teams al Topic teams

Topic Tea Topic Tea am Roles am Roles  Topic Mentor (TM)  Topic Knowledge: High  Availability: Low or as agree ed with Author  Knows most about topic, pro obably on programming team

Topic Tea Topic Tea am Roles am Roles  Advisory role to Author and Team  May step in if Author has to M t i if A th h t quit it  Other duties adhoc

Mentor B Mentor B Benefits Benefits  High recognition for little eff fort and time  Chance for intensive network Ch f i t i t k king with English version ki ith E li h i technical gurus  Flexible hours and responsib Fl ibl h d ib iliti ilities as negotiated with Author ti t d ith A th  Consider mentoring in one T Topic while Authoring in another

Content Curre ency Engineer Comm mitment  Negotiated with Author

Topic Tea Topic Tea am Roles am Roles  Technical Editor  Topic Knowledge: High  Availability: 3 hrs per week f for 3 months  Reviews Author submissions s for Technical accuracy

Topic Tea Topic Tea am Roles am Roles  Coordinates with related TEs s  Handles issues from team me H dl i f t embers b  Reports progress to TE Proje ct Manager  Ready to replace Author if ca alled upon

Technical Ed Technical Ed ditor Benefits ditor Benefits  Chance for mid to high level people to work with the best on technical issues tec ca ssues  Chance to work with other T E's from other Topic Teams and increase technical network  More contact with counterpa rts in English version  Lots of credit for little time Lots of credit for little time  Consider an author or mentor r position in addition to this in a closely related topic closely related topic

Technica al Editor Comm mitment  Verify theoretical accuracy o of Author and Mentor work product p oduct  Coordinate with TE's in other r related Topics for consistency, completeness, an y, p , nd non-redundancy  Ensure relevance of exercise from technical perspective  Consider this as one of sever Consider this as one of se er ral roles to take on ral roles to take on  Serve as a third set of high le evel eyes on the material  When available, Author cont tent should be scrutinized, polite but VERY thorough fe eedback is expected

Topic Tea Topic Tea am Roles am Roles  Style Editor (SE)  Topic Knowledge: Low  Availability: 5 hrs per week f for 3 months  Reviews Authors work for co ompliance with style guidelines

Topic Tea Topic Tea am Roles am Roles  Performs all non-technical re elated editorial services  Reports to SE Project Manag R t t SE P j t M ger  Facilitates issue handling  Alleviates Author from non-w writing duties

Style Edito Style Edito or Benefits or Benefits  Chance to work with people of many disciplines  Good networking opportuniti G d t ki t iti ies  Hands on training in use of G Git  Chance for lower technical le evel person to work hard and gain access to inner workings of T Topic at an intense level  Contact with counterparts in English version  Opportunities to make of it w pp what you wish y Works closely with upper le ver members and English version 

Style E Editor Comm mitment  This is a wordsmithing positi ion  It also covers a lot of other du It l l t f th d uties and communication with ti d i ti ith other teams, Git, Drush, and exercise authors  Good writings and other com G d iti d th mmunication skills are a must i ti kill t but this is an opportunity for a lower tech person to really get into the inner workings o g g f the Topic p  Familiarity with the DD8 pro ocess is a must  Consider taking this same rol Consider taking this same rol le in several different topics as le in several different topics as the skills are the same but ch hance to learn is greater

Topic Tea Topic Tea am Roles am Roles  Reader/Tester  Topic Knowledge: Low but n nit picky  Availability: 3 hrs per week f for 3 – 6 months (low at start)  Reads drafts of Authors work k and tests for issues

Topic Tea Topic Tea am Roles am Roles  Reports testing issues to the t team and/or precursor  Monitors precursor testing an M it t ti nd results d lt  Actively seeks out and report ts on technical problems  Gives feedback on accessibil lity of the writing

Reader/Tester En Reader/Tester En ngineer Benefits ngineer Benefits  Hands on training in use of G Git  Intensive hands on training in I t i h d t i i i n the topic you choose by the th t i h b th authors and mentors of the te eam  Contact with counterparts in C t t ith t t i E English version li h i  Any intermediate level Drupa aler with a particular interest in speciali ing in a certain area specializing in a certain area of Dr pal of Drupal  Any beginner level Drupaler with a particular interest in a topic, or just curious about le topic or just curious about le earning Drupal from the pros earning Drupal from the pros should take this position Works closely with upper le Works closely with upper le ver mabers and English version ver mabers and English version 

Reader/ r/Tester Comm mitment  There will be 3 R/T's to each h topic so coverage is good  Therefore a reasonable effort Th f bl ff t t can be made to accommodate t b d t d t your schedule  You may have to wait for new Y h t it f w versions of the chapter, so i f th h t time will be intermittent and taking on an additional role is suggested, either on the same gg , e topic or Testing a different p g topic  Consider this as one of sever ral roles to take on  When available, Author cont tent should be scrutenized, p polite but VERY thorough fe g eedback is expected p

Topic Tea Topic Tea am Roles am Roles  Content Currency Eng gineer  Topic Knowledge: Any  Availability: 2 hrs per week f for 6 months  Monitors and reports on upco oming changes to Drupal topic

Content Currenc Content Currenc cy Engineer Role cy Engineer Role  Checks issue queue every day y and reports issues to team  Job lasts into post-production J b l t i t t d ti n for update purposes f d t  Keeps content fresh for mont ths after publishing  Monitors and reports on relat ted Topic Team changes

Content Currency Content Currency Engineer Benefits Engineer Benefits  Training in use of the Drupal l Issue Queue  Accessing to the lates inform A i t th l t i f mation on your topic ti t i  Contact with counterparts in English version  Anyone considering taking p part in module development should consider this as just o ne of their roles, solid understanding of the Issue Qu nderstanding of the Iss e Q ueue is essential to contributing e e is essential to contrib ting code to core and modules Works closely with upper le Works closely with upper le ver Drupalers and English ver Drupalers and English  speaking mentors

Content Curre ency Engineer Comm mitment  There will be 3 CCE's to each h topic so coverage is good  Therefore a reasonable effort Th f bl ff t t t can be made to accommodate b d t d t your schedule  I suggest committing ½ hour I t itti ½ h r per day, plus any additional d l dditi l work and research you would d like to go into.  Consider this as one of sever Consider this as one of se er ral roles to take on ral roles to take on  A typical CCE will spend ½ hour per day for the first 3 months, every second day, an months every second day an nd the same timeonce per week nd the same timeonce per week for the second three months, 1 initial hour of training

Univeral Benef Univeral Benef fits to all Roles fits to all Roles  Intense access to experience high level Drupallers  A chance to see how excellen A h t h ll nt book publishing is done t b k bli hi i d  Reputation and status in your r field and job  Connections to English speak king mentors and Drupal insiders for future networking, and de evelopment opportunities  Integrating into the Global D Drupal Community  IN PRINT acknowledgment g of your work, see topic title page y p p g next

Topic Tit Topic Tit tle Pages tle Pages  All Chapter Title Pages will f follow this Sample format:  Migrating yo our site to Drupal  By Boz Hogan n with Mentor Name  Technical Editor: T Technical Editor Name  Quality Assurance b by Reader/Tester Names  Content Currency and Upda Content Currency and Upda ate Maintenance by CCE Names ate Maintenance by CCE Names  Topic Stability: Unstable e – Check website for updates

Afterword: Ha Afterword: Ha andling Fame andling Fame  After publication, you are go oing to notice that people are not only going to treat you with m o y go g to t eat you w t more professional respect, but o e p o ess o a espect, but they are also going to come t to you with questions  Stay humble but helpful y p  The chances are you are goin ng to know the answers they seek. After all, you having just bee , y g j en through intensive exposure on g p your topic with some of the s smartest people in Drupal  Answer them. Be generous w g with your knowledge. y g  If you don't know the answer r, tell them you know someone who is an expert in that area p and you'll find out for them y

Afterword: Ha Afterword: Ha andling Fame andling Fame  Follow up on this.  You've told th truth. After pa Y ' t ld th t th Aft articipating in this project you ti i ti i thi j t will definitely know people t that do have the answers  Realize that these mentors ar R li th t th t re busy people. They often do not b l Th ft d t have time to answer request. However, having helped them on the project, they will know p j , y w you. They WILL take your call y y y or email.  Don't abuse this. Don't call w with a question every day. q y y  Respect their time. Use emai l first, so they can respond when it is convenient for them

Afterword: Ha Afterword: Ha andling Fame andling Fame  Mostly, share what you learn n. You didn't get to this spot by someone being stingy with th so eo e be g st gy w t t heir knowledge. Pass it on. e ow edge. ass t o .  You will find that you will be ecome more and more, the person p people come to for answers, a p , at work and at User Groups p  Most participants in the DGD D7 project were either promoted or moved on to better opportu pp unities. Humbly enjoy your y j y y success and new status.  Lastly, don't lose touch. You y, u now have access to a network of people with vast knowledge. Participate. Join projects. Nurture this network or you m may lose it. Contribute back to Drupal. Drupal

Artif Artif facts facts  A pre-defined set of reports w will be created for issue reporting  TE25CI09-1 comes from TE TE25CI09 1 f TE of Chapter 25 with priority 9 f Ch t 25 ith i it 9  Artifacts are stored in Git, an nd sharing will be automated  Compensation will depend st trongly on artifact evidence

Secti Secti ion 8 ion 8 8. General Admi 8. General Admi inistrative Roles inistrative Roles ( 常规的管 管理角色 )

Administra Administra ative Roles ative Roles  Leader – Answers to Centr ral Steering Committee  Executive Director  Participant Recruiter  Participant Recruiter  Author Project Manager*

Administra Administra ative Roles ative Roles  Mentor Project Manager*  Lead Technical Editor*  Style Editor Manager*  Style Editor Manager  Reader Testing Project Ma anager*

Administra Administra ative Roles ative Roles  Content Maintenance and F Freshness Project Manager*  Technical Support Speciali ist  DD8 Process Specialist  DD8 Process Specialist  Website Development Team m

Administra Administra ative Roles ative Roles  Post production team  Marketing team  Translators(for communicatio ( on with Central Steering g Committee, not for translatin ng book, hopefully)

Administra Administra ative Roles ative Roles  Note, the above roles al ll have descriptions of duties that will be made duties that will be made e available soon most of e available soon, most of them stress communica ation and resolution  * Starred roles correspo Starred roles correspo ond exactly with the role ond exactly with the role on the Topic teams

Secti Secti ion 9 ion 9 9. Central Leade 9. Central Leade ership Structure ership Structure (Trans slation)

Central Leader Central Leader rship Structure rship Structure  The Central Steering Co ommittee is currently being formed being formed  It now consisted of 5 pe eople, I'm looking for 8 PLUS 3 Chinese, 3 Port tuguese, and 3 Spanish speakers  That leaves a majority o of Non-English project members  Participation requires g ood English skill and should be selected local should be selected local lly lly

Central Leader Central Leader rship Structure rship Structure  The Central Steering Comm mittee (CSC) is responsible for major decision in the En for major decision in the En nglish version of the nglish version of the product  It will handle non productio on issues like attorneys, accounting, etc.  Create a framework of stan ndards for the Non-English version, and an outline of re , equired topics q p  All other decisions will be m made locally  This will be a Chinese cont trolled effort