Make engineering pre work issue template

[SAUMILDHANKAR]

Overview

Need a pre work template so new people can know how to make a new issue and know what to do when they first arrive

Action Items

• Write a draft in comments of new template
• Ask team members for advice on what should go in template

Resources/Instructions

Contributing
Site architecture

[ExperimentsInHonesty]

from the ui/ux prework template

Overview

Fill in the following fields as you work on these items on the Hack for LA website project. Add the link of the items you worked on in the list as examples.

Onboarding Action Items

• Join UX/UI Github and Google Drive
• Set up 2FA on Github and mark HfLA membership public
• Read the guide for using our Github Kanban boards (working draft)
• All Hack for LA teams use Figma for our collaborative design. New to Figma? Learn more: Figma for Beginners videos 1-4
• All Hack for LA teams generally work in an Agile framework. Read more about Agile and how it relates to Kanban HERE.

[ExperimentsInHonesty]

Review with team what has been written so far and see if they recommend other items

[ExperimentsInHonesty]

Link to see the board by Good First Issue and the Prioritized backlog column is highlighted
Link to see the board by Good Second Issue and the Prioritized backlog column is highlighted

[ExperimentsInHonesty]

This came from the BOP project

Reporting progress

• Be sure to check the box when you finish an action item.
• Report your progress weekly in a comment below using the following format:
  • Progress:

  • Blockers:

  • Availability
:
  • Estimated date of completion:

Stopping mid issue


Reasons:

• Got personally busy, can’t finish
• 
Only want to do a specific type of task per interview
• There is a blocker in the way of finishing and I still have time to work on other issues


What to do if you have to stop working mid issue:

• Note your progress in the checkboxes
• Add a note in the comments with details
• Move the issue to the questions/review column


Unassigning yourself from this issue

If you are finished with one of the 4 Action Items and you are not going to do the next one

• Move this issue from the ‘In progress’ to the ‘Prioritized Backlog’(see animated GIF below)
• Unassign yourself from this issue (see animated GIF below)

Resources/Instructions

Assign & Unassign yourself to this issue

Move this issue from the ‘Prioritized Backlog’ to the ‘In progress’ & back

[ExperimentsInHonesty]

provide guidance that the only thing on the board new developers and designers need to pay attention to are

Developers & Designers
Prioritized Backlog
In Progress

Developers
Pull Requests

Once a developer has had their good first issue and good second issue PRs approved then they can look at the "PR Needs review (Automated Column, do not place items here manually)" column to find good first issues
good second issues

[github-actions]

@abuna1985

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "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, September 28, 2021 at 12:02 AM PST.}

[abuna1985]

Working Example

Overview

This template will provide steps to set up your development environment and begin contributing to the Hack for LA Website team

Action Items

• Go to the Contributing.md document - https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md
  • Complete Step 2: Installing Git
  • Complete Step 3: Fork the repository
  • Complete Step 4: Clone the forked repository
  • Complete Step 5: Set up Docker
  • Complete Step 6: Build and serve the website locally
• Claim your first issue
  • Go to the Project Board
  • [ ]

Resources/Instructions

[abuna1985]

Closing this issue. Decided to add all of the information into our Contributing Document

https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md

[ExperimentsInHonesty]

UI/UX prework issue #2360

[github-actions]

@abuna1985

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.

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures: "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, October 26, 2021 at 12:03 AM PST.}

[abuna1985]

@ExperimentsInHonesty Engineering pre-work issue template has been created.

@macho-catt I would present the pre-work issue template to the team on Tuesday for feedback. I would also have someone present it to Bonnie on Sunday.

[ExperimentsInHonesty]

review this with the developers to see if they think anything is missing
Issue: Pre-work Template - Developers

Notes for improvement

• remove the role label being automatically added
• add an action item to add the role label.

[macho-catt]

Template has been updated, should be ready to close unless there are additional points to add