Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "TM/Code Ownership"
Line 8: | Line 8: | ||
** Helps dispatching new bugs to component owners first | ** Helps dispatching new bugs to component owners first | ||
** Ownership can be for functionality that spans multiple packages (If functionality is seen by user as a single entity) | ** Ownership can be for functionality that spans multiple packages (If functionality is seen by user as a single entity) | ||
− | * '''Credit for Quality | + | * '''Credit for Quality through Visibility''' |
** Owners of a component should be publicly visible, so they can get the credit for good work | ** Owners of a component should be publicly visible, so they can get the credit for good work | ||
+ | |||
+ | <p/> | ||
<table border=1 cellspacing=0 cellpadding=1> | <table border=1 cellspacing=0 cellpadding=1> | ||
Line 127: | Line 129: | ||
org.eclipse.rse.subsystems.files.ftp | org.eclipse.rse.subsystems.files.ftp | ||
</p></td> | </p></td> | ||
− | <td> | + | <td>Dave McKnight</td></tr> |
<tr> | <tr> | ||
<td>RSE local</td> | <td>RSE local</td> | ||
Line 138: | Line 140: | ||
org.eclipse.rse.subsystems.shells.local | org.eclipse.rse.subsystems.shells.local | ||
</p></td> | </p></td> | ||
− | <td> | + | <td>Kushal Munir</td></tr> |
<tr> | <tr> | ||
<td>RSE examples</td> | <td>RSE examples</td> | ||
Line 163: | Line 165: | ||
org.eclipse.rse.updatesite | org.eclipse.rse.updatesite | ||
</p></td> | </p></td> | ||
− | <td> | + | <td> |
+ | <p>Ted Williams,<br/> | ||
+ | Dave Dykstal | ||
+ | </p></td></tr> | ||
<tr> | <tr> | ||
<td>RSE manual tests</td> | <td>RSE manual tests</td> |
Revision as of 11:53, 13 September 2006
What do we want to achieve by explicit code ownership?
- Integrity of the Design: The owner is responsible for a solid extensible design.
- People other than the owner can make bug fixes, but please let the owner know
- Dont make design-breaking changes without letting the owner know
- Typically there is a single owner for each functionality. Multiple "two-in-a-box" owners are only possible if they work very closely together
- There may be a backup person for an owner, in case the owner is out-of-office.
- Timely Bug Triage: The owner is responsible for reviewing (and probably reassigning) bugs of his area in a timely fashion
- Helps dispatching new bugs to component owners first
- Ownership can be for functionality that spans multiple packages (If functionality is seen by user as a single entity)
- Credit for Quality through Visibility
- Owners of a component should be publicly visible, so they can get the credit for good work
<p/>
Owner | Area | Plugin/Package | Backup owner |
---|---|---|---|
Dave Dykstal | RSE Persistency | org.eclipse.rse.ui/persistence | |
RSE password prompt | |||
RSE JUnit tests | |||
Dave McKnight | RSE dstore |
org.eclipse.dstore.core |
|
RSE services |
org.eclipse.rse.services.files |
||
RSE core model |
org.eclipse.rse.core |
||
RSE views |
org.eclipse.rse.ui.view |
||
Kushal Munir | RSE New Connection Wizard Delegate | org.eclipse.rse.ui/org.eclipse.rse.ui.wizards | |
RSE Archive Handlers | org.eclipse.rse.services.clientserver.archivehandlers | ||
RSE core comm | org.eclipse.rse.core.comm | ||
RSE search |
org.eclipse.rse.files.ui.search |
||
RSE file encodings | (multiple) | ||
Martin Oberhuber | |||
RSE ssh |
org.eclipse.rse.connectorservice.ssh |
||
RSE ftp |
org.eclipse.rse.ftp-feature |
Dave McKnight | |
RSE local |
org.eclipse.rse.connectorservice.local |
Kushal Munir | |
RSE examples |
org.eclipse.rse.examples-feature |
||
RSE content assist | org.eclipse.rse.shells.ui/org.eclipse.rse.shells.ui.view | ||
RSE nightly builds |
org.eclipse.rse.build |
Ted Williams, | |
RSE manual tests | org.eclipse.rse.tests.manual | ||
Javier Montalvo | Discovery | (org.eclipse.tm.core) discovery/* | |
Ted Williams | Terminalview | (org.eclipse.tm.core) terminal/* |