Skip to content

Create guidelines for volunteer staffers to start having access to resources and assets such as email, zoom, etc. #202

Open
@rcscastillo

Description

@rcscastillo

Required Information

Description

Build guidelines and necessary process structure for volunteers to gain access. This proposal aims spark a conversation within the volunteer staff team on how best to proceed gaining access for specific assets and resources. This is an iteration of #193.

The aim is to provide a clear accountability and transparency structure to providing resources to our community members.

For the process of providing resources, the first step could be a request for a progcode email. Then it could be a per-tiered approach (eg. volstaff interested in community will have access to calendly (one-on-one), and other resource sets), comms team would get access to hootsuite/actionsprout/CRMs etc, and partnerships could get access to calendly as well.

Another level could be done when accessing private information about members (eg. member vetting) which would need added consent to the once currently holding that information.

Problem

Right now, there is no clear guideline on how to provide assets and resources to empower volunteer staffers. We need to have a clear, transparent, and accountable process that will enable people who want to contribute become better members.

Benefit

This will provide more accountability and transparency in the process, safeguard private information with the high level of trust, and expand our volunteer staffer base to the targeted 15 members.

Plan

  • Consent to continue
  • @rapi-castillo to provide a list of resources alloted to which volunteer staff member, to give a clear view of which resource is now alloted to what.
  • Schedule discussion
  • Collaboratively build the guideline from the discussion
  • Start another issue for the implementation of the guideline/

Decision Making

On this stage, consent-to-continue

Optional Information

Reference link(s)

...

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions