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"
m |
|||
Line 1: | Line 1: | ||
What do we want to achieve by explicit code ownership? | What do we want to achieve by explicit code ownership? | ||
* '''Integrity of the Design''': The owner is responsible for a solid extensible design. | * '''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 | + | ** People other than the owner can make bug fixes, but please let the owner know. |
− | ** | + | ** Don't 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 | + | ** 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. | ** 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 | + | * '''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 | + | ** Helps dispatching new bugs to component owners first. |
− | ** Ownership can be for functionality that spans multiple packages ( | + | ** Ownership can be for functionality that spans multiple packages (if functionality is seen by user as a single entity). |
− | * '''Credit for Quality through Visibility''' | + | * '''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. |
− | * '''Ownership of Copyright and IP issues''' | + | * '''Ownership of Copyright and Intellectual Property (IP) issues'''. |
** Component owners are responsible for keeping the IP of their component clean. | ** Component owners are responsible for keeping the IP of their component clean. | ||
<p/> | <p/> |
Revision as of 22:37, 26 November 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.
- Don't 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.
- Ownership of Copyright and Intellectual Property (IP) issues.
- Component owners are responsible for keeping the IP of their component clean.
<p/>
Unresolved Ambiguities
- RSE Team Support (Team View, Profiles, Docs, Persistence wrt team support) -- rse.ui.view.team belongs to dmcknigh
- Drag&Drop, Copy&Paste -- is this part of views?
- Rse.core.filters -- ddykstal or dmcknigh?
- EFS - not yet assigned - dmcknigh or kmunir?
Code Ownership Table
Owner | Area | Plugin/Package | Backup owner |
---|---|---|---|
Dave Dykstal | RSE Persistency |
org.eclipse.rse.core/persistence |
|
RSE password prompt |
org.eclipse.rse.core/src/org.eclipse.rse.core.subsystems (credential aspects) |
||
RSE logging |
org.eclipse.rse.logging - all packages |
||
RSE message support |
/org.eclipse.rse.services/clientserver/org.eclipse.rse.services.clientserver.messages |
||
RSE filtering |
org.eclipse.rse.core/src/org.eclipse.rse.core.filters |
||
Dialog Accessibility / UI Controls |
org.eclipse.rse.ui/UI/org.eclipse.rse.ui.Mnemonics |
||
RSE Documentation |
org.eclipse.dstore.doc.isv |
Martin O | |
RSE JUnit tests |
org.eclipse.rse.tests |
Martin O | |
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 local |
org.eclipse.rse.connectorservice.local |
Kushal Munir | |
RSE examples |
org.eclipse.rse.examples.daytime |
Dave Dykstal | |
RSE content assist | org.eclipse.rse.shells.ui/org.eclipse.rse.shells.ui.view | Dave McKnight | |
RSE nightly builds, |
org.eclipse.rse.build |
Ted Williams, | |
Third Party Libs (Jakarta Commons Net, ORO) |
org.eclipse.tm.core/thirdparty/* |
Dave Dykstal | |
RSE manual tests | org.eclipse.rse.tests.manual | ||
Javier Montalvo | Discovery | (org.eclipse.tm.core) discovery/* | RSE ftp |
org.eclipse.rse.ftp-feature |
Dave McKnight, | </tr>
Ted Williams | Terminalview | (org.eclipse.tm.core) terminal/* | Michael Scharf |
Ewa Matejska | CDT Remote Launch |
org.eclipse.rse.remotecdt |
Martin Oberhuber |