Update README.md

[bastienchassagnol]

Add resources for describing EDAM ontologies

Contributing to biocEDAM

This outlines how to propose a change to biocEDAM. For more detailed
info about contributing to this package, report to the
development BioConductor contributing guide, and BiocCheck: Ensuring Bioconductor package guidelines.

Fixing typos

Small typos or grammatical errors in documentation may be edited directly using
the GitHub web interface, so long as the changes are made in the source file.

• YES: you edit a roxygen comment in a .R file below R/.
• NO: you edit an .Rd file below man/.

Prerequisites

Before you make a substantial pull request, you should always file an issue and
make sure someone from the team agrees that it’s a problem. If you’ve found a
bug, create an associated issue and illustrate the bug with a minimal
reprex.

Pull request process

• We recommend that you create a Git branch for each pull request (PR).
• The README should contain badges for any continuous integration services used
  by the package.
• New code should follow the tidyverse style guide.
  You can use the styler package to
  apply these styles.
• We use roxygen2, with
  Markdown syntax,
  for documentation.
• We use testthat. Contributions
  with test cases included are easier to accept.
• For user-facing changes, add a bullet to the top of NEWS.md below the
  current development version header describing the changes made followed by your
  GitHub username, and links to relevant issue(s)/PR(s).

Code of Conduct

Please note that the biocEDAM project is released with a
Contributor Code of Conduct. By contributing to this
project you agree to abide by its terms.

See BioConductor development contributing guide

for further details.

[vjcitn]

I see this as WIP. I will keep an eye out for a merge-ready PR.

[vjcitn]

@bastienchassagnol Should we merge this or is it still WIP?