Your SlideShare is downloading. ×
Focus Group Open Source 04.06.2012 Ryan Ozptek
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Focus Group Open Source 04.06.2012 Ryan Ozptek

848
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
848
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Welcome to Joomla! Ryan W. Ozimek June 4, 2012 - Rome, Italy Focus Group Open Source @cozimekTuesday, June 5, 12
  • 2. Buon pomeriggio, Roma! @cozimekTuesday, June 5, 12
  • 3. Who am I? @cozimekTuesday, June 5, 12
  • 4. Who am I? @cozimekTuesday, June 5, 12
  • 5. Who am I? @cozimek XTuesday, June 5, 12
  • 6. Who am I? @cozimekTuesday, June 5, 12
  • 7. Where am I from? @cozimekTuesday, June 5, 12
  • 8. Where am I from? @cozimekTuesday, June 5, 12
  • 9. Where am I from? @cozimekTuesday, June 5, 12
  • 10. Being president had its benefits @cozimekTuesday, June 5, 12
  • 11. Being president had its benefits @cozimekTuesday, June 5, 12
  • 12. Being president had its benefits @cozimekTuesday, June 5, 12
  • 13. Being president had its benefits @cozimekTuesday, June 5, 12
  • 14. Most importantly ... @cozimekTuesday, June 5, 12
  • 15. Sharing all the secrets! @cozimekTuesday, June 5, 12
  • 16. Time to pull back the curtains @cozimekTuesday, June 5, 12
  • 17. Before we begin... @cozimekTuesday, June 5, 12
  • 18. My core business value... > @cozimekTuesday, June 5, 12
  • 19. Yesterday’s innovators @cozimekTuesday, June 5, 12
  • 20. Today’s innovators @cozimekTuesday, June 5, 12
  • 21. We’re living in a changing world @cozimekTuesday, June 5, 12
  • 22. Joomla powers governments @cozimekTuesday, June 5, 12
  • 23. Joomla powers critical charities @cozimekTuesday, June 5, 12
  • 24. The social, public impact of OSS goes much further than bits and bytes @cozimekTuesday, June 5, 12
  • 25. What is Joomla? @cozimekTuesday, June 5, 12
  • 26. What is Joomla? @cozimekTuesday, June 5, 12
  • 27. The unique birth of a project @cozimekTuesday, June 5, 12
  • 28. The unique birth of a project @cozimekTuesday, June 5, 12
  • 29. Oh 2001... @cozimekTuesday, June 5, 12
  • 30. Open source patriots @cozimekTuesday, June 5, 12
  • 31. Declaration of independence @cozimekTuesday, June 5, 12
  • 32. My contribution @cozimekTuesday, June 5, 12
  • 33. 2 types of organizational leadership models @cozimekTuesday, June 5, 12
  • 34. Corporate model @cozimekTuesday, June 5, 12
  • 35. Benevolent dictator model @cozimekTuesday, June 5, 12
  • 36. Hippie model @cozimekTuesday, June 5, 12
  • 37. Power to the people @cozimekTuesday, June 5, 12
  • 38. A story of growth @cozimekTuesday, June 5, 12
  • 39. A story of growth @cozimekTuesday, June 5, 12
  • 40. Joomla, by the numbers 31,973,928 downloads @cozimekTuesday, June 5, 12
  • 41. Joomla, by the numbers 2,615,968 forum posts @cozimekTuesday, June 5, 12
  • 42. Joomla, by the numbers @cozimekTuesday, June 5, 12
  • 43. Joomla, by the numbers 563,674 users @cozimekTuesday, June 5, 12
  • 44. Joomla, by the numbers 187x @cozimekTuesday, June 5, 12
  • 45. Joomla, by the numbers 2.7% of the Web @cozimekTuesday, June 5, 12
  • 46. Large enterprise support, users @cozimekTuesday, June 5, 12
  • 47. Large enterprise support, users @cozimekTuesday, June 5, 12
  • 48. Joomla’s evolution @cozimekTuesday, June 5, 12
  • 49. What makes Joomla different? @cozimekTuesday, June 5, 12
  • 50. What makes Joomla different? Framework @cozimekTuesday, June 5, 12
  • 51. What makes Joomla different? Framework @cozimekTuesday, June 5, 12
  • 52. Very excited developers @cozimekTuesday, June 5, 12
  • 53. A new toolset @cozimekTuesday, June 5, 12
  • 54. Publishing tweets from a CLI @cozimekTuesday, June 5, 12
  • 55. Publishing tweets from a CLI @cozimekTuesday, June 5, 12
  • 56. Build new extensions faster @cozimekTuesday, June 5, 12
  • 57. Export site to HTML @cozimekTuesday, June 5, 12
  • 58. How does this apply to us? @cozimekTuesday, June 5, 12
  • 59. Why e-gov is important to me @cozimekTuesday, June 5, 12
  • 60. Why e-gov is important to me • This meets a key function of Joomla: communications liberation for everyone @cozimekTuesday, June 5, 12
  • 61. Why e-gov is important to me • This meets a key function of Joomla: communications liberation for everyone • Increasing transparency, empowerment, and accountability @cozimekTuesday, June 5, 12
  • 62. A tough topic to pin down • Talking about what is good for e-Government is similar to asking “what’s good for businesses?” or “what’s good for charities?” @cozimekTuesday, June 5, 12
  • 63. A case study in US gov @cozimekTuesday, June 5, 12
  • 64. A case study in US gov @cozimekTuesday, June 5, 12
  • 65. A case study in US gov • ASP … @cozimekTuesday, June 5, 12
  • 66. A case study in US gov • ASP … • …not .NET but… @cozimekTuesday, June 5, 12
  • 67. A case study in US gov • ASP … • …not .NET but… • ASP Classic @cozimekTuesday, June 5, 12
  • 68. A case study in US gov @cozimekTuesday, June 5, 12
  • 69. A case study in US gov • The challenge of working with another department for all technology needs @cozimekTuesday, June 5, 12
  • 70. A case study in US gov • The challenge of working with another department for all technology needs • Technology was old, and not keeping up with the modern tools @cozimekTuesday, June 5, 12
  • 71. A case study in US gov • The challenge of working with another department for all technology needs • Technology was old, and not keeping up with the modern tools • Direct access to the technology was difficult for House offices @cozimekTuesday, June 5, 12
  • 72. A case study in US gov @cozimekTuesday, June 5, 12
  • 73. A case study in US gov • The key purpose of the websites are to encourage the transparency and accountability of the US federal government, but… @cozimekTuesday, June 5, 12
  • 74. A case study in US gov • The key purpose of the websites are to encourage the transparency and accountability of the US federal government, but… • It simply wasn’t able to keep up with the needs of the offices @cozimekTuesday, June 5, 12
  • 75. A case study in US gov • The key purpose of the websites are to encourage the transparency and accountability of the US federal government, but… • It simply wasn’t able to keep up with the needs of the offices • Campaigns had more modern tools than the offices themselves @cozimekTuesday, June 5, 12
  • 76. A case study in US gov @cozimekTuesday, June 5, 12
  • 77. A case study in US gov • If offices chose to keep up with the times, they needed to go find their own consultants @cozimekTuesday, June 5, 12
  • 78. A case study in US gov • If offices chose to keep up with the times, they needed to go find their own consultants • But…consultants needed to have their own servers in the House @cozimekTuesday, June 5, 12
  • 79. A case study in US gov • If offices chose to keep up with the times, they needed to go find their own consultants • But…consultants needed to have their own servers in the House • Therefore, the barriers to entry and innovation were very high @cozimekTuesday, June 5, 12
  • 80. A case study in US gov @cozimekTuesday, June 5, 12
  • 81. A case study in US gov • So at first, we played the game… @cozimekTuesday, June 5, 12
  • 82. A case study in US gov • So at first, we played the game… • …and used proprietary software @cozimekTuesday, June 5, 12
  • 83. A case study in US gov • So at first, we played the game… • …and used proprietary software • …and tried to get along with ASP @cozimekTuesday, June 5, 12
  • 84. A case study in US gov • So at first, we played the game… • …and used proprietary software • …and tried to get along with ASP • …but we weren’t very happy with the process @cozimekTuesday, June 5, 12
  • 85. A case study in US gov @cozimekTuesday, June 5, 12
  • 86. A case study in US gov @cozimekTuesday, June 5, 12
  • 87. A case study in US gov @cozimekTuesday, June 5, 12
  • 88. A case study in US gov • Reasons to use a standardized CMS like Joomla for the House @cozimekTuesday, June 5, 12
  • 89. A case study in US gov • Reasons to use a standardized CMS like Joomla for the House • High staff turnover @cozimekTuesday, June 5, 12
  • 90. A case study in US gov • Reasons to use a standardized CMS like Joomla for the House • High staff turnover • Lower barriers to entry for staffers @cozimekTuesday, June 5, 12
  • 91. A case study in US gov • Reasons to use a standardized CMS like Joomla for the House • High staff turnover • Lower barriers to entry for staffers • More direct access to technology available during their campaigns @cozimekTuesday, June 5, 12
  • 92. A case study in US gov • Reasons to use a standardized CMS like Joomla for the House • High staff turnover • Lower barriers to entry for staffers • More direct access to technology available during their campaigns • Ability to integrate with CRM services @cozimekTuesday, June 5, 12
  • 93. A case study in US gov • Reasons to use a standardized CMS like Joomla for the House • High staff turnover • Lower barriers to entry for staffers • More direct access to technology available during their campaigns • Ability to integrate with CRM services • Ability to manage custom Web services @cozimekTuesday, June 5, 12
  • 94. A case study in US gov @cozimekTuesday, June 5, 12
  • 95. A case study in US gov • At its peak, 1/4th of US Congress was running Joomla! @cozimekTuesday, June 5, 12
  • 96. A case study in US gov • At its peak, 1/4th of US Congress was running Joomla! • Now, 9 years later, PHP and MySQL are the based standards of the US Congress House of Representatives @cozimekTuesday, June 5, 12
  • 97. Let’s go global! @cozimekTuesday, June 5, 12
  • 98. The #joomla-in-gov project @cozimekTuesday, June 5, 12
  • 99. The #joomla-in-gov project • Started off with a personal frustration from a conference • …a tweet from an airport • …a few excited community members • …a wiki page • …and then, a little love from South Africa @cozimekTuesday, June 5, 12
  • 100. The #joomla-in-gov project @cozimekTuesday, June 5, 12
  • 101. The #joomla-in-gov project @cozimekTuesday, June 5, 12
  • 102. The #joomla-in-gov project @cozimekTuesday, June 5, 12
  • 103. Joomla in Italy @cozimekTuesday, June 5, 12
  • 104. Joomla in Italy @cozimekTuesday, June 5, 12
  • 105. Alessandro Rossi @cozimekTuesday, June 5, 12
  • 106. Joomla in Italy, by the numbers 716,070 forum posts @cozimekTuesday, June 5, 12
  • 107. Joomla in Italy, by the numbers 61,416 registered users @cozimekTuesday, June 5, 12
  • 108. Joomla in Italy, by the numbers 20x @cozimekTuesday, June 5, 12
  • 109. Benefits of using Joomla in gov @cozimekTuesday, June 5, 12
  • 110. Benefits of using Joomla in gov • Lowering costs @cozimekTuesday, June 5, 12
  • 111. Benefits of using Joomla in gov • Lowering costs • Difficult financial times @cozimekTuesday, June 5, 12
  • 112. Benefits of using Joomla in gov • Lowering costs • Difficult financial times • Complies with government mandates @cozimekTuesday, June 5, 12
  • 113. Benefits of using Joomla in gov • Lowering costs • Difficult financial times • Complies with government mandates • With Joomla 2.5, it works with existing databases @cozimekTuesday, June 5, 12
  • 114. Benefits of using Joomla in gov • Lowering costs • Difficult financial times • Complies with government mandates • With Joomla 2.5, it works with existing databases • Alternative to “the cloud” if needed by agencies @cozimekTuesday, June 5, 12
  • 115. Benefits of using Joomla in gov @cozimekTuesday, June 5, 12
  • 116. Benefits of using Joomla in gov • Standardized around the world @cozimekTuesday, June 5, 12
  • 117. Benefits of using Joomla in gov • Standardized around the world • Gov can capitalize on worldwide existing education @cozimekTuesday, June 5, 12
  • 118. Benefits of using Joomla in gov • Standardized around the world • Gov can capitalize on worldwide existing education • Localization possible @cozimekTuesday, June 5, 12
  • 119. Benefits of using Joomla in gov • Standardized around the world • Gov can capitalize on worldwide existing education • Localization possible • Language replacement easy @cozimekTuesday, June 5, 12
  • 120. Benefits of using Joomla in gov • Standardized around the world • Gov can capitalize on worldwide existing education • Localization possible • Language replacement easy • Lower barriers to entry for content creators @cozimekTuesday, June 5, 12
  • 121. Benefits of using Joomla in gov • Standardized around the world • Gov can capitalize on worldwide existing education • Localization possible • Language replacement easy • Lower barriers to entry for content creators • Increases government’s transparency and accountability @cozimekTuesday, June 5, 12
  • 122. Benefits of using Joomla in gov @cozimekTuesday, June 5, 12
  • 123. Benefits of using Joomla in gov • Procurement processes @cozimekTuesday, June 5, 12
  • 124. Benefits of using Joomla in gov • Procurement processes • Rarely fun, often long and tedious @cozimekTuesday, June 5, 12
  • 125. Benefits of using Joomla in gov • Procurement processes • Rarely fun, often long and tedious • US government’s GSA schedule @cozimekTuesday, June 5, 12
  • 126. Benefits of using Joomla in gov • Procurement processes • Rarely fun, often long and tedious • US government’s GSA schedule • Potential restrictions on content population of websites @cozimekTuesday, June 5, 12
  • 127. Benefits of using Joomla in gov • Procurement processes • Rarely fun, often long and tedious • US government’s GSA schedule • Potential restrictions on content population of websites • Security, infrastructure protection, gov guidelines @cozimekTuesday, June 5, 12
  • 128. Benefits of using Joomla in gov • Procurement processes • Rarely fun, often long and tedious • US government’s GSA schedule • Potential restrictions on content population of websites • Security, infrastructure protection, gov guidelines • Compliance for accessibility @cozimekTuesday, June 5, 12
  • 129. Benefits of using Joomla in gov • Procurement processes • Rarely fun, often long and tedious • US government’s GSA schedule • Potential restrictions on content population of websites • Security, infrastructure protection, gov guidelines • Compliance for accessibility • US government’s ADA Section 508 @cozimekTuesday, June 5, 12
  • 130. Benefits of using Joomla in gov @cozimekTuesday, June 5, 12
  • 131. Benefits of using Joomla in gov • Existing infrastructure challenge @cozimekTuesday, June 5, 12
  • 132. Benefits of using Joomla in gov • Existing infrastructure challenge • You often need to use the hardware and technology you’re given @cozimekTuesday, June 5, 12
  • 133. Benefits of using Joomla in gov • Existing infrastructure challenge • You often need to use the hardware and technology you’re given • Diverse audience of site visitors @cozimekTuesday, June 5, 12
  • 134. Benefits of using Joomla in gov • Existing infrastructure challenge • You often need to use the hardware and technology you’re given • Diverse audience of site visitors • Lowest common denominator (bandwidth, tech) @cozimekTuesday, June 5, 12
  • 135. Benefits of using Joomla in gov • Existing infrastructure challenge • You often need to use the hardware and technology you’re given • Diverse audience of site visitors • Lowest common denominator (bandwidth, tech) • Content challenges with diversity @cozimekTuesday, June 5, 12
  • 136. Benefits of using Joomla in gov • Existing infrastructure challenge • You often need to use the hardware and technology you’re given • Diverse audience of site visitors • Lowest common denominator (bandwidth, tech) • Content challenges with diversity • More local = more feedback needed @cozimekTuesday, June 5, 12
  • 137. Benefits of using Joomla in gov • Existing infrastructure challenge • You often need to use the hardware and technology you’re given • Diverse audience of site visitors • Lowest common denominator (bandwidth, tech) • Content challenges with diversity • More local = more feedback needed • More specific = more feedback needed @cozimekTuesday, June 5, 12
  • 138. Things to keep in mind @cozimekTuesday, June 5, 12
  • 139. Things to keep in mind • Audience of Joomla government users @cozimekTuesday, June 5, 12
  • 140. Things to keep in mind • Audience of Joomla government users • Staff members carry diverse roles @cozimekTuesday, June 5, 12
  • 141. Things to keep in mind • Audience of Joomla government users • Staff members carry diverse roles • US House staff @cozimekTuesday, June 5, 12
  • 142. Things to keep in mind • Audience of Joomla government users • Staff members carry diverse roles • US House staff • Time to focus on website content is often shorter than that in the corporate world @cozimekTuesday, June 5, 12
  • 143. Things to keep in mind • Audience of Joomla government users • Staff members carry diverse roles • US House staff • Time to focus on website content is often shorter than that in the corporate world • Turn-over is high, education needs to be easy and learning curve as flat as possible @cozimekTuesday, June 5, 12
  • 144. Best practices @cozimekTuesday, June 5, 12
  • 145. Best practices • Have a back-up and disaster recovery plan @cozimekTuesday, June 5, 12
  • 146. Best practices • Have a back-up and disaster recovery plan • Useful monitoring systems, like Nagios @cozimekTuesday, June 5, 12
  • 147. Best practices • Have a back-up and disaster recovery plan • Useful monitoring systems, like Nagios • Increased levels of security @cozimekTuesday, June 5, 12
  • 148. Best practices • Have a back-up and disaster recovery plan • Useful monitoring systems, like Nagios • Increased levels of security • Preparing for high site traffic, with unexpected peaks and valleys @cozimekTuesday, June 5, 12
  • 149. Best practices • Have a back-up and disaster recovery plan • Useful monitoring systems, like Nagios • Increased levels of security • Preparing for high site traffic, with unexpected peaks and valleys • Coding for the lowest common denominator @cozimekTuesday, June 5, 12
  • 150. Best practices @cozimekTuesday, June 5, 12
  • 151. Best practices • Multi-server strategy @cozimekTuesday, June 5, 12
  • 152. Best practices • Multi-server strategy • Development @cozimekTuesday, June 5, 12
  • 153. Best practices • Multi-server strategy • Development • Testing/Staging @cozimekTuesday, June 5, 12
  • 154. Best practices • Multi-server strategy • Development • Testing/Staging • Production @cozimekTuesday, June 5, 12
  • 155. Best practices • Multi-server strategy • Development • Testing/Staging • Production • Build for the long-term…the very long-term @cozimekTuesday, June 5, 12
  • 156. Best practices • Multi-server strategy • Development • Testing/Staging • Production • Build for the long-term…the very long-term • Create long-term support plans @cozimekTuesday, June 5, 12
  • 157. Best practices @cozimekTuesday, June 5, 12
  • 158. Best practices • Focus early on integration opportunities, a key differentiator @cozimekTuesday, June 5, 12
  • 159. Best practices • Focus early on integration opportunities, a key differentiator • Examples from US House @cozimekTuesday, June 5, 12
  • 160. Best practices • Focus early on integration opportunities, a key differentiator • Examples from US House • Flag requests @cozimekTuesday, June 5, 12
  • 161. Best practices • Focus early on integration opportunities, a key differentiator • Examples from US House • Flag requests • CRM services @cozimekTuesday, June 5, 12
  • 162. Best practices • Focus early on integration opportunities, a key differentiator • Examples from US House • Flag requests • CRM services • External Web services @cozimekTuesday, June 5, 12
  • 163. Best practices • Focus early on integration opportunities, a key differentiator • Examples from US House • Flag requests • CRM services • External Web services • Multi-lingual requirements @cozimekTuesday, June 5, 12
  • 164. Best practices • Get involved or start an open source or Joomla government community • Example from the USA: www.govloop.com @cozimekTuesday, June 5, 12
  • 165. Best practices @cozimekTuesday, June 5, 12
  • 166. Best practices @cozimekTuesday, June 5, 12
  • 167. Best practices • Most importantly: Increase transparency and value to constituents wherever possible @cozimekTuesday, June 5, 12
  • 168. Best practices • Most importantly: Increase transparency and value to constituents wherever possible • Be innovative @cozimekTuesday, June 5, 12
  • 169. Best practices • Most importantly: Increase transparency and value to constituents wherever possible • Be innovative • Build mashups @cozimekTuesday, June 5, 12
  • 170. Best practices • Most importantly: Increase transparency and value to constituents wherever possible • Be innovative • Build mashups • Create new data sets @cozimekTuesday, June 5, 12
  • 171. Best practices • Most importantly: Increase transparency and value to constituents wherever possible • Be innovative • Build mashups • Create new data sets • Layer mapping technology @cozimekTuesday, June 5, 12
  • 172. SeeClickFix.com @cozimekTuesday, June 5, 12
  • 173. SeeClickFix.com @cozimekTuesday, June 5, 12
  • 174. President’s State of the Union @cozimekTuesday, June 5, 12
  • 175. Things to watch out for @cozimekTuesday, June 5, 12
  • 176. Things to watch out for • Slow moving projects due to inherent consensus decision making process in government @cozimekTuesday, June 5, 12
  • 177. Things to watch out for • Slow moving projects due to inherent consensus decision making process in government • Change orders that seem to come from nowhere @cozimekTuesday, June 5, 12
  • 178. Things to watch out for • Slow moving projects due to inherent consensus decision making process in government • Change orders that seem to come from nowhere • Understanding the payment process of the government agency you’re working with @cozimekTuesday, June 5, 12
  • 179. Things to watch out for @cozimekTuesday, June 5, 12
  • 180. Things to watch out for • Clearly understand your main point of contact for billing, technology, and sign-off @cozimekTuesday, June 5, 12
  • 181. Things to watch out for • Clearly understand your main point of contact for billing, technology, and sign-off • Domain names can be difficult to receive, so get them early @cozimekTuesday, June 5, 12
  • 182. Things to watch out for • Clearly understand your main point of contact for billing, technology, and sign-off • Domain names can be difficult to receive, so get them early • Realize that community developed tools might not fit the requirements of government agencies, be ready to change @cozimekTuesday, June 5, 12
  • 183. Grazie FGOS! @cozimekTuesday, June 5, 12
  • 184. Questions? @cozimekTuesday, June 5, 12
  • 185. Feel free to contact me! Ryan Ozimek PICnet Twitter: @cozimek cozimek@picnet.net @cozimekTuesday, June 5, 12