hyphacoop / handbook

Member's handbook describing the vision, processes, and culture of Hypha πŸŒΏπŸ„
https://handbook.hypha.coop
Creative Commons Attribution Share Alike 4.0 International
27 stars 4 forks source link

Main handbook update list #191

Closed benhylau closed 1 year ago

benhylau commented 1 year ago

This is the list of current handbook updates found on the master branch

Legend: (U)PDATE / (K)EEP / (R)EMOVE

We should update this top post with current status of each, so once U/R items are fixed, check it.

Sections

About This Handbook

Hypha Worker Co-operative

Our Virtual Office

--

tripledoublev commented 1 year ago

On the coordination page, I removed the Making Decisions section because it was outdated but I still believe the handbook would benefit from integrating such content. Commenting on this matter as a reminder to rewrite and reintegrate the decision making process.

benhylau commented 1 year ago

TODO

Notes

benhylau commented 1 year ago

Sent PR for:

benhylau commented 1 year ago

@LexaMichaelides pls make sure these are incorporated into our onboarding documentation:

writerly03 commented 1 year ago

@benhylau pretty sure it's a mishmash from the handbook, old onboarding lists you put together (maybe to onboard me?)

writerly03 commented 1 year ago

@tripledoublev I've updated the press page content. What workflow makes the most sense? The copy is here but I can update the file directly here? https://docs.google.com/document/d/1TNOgF49csF4iVGtPN2kz_8I0rLRH_TpM089I382xAsk/edit#heading=h.ke1769r49zw8

tripledoublev commented 1 year ago

@writerly03 The workflow is described on the handbook's README.md file. You can create a branch and then do a PR to the main branch. That being said, I wonder if for such small edits, we could simply edit the file directly.

  1. Check that your local version of the main (master) branch is up to date. If not, you should pull recent changes from GitHub. On the command line you'll have to first use git checkout master and then git pull.
  2. Create a new branch: select New branch (if using GitHub Desktop) and give it a title of whatever you're planning to work on e.g., roles-page-update. On the command line you can use git checkout -b your-branch-name.
  3. Make your edits or changes using a text editor
  4. If you're using the command line, you'll have to stage changes you want to commit. You can use git add file-name to do that.
  5. Commit the change and write a summary message for that commit. If using the command line, you can use `git commit -m "your summary message"
  6. Push the changes upstream to GitHub. With the command line you can use git push
  7. Make a pull request to the master branch from your branch
  8. Assign a co-worker to review the changes
  9. Co-worker reviews and then accepts the pull request, and the update is made
writerly03 commented 1 year ago

@tripledoublev Sorry, should have been more specific in my ask - I know the process to update the file itself. Just wondering if you wanted to do something different for all these little edits since we are all making so many. But I can follow the usual process. I don't find it very intuitive and it takes me a long time so I will likely wait until later in the week to start this part.

writerly03 commented 1 year ago

Closed this issue, but it does tie in the work done on the handbook in April https://github.com/hyphacoop/organizing/issues/495

benhylau commented 1 year ago

Checked off the comp related items

tripledoublev commented 1 year ago

Checked off on/offboarding.

During this edit, I noticed a broken link for a guide on SSH Keys. It is not mentionned on the list here but was wondering if this is something we should add eventually.

tripledoublev commented 1 year ago

Closing this issue since our handbook has been through a complete rework since the creation of these tasks