Skip to content

Latest commit

 

History

History
61 lines (42 loc) · 2.2 KB

UPDATE.md

File metadata and controls

61 lines (42 loc) · 2.2 KB

Updtate

The project and issues are located at

In this document we essentially try to manage a CHNAGELOG as well as plan for managing high level tasks so we organize contributions.

The weekly update is due every Monday midnight EST.

Bullet form updates are requested so we can assess deliverables and reports given to outside collaborators. We docuent in reverse chronological order per week with the latest week first. We organize things per week by topic. Any update reportable to NIST is prefixed with (NIST), each contributor should have at least one report on weekly basis to NIST.

Keep in mind:

  • What have I done?
  • What have I not achieved?
  • What would I like to achieve next time?
  • What should be reported to external collaborators (NIST)?

Monday 28th Feb, 2022

  • Organizing collaborator support

    • (NIST) Meeting time does not match up with NIST, e.g. one day after NIST meeting is not workable for updates. Updates must be done Monday midnight.

    • (todo) Collaborators have set up environment

      • (update?, python, gitbash, github client, pycharm, ...)
    • (todo) Overdue items

      • install software, learn github, earn multiprocessing, showcase FastAPI example
  • Catalog Data

  • Catalog Fast API

    • (todo) collaborate with run fast transfer group on implementing start stoping services
    • (todo, gregor partially implemented) work with gregor on command line to start sto services, you find out how to do, gregor include in cms
    • (missing collaborators implement):
      • cms catalog start
      • cms catalog stop
      • cms catalog status
      • ...