test markdown converter

[ExperimentsInHonesty]

Overview

REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less.

Action Items

REPLACE THIS TEXT -If this is the beginning of the task this is most likely something to be researched and documented.

REPLACE THIS TEXT -If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task.

Resources/Instructions

https://workspace.google.com/marketplace/app/docs_to_markdown/700168918607

[ExperimentsInHonesty]

What you can do if you witness police abuse or brutality

Over the past decade, witnesses and camera footage have played a pivotal role in exposing police brutality. But for many youth, the risks of intervening still carry great weight.

• As long as the events are plainly visible in public, you have the right to observe. You have a right to record the police as long as you are not interfering with the discharge of their law enforcement duties.¹

  • Stand at least 6 feet away from them), and
  • Use your device to record what is happening.

• Do not hide the fact that you are recording, and keep your phone close to your body around chest level. Holding your phone out makes it easier for law enforcement to grab.

• To enhance your privacy, disable the face or fingerprint ID to unlock your phone, and use a passcode with six or more digits.

  • Police officers do not expect privacy when doing their job, but the people they interact with may have privacy rights that require you to notify them of your recording. In many states (see here) you must make people aware that you are recording them.

• Without a warrant, police can’t keep your recording device.² They can’t demand to see or delete your photographs or videos under any circumstances.

• While you are recording, you may be asked to stop or hand over your device. If so, simply remind the police officer of your First Amendment right to take photographs or videos in public, and politely but firmly refuse consent. Note that some officers may unlawfully arrest you for refusing to comply, so decide whether to take this risk.

• Write down as many details as possible. You may be able to contact the person stopped afterwards, and your information could help if they file a complaint. Be sure to include:

  • How many officers were present
  • Their names
  • Their badge and patrol car numbers
  • Where they were from
  • Any use of weapons (including tasers or batons)
  • Any injuries suffered by the person they stopped

• It may take time to heal after witnessing a traumatic event. Allow yourself to process and reach out to friends, family, and medical professionals for ongoing support.

Last updated on June 23, 2022

Notes

Footnotes

1. https://www.aclu.org/know-your-rights/stopped-by-police/ https://www.aclu.org/issues/free-speech/photographers-rights/filming-and-photographing-police; https://www.aclu.org/press-releases/aclu-california-releases-tool-hold-law-enforcement-accountable ↩

2. Riley v. California, 573 U.S. 373, 401 (2014). ↩

[ExperimentsInHonesty]

---

title: Supporting Your Automation with Community
description: To save time and provide a consistent experience, we have default health files for you to customize
status: active
display: true
category: 2

At 100 Automations, we’re committed a building a strong community who shared value is reduction of repetitive work -- whether that is from not having to write code more than once or answer the same question more than once for a lack of documentation.

Additionally, we seek to reduce the amount of time that individual authors will have to spend to properly monitor the people using and contributing to these automations by creating a shared support space, which you’ll see referenced in the contributing, support, and security files.

100Automations wants to list your automation. In order to do that your automation needs to have the following files:

• CONTRIBUTING.md
• SECURITY.md
• SUPPORT.md
• README.md
• LICENSE
• CODE_OF_CONDUCT.md

CONTRIBUTING.md

The contributing.md file communicates how people should contribute to your project.

Include the type of contribution you’re looking for. For example:

• maintenance
• refactoring
• peer review
• advice
• coding

Template:

• Default CONTRIBUTING.md{:target="_blank"} file from our template repository

Example from a project:

• https://github.com/100Automations/true-github-contributors/blob/mixin/CONTRIBUTING.md

Additional resources:

• GitHub guide: Setting guidelines for repository contributors{:target="_blank"}

SECURITY.md

The security.md file tells how people can safely report a security vulnerability in your automation.

Template:

• Default SECURITY.md{:target="_blank"} file from our template repository

Example from a project:

• https://github.com/100Automations/true-github-contributors/blob/mixin/SECURITY.md

Additional resources:

• GitHub guide: Adding a security policy to your repository{:target="_blank"}

SUPPORT.md

The support.md files lets people know how to get help implementing your automation

Template:

• Default SUPPORT.md{:target="_blank"} file from our template repository

Example from a project:

• https://github.com/100Automations/true-github-contributors/blob/mixin/SUPPORT.md

Additional resources:

• see GitHub Adding support resources to your project{:target="_blank"} tutorial

README.md

Usually the first place developers look, so it should be fairly comprehensive with links to the other health files.

Guide:

• 100 Automations Guide: Creating a Good Read.me for Your Automation{:target="_blank"}

Template:

• Default README.md{:target="_blank"} file from our template repository

Example from a project:

• https://github.com/100Automations/true-github-contributors/blob/mixin/readme.md

Additional resources:

• see GitHub's guide: https://docs.github.com/en/free-pro-team@latest/github/creating-cloning-and-archiving-repositories/about-readmes

LICENSE

We recommend GNU 2.0

Template:

• Default LICENSE{:target="_blank"} file from our template repository

Example from a project:

• https://github.com/100Automations/true-github-contributors/blob/mixin/LICENSE

Additional resources:

• see GitHub Adding a license to a repository{:target="_blank"}

CODE_OF_CONDUCT.md

Your new repo will contain a Code of Conduct file.

You just need to add your project name. Please do not edit any other details. If you have suggested revisions, please let us know by opening an issue{:target="_blank"}.

If importing your automation from your own repository, add our default Code of Conduct{:target="_blank"}

Template:

• Default CODE_OF_CONDUCT.md{:target="_blank"} file from our template repository

Example from a project:

• https://github.com/100Automations/true-github-contributors/blob/mixin/CODE_OF_CONDUCT.md

Additional resources:

• See GitHub Adding a code of conduct to your project{:target="_blank"}