# 4. Lab resources

**Slack**

Slack will be used as the primary means of lab communication, such as general lab announcements (#general), sharing links, sharing and/or discussing papers (#papers), and basically any message that can be sent without email. There's also a channel for keeping notes from our lab meetings (#lab-meetings), as well as channels for methods tips (e.g., #physiology-methods) and specific projects. Try to keep each channel on topic, so that people can subscribe only to the channels that concern them. For messages to one person or a small group of people, use the direct message channels.

Full-time lab members should install Slack to their computers and/or phones. Part-time lab members should check Slack regularly. I get Slack updates on my phone and have do-not-disturb mode enabled for evening and night hours (meaning I may not get your messages then); I encourage you to do the same.

**GitHub**

All projects that involve programming of any kind must use some form of version control. We have a Lab [GitHub account ](https://github.com/ackels-lab/)to sync code to the cloud and share it easily with other lab members. We will also use GitHub for sharing script examples and hosting lab toolboxes for general use.

**Cloud and network storage**

We have our own network storage as part of the institute which should be used to store data, documents and files for general lab use (e.g., protocols, manuscripts, etc). To access this, individual accounts need to be set up by our house IT support. In some cases, processed data can be stored using Sciebo or Google Drive, but double-check with Tobias before you start storing significant amounts of data there. The lab Google Drive will be used as a backup for some resources to ensure that the lab will maintain owner access over the files even after individual team members have left.

**Google Calendar**

Google Calendar is used to host a general lab calendar (AckelsLab). Please get in touch with Tobias in case you have not been invited yet
