Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a ReadMe #6

Closed
3 of 5 tasks
SheIsBukki opened this issue Jul 21, 2021 · 3 comments
Closed
3 of 5 tasks

Create a ReadMe #6

SheIsBukki opened this issue Jul 21, 2021 · 3 comments

Comments

@SheIsBukki
Copy link
Member

SheIsBukki commented Jul 21, 2021

Dependency

#8

Overview

We need to have a working READme file to easily onboard new team members and compile relevant information for other teams and CoPs that will interact with us.

Action Items

  • Review the readme file and identify what information is needed and applicable
  • Review GreenEarthOS repo as a guide
  • Review the project one sheet and other documentation to be used in creating content
  • Update project one sheet One-Sheet for Guides Project #8
  • Apply changes to ReadMe

Resources/Instructions

https://github.com/hackforla/guides/blob/main/README.md
Green Earth OS

@SheIsBukki SheIsBukki added this to Ice Box in Guides: Product Management via automation Jul 21, 2021
@SheIsBukki SheIsBukki moved this from Ice Box to Prioritized Backlog in Guides: Product Management Jul 21, 2021
@ghost ghost mentioned this issue Jul 21, 2021
4 tasks
@SheIsBukki
Copy link
Member Author

SheIsBukki commented Jul 26, 2021

On Reviewing the Current Guides ReadMe:

I think we don't need Installation Instructions, Working with forks and branches, Working with pull requests and reviews, and Testing. Licensing too maybe.
I don't know whether PM also have to work on Issues; bugs, features, in the same way engineering team does.

Using the GreenEarthOS ReadMe as a guide:

The GreenEarthOS readme applies better for the Guides readme. All we have to do is create a channel for Guides or share the link to the DM group. We also have to state our meeting time. I don't think we've created our Project Context for Guides, so we have to create that

@ExperimentsInHonesty ExperimentsInHonesty moved this from Prioritized Backlog to In progress (actively working) in Guides: Product Management Jul 26, 2021
@ExperimentsInHonesty
Copy link
Member

Hack for LA Guides

The Guides project seeks to create guides out of the effective practices that we have created/iterated on projects in order to share replicable processes and practices so that we can continue to grow our peer learning and iterative culture, improving outcomes for the whole ecosystem.

@ExperimentsInHonesty ExperimentsInHonesty removed their assignment Aug 16, 2021
@ExperimentsInHonesty ExperimentsInHonesty changed the title Making an Issue to Create a ReadMe Create a ReadMe Aug 16, 2021
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Aug 18, 2021

Current draft
[our logo here] WIP

Hack for LA Guides

The Guides project seeks to create guides out of the effective practices that we have created/iterated on projects in order to share replicable processes and practices so that we can continue to grow our peer learning and iterative culture, improving outcomes for the whole ecosystem.

Project context

The Guides will cover templates, how-to’s, and straightforward instructions to teach members of each communities how to

Help us write our one sheet for the project by volunteering! [insert one sheet here]

Technology used

How to contribute

  • Join the HackforLA slack workspace
  • Join the slack channel #guides and say hi! Tell us your skillset and how you're looking to contribute.
  • One of our product managers will add you to the meeting invite & the project resources
  • Join our team meetings (these are subject to change based on need, if you can't make these times but you want to be on teh team, let us know your availability on slack).
    • Monday & Wednesday 7:30-9:00 am (PDT) / 3:30-5:00 pm (WAT)
    • Friday 8:30-9:00 am (PDT) / 4:30-5 pm (WAT)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

4 participants