Reflect latest incubation status (#664)

docs/apereo-incubation.md

@@ -1,25 +1,51 @@
 # AngularJS-portal aspires to be an Apereo project
 
-AngularJS-portal [is presently][Apereo projects currently in incubation] in [Apereo Incubation][], aspiring to be an [Apereo][] project in the [uPortal][] ecosystem.
+uPortal-home [is presently][Apereo projects currently in incubation] in [Apereo Incubation][], aspiring to be an [Apereo][] project in the [uPortal][] ecosystem.
 
 [![Apereo Incubating badge](https://www.apereo.org/sites/default/files/Incubation%20Logos/incubating%20w-out%20logo%2015mar17.png)](https://www.apereo.org/content/projects-currently-incubation)
 
 + Incubation requested: [2016-11-21][incubation@ proposal]
 + Apereo Board approved for incubation: [2016-12-20][2016-12-20 Apereo Board meeting minutes]
 + Entered incubation (initial conference call): 2017-03-13.
-+ Subsequent check-in calls: [2017-04-10][2017-04-10 incubation status call], [2017-05-25][2017-05-25 incubation status call Google Group topic], [2017-07-12 10 NYC (scheduled)][2017-07-12 incubation status call].
++ Subsequent check-in calls: [2017-04-10][2017-04-10 incubation status call], [2017-05-25][2017-05-25 incubation status call Google Group topic], [2017-07-11 10][2017-07-11 incubation status call] ([audio][2017-07-11 incubation status audio]).
 + Open Apereo 2017 pre-conference seminar: 2017-06-04, including [slides about incubation][Open Apereo 2017 seminar slides re incubation].
 
-
-## Project status vis a vis exit criteria
+## Summary: Project status vis a vis exit criteria
+
+Items are checked where the project believes it now fulfills the exit criteria.
+
+- [ ] 4.1 Legal
+  - [ ] 4.1.1 Out-bound licensing
+  - [ ] 4.1.2 License marking
+  - [ ] 4.1.3 Contributor License Agreements
+  - [ ] 4.1.4 Name trademark clarity
+- [ ] 4.2 Community
+  - [ ] 4.2.a Level of community involvement
+  - [ ] 4.2.b Organization of community
+  - [ ] 4.2.c Operation of community
+- [x] 4.3 Governance
+- [x] 4.4 Voting practices
+- [ ] 4.5 Conflict resolution policy
+- [ ] 4.6 Release planning
+- [ ] 4.7 Successful release during incubation
+- [ ] 4.8 Alignment and synergy with other Apereo software products
+- [ ] 4.9 Infrastructure
+  - [ ] 4.9.a Version control
+  - [ ] 4.9.b Issue tracking
+  - [ ] 4.9.c Communication channels
+  - [ ] 4.9.d Plans, directions, and objectives are readily identifiable
+  - [ ] 4.9.e Website: current and with instructions for installation, configuration
+
+
+## Detail: Project status vis a vis exit criteria
 
 (See [exit criteria][]).
 
 ### 4.1 Legal
 
 #### 4.1.1 Out-bound licensing
 
-AngularJS-portal and uw-frame include the Apache 2 license (approved for Apereo outbound) as LICENSE, but do not include the NOTICE file intended for inclusion with Apache2-licensed products.
+uPortal-home and uPortal-app-framework include the Apache 2 license (approved for Apereo outbound) as LICENSE, but do not include the NOTICE file intended for inclusion with Apache2-licensed products.
 
 Next actions:
 
@@ -48,11 +74,9 @@ Next actions:
 
 #### 4.1.4 Name trademark clarity
 
-Next actions:
+Naming considerations: Names should reflect uPortal commitment and represent how the product should be used.
+
 
-+ New software product names that better reflect nature and do not infringe on others' trademarks.
-+ Names should reflect uPortal commitment and represent how the product should
-be used.
 + Proposed names:
   + `uw-frame` → `uPortal-app-framework`
     + The uPortal App Framework will house common functionality to be leveraged
@@ -66,6 +90,14 @@ be used.
     + Developers provide `uPortal-home-config` for environment specific
       configuration.
 
+Next actions:
+
++ Implement repo re-naming in the course of migrating repos into a `uPortal-Project` GitHub organization. (Intended for Q3 2017).
++ Apply product re-naming in documentation
++ Apply product re-naming in source
+
+
+
 ### 4.2 Community
 
 #### a. Level of community involvement
@@ -75,13 +107,22 @@ be used.
 
 Next actions:
 
-+ Open, public incubation status check-in conference call. (Continuing in Q3 2017).
++ Open, public incubation status check-in conference calls. (Continuing in Q3 2017).
 + Move GitHub repositories to a uPortal-project context. (Intended for Q3 2017).
 
 #### 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?
 
+Roles:
+
++ [Committers]
++ [Contributors]
+
+Next actions
+
++ Document any roles not yet listed.
++ Document how the roles interact.
 
 #### c. Operation of community
 
@@ -96,6 +137,8 @@ Next actions:
 
 + [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
 
 + [Adopted Apache-style rules][Committers]
@@ -112,21 +155,26 @@ Next actions:
 
 ### 4.6 Release planning
 
-Releases come together organically. They're simply the changes from the accepted Pull Requests since the prior release, with Semantic Versioning observed.
+Releases come together organically. They're the changes from the accepted Pull Requests since the prior release, with Semantic Versioning observed.
 
 Next actions:
 
++ Move product issue tracking into a public context. Currently product issue tracking to the extent it exists is implied from the Scrum stories on the MyUW product and sprint backlogs. Scrum stories and product issue tracker entries for bugs, features, etc. aren't the same thing.
 + Further document release planning, beyond just release execution.
 + Further document adoption of Semantic Versioning.
 + Start looking a few more milestones out
 + Consider adopting a predictable release cadence
 
 ### 4.7 Successful release during Incubation
 
-AngularJS-portal has had many releases.
+uPortal-home has had many releases.
 
 Let's say Incubation starts for this purpose after governance and licensing is squared and the repos are moved to a uPortal-project context. Successfully releasing after those changes are in place will demonstrate that the product can still release under the new arrangements.
 
+Next actions:
+
++ Make the transition to a uPortal-project GitHub organization context, then, cut a release.
+
 ### 4.8 Alignment and synergy with other Apereo software products
 
 Depends on and leverages uPortal.
@@ -177,7 +225,7 @@ Next actions:
 
 #### e. Website: current and with instructions for installation, configuration
 
-Both AngularJS-portal and uw-frame use GitHub Pages to generate documentation websites, including installation and configuration instructions. Documentation of the uPortal integration specifically is weak.
+Both uPortal-home and uPortal-app-framework use GitHub Pages to generate documentation websites, including installation and configuration instructions. Documentation of the uPortal integration specifically is weak.
 
 Next actions:
 
@@ -191,7 +239,8 @@ Next actions:
 [2016-12-20 Apereo Board meeting minutes]: https://www.apereo.org/sites/default/files/meeting_minutes/2016/Apereo%20Board%20Minutes%20-%20Dec%202016%20-%20002.pdf
 [2017-04-10 incubation status call]: https://groups.google.com/a/apereo.org/d/msg/uportal-user/rN76LaT-VGQ/dikxNY9wAQAJ
 [2017-05-25 incubation status call Google Group topic]: https://groups.google.com/a/apereo.org/d/topic/uportal-user/7CmkrP-2Dic/discussion
-[2017-07-12 incubation status call]: https://docs.google.com/document/d/1LGBcsL-hg6a6kWktE4HgThjpF7idc_AwFcV4op6NLy8/edit?usp=sharing
+[2017-07-11 incubation status audio]: https://www.youtube.com/watch?v=3YPS_IWJ_tM
+[2017-07-11 incubation status call]: https://docs.google.com/document/d/1LGBcsL-hg6a6kWktE4HgThjpF7idc_AwFcV4op6NLy8/edit?usp=sharing
 [exit criteria]: https://www.apereo.org/content/apereo-incubation-process#S4
 [Open Apereo 2017 seminar slides re incubation]: https://docs.google.com/a/wisc.edu/presentation/d/1C-xRJoXWJKObfhmGV-7KYoZmiT5EyKHcQ36JVF6sGxk/edit?usp=sharing.
 [Committers]: https://github.com/UW-Madison-DoIT/angularjs-portal/blob/master/committers.md