hackforla / YouthJusticeNav

A project with UCLA law school to help defendants in the Juvenile Justice system in Los Angeles County
GNU General Public License v2.0
1 stars 2 forks source link

test markdown converter #123

Open ExperimentsInHonesty opened 1 year ago

ExperimentsInHonesty commented 1 year ago

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 commented 1 year ago

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.

Last updated on June 23, 2022

Notes

[^1]:

 [https://www.aclu.org/know-your-rights/stopped-by-police/](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/issues/free-speech/photographers-rights/filming-and-photographing-police); [https://www.aclu.org/press-releases/aclu-california-releases-tool-hold-law-enforcement-accountable](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 commented 1 year ago

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

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

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

Template:

Example from a project:

Additional resources:


SECURITY.md

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

Template:

Example from a project:

Additional resources:


SUPPORT.md

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

Template:

Example from a project:

Additional resources:


README.md

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

Guide:

Template:

Example from a project:

Additional resources:


LICENSE

We recommend GNU 2.0

Template:

Example from a project:

Additional resources:


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:

Example from a project:

Additional resources: