Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emails for unanswered questions #2355

Open
Tracked by #4361
niknetniko opened this issue Oct 21, 2020 · 3 comments
Open
Tracked by #4361

Emails for unanswered questions #2355

niknetniko opened this issue Oct 21, 2020 · 3 comments
Labels
low priority Thing we want to see implemented at some point

Comments

@niknetniko
Copy link
Member

niknetniko commented Oct 21, 2020

Issue to collect ideas and feedback about emails for questions. Other relevant issues with mail-related comments are #2265 and #1788.

  • Choosing frequency: daily digests, immediately, weekly digest (others?)
    • Choose moment when using digests, e.g. every Friday around 10 am the weekly digest
  • Enabling/disabling, probably on the user profile somewhere
    • Maybe with option per course, although I'm not sure this is very usefyul.
    • Maybe some notion of being online or in an exercise session, in which emails are not sent. This would probably be on the course level, not on the user level. This is probably only useful for the immediate frequency.

Undecided:

  • Some timeframe in which to send mails, e.g. office hours.
    • This is only useful if using the "immediate" mail frequency.
    • Questions made during the "off time" will probably need to be bundled, to prevent having to send a lot of mails at 9 am when office hours start
  • Emails to students (e.g. if a question is marked as answered). Since we don't really have "answers" yet, we can't send the answer in the mail itself. This would also require the notion of being online or in an exercise session, to prevent students from getting mails during the exercise session.
@niknetniko niknetniko added the feature New feature or request label Oct 21, 2020
@niknetniko niknetniko added this to the 4.1 milestone Oct 26, 2020
@niknetniko niknetniko removed this from the 4.1 milestone Nov 23, 2020
@bmesuere bmesuere added this to Roadmap Apr 17, 2022
@bmesuere bmesuere moved this to Unplanned in Roadmap Apr 17, 2022
@rien
Copy link
Member

rien commented Oct 12, 2022

I think a good first step would be a setting per course membership for teachers (or even students) to send a mail for every new question.

@rien
Copy link
Member

rien commented Nov 28, 2022

@bmesuere which priority do we want to assign to this issue?

@rien rien added the low priority Thing we want to see implemented at some point label Nov 28, 2022
@bmesuere bmesuere moved this from Unplanned to Todo in Roadmap Jan 27, 2023
@bcoppens
Copy link

Maybe some quick thoughts / observations about this: for a course we have added a set of optional exercises on Dodona, where we enabled the questions-feature. I had assumed implicitly that I would have gotten mails when there would have been questions; had not the co-teacher told me that there were questions, I think I would never have realised that students had asked questions. Even now, because this is an optional set of exercises without a specific deadline, and we don't use Dodona as a daily driver, as a teacher, I'm probably going to forget to check Dodona regularly, making the 'questions' feature not as useful as it could be, at least for me.

The original comment lists different kinds of cool & potentially useful options, but which all probably would take quite some time and effort to design and implement. However, to a first approximation, just having the option 'send an email when a question is asked' would be more than enough: people who check Dodona daily anyways can leave it disabled; people who only use it for asynchronous optional exercises can enable it.

@bmesuere bmesuere removed the feature New feature or request label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
low priority Thing we want to see implemented at some point
Projects
Status: Todo
Development

No branches or pull requests

4 participants