Skip to main content Link Search Menu Expand Document (external link)

Contributor guidelines for β€œFAIR Phytoliths: Increasing the FAIRness of phytolith data”

First of all, thank you for considering to contribute to this initiative! :ear_of_rice:

The FAIR Phytoliths project has grown from initial efforts by Emma Karoune to raise awareness on limited data sharing within the community of phytolith researchers. This initiative is supported by the International Phytolith Society (IPS) and represents the first steps towards the FAIRification of phytolith data.

Please check out our roadmap and our community’s code of conduct to help you get started, and the home page for an overview of the project (if you have not read it yet)!

Below you can find the main guidelines for contributing to the FAIR Phytoliths project. This repository is available under CC BY 4.0 license, so you are welcome to use, reuse, remix, share and build upon the existing materials. We appreciate all your suggestions and contributions.

How can I contribute?

Any person who deals with phytoliths, either in academia or in the private sector, can participate in this project. There are different ways in which you can contribute and hence different degrees of involvement:

  • Help us to gather information about current data sharing practices and opinions on why open practices are not very common within the phytolith community and how we can improve as a community, by filling this survey.

  • Provide phytolith datasets from South American and European studies in which you participated to help us assessing them and establishing the breadth of phytolith data (including archaeological, palaeoecological, modern botanical studies, etc.). You can send them by email at Datasets can be already published fully or partially, or even unpublished: we will not share them unless you give us permission to do so!

  • Submitting feedback about any aspect of the project. You can reach us by email at or on twitter. Otherwise, you can open an issue in this repository.

  • If you are willing to get more involved in this project (e.g., become a main contributor/maintainer) you can send us an email at Please, consider including your contact information and your motivations for becoming part of the core team of contributors.

Acknowledgement of contributors

We value your time and effort. Once you get involved in this project in any way, we are committed to keep you updated with the results.

We are adopting an inclusive and generous authorship model to reflect the work made by the core team, active contributors and the wider phytolith community to this project. Please, note that in order for your contribution to be recorded you need to have a GitHub account. Our barrier for entry to the list of contributors is very low. If you have contributed in any of the ways in the table below, then please ask one of the core team to use the all contributors bot :robot: to add you to the list (you will need to provide us with your GitHub user name). Or comment on an issue or pull request, asking @all-contributors to add a contributor.

@all-contributiors please add @username for name contributions

An example of this is:

@all-contributors please add @EKaroune for documentation, blogs

A pull request will be automatically generated and this can then be approved and merged by a core team member.

As a contributor, you are also invited to provide more information about your work and your contributions to this project here! To upload your profile, please ask one of the core members, send an email to or open a pull request.

Type of contributions

The FAIR Phytoliths project uses the emoji-key to recognise everyone who contributes to the project.

Emoji Represents
πŸ”Š Audio - Podcasts, background music or sound effects
♿️ Accessibility - Reporting or working on accessibility issues
πŸ› Bug reports - Reports bugs in reposiory and website
πŸ“ Blogposts - Writing blogposts
πŸ’» Code - R code for analysis
πŸ–‹ Content - Publication drafting and editing/revising
πŸ”£ Data - Contributing or creating data for the project (both tests and datasets)
πŸ“– Documentation - Creating or editing documentation for the project, Wiki, or other source of documentation
🎨 Design - Logo, iconography, visual design, etc.
πŸ’‘ Examples
πŸ“‹ Event organizers
πŸ’΅ Financial support - People or organisations who provide financial support
πŸ” Funding/Grant finders - People who help find financial support, help to write or write letters of support for grant applications
πŸ€” Ideas and planning
πŸš‡ Infrastructure - Hosting, build-tools, website building, etc.
🚧 Maintenance - People who help in maintaining the repository
πŸ§‘β€πŸ« Mentoring - People who mentor new contributors
πŸ“¦ Packaging - Porting to support a new platform
πŸ”Œ Plugin/Utility libraries
πŸ“† Project management
πŸ’¬ Answering questions in issues, Stack Overflow, Gitter, Slack, etc.
πŸ”¬ Research - Literature review and survey
πŸ‘€ Reviewed pull requests
πŸ›‘οΈ Security - Identify and/or reduce security threats, GDPR, privacy, etc.
πŸ”§ Tools
🌍 Translation - Translated content
⚠️ Tests
βœ… Tutorials - Creating, helping with tutorials and other educational/training activities
πŸ“’ Talks - Giving talks and making presentations
πŸ““ User testing
πŸ“Ή Videos

Do you want to be more involved?

If you would like to be more involved in the project, want to make a substantial contribution that goes beyond a one-off task, and want to be a named author on a publication, please see our authorship guidelines that include authorship criteria and an author name ordering process.

Need help?

Feel free to get in touch with us by email at or on twitter.

Table of contents