Deelnemer inschrijven: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
When adding a new participant, make sure you complete the following actions, or make sure they are executed by someone else: | When adding a new participant, make sure you complete the following actions, or make sure they are executed by someone else: | ||
* Add the personal data to participants.txt in git, also make sure to commit and push this change | * Add the personal data to participants.txt in git, also make sure to commit and push this change | ||
<pre>Deelnemer 42, ingeschreven op % | <pre>Deelnemer 42, ingeschreven op `date +%Y-%m-%d` | ||
"Full Name (Nickname)" <email@example.com> | "Full Name (Nickname)" <email@example.com> | ||
%yyyy-%mm-%dd | %yyyy-%mm-%dd | ||
Revision as of 09:59, 7 October 2015
Checklist voor bestuursleden om het toevoegen van nieuwe deelnemers goed te laten verlopen
When adding a new participant, make sure you complete the following actions, or make sure they are executed by someone else:
- Add the personal data to participants.txt in git, also make sure to commit and push this change
Deelnemer 42, ingeschreven op `date +%Y-%m-%d`
"Full Name (Nickname)" <email@example.com>
%yyyy-%mm-%dd
Pistraat 314 - 1337 XY Den Haag
+31601189998819991197253
Make sure the signup-form makes it's way to the secretary- Add the person's e-mail address to the participantsonly and revspace mailinglists
- Create an ldap account for the user, the unix userid is 10000+signup-number
- When the participant has/wants an ibutton:
- Charge the participant a €15,- deposit
- Write a secret into the ibutton
- Add the secret and id to the ibutton acl
- Distribute the ibutton acl
- Let the participant test the ibutton
- Make a bar-account for the participant
- Give them the tour/introduction if they haven't had it yet
- Mail then the NewParticipantMail text