Requirements draft: volunteer management

Working groups Admin and Tech Working Group
1

After conversations with @Lai we have identified that we need a solution to ease the management of volunteers.

This is an early draft of the requirements for this software.

MUST:

  • Have user and access management
  • Allow the CRUD (1) of resources (2)
  • Allow the CRUD of roles assignable to resources
  • Allow the CRUD of states assignable to resources (eg. to be contacted / confirmed / etc)
  • Allow the CRUD of “time slots” with different states assignable to resources
  • Visualisation of the time slots as a timesheet

(1) Create / Read / Update / Delete
(2) Volunteers will be managed as resources for the purposes of the solution (to avoid confusion between volunteers as users and volunteers as resources with their different roles)

1 Like
2

The first iteration of this project is already committed in the Cooperation Birmingham Github group, please request access on the following thread to contribute: https://testing.forum.cooperationbirmingham.org.uk/t/code-repository-on-github/

A CI/CD pipeline to Digital Ocean droplets have been established using webhooks from the GitHub repos so I guess commits to master branch should be restricted (gotta look into that).

Backend is deployed here: https://api-coop.carlosgm.com/
Frontend is deployed here: http://161.35.32.90/

(Both URLs are temporary)