Alternative UI for Apereo uPortal (originally built for MyUW)

View on GitHub

uPortal-home aspires to be an Apereo project

uPortal-home is presently in Apereo Incubation, aspiring to be an Apereo project in the uPortal ecosystem.

Apereo Incubating badge

Summary: Project status vis a vis exit criteria

Items are checked where the project believes it now fulfills the exit criteria.

Detail: Project status vis a vis exit criteria

(See exit criteria).

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 dependencies under Apache 2 and other permitted licenses.

Next actions:

4.1.2 License marking

All source files are marked with the Apereo Apache2 license header.

Next actions:

4.1.3 Contributor License Agreements

All major contributors have ICLAs on file.

Did not secure ICLA from one minor past Contributor. Deferred further worry about this by accepting the Contributor’s Contributions (if any are still relevant) via Apache2 clause 5, as noted in LICENSE.

If this ever becomes a problem a careful audit might reveal that no Contributions from this Contributor are still relevant, through the natural turnover of modules and code within the project. In practice this is unlikely to ever be a problem.

Next actions:

4.1.4 Name trademark clarity

Naming considerations: Names should reflect uPortal commitment and represent how the product should be used.

Benito Gonzalez confirmed via US Patent and Trademark search that uPortal-home is not registered.

Next actions:

(Currently, the framework and the core product are configurable, but it’s not nearly as clean as envisioned.)

4.2 Community

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?)

Next actions:

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?


Next actions

c. Operation of community

What activities/events/artifacts are created/managed by the project to foster participation and development? How are decisions made?

Next actions

4.3 Governance

Committers include a non-University-of-Wisconsin committer (Christian Murphy).

4.4 Voting practices

4.5 Conflict resolution policy

No formal conflict resolution policy is in place.

Next actions:

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.

Next actions:

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

Depends on and leverages uPortal.

Aspires to depend on and leverage more feasible microservices and hopes to evolve with uPortal itself in this direction.

Next actions:

4.9 Infrastructure

a. Version control

Using GitHub repositories in uPortal-Project context.

b. Issue tracking

Intend to use GitHub issue tracking for product issue tracking.

Next actions:

c. Communications channels

Currently piggyback on uPortal email lists, only somewhat effectively.

Next actions:

d. Plans, directions, and objectives are readily identifiable

Long range plans don’t so much exist.

cf. roadmap

Next actions:

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. Documentation of the uPortal integration specifically is weak.

Next actions: