What: update project proposals doc

Why:

* capture new Annual Review for sandbox
* small updates as discussed to refresh the doc.

This change addresses the need by:

*  capture contents from cncf#815
* call out no lobbying for sponsors.

process/project_proposals.adoc

@@ -1,4 +1,4 @@
-== CNCF Project Proposal Process v1.3
+== CNCF Project Proposal Process v1.4
 
 === Introduction 
 
@@ -21,9 +21,20 @@ image::sandbox-process.png[Sandbox process]
  * TOC reviews proposal in spreadsheet and presentation, project passes for inclusion with a simple majority vote. 
  * TOC may engage with project to ask further questions
  * Projects may re-apply after six months
+ * Annual reviews are performed in order to check in with sandbox projects, ascertain their progress, and address any outstanding questions
+ * A TOC representative volunteers to lead the review once the project files a PR.
+ * The assigned member reviews the content of the PR and analyzes the project for community health indicators, their findings are placed within a thread in the private TOC channel for discussion
+ * findings should highlight important facts about the project that could influence the TOCs decision around the future of the project, its status in sandbox, its path to incubation, etc.
+ * the thread should always include whether the Project's view of themselves and the ask of the CNCF is reasonable to assist the project moving forward.
+ * Projects are invited to the public TOC meeting to engage in TOC led discussion around the project. Projects are not obligated to attend.
+ * The assigned TOC member provides a summary of the project and leverages the thread's content as the basis of discussion.
+ * Discussion typically focuses on what is going well with the project and areas to improve
+ * Project are invited to use this time to voice any concerns and requests for help they may have that are not captured in the PR (or highlight asks within the PR).
+ * At the conclusion of the public meeting, the TOC votes to approve all annual reviews covered. Should a concern registered on a project, the votes will be held separately.
+ * After the meeting wraps up, the assigned TOC member may summarize the discussion on the PR in the form of a comment to document information for the project and community.
 . *Governance / legal issues*
  * CNCF staff handle governance / legal issues
- * This can happen after TOC Sandbox Sponsors step forward
+ * This can happen after TOC Sandbox Sponsors step forward - Lobbying for a sponsor is not permitted.
 
 See the https://github.com/cncf/toc/blob/main/process/sandbox.md[Sandbox guidelines] for the definition of and motivation behind the CNCF Sandbox.
 
@@ -37,7 +48,7 @@ image::incubation-process.png[Incubation process]
 
 . *Project Proposal* 
  * Incubation proposed through a https://github.com/cncf/toc/pulls[GitHub pull request]
- * The proposal moves to Due Diligence when a TOC member steps forward as an Incubation Sponsor.
+ * The proposal moves to Due Diligence when a TOC member steps forward as an Incubation Sponsor - Lobbing for a sponsor is not permitted.
  * The status of outstanding Incubation proposals is reported on a monthly basis in the TOC public meeting. This highlights projects looking for sponsorship, and provides a check-in on DD progress for sponsored projects. 
  * A potential sponsor can indicate that they are interested but don't have capacity to work on DD at this time, to set a project's expectations.
  * The TOC may agree that the project does not (yet) meet the https://github.com/cncf/toc/blob/main/process/graduation_criteria.adoc#incubation-stage[Incubation requirements] and give feedback on why this is the case. If the project is not already in the CNCF, the TOC may suggest that project apply for Sandbox instead.
@@ -73,7 +84,8 @@ image::incubation-process.png[Incubation process]
  * The proposal addresses how the project has grown since incubation and any concerns from incubation DD in addition to the standard graduation requirements.
  * Projects will be reviewed on a rolling basis as they apply, instead of two meetings a year. 
 . * If a TOC member steps forward to support the project as a sponsor and determines the Graduation DD document is finalized, the TOC member kicks off two week period of time for public comment on the TOC mailing list
- * The email should contain a link to the proposal pull request and incubation DD document.
+ * Lobbying for a sponsor is not permitted.
+ * The email should contain a link to the proposal pull request and graduation DD document.
  * All TAGs, end users, TOC members, and community members are welcome to comment at this time on the mailing list.
  * Historically, projects have done a TOC presentation as part of the graduation process. The TOC has gotten rid of the presentation requirement. 
 * If the TOC does not sponsor the project to move forward at that time, they will provide feedback to the project and the PR will be closed.