search

hackforla / knowledgebase-content

GNU General Public License v2.0
0 stars 0 forks source link

Guide: Picking the work you do at HfLA #57

Open daniellex0 opened 3 years ago

daniellex0 commented 3 years ago

Overview

We need to create a guide for picking the work you do at HfLA so that you get what you need for your goals and so that you help the community

Action Items

The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.

Projects to Check

Tasks

ExperimentsInHonesty commented 6 months ago

This issue needs a link to the issue template for experience profile and guidance for how to find issues for items that they don't yet have experience with, by looking at the project boards and issues.

ExperimentsInHonesty commented 6 months ago

This issue would be helped by having all the teams at HfLA add labels to their issues with the type of work that the issue contains. We are working on developing that set of issue labels and will be rolling it out on the website team on behalf of the internship project at some point. But it's not a near term goal. We expect it to take 12 months to deliver it just for developers, and even more time to roll it out for research and design.

JesseTheCleric commented 1 week ago
Prior version of issue

### Overview We need to create a guide for picking the work you do at HfLA so that you get what you need for your goals and so that you help the community. ### Action Items - [ ] Gather examples of how other Hack for LA projects or volunteers have done this (if applicable), adding each example as a link in the resources section below - [ ] If the guidance you received from the teams that have done this practice was not sufficient, remove the "Guide: Gather Examples" label and add the "Guide: Research" label - [ ] Research existing information about [name of item] in [relevant resources, articles, etc.] - [ ] Once done, evaluate if the guide requires a template. If it does then - [ ] if yes, remove the "Guide: Research" label and add the "Guide: Draft Template" label - [ ] Create a draft template - [ ] Once done, remove the "Guide: Draft Template" label and add the "Guide: Draft Guide" label - [ ] if no, remove the "Guide: Research" label and add the "Guide: Draft Guide" label Create a draft guide, either in markdown format in this issue or a google doc in the [ux/ui google drive](https://drive.google.com/drive/u/1/folders/1os-4KyGnL0SXIeyfoDICOEpG5CO_1MaV) - [ ] Once done, remove the "Guide: Draft Guide" label and add the "Guide: Needs Peer Review" label - [ ] Review the guide with UX/UI community of practice - [ ] Once done, remove the "Guide: Needs Peer Review" label and add the "Guide: Leadership Review" label - [ ] Present to the Hack for LA leadership team for sign off - [ ] Once approved, remove the "Guide: Leadership Review" label and add the "Guide: ready publication" label ### Resources Update issue hackforla/UI-UX#15 with the name of item you are working on #### Details that should be in the guide - filling skill gaps - solidifying by teaching others - making guides and or articles to show mastery - communicating to your project lead that you want more challenge if the work is to easy - choose the project whose phase is right for you. e.g. need a portfolio item? - is topic area of project actually important to your career.

JesseTheCleric commented 1 week ago
Assignee, Labels, Project Board Placement, and Milestones for this issue in the UI/UX Repo:

image