Welcome Mail Template
This mail is supposed to be sent to new core team members and staff members or interns. Please fill the [FILLME] placeholders and remove or add information if needed.
Subject: FSFE team account information Dear [FILLME], Welcome to the FSFE! This message contains some basic instructions and references to access the FSFE internal services for team members and interns. Please take some time to read it carefully; in case of doubts or problems, don't hesitate to ask for help: just write to email@example.com * Account First of all, you should make sure to have an FSFE account. This step is required to give you access to some of our internal services, so please do it as soon as possible. Then you can go through the remaining steps in this document to have access to other services. If you do not already have an account, you should: * Sign up at: https://fsfe.org/fellowship/ams/index.php?ams=register * Be sure to choose a good password and keep it safe. Please see the suggestions at https://www.google.com/accounts/PasswordHelp * Notify your contact person that you have created your account so that it can be activated, and wait for the e-mail message notifying the account activation. * Instant messaging As soon as your account is activated, you are encouraged to start using the FSFE XMPP instant messaging account, so that we can give you better support with the initial tasks. You can find setup instructions at https://wiki.fsfe.org/TechDocs/XMPP * Email communication After activation, you will be subscribed to the internal mailing list firstname.lastname@example.org. This is where we coordinate our activities: normally the assumption is that what was posted on team@, stays on team@, in order to allow people to speak openly. So please be careful. Interns and new employees will additionally be subscribed to email@example.com for staff-related coordination. The same rules for confidentiality apply. You just became a member of the FSFE's General Assembly? We will also subscribe you to firstname.lastname@example.org. * GnuPG key for encryption To secure our communication, encryption of email messages is crucial and widely used within the FSFE. We prefer using GnuPG/GPG keys (a.k.a. PGP). If you don't already have one, please create a GPG key and add your @fsfe.org email address to it. Ideally you also upload it to keyservers to enable others to find your key when trying to contact you. Have a look at <https://emailselfdefense.fsf.org> for more details and help. * Other technical services To get an overview on the other services provided by your FSFE account, you can see the page: https://wiki.fsfe.org/TechDocs. Here's a short overview of some important ones: * Ticket System (OTRS): An important part of our external communication is the Ticket System (OTRS) on https://tickets.fsfe.org. Depending on your position you may have been added to certain queues. * Git / SVN: Quite a lot of the FSFE's information and websites are stored on version control systems like Git and SVN (the latter becoming less important). In order to receive a Git account, you'll have to login at least once with your FSFE credentials – this is also required for giving you read/write access to certain repositories. * Are you an intern? If you are beginning an intership at FSFE, you will find lots of useful information in our "Interns Howto": https://wiki.fsfe.org/Internal/InternsHowto (you will be able to access this page as soon as your FSFE account is enabled) On that page you will find further instructions to set up your access to the remaining FSFE internal services. Please also shortly introduce yourself to email@example.com so people know about you and your working areas. In this email, please also attach your public GPG key. * Further questions Your personal mentor is [FILLME], who volunteered to help you get an idea of the overall structure and how team@ works. If you have any questions about the FSFE team, please get in touch with her or him. For technical questions about the internal services, please ask for help writing to firstname.lastname@example.org Best regards!