hackforla / hackforla/guides

Issues We Need to Make

Open
#54 2 comments 0 reactions 1 assignee Claimed by @carolzjy View on GitHub
feature: administrative role: Product size: 2pt
Dominant language
No language data
Stars
12
Forks
0
PR merge metrics
No merged PRs in 30d

Description

### Overview
We need to make issues so that we can achieve our milestones.

### Action Items
- [x] List out all milestones
- [ ] Identify if there is an issue missing that is referenced in our Objectives spreadsheet
- [ ] Identify if there is an issue missing that is logical even if not referenced in our spreadsheet
- [ ] Make sure to breakdown any issues that will be too large on their own, and can be broken down.

### Issues to make (this is being updated)
Milestones:
1. Compliance
2. Security
3. Project Management
4. New Guide Instructions
- Project landing page
- [ ] #55
- [ ] #62
- [ ] #63
- Basic guides stable: Break down #14 into smaller issues
- write a guide
- insert screenshots and images
- Basic templates stable: Break down #14 into smaller issues
- guide
- image

5. Format Standardization
- Edit all the guides to match the format:
- [ ] Finish all existing ["Cleanup Guide Template:" issues](https://github.com/hackforla/guides/issues?q=is%3Aissue+is%3Aopen+Cleanup+Guide+Template+milestone%3A%2205.+Format+Standardization%22)
- [ ] Confirm all existing guides match new format
- Once stable, confirm completion by cross checking the folders and the issues: ?

6. CoP Coordination
- Conduct interviews to determine their current process: Conduct interviews with CoPs on the topics below
- [ ] #64
- Review the guides to see how they fit into their CoP roadmap
- Learn their sentiments about the guides, tracker, and project landing page

7. Tracker Requirements
- Acting as a manual tracker: ?
- Define requirement for an automated tracker
- [ ] Gather requirements for automated tracker #43

8. Document Processes
- Draft landing page that defines each step of ideation to publication
- [ ] #65
- [ ] #66
- [ ] #67

9. Automate Processes
- Create Automations:
- [ ] #68
- [ ] #69

10. Feedback Instructions
- Published landing page
- [ ] Gather requirements for landing page
- [ ] Gather/ edit content for landing page
- [ ] Create a draft mvp page

11. Revision Instructions
- Project landing page
- [ ] Gather requirements for landing page
- [ ] Gather/ edit content for landing page
- [ ] Create a draft mvp page
- Create a defined path to edit guides
- [ ] Define path for editing guides

12. Publication
- Stable guide templates: ?
- Have at least 10 finished guides before publishing: ?

13. Credit
- Credit on the guide: ?
- LinkedIn
- GitHub
- Others
- Authors should be able to link to guides from external platforms: ?
- from author's LinkedIn
- Publish on external websites
- Others

14. Incent creation/completion
- Research into the motivations of the people who created guides already
- Research into the motivations of people who have not created any guide
- Learn how they want to be credited or otherwise incentivized
- Tracker
- Project landing page
- Credits

15. Incent draft feedback/editing
- Research into the motivations of people who have edit guides
- Research into the motivations of people who that have not edited any guide

16. Incent publication feedback/editing
- Research into the motivations of people who have edit published guides
- Research into the motivations of those who have not edited any published guides

### Resources/Instructions
REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.