EFI Community Manuscript Guidelines

EFI maintains a community manuscript/project repository as a clearinghouse that allows anyone in the EFI community to see what manuscripts, and other similar deliverables, are in the process of ideation, analysis, text drafting, submission, revision, and acceptance for publication. It is for anyone in the community to express interest in participating on manuscripts/projects that are open to collaboration.

GitHub Repository: https://github.com/eco4cast/efi-projects

There are three goals for this repository

  1. As the EFI Community continues to mature and new people join, we want to make sure to be open and welcoming of opportunities to contribute as co-authors on manuscripts and similar deliverables 
  2. We want to provide a mechanism to check for any overlooked co-authors as a manuscript is in preparation for submission
  3. There may be manuscripts for which EFI will provide funds for page charges. Eligible manuscripts must be listed in this repository.

In the repository, you will find the list of active projects as well as information about:

  1. What defines a manuscript as being an EFI manuscript
  2. Potential funding for page fees and how to request funding
  3. Color code and labels for types of manuscripts
  4. Get instructions on registering manuscript ideas and how to access and express interest in posted manuscripts

How Manuscripts or Projects are Communicated to the EFI Community

After a new project or manuscript idea gets posted as an Issue, the EFI administrators will share it on the EFI Slack group, and it will also be included in the newsletter issue released after the manuscript is posted. EFI Newsletters come out every 4-6 weeks.

Acknowledgments 

These guidelines for sharing and expressing interest in EFI community-developed manuscripts was inspired by the processes used by the Global Lakes Ecological Observatory Network (GLEON) and Zarr-Python for managing their projects.