Add a few more consistency edits to lifecycle docs

Signed-off-by: Marcela Melara <[email protected]>

process/TI-Gives+Gets.md

@@ -39,10 +39,11 @@ Also note that benefits may actually vary based on resources and funds availabil
 
 All requirements of Sandbox must be fulfilled. PR filed to promote TI to Incubating stage.
  * TI must have documented, initial group governance.
- * WG and Project has met no less than 5 times within the last calendar quarter
  * Maintains a diversified contributor base (i.e. not a single-vendor project) with an active flow of contributions, and documents the current list of maintainers:
    * WG must have a minimum of five participants with a minimum of three different organization affiliations.
-   * Project and SIG must have a minimum of three contributors with a minimum of two different organization affiliations. 
+   * Project and SIG must have a minimum of three contributors with a minimum of two different organization affiliations.
+ * WG and Project has met at least 5 times within the last calendar quarter since becoming Sandbox.
+ * SIG must have made substantial progress on a deliverable.
  * Project must have defined a contributor guide, which makes it clear how and when contributors should be given increasing responsibilities towards maintainership of the project. (Example guides: Sigstore, AllStar)
  * Project should be able to show adoption by multiple parties and adoption's value to the open source community and/or end users (may include adoption of beta/early versions) with the intent to showcase wide adoption by the project's consumers.
  * TI that develops code:

process/project-lifecycle.md

@@ -89,10 +89,11 @@ Incubating projects represent maturing but not fully realized projects. Incubati
 
 #### Incubation Entry Requirements and Considerations
 
+All requirements of Sandbox must be fulfilled, plus:
 * Projects must have a minimum of three maintainers with a minimum of two different organization affiliations, and document the current list of maintainers.
+* Projects must have met at least 5 times within the last calendar quarter since becoming `Sandbox`.
 * Projects must have defined a contributor guide, which makes it clear how and when contributors should be given increasing responsibilities towards maintainership of the project. (Example guides: [Sigstore](https://github.com/sigstore/community/blob/main/MEMBERSHIP.md), [AllStar](https://github.com/ossf/allstar/blob/main/contributor-ladder.md))
 * Projects should be able to show adoption by multiple parties and adoption's value to the open source community and/or end users (may include adoption of beta/early versions) with the intent to showcase wide adoption by the project's consumers.
-* Projects must be aligned with the OpenSSF mission _and_ either be a novel approach for existing areas or address an unfulfilled need. It is expected that the initial code or specification developed by an OpenSSF WG be kept within their repository and will not function as a Project in its own right. Should the initial WG code or specification grow and mature that it warrants its own Project status, then it is subject to Sandbox entry requirements. It is preferred that extensions of an existing OpenSSF project collaborate with the existing project rather than seek a new project.
 * Projects must have documented, initial project governance.
 
 #### Project Process: Sandbox to Incubation and direct entry to Incubation

process/working-group-lifecycle.md

@@ -33,7 +33,7 @@ Once the WG has further defined its goals and garnered enough support it can app
 ## To become `Incubating`:
 
 * Have a charter or mission statement for review by TAC
-* Have met at least 5 times
+* Have met at least 5 times within the last calendar quarter since becoming `Sandbox`
     * For these, meeting notes (or ideally recordings) must be public
 * Have at least 5 contributors from at least 3 different organizations attending regularly
 * TAC will vote to approve or provide constructive guidance