- enable the team to communicate with each other
- make data available to the team so that they can get started directly after the kickoff
- set up project tools
- create private Slack channel and add team members
- set up NextCloud (if necessary)
- data transfer via NextCloud (or other means when data is not GDPR relevant)
- coordinate kickoff workshop
- separate 1-1 onboarding call with team lead (optional)
- 2.In the folder, create a team_base from the team_base template (right-click -> Google docs --> from template -> template_team_base and rename / adapt it as necessary
- 3.Share the folder (right-click on folder name -> share -> under general access set to "anonye with the link". Copy the link and pin it to the Slack channel as a bookmark.
- 2.The declaration outlines the requirements for the highest security setup (including the requirement to create a separate user account), so please make sure to adapt them to your specific project by removing passages not needed for your project. If you're unsure, ask our data privacy team (#data-protection-privacy Slack channel).
- 3.Export as PDF and and reupload the PDF to the folder for the team (see previous step)
- 4.Team members should sign this declaration and send it to you (e.g. via Slack DM or email). You can then upload the signed declarations to the project folder in 10_project_coordination (see "Initial Slack communication with team members" below).
Who: Project lead or project coordinator
Requirements: Membership in CorrelAid GitHub Repository.
Everyone who is a member of the CorrelAid GitHub organization can create repositories. You can check whether you are a member by going to "Your organizations" in your GitHub profile. If you are not part of the organization, you can also ask another member of the organization or ask to become part of it by asking in #infrastructure Slack channel.
Usually, our project teams use GitHub for collaboration. To request a repository in the CorrelAid GitHub team, please proceed as followed:
- 1.in your project team channel, collect the GitHub of all team members.
- 2.On GitHub, click the new button
- 3.Pick one of the templates that we have created as boilerplates for project repositories. If none fits, create an empty repository with a README and (optionally) gitignore for the language(s) you'll be using. The existing templates are:
- 4.Make sure to pick CorrelAid as the owner using the dropdown.
- 5.Choose repository visibility. Should be private by default unless it's an open source project and/or open data project
- 6.LICENSE can be left empty. If it's an open source project, choose MIT.
- 7.In Settings -> General, enable Projects for the repository so that the team can create a kanban style board for their issues if they want to.
Continue here once you have the GitHub profiles from the team members
- 7.invite team members as outside collaborators via Settings -> Collaborators and Teams. The default permission should be write, the team lead can also get manage.
This is necessary if the project data is sensitive or GDPR relevant. If you work with open data, you can probably skip this!
While our project teams usually use GitHub for their project work, we use our NextCloud instance for the initial data transfer from the organization to CorrelAid and from CorrelAid to the project team members.
Ask one of the project coordination admins (see below) to create a folder with your project id (e.g. 2021-02-COR) in the
06_projectsfolder structure to enable the data transfer. Project coordination admins with the necessary permissions are (so far):
This folder will only be shared with you, the project team and the NPO representatives.
- 2.Click the plus to create a new folder. Name it with the project id.
- 3.Enter the folder by clicking on it. In it, create a folder
- 4.Click on the share symbol next to the plus symbol. Invite everyone that needs access to the data via their email:
- other project coordinators with their CorrelAid email
- NPO representatives who share the data
- team members who need to access the data
The share symbol is on the right end of the "breadcrumbs"
Please make sure that you're only sharing the project folder and not the whole of 06_projects! If you are inside the project specific folder (2000-00-TES in the example) it's fine!
Once you have your Slack channel, invite or request to invite all selected team members to the Slack channel as members by inviting them to the Workspace and adding the created channel to the default Slack channels that they'll be added to (we have a standard plan).
If applicable, you should also invite the representatives of the NPO to the Slack workspace/channel. They might prefer to be invited as a guest if they also use Slack for their own organization. Check with them regarding their preferences. Having the NPO representative(s) on Slack makes team communication easier and increases NPO engagement.
It's always nice if people join a Slack channel and there is already a message waiting for them to get a conversation going. Hence, you should post a welcome message.
Goals of the message:
- get to know team members
- point out Google drive folder and other bookmarks on the Slack channel
- get necessary information and give actionable items
- get GitHub profiles
- sign declaration on data protection and security (if applicable)
Post an emoji poll on Slack to coordinate a date for the kickoff workshop.
Make sure to inform your team members at some point about the data privacy and security considerations for the project. If you are unsure about what applies to your project, ask the project coordinator - they should know this. Express yourself as clearly as possible in DO's and DON'Ts. For examples, please see here. You can do this as part of the kickoff or the onboarding process