I'm giving my opinion as a community liaison, but @Pginer-WMF's input will be very important as well.

Where should the "add reminder" button be? The simplest solution seems to be adding another tab to the screen next to the "star" (watchlist) menu

Do you plan to add an icon, or a label (like "view history")?

I would suggest to put it in the dropdown menu if the content is collapsed. The article reminder is not a primary feature like the "edit " link or the watchlist star.

What should there be in the menu?

By "in the menu", you mean knowing what is in the displayed when the person has clicked on the link?

Do we have a set range of options to choose from, or a free-text number with days?
Related to the above, if we go with free-text number, do we validate? Do we have a range? Do we have a date-picker?

There is free-text number with days for the block form. That's not really optimum, based on the fact that people have to set the links in English. :)
A date picker would be a good option.

The MVP should support a user-comment. We should limit the character-count to something sensible that appears in the notification.

What's the limit on the notification?
The reminder is a personal note, that I see by definition as concise: "proofread", "update when the election is over", etc. Let's set a value, and see if there is people asking for more space. I advice to have a label that will remind users to be concise.

What does it look like if the article already has a reminder? We can mimic the behavior of the watchlist where the star is empty/full depending on whether it is used.

Good idea.

Speaking of which, what happens if you click that interface when a notification was already set? In the MVP we don't do 'delete' reminder, do we allow for several reminders for the article?

If there is a reminder already set, we can simply edit it when you click on it.

But yes, there is the case when multiple reminders have to be set:

• if you are helping new users, you may want to set reminders to have a look at the article they are working on regularly
• set one reminder for a group of articles. This case may be solved if we allow links in the description.

Possible features requests:

• set a reminder for another user. For example, people participating to a writing context may be subscribed to a global reminder
• have a pre-set reminder, for instance for a community consultation: you click on a link, that the reminder is set

Or should we show the previous reminder you set up? And how will that look like (editable/ non-editable)?

Editable, I would say, with an "update" button.

Do we open a popup under the button with the above details? Is it a screen-centered dialogue? (I personally prefer a popup, but we should discuss)

It depend on what you have to display: if there is plenty of information a screen-centered dialogue would be preferable.

Do we have a set range of options to choose from, or a free-text number with days?

Based on previous conversations I considered the following scenarios in order of relevance:

• The user has no time for a change right now, and wants to continue working in the next working session. "I'll add a picture tomorrow, I have to go to my dancing classes now..."
• The user wants to check back to see how the article evolved after certain editing activity. "I'll review the page once this section is more evolved".
• The use wants to check one a real-world event happens. "I'll add the election result once elections are over".

From these examples, it makes sense to give priority to speed and setting a time period in the short term, while it may make sense to still allow a custom date. A common pattern to solve those cases is to provide a calendar input with some quick smart defaults for the user to pick from. A mockup below illustrates the idea:

Define a reminder by the minutes may be appreciated: "I'll check on it later today, I have to go to Pau's dancing classes now..."
That would help me a lot, at least, to recheck on pages where I've left messages later in the day. :)

In T168665#3390677, @Trizek-WMF wrote:

Define a reminder by the minutes may be appreciated: "I'll check on it later today, I have to go to Pau's dancing classes now..."
That would help me a lot, at least, to recheck on pages where I've left messages later in the day. :)

We need to find the right balance between speed and precision. In terms of the granularity level, I think days can work for an MVP. If we want to go more precise, maybe some general ranges (morning, evening, and night) can be enough. Also, the suggested shortcuts can be more dynamic and take into account the present moment to show the most relevant options (e.g., suggesting "Later this eek" only if you are at the beginning of the week).

The MVP should support a user-comment. We should limit the character-count to something sensible that appears in the notification.

If we want to support the process to be as fluent as possible, the comment can be optional for the user to fill. A default "Review this page" message can be used if the user does not provide a custom one.

Regarding limiting the length, it seems ok. I think we should pick an text area size that encourages users to be clear (to avoid a couple of words they may not even understand some days later when they receive the notification) without encouraging to write too long messages.

Where should the "add reminder" button be? The simplest solution seems to be adding another tab to the screen next to the "star" (watchlist) menu

For an MVP extending the "More" menu of the tabs make sense. Looking forward, I was exploring some ideas on where this could make sense. Here are a couple of possibilities:

• Making the reminders part of a more general task list for editors for editing activities they want to do on a page. This may deserve a more prominent entry point as a quick way for users to organise their editing work, but being also a natural fit for a reminder.

• Making the reminders part of the notification System makes also sense, since it can be perceived as creating new notifications for later. The notification panel can provide a useful persistent entry point, and the notification page can allow for more advanced adjustments (e.g., view all the reminders that are pending to be received and manage them).

These are just two approaches, and many more are possible. Even if we plan for a smaller initial step is good to also think on which long term concepts and from which angles we want to present to our users.

In T168665#3391291, @Pginer-WMF wrote:

The MVP should support a user-comment. We should limit the character-count to something sensible that appears in the notification.

If we want to support the process to be as fluent as possible, the comment can be optional for the user to fill.

Agreed, it is already optional in the (almost-merged) API.

Regarding limiting the length, it seems ok. I think we should pick an text area size that encourages users to be clear (to avoid a couple of words they may not even understand some days later when they receive the notification) without encouraging to write too long messages.

Yeah, I'm thinking edit summary length (255) or even shorter is a good benchmark.