Best Practices
This is a living document which shall always be considered a “draft,” as incoming and veteran members of the lab may want to contribute ideas or revisions. This is a place to begin, a place to return to, a place to ground ongoing conversations. Modeled after SWFSC SAEL Lab Manual Shared values and best pratcies.
PIFSC Glider Lab Best Practices
Communication
We use the PIFSC Gliders Google Space and Google Meet for informal discussions between lab members and project teams. To be added to the Google Space please contact Selene Fregosi selene.fregosi@noaa.gov
We use GitHub projects to keep track of tasks and projects. All lab members are expected to check & respond to email, chats, and GitHub Projects regularly.
Safety
Lab members are expected to follow all safety protocols. If they are not sure of the protocol, then they should request this information.
Lab members should never feel obligated to perform a task that they do not feel is safe.
Lab members are encouraged to speak up if they feel they need training to perform a specific task safely.
If lab members have a safety concern, they should bring it up with their supervisor or the other lab members.
If a lab member feels their safety concerns are not being taken seriously, or have any other lab safety questions, they can consult the acting PIFSC Safety Officer
.
Data management
- We use Google Drive, Google Cloud Platform, GitHub, and physical PIFSC servers to store and share data, documentation, and resources. More information can be found on the Data Management page.
Website Development
As described above, this website is intended to be a place glider team members can both use as a reference and contribute to. The website is built using Quarto, which uses text file .qmd files and markdown syntax to build content. .qmd files can be edited in any text editor, RStudio, or VSCode. For help contributing to this website, Use the ‘Report an issue’ link on the top left of this page to create a GitHub Issue and request assistance.