Webcast So C 2009, Why Community Matters

769 views
691 views

Published on

Webcast for the Summer of Code 2009 participants, explaining why cummunity matters, and sharing some personal expierences from past years Summer of Code editions

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
769
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This keynote is about Joomla, the concept of “All together”What has been achieved by Joomla! only could be done with an active communityUsing the FOSS philosophy that is materialized by the GPLEnabling people to work together, with full freedom of choiceFreedom in de following context:Freedom to use the software (or not)Freedom to collaborate (or not)Freedom to make money (or not)Freedom to changeFreedom to shareFreedom to contributeFreedom to ...<number>
  • Webcast So C 2009, Why Community Matters

    1. 1. The Joomla! project Why community matters! Webcast Summer Of Code 2009 Wilco Jansen May 22, 2009
    2. 2. What are we going to talk about? 2
    3. 3. What are we going to talk about? A project like Joomla can only be achieved with an active community, in case of Joomla! the FOSS philosophy is used and the project materialized by the GPL
    4. 4. The beginning… 4
    5. 5. On 31 August 2005 5
    6. 6. On 27 April 2009 6
    7. 7. User Groups Around the world 7
    8. 8. To boldly go where no one has gone before? • 4.640.631 visitors and 24.235.484 page hits past month • 1.611.740 posts, 360.683 topics and 276.761 users in our forum • Almost 10.000.000 download • 82.000 registered developers and 2.255 registered projects on Joomlacode • 4.688 registered (active) projects on our extensions site • 60+ supported languages
    9. 9. To boldly go where no one has gone before?
    10. 10. To boldly go where no one has gone before? 10
    11. 11. The key for the growth of Joomla! 11
    12. 12. The licence 12
    13. 13. Community 13
    14. 14. Leadership
    15. 15. “All together”
    16. 16. 16
    17. 17. The Summer of Code link
    18. 18. 5th year Google Summer of Code 2005 – 6 projects 2006 – 8 projects 2007 – 10 projects 2008 – 15 projects and...
    19. 19. 18 projects accepted!
    20. 20. Lessons learned (mentor version) • Let the student make a plan before start • Talk every week on work at hand, and work planned next week, keep a constant eye on the schedule • As mid-term approached (6-12 July), make sure coding starts in time (23 May according to Google, but start earlier on if possible! • Summer hollidays are parallel with SoC...students will dissapear, and re-emerge! • No code during mid-term = 100% failure in the end • An active way motivating involvement is to let the students actively blog • The ambition level of every project so far has proven to be to high, accept lesser work completed, better some stages finished well then have nothing in the end • Some students are new to open source, make sure they understand the do's and don't in FOSS projects • Always remember this should be a learning expierence by students!
    21. 21. Lessons learned (student version) • Plan first, then act! See also mentor remarks • Handle SoC as a full time job, you are getting payed ;-) • Time needed to complete code is always short, start soon and set reasonable milestones • You mentor is there to help, use their knowledge! • Use the tools provided to interact with other mentors and students (Skype chat is a good source) • No code = fail mid/end-term, no code at mid-term is also fail, make sure to start coding and go through the results at least once per 2 weeks with your mentor • Learn from others, there are plenty of examples out there • If you use work from others, make sure you add a comment

    ×