Jump to: navigation, search

Difference between revisions of "Getting Involved with the Community"

(Attend and Connect)
 
(13 intermediate revisions by 9 users not shown)
Line 1: Line 1:
===Getting involved with the community===
+
As an Eclipse user or developer, your first (and best) way to get involved with the community is to use the Eclipse IDE for your development and explore what the many [http://www.eclipse.org/projects/listofprojects.php Eclipse projects] have to offer you. Let your interest areas guide you towards the projects that you find most interesting.
  
As a developer, your first (and best) way to get involved with the community is to use the Eclipse IDE for your development and explore what the many Eclipse projects have to offer you and your fellow developers. Let your interest areas guide you: if you're interested in modeling and visual editing, consider the [http://eclipse.org/emf Eclipse Metadata Framework (EMF)], [http://eclipse.org/gef Graphical Editing Framework (GEF)], and [http://eclipse.org/gmf Graphical Modeling Framework (GMF)] projects; if you need to generate reports, consider the [http://eclipse.org/birt Business Intelligence Reporting Tools (BIRT)] project. There are many projects; as you get more familiar with the community you'll develop a natural tendency to explore them all.
+
Don't wait too long to get directly involved with the community. Here are some suggestions on ways to participate. Feel free to add your own ideas to the list.
  
Don't wait too long to get directly involved with the community. The "newbie" [news://news.eclipse.org/eclipse.newcomer news group] is monitored by seasoned Eclipse users and developers who are happy to answer your questions. Be sure to read "[http://www.catb.org/%7Eesr/faqs/smart-questions.html How to Ask Questions The Smart Way]" by Eric Raymond and Rick Moen before you post; well formed questions tend to be answered while poorly worded ones are not. If you want to keep track of conversations occuring with the Eclipse community (primarily between developers), consider adding yourself to one or more [http://www.eclipse.org/mail/ mailing list]. Each project has its own mailing list. Some mailing lists (like [https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev cross-project-issues-dev]) span projects and are a good source of information concerning the integration of the various projects.
+
==Communicate==
  
Perhaps your most valuable resource as a member of the Eclipse community is [https://bugs.eclipse.org/bugs/ Bugzilla]. Bugzilla is your main interface to the developers; it is how you contribute directly to projects. As the name implies, Bugzilla is primarily used to report bugs. But it's used for more. You can request new features and even pose questions through Bugzilla (though questions are probably better suited for the news group). Be sure to read [http://www.chiark.greenend.org.uk/%7Esgtatham/bugs.html How to Report Bugs Effectively].
+
*Ask questions in the [http://www.eclipse.org/forums/index.php?t=thread&frm_id=89&S=1db1efea1e722a0831f5b49b8e0fd8dc newcomer forum]. The forum is monitored by seasoned Eclipse users and developers who are happy to answer your questions.
 +
**Be sure to read "[http://www.catb.org/%7Eesr/faqs/smart-questions.html How To Ask Questions The Smart Way]" by Eric Raymond and Rick Moen before you post.
 +
**Well formed questions tend to be answered while poorly worded ones are not.
 +
 +
*Contribute to conversations occurring within the Eclipse community (primarily between developers) by adding yourself to one or more [http://www.eclipse.org/mail/index_all.php mailing lists]. Each project has its own mailing list and there are some lists (like [https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev cross-project-issues-dev]) that span projects and provide a good source of information concerning the integration of various projects.
  
If you want to keep informed about the progress of bugs through the system, you can register (by configuring "User Watching") to be notified when a bug is created or modified. This is a great way to be a "fly on the wall" as bugs are worked through the system. You can learn about the process while you learn about Eclipse just by watching these notes.
+
*Use [[IRC]] channels related to Eclipse to discuss Eclipse-related technologies, chat with the developers of Eclipse and ask questions.
 +
 
 +
*Participate in Eclipse's social media groups:
 +
**[http://www.facebook.com/#!/pages/Eclipse/259655700571 Facebook]
 +
**[http://www.linkedin.com/groups?mostPopular=&gid=36807 LinkedIn]
 +
**Twitter #eclipse
 +
**[https://www.xing.com/net/pric45b99x/eclipsefoundation/ Xing]
 +
 
 +
*Give your opinions and share advice by adding your Eclipse-related blog to [http://www.planeteclipse.org Planet Eclipse].
 +
 
 +
*Tell people about the Eclipse solutions you like best by favourite-ing them and posting reviews on [http://marketplace.eclipse.org Eclipse Marketplace].
 +
 
 +
*Rate and comment on the demos, podcasts, videos and webinar resources listed on [http://live.eclipse.org/ Eclipse Live].
 +
 
 +
==Suggest Improvements==
 +
 
 +
*File bugs, request new features and pose questions through [https://bugs.eclipse.org/bugs/ Bugzilla].
 +
**Be sure to read [http://www.chiark.greenend.org.uk/%7Esgtatham/bugs.html How to Report Bugs Effectively] by Simon Tatham (or at least the short [https://bugs.eclipse.org/bugs/page.cgi?id=bug-writing.html Bug Writing Guidelines]).
 +
**If you want to keep informed about the progress of bugs through the system, you can register (by configuring "User Watching" in the [https://bugs.eclipse.org/bugs/docs/html/userpreferences.html#emailsettings Email Settings]) to be notified when a bug is created or modified. This is a great way to be a "fly on the wall" as bugs are worked through the system. You can learn about the process while you learn about Eclipse just by watching these notes.
 +
 
 +
==Contribute Patches==
 +
 
 +
The easiest way to contribute code to a project is to provide a patch for a bug.
 +
 
 +
* Bugs marked [https://bugs.eclipse.org/bugs/buglist.cgi?keywords=helpwanted%2C%20bugday%2C%20;query_format=advanced;keywords_type=allwords;list_id=1935335;bug_status=NEW;bug_status=REOPENED "helpwanted" or "bugday"] are a good starting point ("bugday" bugs are oftentimes relatively easy ones to fix)
 +
 
 +
It's a good idea to communicate with a project that you intend to work with. If you need help getting started, or sorting out a problem, ask. [http://www.eclipse.org/projects/listofprojects.php All projects] have a website that will provide you with contact information. All project communication is done transparently through mailing lists or Bugzilla.
 +
 
 +
Bigger contributions, including entirely functionality, may be welcome as well. It's a generally good idea to communicate with the project before you put too much effort into a large contribution to ensure that the contribution fits in with the scope and plan of the project.
 +
 
 +
==Create==
 +
 
 +
*Create demos and how-to resources on Eclipse like videos, podcasts and webinars and post them to [http://live.eclipse.org/ Eclipse Live].
 +
 
 +
*Start your own project on [http://code.google.com/a/eclipselabs.org Eclipse Labs]. Eclipse Labs provides the infrastructure services typically required by open source projects, such as code repositories, bug tracking and project web sites and is hosted by Google. The projects here are not hosted by the Eclipse Foundation and do not have to follow the Eclipse Foundation development and intellectual property policies. It's an ideal place to work on experimental, niche and early stage projects. 
 +
 
 +
*Eclipse Projects always need help with documentation. Once you're familiar enough with a project, contribute pages to the [http://wiki.eclipse.org Eclipse wiki].
 +
 
 +
*It's great when people help by reporting bugs, but it's even better when they create patches to fix them!  You can submit your fix via [https://bugs.eclipse.org/bugs/ Bugzilla].
 +
 
 +
==Attend and Connect==
 +
If you are just interested in learning more, demo-ing, networking and meeting others in the community, there's a good deal of events for you.
 +
 
 +
* Participate in the [http://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014 Eclipse Demo Camps]. Learn from the demos or demo your own code. Or organize a demo camp and invite others.
 +
* Check for [http://wiki.eclipse.org/Eclipse_Day Eclipse Days] organized in your geography.
 +
* Attend the Eclipse Foundation's conferences in North America and Europe. Learn and network, or become a speaker.
 +
 
 +
Up-to-date information about all events is available at [http://events.eclipse.org events.eclipse.org]
 +
 
 +
==Evangelize==
 +
 
 +
*Start or participate in a [http://wiki.eclipse.org/Regional_Communities Regional Eclipse Community] group with others in your local area.  Regional Eclipse Communities allow people to meet in person and discuss topics of particular interest in your area.  RECs are a great way to collaborate in your native language.
 +
 
 +
*Sign up for a local IT event in your area and give a presentation on Eclipse.
 +
 
 +
*Tell your friends about Eclipse and help us spread the word!
 +
 
 +
==Miscellaneous==
 +
 
 +
*Become a [http://eclipse.org/donate/ Friend of Eclipse] by donating financially.  Donations are used to provide services for the Eclipse community, like providing more bandwidth for users and committers, purchasing additional servers to host Eclipse projects, sending students to EclipseCon and sponsoring Eclipse community events.
 +
 
 +
*Help translate Eclipse into other languages through the [https://babel.eclipse.org/babel/ Babel project].
 +
 
 +
[[Category:How to Contribute]]

Latest revision as of 23:44, 25 February 2014

As an Eclipse user or developer, your first (and best) way to get involved with the community is to use the Eclipse IDE for your development and explore what the many Eclipse projects have to offer you. Let your interest areas guide you towards the projects that you find most interesting.

Don't wait too long to get directly involved with the community. Here are some suggestions on ways to participate. Feel free to add your own ideas to the list.

Communicate

  • Ask questions in the newcomer forum. The forum is monitored by seasoned Eclipse users and developers who are happy to answer your questions.
    • Be sure to read "How To Ask Questions The Smart Way" by Eric Raymond and Rick Moen before you post.
    • Well formed questions tend to be answered while poorly worded ones are not.
  • Contribute to conversations occurring within the Eclipse community (primarily between developers) by adding yourself to one or more mailing lists. Each project has its own mailing list and there are some lists (like cross-project-issues-dev) that span projects and provide a good source of information concerning the integration of various projects.
  • Use IRC channels related to Eclipse to discuss Eclipse-related technologies, chat with the developers of Eclipse and ask questions.
  • Give your opinions and share advice by adding your Eclipse-related blog to Planet Eclipse.
  • Tell people about the Eclipse solutions you like best by favourite-ing them and posting reviews on Eclipse Marketplace.
  • Rate and comment on the demos, podcasts, videos and webinar resources listed on Eclipse Live.

Suggest Improvements

  • File bugs, request new features and pose questions through Bugzilla.
    • Be sure to read How to Report Bugs Effectively by Simon Tatham (or at least the short Bug Writing Guidelines).
    • If you want to keep informed about the progress of bugs through the system, you can register (by configuring "User Watching" in the Email Settings) to be notified when a bug is created or modified. This is a great way to be a "fly on the wall" as bugs are worked through the system. You can learn about the process while you learn about Eclipse just by watching these notes.

Contribute Patches

The easiest way to contribute code to a project is to provide a patch for a bug.

  • Bugs marked "helpwanted" or "bugday" are a good starting point ("bugday" bugs are oftentimes relatively easy ones to fix)

It's a good idea to communicate with a project that you intend to work with. If you need help getting started, or sorting out a problem, ask. All projects have a website that will provide you with contact information. All project communication is done transparently through mailing lists or Bugzilla.

Bigger contributions, including entirely functionality, may be welcome as well. It's a generally good idea to communicate with the project before you put too much effort into a large contribution to ensure that the contribution fits in with the scope and plan of the project.

Create

  • Create demos and how-to resources on Eclipse like videos, podcasts and webinars and post them to Eclipse Live.
  • Start your own project on Eclipse Labs. Eclipse Labs provides the infrastructure services typically required by open source projects, such as code repositories, bug tracking and project web sites and is hosted by Google. The projects here are not hosted by the Eclipse Foundation and do not have to follow the Eclipse Foundation development and intellectual property policies. It's an ideal place to work on experimental, niche and early stage projects.
  • Eclipse Projects always need help with documentation. Once you're familiar enough with a project, contribute pages to the Eclipse wiki.
  • It's great when people help by reporting bugs, but it's even better when they create patches to fix them! You can submit your fix via Bugzilla.

Attend and Connect

If you are just interested in learning more, demo-ing, networking and meeting others in the community, there's a good deal of events for you.

  • Participate in the Eclipse Demo Camps. Learn from the demos or demo your own code. Or organize a demo camp and invite others.
  • Check for Eclipse Days organized in your geography.
  • Attend the Eclipse Foundation's conferences in North America and Europe. Learn and network, or become a speaker.

Up-to-date information about all events is available at events.eclipse.org

Evangelize

  • Start or participate in a Regional Eclipse Community group with others in your local area. Regional Eclipse Communities allow people to meet in person and discuss topics of particular interest in your area. RECs are a great way to collaborate in your native language.
  • Sign up for a local IT event in your area and give a presentation on Eclipse.
  • Tell your friends about Eclipse and help us spread the word!

Miscellaneous

  • Become a Friend of Eclipse by donating financially. Donations are used to provide services for the Eclipse community, like providing more bandwidth for users and committers, purchasing additional servers to host Eclipse projects, sending students to EclipseCon and sponsoring Eclipse community events.
  • Help translate Eclipse into other languages through the Babel project.