1. Tridion Power Tools A Tridion Community Project Presented by the 2011 SDL Tridion MVP and Community Builders

2. For the latest on the PowerTools, visit: http://code.google.com/p/tridion-2011-power-tools/ Consider an SVN client like Tortoise See link to the group Site is open to the public For the latest on the PowerTools, visit: http://code.google.com/p/tridion-2011-power-tools/ Consider an SVN client like Tortoise See link to the group Site is open to the public Sept. 29 – Oct. 1, 2011Tridion Power Tools2

3. PowerTools Session Objectives Create a Compatible Power Tool “Framework” Make PowerTools compatible with SDL Tridion 2011, SP1, and future releases Develop Roadmap Create post-retreat product plan, chose code repository Deliver – Working PowerTool based on current APIs – Prioritized list based on importance and difficulty – Documentation template Sept. 29 – Oct. 1, 2011Tridion Power Tools3

4. Concern on Coding Style Distinction between coding style for: Focus on creating a working example, regardless of final approach. Consider examples of both. Teaching easy-to-understand easy-to-replicate Development refactored maintainable Sept. 29 – Oct. 1, 2011Tridion Power Tools4

5. Concern on Ownership Project visibility – Promote project – Encourage participation – Don’t wait for community involvement Open source preference Protect project from changes to individual contributors – Use personal email accounts – Be careful with employee intellectual property contract clauses and proprietary information – Protect SDL by focusing on “community” aspect (un-official tool outside of CS and PS support) Sept. 29 – Oct. 1, 2011Tridion Power Tools5

6. Compatibility Leverage Core Service Use new UI customization options – Show/hide based on permissions – Context menu – Ribbon Sept. 29 – Oct. 1, 2011Tridion Power Tools6

7. Project Roadmap Project Setup – Leads and Participants – Versioning via Google Code Project Product Management (Functional) Design and Change Management (Technical) Sept. 29 – Oct. 1, 2011Tridion Power Tools7

8. Project Setup Leads and Participants Leads – 3 MVP technical leads – 1 MVP functional lead Participants – 5-10 community contributors overall – 2-3 community contributors per tool – As many testers as are available Encourage participation, increase visibility (blog, tweet, forums) and keep an eye out for replacements for positions Sept. 29 – Oct. 1, 2011Tridion Power Tools8

9. Project Setup Versioning Chosen Solution – Using Chris Summer’s (Urban Cherry) Google Code Project – MVPs and CBs assigned as contributors Though a community-driven, the Power Tools project needs leads to guide project to completion. Leads should encourage participation but should work towards delivering functionality and not be held up by slow adoption. Sept. 29 – Oct. 1, 2011Tridion Power Tools9

10. Product Management lead by Functional Lead Functional lead for requirements, tool prioritization, and soliciting community feedback Requirements will come from old tool(s), lacking functionality in current product, and solicited feedback. Communicates bugs and issues and usefulness to SDL (informal via email, Ideas submissions) Managing acceptance criteria, categorizing tools Sept. 29 – Oct. 1, 2011Tridion Power Tools10

11. Design and Change Management by Technical Leads Lead by Technical leads Simple and informal process Project team should review individual tools at least twice a year. Consider scheduling a 6- month review at project onset. Sept. 29 – Oct. 1, 2011Tridion Power Tools11

12. Copyright and License Open source, specific license: GNU currently chosen (if not confirmed, deadline: 11/1/11 determined by discussion and consensus on Google Code Site) Other Options: – MIT – Standford – Berkeley – Other Assumption: Open Source “community-ware” Allow option for SDL to build functionality and code back into the product Add liability and disclaimers Sept. 29 – Oct. 1, 2011Tridion Power Tools12

13. SDL Tridion Power Tools Prioirty NameDescriptionAudience Suggested Location Original Author PriorityDifficultyStatusNotes Count Items Count items in a publication, folder or structure group All Context Menu on OrgItems Quirijn Slings HighEasy Needed more than ever as this is missing from the GUI Add User Add a user directly (from a domain or directory service) Power User Added to existing add user screen Quirijn Slings HighEasyCompleteCreated by Tory Show ListsShows the output of different Tridion XML Lists, with column and row filters DeveloperPowerTool Button on Ribbon Nuno Linhares MediumEasy See “official” list on Google Project. Priority is for “low hanging fruit” – easy yet high priority items. Sept. 29 – Oct. 1, 2011Tridion Power Tools13

14. PowerTools Session Objectives Create a Compatible Power Tool “Framework” Make PowerTools compatible with SDL Tridion 2011, SP1, and future releases Develop Roadmap Create post-retreat product plan, chose code repository Deliver – Working PowerTool based on current APIs – Prioritized list based on importance and difficulty – Documentation template Sept. 29 – Oct. 1, 2011Tridion Power Tools14

15. Next Steps Monthly meetings – on Skype (for both PowerTools) by Julian – let him know when and topic – (Webinars for MVP sharing with community) Assumption: meeting encourages collaboration Establish coding guidelines Create disclaimer language Have a working example by Oct. 15, 2011! (merge versions) Sept. 29 – Oct. 1, 2011Tridion Power Tools15