Your SlideShare is downloading. ×
  • Like
Contribute to Eclipse projects
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Contribute to Eclipse projects


This presentation give hints on How to become a contributor on Eclipse projects.

This presentation give hints on How to become a contributor on Eclipse projects.

Published in Technology , Sports
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On SlideShare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. How to contribute to Eclipse projects? Mickael Istria - EclipseDay Grenoble 2013 @mickaelistria
  • 2. Which project(s) to contribute to? ● Any project that: – You like and want to get involved in, – You use or depend on and want to keep good/make better, – Which makes sense in your strategy
  • 3. What form can a contribution have? ● Documentation ● User support ● Bug reports ● Suggestion of improvements, based use-cases ≠ “Hey, that sucks!”, “it's retarded”, “WTF?” ● Code
  • 4. Contribute through the right media: The taxi analogy Want to get into a project? 1. Be where it expects you. 2. Make sure they notice you if you want to get into it!
  • 5. Contribute through the right media IRC
  • 6. Choose the right media[project]-dev
  • 7. Should I open a bug or not? In case of doubt, DO IT ! Don't be shy. - Your idea may be the best idea ever submitted - Opening a bug doesn't hurt, doesn't cost, isn't bad - Being wrong doesn't hurt and cost (not knowing you're wrong cost you time/money/happiness)
  • 8. About criticity Young Lady or Old Hag? Criticity is not objective. It depends on you, your project, your stategy... Other contributors may not share your concerns.
  • 9. Don't expect people to do things for you (There is no fun image to illustrate slavery.) You can wish, hope, negociate, buy, lobby,... but not require people to work on your use-case.
  • 10. Obvious good ideas & good pieces of code In most cases, your idea will be easily approved, and your contribution quickly merged into code-base. Some other contributors might even like your idea so much that they'll turn it into code without more effort on your side!
  • 11. Discutable ideas That's the most difficult part: discuss, argue, justify your idea is good. In such cases, it's good to provide some things to demo.
  • 12. What to do where? ● Help users on Eclipse forums ● Write doc on Eclipse wiki ● Tell developers you write doc on Eclipse mailing-list ● Submit bugs via Eclipse Bugzilla ● Submit suggestions via Eclipse Bugzilla ● Discuss your ideas on Eclipse Bugzilla ● Provide code on Eclipse Gerrit Committers will assist you in integrating stuff into the project.
  • 13. Bugzilla is the heart of the contribution process, where most insteresting discussions take place.
  • 14. Follow a project ● ● ● Follow mailing-list Follow user on Bugzilla:, under “User Watching” Follow Gerrit reviews for the project:
  • 15. Weigh in the project ● ● Give your opinion on mailing-list, Bugzilla entries and Gerrit reviews (that you're now all following) Write code and contribute it via Gerrit.
  • 16. Quick note about Gerrit ● Empowering reviews: – – Ease discussion about (important) details – Ease collaboration – ● Ease technical discussions with better tool Ease knowledge transfer Gives some hints and instructions including: – Necessary Git Hooks – CLA approval – Useful Git commands (CLI and EGit)
  • 17. Quick demo: A bug lifecycle with Bugzilla and Gerrit