docs: clarify status of incubation items with per-heading checkboxes

docs/apereo-incubation.md

@@ -55,9 +55,9 @@ Items are checked where the project believes it now fulfills the exit criteria.
 
 (See [exit criteria][]).
 
-### 4.1 Legal
+### [x] 4.1 Legal
 
-#### 4.1.1 Out-bound licensing
+#### [x] 4.1.1 Out-bound licensing
 
 uPortal-home and uPortal-app-framework include the Apache 2 license (approved
 for Apereo outbound) as LICENSE and accompanying NOTICE file acknowledging
@@ -68,7 +68,7 @@ Next actions:
 + Stop using Maven, stop delivering a `.war`, and thereby stop having Java
 dependencies and further simplify licensing posture.
 
-#### 4.1.2 License marking
+#### [x] 4.1.2 License marking
 
 All source files are marked with the Apereo Apache2 license header.
 
@@ -77,7 +77,7 @@ Next actions:
 + Re-implement license header checking without relying upon Maven. Sooner or
 later this project will stop using Maven.
 
-#### 4.1.3 Contributor License Agreements
+#### [x] 4.1.3 Contributor License Agreements
 
 All major contributors have ICLAs on file.
 
@@ -97,7 +97,7 @@ Next actions:
   CLA agreement process. (Click-through assurance that demonstrated CLA
   agreement through more arduous process, not click-through agreement to CLA.)
 
-#### 4.1.4 Name trademark clarity
+#### [x] 4.1.4 Name trademark clarity
 
 Naming considerations: Names should reflect uPortal commitment and represent how
 the product should be used.
@@ -132,9 +132,9 @@ Next actions:
 nearly as clean as envisioned.)
 
 
-### 4.2 Community
+### [ ] 4.2 Community
 
-#### a. Level of community involvement
+#### [ ] a. Level of community involvement
 
 > What is the number of participants? What level of participation is there? What
 > activities do participants undertake or what artifacts have they created?)
@@ -147,7 +147,7 @@ Next actions:
 + Answer the question: What activities do participants undertake or what
   artifacts have they created?
 
-#### b. Organization of community
+#### [ ] b. Organization of community
 
 > What roles are in place? Who occupies those roles? How do those roles interact
 > among one another and with the community?
@@ -163,7 +163,7 @@ Next actions
 + Document any roles not yet listed or documented.
 + Document how the roles interact.
 
-#### c. Operation of community
+#### [ ] c. Operation of community
 
 > What activities/events/artifacts are created/managed by the project to foster
 > participation and development? How are decisions made?
@@ -180,19 +180,19 @@ Next actions
 + Answer question: what activities/events/artifacts are created/managed to
   foster participation and development?
 
-### 4.3 Governance
+### [x] 4.3 Governance
 
 + [Committers][] are documented, with Apache-style governance by the Committers,
   process for adding Committers, and governance fail-safe falling back on
   uPortal steering.
 
 Committers include a non-University-of-Wisconsin committer (Christian Murphy).
 
-### 4.4 Voting practices
+### [x] 4.4 Voting practices
 
 + [Adopted Apache-style rules][Committers]
 
-### 4.5 Conflict resolution policy
+### [ ] 4.5 Conflict resolution policy
 
 + Inherits code of conduct considerations from uPortal which participates in the
   [Apereo Welcoming Policy][]. However, Apereo Welcoming Policy is not yet a
@@ -210,7 +210,7 @@ Next actions:
 + Advocate for maturing the Apereo Welcoming Policy to function as an adequate
   "code of conduct" for this and other Apereo projects
 
-### 4.6 Release planning
+### [ ] 4.6 Release planning
 
 Releases come together organically. They're the changes from the accepted Pull
 Requests since the prior release, with Semantic Versioning observed.
@@ -226,14 +226,14 @@ Next actions:
 + Start looking a few more milestones out
 + Consider adopting a predictable release cadence
 
-### 4.7 Successful release during Incubation
+### [x] 4.7 Successful release during Incubation
 
 uPortal-home has had many releases, including many during incubation after
 governance and licensing squared and the repos moved to a uPortal-project
 context. Successfully releasing after those changes demonstrated that the
 product can still release under the Apereo arrangements.
 
-### 4.8 Alignment and synergy with other Apereo software products
+### [ ] 4.8 Alignment and synergy with other Apereo software products
 
 Depends on and leverages uPortal.
 
@@ -247,13 +247,13 @@ Next actions:
 + Factor out messages (announcements and notifications) as a microservice
 + Explore relationship with nascent Edinburgh Notifications
 
-### 4.9 Infrastructure
+### [ ] 4.9 Infrastructure
 
-#### a. Version control
+#### [x] a. Version control
 
 Using GitHub repositories in `uPortal-Project` context.
 
-#### b. Issue tracking
+#### [ ] b. Issue tracking
 
 Intend to use GitHub issue tracking for product issue tracking.
 
@@ -262,7 +262,7 @@ Next actions:
 + Use GitHub issue tracking for product management in earnest. (This subset of)
   MyUW Scrum team user stories become references to public issue tracker issues.
 
-#### c. Communications channels
+#### [ ] c. Communications channels
 
 Currently piggyback on uPortal email lists, only somewhat effectively.
 
@@ -275,7 +275,7 @@ Next actions:
 + Consider how to better fit into existing uPortal email lists, or create new
   lists.
 
-#### d. Plans, directions, and objectives are readily identifiable
+#### [ ] d. Plans, directions, and objectives are readily identifiable
 
 Long range plans don't so much exist.
 
@@ -285,7 +285,7 @@ Next actions:
 + Navigate tension between product roadmapping and agile, organic discovery of
   product progress
 
-#### e. Website: current and with instructions for installation, configuration
+#### [ ] e. Website: current and with instructions for installation, configuration
 
 Both uPortal-home and uPortal-app-framework use GitHub Pages to generate
 documentation websites, including installation and configuration instructions.