What are the choices about this text?

We'd like @jmatazzoni to come up with text for this.

@Eee888 Can you put the current placeholder text from the commit in the description (explaining where each message is used), as well as any messages without placeholder text?

In T168385#3373672, @Mattflaschen-WMF wrote:

@Eee888 Can you put the current placeholder text from the commit in the description (explaining where each message is used), as well as any messages without placeholder text?

Thanks. For each message, please also explain briefly where it's used/the purpose. You can base this on qqq.

I think @Eee888, @Mooeypoo and I can handle the API parameters (used by developers, not user-facing) in code/code review, so the product people can focus on the others. So I'll remove the API ones from here.

Notify me about this article when I asked.

I know the global task has been named Article reminder, but I think many people would like to have it for all pages. So I would advice to use "page" instead of "article" in messages. Use "page" will make all messages consistant.

You also have a typo: Cancle -> Cancel :)

echo-reminder-comment-input-placeholder

I'm not sure to understand the purpose of this message. It it where users can leave a note about the reminder? I don't see the label for this field.

Thanks @Trizek-WMF , I'll fix the "article"->"page" and the tipo of course :)

If you'll look at the attachment I've just added, I'm sure you'll understand the comment placeholder thing.

In T168385#3434790, @Eee888 wrote:

If you'll look at the attachment I've just added, I'm sure you'll understand the comment placeholder thing.

Thanks, I see now. I don't know if the label is clear enough. Maybe something like "add your note" or "What I have to review" may be more understandable. @Pginer-WMF, any idea?

Based on what I read in T2582, here's my suggestion for language:

Header: Scheduled reminder: Pagename
Body: UserComment

Or, if we think the header will be too long:

Header: Reminder: Pagename
Body: UserComment

Do we know all the other elements of this notification? The icon, etc. It is usually very helpful if developers/proposers fill out the Notification Request Form, as part of their primary ticket .See below.

New Notification Request Form

Filling out this form will help developers and product people understand your idea and will provide the information required to implement it. To see examples of the types of answers required, have a look at this sample form. To understand unfamiliar terms, visit the glossary. 

Basic information

  - Purpose of the notification:  
  - Notification name:  
  - What triggers notification?: 
  - "Notice" or "Alert"?:  
  - Notification type (standard, bundled, expandable bundle):  

Wording

For a single message

• Header: 
• Body:  

For Bundled Messages

• Main, bundling message:
• Subsidiary, bundled message:

Links

  - Primary link target:
  - Primary link label (for email display only):

  - #1 secondary link target: 
  - #1 secondary link label:

  - #2 secondary link target:
  - #2 secondary link label:

Icon

  - Icon name:  
  - Link to graphic/example: 

In T168385#3439975, @jmatazzoni wrote:

Do we know all the other elements of this notification? The icon, etc.

There is no icon yet. It's tracked at T170517: Icon for Article Reminder.

In T168385#3434828, @Trizek-WMF wrote:

Thanks, I see now. I don't know if the label is clear enough. Maybe something like "add your note" or "What I have to review" may be more understandable.

I like "What I have to review" or "What to remind me about". What do you think?

In T168385#3439975, @jmatazzoni wrote:

Do we know all the other elements of this notification?

Thanks for reminding us about this. Most of these are already decided, and I've documented them at T165754: create new notification type for the article reminder.

The remaining open spec issues for the notification itself are:

• Current task (language)
• T170731: Determine bundling behavior for page reminder notifications
• T170517: Icon for Article Reminder

I don't believe we need secondary links, but correct me if I'm wrong.

What about having a link to the page history?

I'm not firm on it, but it seems likely that reminders might want to be bundled. Here is a possible main bundling message:

• You've received X scheduled reminders. [where X is the number received]

I don't think the bundled messages need to change.

In T168385#3479391, @jmatazzoni wrote:

• You've received X scheduled reminders. [where X is the number received]

"You have X reminders." is enough, don't you think? "received" and "scheduled" are obvious and can be skipped.