No. Existing projects already have governance mechanisms in place to handle multiple components within the project. There is no need for the TSC to get into that micromanagement of the projects and its components. Projects may decide to manage component development as subprojects but no formal definition of subproject is intended by the TSC.
When a project sends to the TSC its quarterly report, it needs to include anything relevant from all related efforts.
From a decision process perspective, it is expected that all maintainers have a maintainer vote and maintainers need to work out between themselves who maintains which pieces and how they resolve conflict. Projects should document how decisions are made and by whom.
Of course, if any conflict were to rise between maintainers within a project that can not be resolved by the project's own governance, the issue can be brought up to the TSC for arbitration.
For house keeping purposes, existing projects that were originally started via a HIP but in practice are not being managed as "top level projects" are officially rescinded from the top level nomination and rolled over into their related project. Specifically, this concerns the following projects which will then be considered to be part of Fabric:
2017-02-28 - New Project: Fabric Go SDK Proposal - approved 2017-03-17
2016-08-09 - New Project: Fabric Python SDK Proposal - approved 2016-09-08
2016-06-02 - New Project: Chaintool Proposal - approved 2016-06-16
2016-05-24 - New Project: Java Chaincode support for Hyperledger Fabric Proposal - approved 2016-05-26
2016-05-03 - New Project: Exerciser for the Hyperledger Fabric v0.2 Proposal - approved 2016-05-12
Source: Proposals through 2018
A new project proposal that is a feature unique to an existing project will be guided to that existing community to see about joining it. If discussion with the existing project community leads to not joining it then the proposal will be reviewed on its own merits as an independent project.
Projects that are dependent of one of the other projects should be folded under that project. This means Composer becomes Fabric Composer, Explorer becomes Fabric Explorer etc.
Subproject status and reporting should be reported through the top level project. For example, Fabric Explorer status would be included in the Fabric quarterly reports..