Project

General

Profile

Feature #14507

Have the monthly meeting reminder automatically avoid Fridays, Saturdays, and Sundays

Added by anonym 10 months ago. Updated 4 days ago.

Status:
Confirmed
Priority:
Elevated
Assignee:
Category:
-
Target version:
Start date:
08/30/2017
Due date:
% Done:

0%

QA Check:
Ready for QA
Feature Branch:
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

E.g. don't allow them to happen on Fri, Sat, Sun.

monthly-meeting.eml (922 Bytes) sajolida, 04/16/2018 02:26 PM


Related issues

Related to Tails - Feature #7763: Move our meeting reminder to Puppet Confirmed 03/03/2015
Related to Tails - Feature #14503: Document Monthly Meetings fixes In Progress 08/30/2017

History

#1 Updated by anonym 10 months ago

#2 Updated by anonym 10 months ago

  • Assignee changed from anonym to sajolida
  • QA Check set to Info Needed

I need to know how I can proceed!

#3 Updated by anonym 10 months ago

  • Assignee changed from sajolida to anonym
  • QA Check deleted (Info Needed)

#5 Updated by sajolida 10 months ago

Maybe encoding this in a crontab line would be to weird. We could
instead delegate to meeting.rb the "is it time to send an email?"
decision, i.e.:

  • run meeting.rb everyday, with a command-line parameter that
    triggers the desired behavior, and without --date;
  • either teach meeting.rb what the desired behavior is, i.e.
    only send email when it thinks it should (based on the algorithm
    you've picked); or do the computation by hand for the next 2 years,
    write the result in some YAML file, and teach meeting.rb to use
    this data as part of its input. With the second way,
    each team who wants a meeting reminder can then build their
    own schedule (including exceptions to the general rule) manually or
    programmatically and feed meeting.rb with it; it requires yet
    another Git repo to store the data, giving access to that repo to
    the right people, and programming meeting.rb defensively enough, so
    it might require a little bit more work.

#6 Updated by intrigeri 10 months ago

  • Priority changed from Normal to Elevated
  • Target version changed from Tails_3.2 to Tails_3.3

(IMO this should happen in September but it can wait after the 3.2 release.)

#7 Updated by intrigeri 9 months ago

I think we could (and perhaps should) update the time of the meeting in the current cronjob without waiting for the date to be computed in a more clever way: the former is currently always wrong, while the latter will only occasionally be wrong. sajolida, do you want a ticket for that?

#8 Updated by sajolida 9 months ago

  • Subject changed from Implement new Monthly Meeting reminder rules to Have the monthly meeting reminder automatically avoid Fridays, Saturdays, and Sundays

I just changed the time in the template email.

#9 Updated by anonym 7 months ago

  • Target version changed from Tails_3.3 to Tails_3.5

#10 Updated by intrigeri 7 months ago

  • Assignee deleted (anonym)

#11 Updated by intrigeri 6 months ago

  • Target version changed from Tails_3.5 to Tails_3.6

Called for help on -summit@.

#12 Updated by muri 5 months ago

hi,

i've written a python script that can be used to send a meeting reminder. it was easier for me than to get into ruby ;) if its not useful, no worries, it was fun either way ;)

by default it shows the next meeting date.

/meeting.py 
The monthly Tails meeting in February will be on Tuesday 06. February 2018

if the meeting falls on fr,sa,su it add 3 days to the meeting date.

With -r one can set multiple days in advance, when a reminder should be sent:


./meeting.py -r 10,24
The monthly Tails meeting in February will be on Tuesday 06. February 2018
One reminder would be sent on Saturday 27. January 2018.
One reminder would be sent on Saturday 13. January 2018 - thats today!

With -mail it outputs the invitation mail on stdout, with -sendmail (and an email address via --to) it sends the invitation to that address via local smtp server. with -e/--encrypt and an email address it encrypts the output/the mail for that email address (for that, the key needs to be in the keyring of the user running the script and key in the keyring must not be expired).
If -r and -(send)mail are combinded, the invitation is only sent/printed to stdout if the day the script is run is a 'reminder day'.

https://0xacab.org/muri/meeting

(update 20180115: changed -d to -r and now -d is used for setting the day the meeting should be. description above adapted accordingly)

#13 Updated by u 5 months ago

  • Related to Feature #14567: Investigate mobile messaging applications added

#14 Updated by u 5 months ago

  • Related to deleted (Feature #14567: Investigate mobile messaging applications)

#15 Updated by u 5 months ago

  • Related to Feature #7763: Move our meeting reminder to Puppet added

#16 Updated by u 5 months ago

  • Assignee set to sajolida

We need

  1. someone who knows what the interface (input, output) of the script should be to check it satisfies our needs (sajolida?);
  2. someone to review the code (intrigeri);
  3. someone to deploy it somewhere (depends on whether we want to take this opportunity to move it to our infra (#7763, and then intrigeri can do this as a volunteer) or not (and then it has to be sajolida))

So i'm now assigning this to sajolida for the time being and let him take the next steps described above.

#17 Updated by sajolida 3 months ago

  • Target version changed from Tails_3.6 to Tails_3.7

#18 Updated by sajolida 2 months ago

  • File monthly-meeting.eml added
  • Assignee deleted (sajolida)
  • Target version deleted (Tails_3.7)

I'm uploading here all the info about the current reminder:

0 0 24 * *    DATE=$(date --date="$(date '+\%Y-\%m-03 +1 month')" +\%F) ; ruby $HOME/meeting/meeting.rb --locale en_US.UTF-8 --template $HOME/monthly-meeting.eml --date $DATE --subject "Tails contributors meeting: $(date --date=$DATE '+\%A \%B \%d')" --from "tails-project@boum.org" --to "tails-dev@boum.org tails-project@boum.org tails-ux@boum.org tails-l10n@boum.org" 

I'm not volunteering to do this coding.

#19 Updated by intrigeri about 2 months ago

  • Target version set to Tails_3.7
  • QA Check set to Ready for QA

u wrote:

We need

  1. someone who knows what the interface (input, output) of the script should be to check it satisfies our needs (sajolida?);

I'll do that. FTR "the script" == muri's code, that has been waiting to be reviewed since 4 months. If the script needs adjustments I'll ask muri if he wants to do it.

#20 Updated by intrigeri about 2 months ago

  • Assignee set to intrigeri

#21 Updated by intrigeri about 2 months ago

  • Target version changed from Tails_3.7 to Tails_3.8

#22 Updated by intrigeri 21 days ago

  • Blocked by deleted (Feature #14503: Document Monthly Meetings fixes)

#23 Updated by intrigeri 21 days ago

#24 Updated by intrigeri 4 days ago

  • Target version changed from Tails_3.8 to Tails_3.9

Also available in: Atom PDF