After reading the HumanOps.rst text some some comments come to my mind so I decided they are worth sharing with you all in order to update the contents, if you might so.

I believe that not only "Humans impact systems" but also that "Systems impact humans" as well. As a matter of fact, I'd better say Being part of systems impact on humans, which is. in fact, the main reason behind all this HumanOps concept, if I am not wrong.

That is why the explicit text of the document sounds a bit contradictory to me since, in one hand, it is said that humans are part of the system (point 1) and, on the other hand, that the interaction between human operators and the system goes both ways... (point 2), which implicitly considers both, systems and humans, as separate entities.

I feel some clarification is in order here, do you agree?

Hi! I just noticed that your site has a link to submit to github:

https://github.com/HumanOps/HumanOps/blob/master/links.rst

and I believe it should be

https://github.com/HumanOps/HumanOps/blob/master/links.md

Thanks! Also love the idea of this project :)

Hello,

I have just came across HumanOps from Reddit. I love it's message and will certainly reference it in the future. It's a great and simple resource which needs to continue exist for the software industry, Hopefully we can work on picking up the meetup scene as we come out of the pandemic and surely the pandemic can actually be a rich canvas for the importance of HumanOps.

I have just been reading across the repositories and found a few things that would be good to clean up. These things I hope can combine to make things slightly simpler, more digestible and therefor more impactful. I don't want to change the core message of anything. Just spruce things up a bit.

I see that there haven't been any changes in a few years but hoping someone can pick these up. I will try to do some digging and reach out if i'm unable to get a response.

Changes requested

• HumanOps GitHub Organisation link to HTTPS as default.

• Use the HumanOps Logo for the GitHub Org!

• Prune branches and close GitHub Issues across all repositories.

• Swap to main branches couldn't hurt. Feels more modern.

• It would be good to implement some type of owners file. So, it is clear that the project has maintainers and who they are.

• It is unclear which website is in-use from the 2 'site' related repositories. It would be good to put a deprecation notice in the readme of one and use repository archive feature of github. https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository - HumanOps/site#26

• The principles in the HumanOps repository and the website should be aligned. I can see that things are explained a little bit more in the HumanOps md/rst. But I think the website should be a subset of this. So, the problem, aims and mantra from the site should also be included exactly as written in the HumanOps repo. I'm not proposing any re-architecture or automation or anything like that. Just to manually keep the 2 things exactly in-sync. In support of this I am raising minor changes to the site and HumanOps repo to align.

• #13 - PR for alignment. This aligns the content as described above without taking anything anything meaningful away I believe. The language is sometimes a bit more snappy and it's wrote all from one perspective in one way (because it's been edited by one person). It addressed an issue raised long ago around where they had some confusion around impacting the system and being part of the system (#10). Taken out the .rst for .md. Consistently use ampersands. Soften words like 'eliminate' to be more accurate. Consistent use of 'systems' instead of infrastructure in some places. Brought alignment between the "mantra" and the "principles" sections and the website because that was a bit confusing. Ensure all links work and only https links accepted. Hopefully you can see that the important stuff is all consistent and this all just makes sense!

• HumanOps/humanops.com#3 - PR for corresponding simple content changes to website.

I'd be very much interested in committing to maintain if possible because I see the resource should basically stay as-is only be open to minor changes and (for example) be responsive to link additions if people wish.

Again, thank you very much for this resource!

I would love to translate the texts to Spanish. How do you want to handle translations?