1. License or copyright information, if present 2. Package statement 3. Import statements 4. Exactly one top-level class Exactly one blank line separates each section that is present. 3.1 License or or copyright information, if present If license or copyright information belongs in a file, it belongs here. 3.2 Package statement The package statement is not line-wrapped. The column limit (Section

reluctant to use clever or unusual constructs: the absence of a prohibition is not the same as a license to proceed. Use your judgment, and if you are unsure, please don’t hesitate to ask your project leads consistent with how you comment and what style you use where. File Comments Start each file with license boilerplate. File comments describe the contents of a file. If a file declares, implements, or tests comments. Legal Notice and Author Line Every file should contain license boilerplate. Choose the appropriate boilerplate for the license used by the project (for example, Apache 2.0, BSD, LGPL, GPL). If

guidelines for doc strings below. Modules Every file should contain license boilerplate. Choose the appropriate boilerplate for the license used by the project (for example, Apache 2.0, BSD, LGPL, GPL) Functions

Reusable  Metadata and data described with plurality of accurate and relevant attributes  Clear license, associated with provenance, meets community standards Reproducibility and RDM [https://www.go-fair