# Publications and Contributors Our goal is to consistently, accurately and transparently attribute the contribution of each contributor to papers, software, data products and other scientific outputs that our group leads or contributes to. We seek to encourage participation in manuscripts by interested parties, not limited to scientists, developers, and students who are directly involved in our projects. We hope to recognize each contributor who has made a significant and defined contribution. Below we define group protocols and expectations for being acknowledged and acknowledging contributions to different types of content. We generally follow the [Contributor Roles Taxonomy (CRediT)](https://credit.niso.org/) to define contributions, but are open when collaborators use other approaches. ## Types of Scientific Output There are a variety of types of scientific output, both peer reviewed and otherwise, to which authorship applies. These include journal articles, conference proceedings, data and software archives, white papers, and more. It is often the case that the list and order of authors will different across different components of a project. For example, the lead author on a data archive may be different from the lead author of the associated paper, reflecting who is primarily responsible for the work. Furthermore, the list of authors on multiple outputs of a project may vary based on contributions. ## Publication and archives There are a variety of websites appropriate for archiving scientific products beyond peer reviewed publications. GitHub works well as a place to browse and share code, but is insufficient as an archive. The version of code used in a publication will be versioned on GitHub and also archived and given a digital object identifier (doi). Archiving is often done on Zenodo, but other venues may be appropriate. In many cases it makes sense to separately archive code and data, especially when these may be used independently. But this is not always necessary.