awesome-web-archiving/CONTRIBUTING.md

# Contribution Guidelines

Please ensure your pull request adheres to the following guidelines:

* Use the following format:
  * `[Name](link)` - Brief Description of what the module does. (Status: *Stable* or *In Development*)
* Make an individual pull request for each new item.
* Link additions should be inserted alphabetically to the relevant category.
* New categories or improvements to the existing categorization are welcome.
* Check your spelling and grammar.
* The pull request and commit should have a useful title.

Unsure whether something fits here or not? Answering these questions will help.

* Is the tool used in a formal web archiving programme?
* Does it archive or capture and preserve other people's data not just backup your own?
* Does it make use of widely accepted web archiving standards ([WARC](https://iipc.github.io/warc-specifications/), [Memento](https://tools.ietf.org/html/rfc7089), [CDX](https://archive.org/web/researcher/cdx_file_format.php), etc.)?
* Is it focused on a broader sense of web sites and web-like platforms (public, interlinked), and not on individual applications that just happen to use a browser as a runtime environment?
Fix awesome lint issues (#75) * Add license as a seprate file * Fix awesome lint issues * Update list descrition to comply with guidelines * Move deprecated items to a seprate file to comply with guidelines 2020-02-25 09:47:58 -05:00			`# Contribution Guidelines`

			`Please ensure your pull request adheres to the following guidelines:`

			`* Use the following format:`
Elaborate description and make tags italic (#90) * Elaborate on the description of the list * Make tags after description italic * Prevent a wildcard from being treated as a markdown symbol * Make list indentation consistent * Update description with inspiration from the Wikipedia page 2020-03-26 17:00:22 -04:00			* `[Name](link)` - Brief Description of what the module does. (Status: Stable or In Development)
Fix awesome lint issues (#75) * Add license as a seprate file * Fix awesome lint issues * Update list descrition to comply with guidelines * Move deprecated items to a seprate file to comply with guidelines 2020-02-25 09:47:58 -05:00			`* Make an individual pull request for each new item.`
			`* Link additions should be inserted alphabetically to the relevant category.`
			`* New categories or improvements to the existing categorization are welcome.`
			`* Check your spelling and grammar.`
			`* The pull request and commit should have a useful title.`
Add @ato's guidelines from Slack discussion. (#81) * Add @ato's guidelines from Slack discussion. * Words are hard. 2020-03-05 10:16:20 -05:00
			`Unsure whether something fits here or not? Answering these questions will help.`

			`* Is the tool used in a formal web archiving programme?`
			`* Does it archive or capture and preserve other people's data not just backup your own?`
			`* Does it make use of widely accepted web archiving standards ([WARC](https://iipc.github.io/warc-specifications/), [Memento](https://tools.ietf.org/html/rfc7089), [CDX](https://archive.org/web/researcher/cdx_file_format.php), etc.)?`
			`* Is it focused on a broader sense of web sites and web-like platforms (public, interlinked), and not on individual applications that just happen to use a browser as a runtime environment?`