Update CONTRIBUTING.md

Author: geritwagner

CONTRIBUTING.md

@@ -7,47 +7,6 @@ You can contribute in many ways:
 
 ## Types of Contributions
 
-### Report duplicate error (FP or FN)
-
-Provide the case in the following format, allowing us to add it to the `tests/test_cases.json`:
-
-```json
-{
-    "id": "abrahao_parigi_gupta_cook_2017_pnas_short_vs_full",
-    "note": "Same paper; record_b uses abbreviated author formatting and omits venue fields; record_a includes DOI.",
-
-    "record_a": {
-        "ENTRYTYPE": "article",
-        "ID": "1",
-        "doi": "10.1073/PNAS.1604234114",
-        "author": "Abrahao, Bruno and Parigi, Paolo and Gupta, Alok and Cook, Karen S.",
-        "title": "Reputation offsets trust judgments based on social biases among Airbnb users",
-        "journal": "Proceedings of the National Academy of Sciences",
-        "number": "37",
-        "pages": "9848--9853",
-        "volume": "114",
-        "year": "2017"
-    },
-    "record_b": {
-        "ENTRYTYPE": "article",
-        "ID": "2",
-        "author": "B. Abrahao; P. Parigi; A. Gupta; K. S. Cook",
-        "year": "2017",
-        "title": "Reputation offsets trust judgments based on social biases among Airbnb users"
-    },
-
-"expected_duplicate": true
-}
-```
-
-### Fixing duplicate errors
-
-All changes to deduplication logic (`prep`, `sim`, `match`) should be accompanied with a test case in the pull request.
-
-TODO:
-- before merging, the ldd-full tests should be run to determine how the changes affect overall performance. (TBD: locally? how will it be triggered? how do we ensure that the right version/branch is tested? How are results added in the pull request? Do we want to consider performance implications?)
-- consider possiblity of schema inconsistency
-
 ### Report Bugs
 
 Report bugs at https://github.com/CoLRev-Environment/bib-dedupe/issues.
@@ -92,13 +51,13 @@ Ready to contribute? Here's how to set up BibDedupe for local development.
 1. Fork the `bib-dedupe` repo on GitHub.
 2. Clone your fork locally:
 
-    ```sh
+    ```
     git clone git@github.com:your_name_here/bib-dedupe.git
     ```
 
 3. Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up your fork for local development:
 
-    ```sh
+    ```
     mkvirtualenv bib-dedupe
     cd bib-dedupe/
     pip3 install poetry
@@ -107,7 +66,7 @@ Ready to contribute? Here's how to set up BibDedupe for local development.
 
 4. Create a branch for local development:
 
-    ```sh
+    ```
     git checkout -b name-of-your-bugfix-or-feature
     ```
 
@@ -116,14 +75,14 @@ Ready to contribute? Here's how to set up BibDedupe for local development.
 5. When you're done making changes, check that your changes pass the
    tests and pre-commit hooks:
 
-    ```sh
+    ```
     pytest
     pre-commit run -a
     ```
 
 6. Commit your changes and push your branch to GitHub:
 
-    ```sh
+    ```
     git add .
     git commit -m "Your detailed description of your changes."
     git push origin name-of-your-bugfix-or-feature
@@ -139,8 +98,9 @@ Before you submit a pull request, check that it meets these guidelines:
 2. If the pull request adds functionality, the docs should be updated. Put
    your new functionality into a function with a docstring, and add the
    feature to the list in README.rst.
-3. The pull request should work for the Python versions specified in the `pyproject.toml`.
-   Make sure that the tests pass for all supported Python versions.
+3. The pull request should work for Python 3.5, 3.6, 3.7 and 3.8, and for PyPy. Check
+   https://travis-ci.com/CoLRev-Ecosystem/bib-dedupe/pull_requests
+   and make sure that the tests pass for all supported Python versions.
 
 ## Coding standards