My work schedule for 8-9/2022

The NLNet funding from 2020 is still available, until October 1. I don’t know whether I’ll be looking for more funding after that, but for these 2 months, my (optimistic plan) is as follows:

  • July 31 – August 6: Preparations for working on the funded tasks:
    • Remove “Create” flow from Vervis code
    • Finish research on code review systems
    • Decide if patch trackers will handle ticket features
    • Finish coding Vervis new route system
  • August 7 – August 20: Object Capabilities (S17 & V12)
  • August 21 – September 3: Authorization, roles, groups, permissions (S11 & V11)
  • September 4 – September 17: Opening merge requests (S2 & V3)
  • September 18 – October 1: Merge request lifecycle (S6 & V6)

It’s a tight schedule and I’m okay with not completing everything on time, but I do expect to finish at least half of the funded tasks :slight_smile:

Current Status (as of September 17)

  • Preparations for working on the funded tasks
    • Remove “Create” flow from Vervis code: done
    • Finish research on code review systems: done
    • Decide if patch trackers will handle ticket features: done
    • Finish coding Vervis new route system: almost done, need to test DB migrations and deploy
  • Object Capabilities (S17 & V12): DONE, RfP approved by NLNet
  • Authorization, roles, groups, permissions (S11 & V11): THE CURRENT TASK, mostly done in spec, but not implemented
  • Opening merge requests (S2 & V3): ALSO CURRENT TASK, mostly done in spec, almost done with basic implemention but no UI because most Vervis UI is temporarily disabled due to big changes in its core; Working on re-enabling enough UI to have a demo of opening a MR
  • Merge request lifecycle (S6 & V6): WIP, basic merging implemented, but very unlikely to finish this before October
4 Likes