TSC review changes

* Move statement about only applying when projects don't have a policy
  to the top.
* Move activity definition earlier.
* Add clause about HLF staff generates data and TSC acts.
* Remove repository inactivity section (handled in a different action).

inactivity.md

@@ -11,26 +11,18 @@ As part of the normal lifecycle of a project codebases and maintainers come and
 
 ## Maintainer Inactivity
 
-Hyperledger very much appreciates the contributions of all maintainers but removing write privileges is in the interest of an orderly and secure project.
+This policy applies to projects that do not have an explicit maintainer inactivity policy. Where a project has an established and functioning policy, only that project's policy will apply.
 
-Maintainers who have not contributed to a Hyperledger project for (`exact timeframe to be decided`) 3 / 4 / 6 months will be retired from active maintainer status and moved to an emeritus status. Any permissions to approve pull requests or commit code and any other such privileges associated with maintainer status will be removed.
+Hyperledger very much appreciates the contributions of all maintainers but removing write privileges is in the interest of an orderly and secure project.
 
 Activity can be code contributions, code reviews, issue reporting, or any other such activity trackable by GitHub attributed to a Hyperledger repository.
 
+Maintainers who have not had any activity in a Hyperledger project for (`set by TSC vote`) 3 / 6 months will be retired from active maintainer status for that project and moved to an emeritus status. Any permissions to approve pull requests or commit code and any other such privileges associated with maintainer status will be removed.
+
 The inactive maintainer will be notified of this via an "at" @ mention in a pull request moving their name from a project's active maintainers to the emeritus maintainers, and will have at least one week to respond to the proposal.
 
 Inactive maintainers who express an intent to continue contributing may request a three-month extension. Typically, only one such extension will be granted.
 
-Maintainers who have been moved to emeritus status may be re-added by the projects when their contributions resume and the existing maintainers approve their reactivation.
-
-This policy applies to projects that do not have an explicit maintainer inactivity policy. Where a project has an established and functioning policy, the project's policy shall prevail.
-
-## Repository Inactivity
-
-Any repository that has not had a release for (`exact timeframe to be decided`) 12 months or that has had no commits for 6 months may be archived by the TSC or Hyperledger staff.
-
-Projects will be notified via a PR in the appropriate repository and a notice in the project corresponding Discord channel and mailing list if they exist.
-
-Generally speaking, projects that expressed a request to keep the repository active will be honoured. However, this request may not be honoured if a project has many out of date dependencies, particularly ones relating to security vulnerabilities.
+Maintainers who have been moved to emeritus status may return to active status when their activity within the project resumes and the existing maintainers approve their reactivation.
 
-A request by a project to un-archive a repository for the purposes of active contribution will be honored, unless the project is in a dormant or end-of-life state. In those cases the project lifecycle issues will need to be resolved first.
+A Hyperledger Foundation staff member will provide a report of the most recent GitHub tracked actions for contributors at regular intervals to the Technical Steering Committee.  It will be the Committee's responsibility to act on the data.