Volunteers/Volunteer Roles

From Noolaham Foundation
< Volunteers
Revision as of 11:00, 27 June 2020 by Natkeeran (talk | contribs) (Natkeeran moved page Volunteers List/Volunteer Roles to Volunteers/Volunteer Roles over redirect)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

All of Noolaham Foundation's concerns and activities are organized as processes and projects as noted above. Volunteers are welcome to contribute at all levels respecting accountability, reporting and communication procedures outlined in this manual. Specially, volunteers contribute via the following roles:


Process/Project/Chapter Volunteer
Process/ Project Volunteers support Noolaham Foundation’s various processes and projects that range from digitization to writing software, from contributing content to help organize an event. Process/Project Volunteers at all times and at all stages of the process/project shall work in collaboration with the Noolaham Foundation staff. Volunteers and staff from different offices, regions and countries work together as a team. All progress and updates related to the particular process/project should be transparent and be communicated to the entire team through the respective email thread and/or Slack.

Volunteers affiliated with a particular Noolaham Chapter form the volunteer team for that Chapter.

Process/Project Affiliated Advisor
Experienced volunteers who can provide advice/consultation regarding a specific Noolaham Foundation’s project/task, i.e. reading palm leaf manuscripts and providing advice to contextualise and create quality metadata.

Project/Process Mentor
Process/Project Mentors or Co-Mentors provide an ongoing oversight and guidance for process and projects. Sector Manager (staff), and Project/Project Mentors/Co-Mentors form the leadership team for a process or project. They supplement and support the staff and volunteers capability. Process/Project Mentors should not do job assignments or change priorities without consulting the Chief Program Officer. All progress and updates related to the process/project should be transparent and be communicated to the entire team through the respective email thread and/or Slack.

Governance Board Member
Contributes to the Governance Board as described in the Governance Board section above.