...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Current Roadmap | Proposed/Beyond One Year | Completed |
|---|
| HTML Comment | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
Colors to use with panels to show status...
|
Hyku Mission
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Curabitur vestibulum tristique urna. Aenean suscipit ipsum ac sagittis consequat. Cras volutpat massa eget hendrerit laoreet. Nam sed faucibus erat, vitae congue enim. Donec auctor tempus lorem et rutrum. In efficitur erat vitae erat blandit fermentum. Cras molestie in tellus dapibus ornare. Praesent eget aliquet risus. Aenean non sodales lorem. Nunc in nulla nec est auctor sollicitudin. Curabitur pharetra vitae mauris ac rutrum. Vestibulum vitae mauris vitae tortor pulvinar viverra. Sed facilisis sed mauris eu bibendum. Interdum et malesuada fames ac ante ipsum primis in faucibus.
...
Targeted within the Next Year (from today)
Listed roughly in priority order and the expected order of implementation. Some efforts may be implemented at the same time. The priority order may shift based on available resources and community interest.
...
| hidden | true |
|---|
Colors to use with panels to show status...
...
#339860...
#c8f3c8...
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Bugfixes & Ongoing Maintenance WorkThe Hyrax Working Group is charged with supporting core maintenance and development for Hyrax in order to provide a stable base of support for the solution bundle. This working group is not meant to be a replacement for community-led development efforts and/or contributions, but rather, it is meant to augment such efforts. This group may work on some Roadmap Items. When they do, the group will be identified in the Status Summary section of the item. Status Summary/Major Activities:
|
| Panel | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Group and responsibility managementRe-architect groups and responsibilities to improve clarity of function. Status Summary/Major Activities:
|
| Panel | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Enhanced batch edit interfaceBuild out batch edit functionality to meet the needs, specifically, of digital collections-based repository implementations. Status Summary/Major Activities:
|
Code Requirements
Requirement | Met? | How? |
Code must be released at version >= 1.0 | YES | Version 1.0.1 |
Good unit test coverage measured by community (e.g. 100% or 75% of what’s important) | YES | 93% |
uses CI (Preferably Travis-CI, unless there is a compelling reason to do something else) | YES | Travis |
uses Coverage tool (coveralls or simplecov) | YES | Coveralls |
Show compatibility with current Rails versions and other dependencies, when was it last tested; note compatibility with prior versions when available. Compatibility can be specified in the gemspec(s) or verified via CI matrix. | YES | Travis tests against ruby 2.4.1 v.1.0.1: Rails 5.1.6; Hyrax 2.3.3 |
Hierarchy of promises asserted in clearly defined acceptance tests | YES |
...
Requirement | Met? | How? |
LICENSE file, Apache 2 (or compatible) | YES | |
YES | ||
Statement of purpose | YES | See GH header: https://github.com/samvera-labs/hyku |
Basic install steps | YES | |
Identify any volatile/experimental features | N/A | |
How to contribute | YES | |
How/Who to contact for help | YES | |
Known issues documented in github Issues tickets (not just listed in text) | YES | |
Tutorial / Walkthrough / Example usage | YES | |
Resolve TODO items in documents and remove them | NO | There are 10 TODO items in the code. |
All Contributors should have signed Hydra Contibutor License Agreement (CLA) | YES | Compare https://github.com/samvera-labs/hyku/graphs/contributors With https://wiki.duraspace.org/pages/viewpage.action?pageId=87460368 |
Use Requirements
Requirement | Met? | How? |
Community use by three or more institutions | YES | PALNI/PALCI with Notch8, King’s Fund with CoSector, British Library with Ubiquity, Texas Digital Library - Bridge2Hyku Project |
In active use for six months | YES | Notch8, Ubiquity, CoSector and TDL have been working with the software for over 6 months. Prior to that DuraSpace, Stanford and DPLA were working on the software. Throughout that time the software has been in active development. |
Has an ongoing maintenance plan. | YES | Hyku has a product owner, and an Interest Group. The group is working on a gap analysis and roadmap. |
...