Feature #14725

Quarterly reminder to tails-project@ about sponsorship (from [misc])

Added by intrigeri 2017-09-26 08:45:58 . Updated 2018-10-01 16:07:50 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2017-09-26
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

We want to let all active contributors know that it’s an option to be reimbursed when attending events on behalf of Tails. Once we have publicly available doc about how it works, we’ll set up an automated reminder that points tails-project@ to it.


Subtasks


Related issues

Related to Tails - Feature #7763: Move our email reminders (e.g. for meetings) to Puppet In Progress 2015-03-03
Blocked by Tails - Feature #14727: Publicly document how active contributors can be sponsored to attend events on behalf of Tails Resolved 2017-09-26

History

#1 Updated by intrigeri 2017-09-26 09:45:09

  • blocked by Feature #14727: Publicly document how active contributors can be sponsored to attend events on behalf of Tails added

#2 Updated by sajolida 2017-09-26 16:53:34

  • related to Feature #7763: Move our email reminders (e.g. for meetings) to Puppet added

#3 Updated by sajolida 2018-08-14 09:18:58

  • Target version set to Tails_3.10.1

#4 Updated by sajolida 2018-09-10 12:19:28

The email could be:

Subject: Reminder about sponsorship to attend events on behalf of Tails

This is an automatic reminder.

In general, you should not have to spend your own money to attend relevant events, such as conferences, on behalf of Tails: in most cases the project will reimburse the corresponding expenses.

See our documentation about how to get such a sponsorship:

https://tails.boum.org/contribute/sponsorship_to_attend_events/

#5 Updated by sajolida 2018-09-10 12:19:51

  • Subject changed from Quarterly reminder to tails-project@ about sponsorship to Quarterly reminder to tails-project@ about sponsorship (from [misc])

#6 Updated by sajolida 2018-09-18 16:25:34

  • QA Check set to Ready for QA

I installed a cronjob for that and tested it as much as I could.

Next step is to wait until October 1 and see if it’s sent correctly to tails-project.

#7 Updated by sajolida 2018-10-01 16:07:50

  • Status changed from Confirmed to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Done: https://mailman.boum.org/pipermail/tails-project/2018-October/001190.html.