cu-mkp/m-k-manuscript-data

create roadmaps for project priorities

njr2128 opened this issue · 2 comments

see for example https://test.zenodeo.org/roadmap

make use of milestones?

  • assemble feature requests
  • estimate when they can be completed (lots of variables - complexity, people, availability, code decencies, personnel dependencies, etc.)
  • prioritize/rank them
  • assign to specific milestones

This is actually on two levels:

  1. For each project / repo
  2. For M&K as whole (related to #2050)
  • Edition build
  • Google Credits
  • Sandbox - content strategy already (editorial protocol, where stuff is) implemented, but need to mature design (big need -- CSS, Javascript, HTML5) + organization (summer 2022 URF work)
  • Architecture infrastructure of M&K and DevOps (maintenance of AWS S3 and Cloudfront, voyant server, DigitalOcean droplets, reclaimhosting?, Github) -- skills needed are cloudcomputing operations

  • long-term project support and maintenance
    • cost projections -- identify and estimate costs for critical assets and infrastructure (Flickr, vimeo, AWS)
    • Archiving + Lifecycle strategy and implementation (how do we sunset or archive parts of the Project)
      • Fieldnotes
      • issue tracker archive
      • depositing of assets in AC
      • M&K wordpress site (summer 2022 URF and Caroline)
    • what does not (or cannot) get handed over to the Libraries?
    • funding and governance scenarios (responsibility identification)