hackforla / hackforla/admin-calendaring
Feasibility of Slack Audit being separated from rest of Calendar audit
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### Dependency
- Make size and any other labels this requires
### Overview
Determine feasibility of separating the slack audit from the main calendar audit
### Action Items
- [x] Define steps it would take
- [x] Review feasibility (we determined YES)
- [ ] If feasible, make new repo
- [ ] move this issue to the repo
- [ ] Make issues from comments in the repo
- [ ] Move resource `Update Slack channels` to new repo wiki
- [ ] Review this page https://github.com/hackforla/admin-calendaring/wiki/Cancel-a-meeting-permanently and update any Slack guidance
### Resources/Instructions
- [Slack Channel Audit Folder](https://drive.google.com/drive/folders/1zdou4SbtPGiK5TxJaWvDJmsWN5jRy5NS?usp=share_link)
- [Slack Channel Audit](https://docs.google.com/spreadsheets/d/1VhuLsQvnIBI8lRpom5hCLcWgjj9J8t3q-fnFxDiNVyo/edit#gid=0)
- [How to Set Reminders in Slack](https://drive.google.com/file/d/1amE3moiLQaHCqErJlrBMhqnioXdq0SUq/view)
- [Update Slack channels](https://github.com/hackforla/admin-calendaring/wiki/Update-Slack-channels)
Contributor guide
Research direction
Start by reviewing the issue checklist, the Update Slack channels wiki page, and the Cancel a meeting permanently page. Confirm the remaining repository and documentation tasks, then verify that the issue is moved, comment-derived issues are created, the resource is in the new wiki, and Slack guidance is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100