Jump to: navigation, search

Difference between revisions of "VE/Contributing"

< VE
(How to contribute to VE?)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
===How to contribute to VE?===
 
===How to contribute to VE?===
 +
#For starters, you will need the Eclipse 3.3 SDK, and a Java 5 JDK from [http://java.sun.com Sun].
 +
#Then a checkout of the relevant projects. There is a team project set attached to that {{bug|203317}}.
 +
#There is a small extra step: there is a jar in emf/ant that needs to build first. Get the Jardesc attached to {{bug|203449}}, and save it in at the root of the org.eclipse.emf.ant project. Edit it to match you workspace path (right click, Open Jar packager), then create the jar. The comment threads in {{bug|203449}} also suggest a better way, without using a jardesc.
  
For a start, you will need the Eclipse 33 SDK, and a Java 5 JDK from SUN.
+
===What to do next?===
Then a checkout of the relevant projects.
+
There is a team project set attached to that bug:
+
https://bugs.eclipse.org/bugs/show_bug.cgi?id=203317
+
 
+
There is a small extra step: there is a jar in emf/ant that needs to build first
+
https://bugs.eclipse.org/bugs/show_bug.cgi?id=203449
+
Get the Jardesc attached to the bug above, and save it in at the root of the org.eclipse.emf.ant project
+
Edit it to match you workspace path (right click, Open Jar packager), then create the jar.
+
 
+
===What to do next ? ===
+
 
+
 
Then you can pick a bug, a small one, like an enhancement request, something that you can relate to, something that bugs YOU, rather a small end user feature.
 
Then you can pick a bug, a small one, like an enhancement request, something that you can relate to, something that bugs YOU, rather a small end user feature.
 +
 
Here is a list of all open bugs:
 
Here is a list of all open bugs:
 +
 
http://tinyurl.com/2an8jw
 
http://tinyurl.com/2an8jw
  
When you pick a bug, cc your self on it, add a comment telling that you are working on it, and start the discussion in the bug comments.
+
When you have decided on a bug, CC your self on it, add a comment telling that you are working on it, and start the discussion in the bug comments. If you have questions, post them here or on the [https://dev.eclipse.org/mailman/listinfo/ve-dev ve-dev] mailing list. Then as soon as you have the smallest fix working, attach a patch to the bug, and send a heads up on the ve-dev list.
If you have questions, post them here or on the ve-dev list.
+
 
Then as soon as you have the smallest fix working, attach a patch to the bug, and send a heads up on the ve-dev list.
+
 
There is a documentation on how to write patches and contributing to eclipse there:
 
There is a documentation on how to write patches and contributing to eclipse there:
 +
 
http://eclipsezilla.eclipsecon.org/show_bug.cgi?id=77
 
http://eclipsezilla.eclipsecon.org/show_bug.cgi?id=77
  
 +
===Tips and tricks===
 +
List your tips and tricks here.
  
===Tips and tricks ===
+
[[Category:How to Contribute]]
List your tips sand tricks here.
+

Latest revision as of 16:20, 21 September 2007

How to contribute to VE?

  1. For starters, you will need the Eclipse 3.3 SDK, and a Java 5 JDK from Sun.
  2. Then a checkout of the relevant projects. There is a team project set attached to that bug 203317.
  3. There is a small extra step: there is a jar in emf/ant that needs to build first. Get the Jardesc attached to bug 203449, and save it in at the root of the org.eclipse.emf.ant project. Edit it to match you workspace path (right click, Open Jar packager), then create the jar. The comment threads in bug 203449 also suggest a better way, without using a jardesc.

What to do next?

Then you can pick a bug, a small one, like an enhancement request, something that you can relate to, something that bugs YOU, rather a small end user feature.

Here is a list of all open bugs:

http://tinyurl.com/2an8jw

When you have decided on a bug, CC your self on it, add a comment telling that you are working on it, and start the discussion in the bug comments. If you have questions, post them here or on the ve-dev mailing list. Then as soon as you have the smallest fix working, attach a patch to the bug, and send a heads up on the ve-dev list.

There is a documentation on how to write patches and contributing to eclipse there:

http://eclipsezilla.eclipsecon.org/show_bug.cgi?id=77

Tips and tricks

List your tips and tricks here.