Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Virgo/Community"

m (Mins for 18 May 2010)
Line 1: Line 1:
 
[[Category:Virgo]] [[Category:EclipseRT]]
 
[[Category:Virgo]] [[Category:EclipseRT]]
 
{{Virgo}}
 
{{Virgo}}
Tweet about #virgort, join the [https://dev.eclipse.org/mailman/listinfo/virgo-dev virgo-dev] mailing list, or use [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;order=Importance;classification=RT;product=Virgo| bugzilla].  
+
You can join the Virgo community by tweeting about #virgort, subscribing to the [https://dev.eclipse.org/mailman/listinfo/virgo-dev virgo-dev] mailing list, or using [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;order=Importance;classification=RT;product=Virgo| bugzilla].  
  
There is also a weekly, one hour call at 14:00 UTC on Tuesdays to discuss Virgo. See [[Virgo/Discussion/Meetings|meetings]] for details.
+
= Meetings =
  
= Minutes  =
+
There is a weekly, one hour call at 14:00 UTC on Tuesdays to discuss Virgo. See [[Virgo/Discussion/Meetings|meetings]] for details.
 +
 
 +
== Minutes  ==
  
 
* [[Virgo/Community/Minutes-2010-05-18|Minutes of 18 May 2010]]
 
* [[Virgo/Community/Minutes-2010-05-18|Minutes of 18 May 2010]]
 
* [[Virgo/Community/Minutes-2010-05-11|Minutes of 11 May 2010]]
 
* [[Virgo/Community/Minutes-2010-05-11|Minutes of 11 May 2010]]
 
* [[Virgo/Community/Minutes-2010-05-04|Minutes of 4 May 2010]]
 
* [[Virgo/Community/Minutes-2010-05-04|Minutes of 4 May 2010]]
 +
 +
= Contributions =
 +
 +
Please read the [http://www.eclipse.org/legal/termsofuse.php Eclipse.org Terms of Use] before making any contribution.
 +
 +
Then attach your code or patch to a bugzilla bug so that the necessary due diligence and IP checks can be performed.
 +
 +
You should probably discuss large contributions on the virgo-dev mailing list first so everyone knows what's going on.
 +
 +
Contributions should include unit tests whenever possible. This ensures that the contributed code is well structured and can be unit tested as well as preventing a technical debt of untested code.

Revision as of 06:44, 20 May 2010



You can join the Virgo community by tweeting about #virgort, subscribing to the virgo-dev mailing list, or using bugzilla.

Meetings

There is a weekly, one hour call at 14:00 UTC on Tuesdays to discuss Virgo. See meetings for details.

Minutes

Contributions

Please read the Eclipse.org Terms of Use before making any contribution.

Then attach your code or patch to a bugzilla bug so that the necessary due diligence and IP checks can be performed.

You should probably discuss large contributions on the virgo-dev mailing list first so everyone knows what's going on.

Contributions should include unit tests whenever possible. This ensures that the contributed code is well structured and can be unit tested as well as preventing a technical debt of untested code.

Back to the top