Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Project Migration (VRMS Recruitment - Open Roles) #1668

Closed
13 tasks done
Tracked by #1669
JackHaeg opened this issue Jun 13, 2024 · 4 comments
Closed
13 tasks done
Tracked by #1669

GitHub Project Migration (VRMS Recruitment - Open Roles) #1668

JackHaeg opened this issue Jun 13, 2024 · 4 comments

Comments

@JackHaeg
Copy link
Member

JackHaeg commented Jun 13, 2024

Overview

We need to prepare the Project Boards for the forced migration that GitHub is doing in August, so that it is already working well for the team by then. This issue is focused on saving all of the open role cards from VRMS.

Action Items

  • copy this template to a comment below
    ### Text from project board card
    ```
    [INSERT MARKDOWN HERE]
    ```
    - [ ] Copy text above and create a new recruiting issue issue on the active VRMS project board for this post. 
      - [ ] Label the issue with "feature: recruiting new team members"
      - [ ] Label the issue with "recruiting: no" or "recruiting: yes"
    - [ ] hide this comment when completed.
    
  • copy markdown from a role card into your new comment where it says `[INSERT MARKDOWN HERE]
  • Follow this approach for all cards across all of the project boards below.
  • Review & delete card from project board?
  • Review & create individual issues for each open role on the active project board to include only the text from these cards.
  • Close issue.

Resources/Instructions

Open Role Project Boards Reviewed:

HfLA elected to use a different approach / template for open roles.

@JackHaeg
Copy link
Member Author

JackHaeg commented Jun 13, 2024

Text from project board card, Product Management Open Roles

<img src="https://www.hackforla.org/assets/images/projects/vrms.png" />

**Project Name** : VRMS (Volunteer Relationship Management System)

**About the Project:** Arguably the awesomest project in hack for la! This is a project where we plan to manage and store information about volunteers, projects, and events. This can become the reason why hack for la works.

**Volunteer Opportunity:** We need structure! We are a scrappy group of developers who are inspired but a little lost when it comes to planning.

**Responsibilities:**  We want someone to run the board, the weekly meeting, and have a clear plan for how we can make this project succeed.

**Duration:** Ongoing, 6 hours per week

**Meetings:**
- Monday 7-8pm PST (Mandatory)
- Thursday 6:30-7:30pm PST (Optional Dev Meeting) (You would not run this one)

**Who to communicate your interest to**
Slack channel [#vrms](https://hackforla.slack.com/archives/CRGH5HM0Q)
Contact Josh Bubar or Trillium Smith

- Role = Filled, NOT recruiting

  • Copy text above and create a new recruiting issue issue on the active VRMS project board for this post.
    • Label the issue with "feature: recruiting new team members"
    • Label the issue with "recruiting: no" or "recruiting: yes"
  • hide this comment when completed.
  • Added to Recruit volunteers for team open roles #1670

@JackHaeg

This comment was marked as resolved.

@JackHaeg

This comment was marked as resolved.

@JackHaeg
Copy link
Member Author

HfLA elected to use a different approach / template for open roles. ALL Open Role Updates are available here:

All of the open role descriptions have been copied to this issue above, which will serve to track open roles moving forward. Closing this issue as complete.

@github-project-automation github-project-automation bot moved this from In progress to Final QA (product) in P: VRMS: Project Board Jun 18, 2024
@JackHaeg JackHaeg moved this from Final QA (product) to Done in P: VRMS: Project Board Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant