Skip to main content
Jump to: navigation, search

Difference between revisions of "Linux Tools Project/New Subproject Checklist"

 
Line 1: Line 1:
{{#eclipseproject:technology.linux-distros}}
 
 
{{Linux_Tools}}
 
{{Linux_Tools}}
  
Line 7: Line 6:
 
* Public source code should be commented with proper javadoc. Project settings should be setup to warn developers about that.
 
* Public source code should be commented with proper javadoc. Project settings should be setup to warn developers about that.
 
* Project's [http://eclipse.org/linuxtools/ web site] should be enhanced by a new section for the subproject.
 
* Project's [http://eclipse.org/linuxtools/ web site] should be enhanced by a new section for the subproject.
* End user documentation should be written in Eclipse wiki [[Linux_Tools_Project/User_Guides]]. Even non end user visible subprojects should have documentation describing it's usage.
 
* Each sub-project should have a doc plugin generated from the wiki page using [[Mylyn/Incubator/WikiText]].
 
* Bugzilla component for the given subproject should be added.
 

Latest revision as of 12:58, 11 April 2022

Linux Tools
Website
Download
Community
Mailing ListForumsIRCmattermost
Issues
OpenHelp WantedBug Day
Contribute
Browse Source
  • Java package names should start with org.eclipse.linuxtools.<subproject>
  • Properly hide internal classes in internal packages. The internal classes should go into org.eclipse.linuxtools.internal.<subproject> namespace. Private packages should not be exported by the bundles unless marked as x-internal.
  • View, editor and so on ids in plugin.xml should be in the form "org.eclipse.linuxtools.*"
  • Public source code should be commented with proper javadoc. Project settings should be setup to warn developers about that.
  • Project's web site should be enhanced by a new section for the subproject.

Back to the top