DRAFT: Issues to create by developers

[JessicaLucindaCheng]

Thank you for wanting to help us write an issue! Before writing an issue, please read How to create issues.

Instructions

1. Look through the issues that need to be written up below and pick one to create/write up. If you have questions, please contact the person who wrote it through Slack.
2. In the Issue creator/writer field under the Issue Creation section, put @ and your Github Handle and click the "Update comment" button. For example,
   Issue creator: @JessicaLucindaCheng
3. Add your Availability and ETA for writing this issue.
4. Follow the instructions for How to create issues
   4.a. Add a points label to the issue you created. A point is a time estimation for how long you think it will take to complete an issue. 1 point is equal to 6 hours of work.
5. When you are done writing the issue, fill in the Issue # with the number on the issue you created. For example,
   Issue #2676

Resources

• How to create issues
• How to read and interpret labels
• How to add a label

[JessicaLucindaCheng]

To Dos for Jessica:

• Add instructions for someone using a template
  • Should add instructions to pre-check if an issue exists before adding it to this list of issues to create.
• Try to make it similar to the one for pms/devs meeting template
• Add instructions for how to add Slack id/link: Example: https://hackforla.slack.com/team/U02NWK24H3N
  • Should I do it with name? Example: Jessica Cheng
• Should I include a field with ETA and Availability for the Issue creator/writer?

TEMPLATE FOR A PROBLEM

If you have questions about this problem, contact (Your Slack Name)[https://hackforla.slack.com/team/put-your-member-id-here] through Slack.

### What is the problem? (In one or two sentences.)

### Link(s) to the problem (if any): Link to website pages. For GitHub Action problems, a link to the pull request or issue where the problem was seen. 

### Screenshots of problem
### Slack for person adding issue to be created: https://hackforla.slack.com/team/put-member-id-here
<details>
  <summary>Screenshot(s) of the problem</summary>
  Drag and drop image(s) here
</details>


### Issue Creation (below is for the person creating and writing up the issue formally to fill out)
- Issue creator: @ issue writer's GitHub handle
- Issue #write issue number here
- Availability:
- ETA for writing this issue:

---

TEMPLATE FOR OTHER ISSUES TO BE CREATED

If you have questions about this problem, contact (Your Slack Name)[https://hackforla.slack.com/team/put-your-member-id-here] through Slack

### What issue needs to be created? (In one or two sentences.)

### Link(s) (if any):

### Screenshots (if any)
<details>
  <summary>Screenshot(s)</summary>
  Drag and drop image(s) here

</details>


### Issue Creation (below is for the person creating and writing up the issue formally to fill out)
- Issue creator: @ issue writer's GitHub handle
- Issue #write issue number here
- Availability:
- ETA for writing this issue:

[JessicaLucindaCheng]

Closing this issue because we aren't going to implement this.

[ExperimentsInHonesty]

@SAUMILDHANKAR

[ExperimentsInHonesty]

@JessicaLucindaCheng

[ExperimentsInHonesty]

test

[github-actions]

Hi @JessicaLucindaCheng, 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 :)