Rise and Fall and Rise of CDT

1,086 views
998 views

Published on

Goes through the history of the CDT and shares the lessons learned to help other projects.

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,086
On SlideShare
0
From Embeds
0
Number of Embeds
237
Actions
Shares
0
Downloads
30
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Welcome, I'm Doug Schaefer, the CDT Project Lead. I've been with the CDT project for almost seven years now.
  • Rise and Fall and Rise of CDT

    1. 1. The Rise and Fall and Rise of the CDT Project Lessons on Building Communities
    2. 2. The Rise and Fall and Rise and Fall and Rise and Fall and Something... of the CDT Project The Never Ending Exercise on Building Communities
    3. 3. The Epic History of the CDT
    4. 4. The Epic History of the CDT in 15 minutes...
    5. 5. In the beginning... “The Eclipse Tools PMC is pleased to announce some exciting developments to the CDT project hosted on eclipse.org. First, QNX will be contributing some C/C++ core technology from their recently announced product to eclipse.org.”
    6. 6. The First CDT Summit – June 2002
    7. 7. Doug gets involved and makes a mess: The CDT Indexer
    8. 8. The CDT 2.0 Summit Thanks for coming. Can you commit to helping? Anyone? Anyone?
    9. 9. The first EclipseCon CDT BOF: OMG, people are standing in the hall, and what's with all these build systems...
    10. 10. “For the good of the project I'll put in my +1. Unfortunately, however, we are going to start losing developers that are working full time on the CDT starting August 1. “
    11. 11. CDT Summit III You know all those things you care about? well, no one is working on them...
    12. 12. It works, the CDT contributor community grows. Intel, Nokia, Freescale, Texas Instruments, Symbian, Google, Ericsson, Broadcom, QNX, IBM, Wind River
    13. 13. Doug's Words of “Wisdom”
    14. 14. Prepare to be frustrated
    15. 15. Wear two hats
    16. 16. Be vendor neutral, Leverage “co-opetition”
    17. 17. Asking for contributions isn't enough Create the need
    18. 18. Meet face to face, build relationships
    19. 19. None of your committers will be full time
    20. 20. Code like you won't be there tomorrow
    21. 21. Be needy, but not too needy
    22. 22. Forks are bad, But they can be good
    23. 23. “Can Eclipse Survive without IBM?”
    24. 24. “Don't ship a product on x.x.0, wait for x.x.1”
    25. 25. Communicate, Communicate, Communicate and be honest, build trust
    26. 26. And, BTW, a little dumb ass luck goes a long way
    27. 27. Thank you!

    ×