...
- How should we handle deprecation?
- Johnson: Reach out to product owners and discuss the possibility of scheduling sprints
- Product Owners should have a model for sprints which allows them to assign work
- Asking if we should deprecate
- Do we need to further identify projects which have a Product Owner but don't meet standards
- That's every Gem identified (i. e. none meet the requirements)
- Maybe some small percentage does (example: hydra-derivatives)
- Sprint Structure
- This group should decline to schedule sprints for projects which don't meet the minimum requirements
- Getting all of the projects classified as Core Components up to minimum requirements should be the highest priority
- Phase 2
- Pendragon:
- Understood Phase 2 to be less focused upon generating sprints and demand to product owner requests for features
- Instead, getting Core Components up to spec consistently
- Following this, then scheduling sprints for future features would be possible
- Johnson:
- Understood Phase 2 to be a more general call for availability for Core Component development sprints
- Has work ready on Active Fedora, but no mechanism to schedule a sprint using this Working Group
- Botimer:
- Where there is more ambiguity, push these off to gain more momentum later
- Pendragon:
- Taking ActiveFedora as an example
- Cannot perform maintenance as it does not have a code coverage measure for testing
- Need to address this first (as well as for all Core Components)
- Taking ActiveFedora as an example
- Johnson:
- Then, an initial sprint should be scheduled with addressing code coverage as the initial tickets for the sprint
- How would I proceed in doing this?
- Pendragon:
- Contact product owners instead, and then look to schedule sprints
- Otherwise, if we wait for product owners to contact us, the work might not be taken
- Armintor:
- Perhaps start with ActiveFedora, document where we find the gaps, and then proceed to reach out to less related projects?
- Pendragon:
- Looking at the spreadsheet...ActiveFedora just needs Coveralls (15 minutes)
- Johnson:
- Assumed that we follow the Product Owner's lead
- If no one shows up to own it, we propose deprecation at a later date
- Botimer:
- This could be dangerous...adversarial
- We've got volunteers for Product Owners
- But, this becomes a threat, "if you don't ask us", we don't act to assist to these volunteers
- Armintor:
- Assess what the gaps are in the project
- Send the report to the Product Owner
- We are chartered with assessing whether or not a project is supported any longer
- Assess what the gaps are in the project