website
website copied to clipboard
hackforla
Wiki: Research Plan Review: Impact Page Research
Overview
We need to make all the research pages in the wiki uniform so that we can determine what is missing and what next steps are
Action Items
- [x] Review the Impact Page Research page of the wiki to make sure it has the correct format
- [x] Add any titles that are missing (see template below)
- [x] Move content into the correct categories
- [x] Order the items the same way that they exist in the format template
- [x] Take Inventory of Assets
- [x] Name of Research
- [x] Research Date:
- [x] Current Status
- [x] Outstanding task items
- [x] Research Plan (including Audience Identification documentation)
- [x] Scripts
- [x] Interview recordings & Transcripts
- [x] Synthesis (Miro or Figjam)
- [x] Presentation of Findings
- [x] Action Items Spreadsheet
- [x] Check to see if there are more assets or assets (in the Google drive) from related research that are needed on this page, and add them
- [x] Evaluate all the research assets and summarize the status of the research under "Current Status"
- [x] List out next steps under "Outstanding Task Items"
Resources/Instructions
Format for wiki page
# [Name of Research]
## Research Date:
## Summary of Research
### Question
### Purpose
### Methods
## Current Status
## All Issues
- Label: [Feature: RP ]()
## Outstanding task items
## Assets
### Research Plan (including Audience Identification documentation)
### Scripts
### Interview recordings & Transcripts
### Synthesis (Miro or Figjam)
### Presentation of Findings
### Action Items Spreadsheet
---
The last review was completed by _name_____ on ___date____ on issue [#](https://github.com/hackforla/website/issues/____)
---
### Related Wiki Pages
- [Research Home page](Research)
Hi @sacamp.
Good job adding the required labels for this issue. The merge team will review the issue and add a "Ready for Milestone" label once it is ready for prioritization.
Additional Resources:
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @vaisali89, thank you for taking up this issue! Hfla appreciates you :)
Do let fellow developers know about your:- i. Availability: (When are you available to work on the issue/answer questions other programmers might have about your issue?) ii. ETA: (When do you expect this issue to be completed?)
You're awesome!
P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :)
@vaisali89
Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.
- Progress: "What is the current status of your project? What have you completed and what is left to do?"
- Blockers: "Difficulties or errors encountered."
- Availability: "How much time will you have this week to work on this issue?"
- ETA: "When do you expect this issue to be completed?"
- Pictures (optional): "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.
You are receiving this comment because your last comment was before Tuesday, August 2, 2022 at 12:20 AM PST.
@vaisali89
Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.
- Progress: "What is the current status of your project? What have you completed and what is left to do?"
- Blockers: "Difficulties or errors encountered."
- Availability: "How much time will you have this week to work on this issue?"
- ETA: "When do you expect this issue to be completed?"
- Pictures (optional): "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.
You are receiving this comment because your last comment was before Tuesday, August 9, 2022 at 12:20 AM PST.
@vaisali89
Please add update using the below template (even if you have a pull request). Afterwards, remove the 'To Update !' label and add the 'Status: Updated' label.
- Progress: "What is the current status of your project? What have you completed and what is left to do?"
- Blockers: "Difficulties or errors encountered."
- Availability: "How much time will you have this week to work on this issue?"
- ETA: "When do you expect this issue to be completed?"
- Pictures (optional): "Add any pictures of the visual changes made to the site so far."
If you need help, be sure to either: 1) place your issue in the developer meeting discussion column and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel.
You are receiving this comment because your last comment was before Tuesday, August 16, 2022 at 12:21 AM PST.
@vaisali89 The following seems like it makes sense
- name of the research: Impact Page Research (on this issue)
- Name of wiki page: Research 7 : Impact Page Research
- URL of wiki page: https://github.com/hackforla/website/wiki/Research-7-:-Impact-Page-Research
- Google Drive: R007: Impact Page Research
But then the labels for it do not (no issues tied to label)
- label for RP7: Best Practices for Non Profit
- Impact research label: RP009
- [ ] rename label RP007 to Impact Page Research
- [ ] rename label RP009 to Wins Page Research
- [ ] make a new label for Best Practices for Non Profit
- [ ] add the RP007 label to this issue
- [ ] add the link to all issues that use the RP007 label into its wiki page
- [ ] Check all the issues labeled research that do not have an RP label already assigned, to see if they are connected to this issue.
- [ ] add RP[replace with number] to this issue and any issues that need it
