<commit_before><commit_msg>contributing.md guide added<commit_after>### Contribution Best Practices

* Read this [how-to about Github workflow here](https://guides.github.com/introduction/flow/) if you are not familiar with.

* Read all the texts related to [contributing for an OS community](https://github.com/HTTP-APIs/hydrus/tree/master/.github).

* Read this [how-to about writing a PR](https://github.com/blog/1943-how-to-write-the-perfect-pull-request) and this [other how-to about writing a issue](https://wiredcraft.com/blog/how-we-write-our-github-issues/)

* If you find a problem, first ask for [help in the chat](https://gitter.im/HTTP-APIs/Lobby), then consider opening a issue.
    
* Before opening a PR be sure that all the tests pass successfully. If any is failing for non-related reasons, annotate the test failure in the PR comment.

* Any change should be PRed first in `develop`, `master` can only receive merge from develop.
    
* In general,anybody can fork the repo and start working on the fork. Once you have something done we can consider opening a branch in which different people working on the same code/project can collaborate.

* Everything should work and be tested for Python 3.5.2 and above.
    
* In general, no permission is needed to work on the code. Fork `master`, submit a PR and ask for reviewing. PR is the natural place for code comparison and corrections.
{'fraction_non_alphanumeric': 0.0868945868945869, 'fraction_numerical': 0.004985754985754986, 'mean_word_length': 4.109090909090909, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 5, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4475716', 'n_tokens_mistral': 389, 'n_tokens_neox': 377, 'n_words': 179}