From version < 11.2 >
edited by Manuel Leduc
on 2020/05/07 12:17
To version < 12.1 >
edited by Manuel Leduc
on 2020/05/07 12:18
< >
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,6 +4,160 @@
4 4  
5 5  They are usually visually distinguishable by an (% class="mark" %)##@##(%%) prefix followed by the identifier of an user, often in hypertext form (e.g., @[[mleduc>>https://www.xwiki.org/xwiki/bin/view/XWiki/mleduc]]).
6 6  
7 +{{toc numbered="true"/}}
8 +
9 +== Mentions Integration ==
10 +
11 +It should be possible to add mentions to users or groups wherever xwiki syntaxes are supported.
12 +
13 +A non comprehensive list includes:
14 +
15 +* documents body
16 +* comments (integrate rich editor)
17 +* annotations (integrate rich editor)
18 +* textarea fields in AWM (the rich editor is a user choice in the AWM settings)
19 +* WARNING: other places ?
20 +
21 +In the rich editor it should be easy to include a mention using only the keyboard, and without having to use the macro section of the rich editor menu.
22 +
23 +Mentions must be visually identifiable in the text, for instance the user name or group group could have a specific background color. Similarly, mentions to the current user and/or a group in which the current is must be highlighted in specific colors.
24 +
25 +The default content of the display mention should be the first name + last name of the user. It should be possible to change it to it first name only, or to the login of the user. I don't know if it's a good idea to be able to allow to change the text of the mention for a free text (confusing, risk of link scamming...).
26 +
27 +Mentions of removed users should still be display clearly, eventually identified visually that the user has been removed (which is not easy to identify in the context of AP for instance).
28 +
29 +== Notifications ==
30 +
31 +=== Notifications rules ===
32 +
33 +Mentioning a user of a group must trigger a even, eventually leading to the notification of the concerned users.
34 +
35 +Nonetheless, user should not be notified several time for the same mention (e.g., when a document is edited and a mention was previously in the document).
36 +
37 +=== Notifications content ===
38 +
39 +The content of a notification must include as much content as possible regarding the context in which the mention occurred. This content must be as specific as possible according to the type of entity in which the mention occurred.
40 +
41 +A non comprehensive list includes:
42 +
43 +* the user that made the mention
44 +* the type of entity in which the mention occurred
45 +* (((
46 +a direct link to the entity, e.g.,
47 +
48 +* the body of a document, ideally an anchor to the § where the mention occurs.
49 +* an anchor to a comment
50 +* an anchor to an annotation
51 +)))
52 +
53 +=== Notifications answer ===
54 +
55 +The most basic scenario is to click on the link in the notification and to interact with the wiki as usual
56 +
57 +More advanced scenarios includes:
58 +
59 +* having a form to interact with the content directly in the content of the notification created by the mention (TODO: create task)
60 +* being able to answer directly to mail eventually received as a notification of a mention (TODO: create trask)
61 +
62 +=== Notifications settings ===
63 +
64 +Notifications of mentions should be integrated in the notifications settings of the wiki, using the notifications framework provided by XWiki.
65 +
66 +Notifications must be activated by default to help users discover the new feature by receiving mentions.
67 +
68 +[[image:file:///home/mleduc/.config/Typora/typora-user-images/image-20200507101357956.png?lastModify=1588846637||alt="image-20200507101357956"]]
69 +
70 +== Extensibility ==
71 +
72 +While the nominal scenario is the integration of mentions inside a xwiki instance (and its sub-wikis). The mentions features must be extensible to let extensions add new features on tops of the mentions.
73 +
74 +The main use case of this is the integration of user mentions on ActivityPub (see [[https:~~/~~/design.xwiki.org/xwiki/bin/view/Proposal/ActivityPub>>url:https://design.xwiki.org/xwiki/bin/view/Proposal/ActivityPub]]).
75 +
76 +The list of extension points should include:
77 +
78 +* users suggestions in the rich editor
79 +* an extension point on the notifications emission.
80 +
81 +In addition, the core of the mentions must support unknown type of external users.
82 +
83 += Discussions =
84 +
85 +== Requesting view rights ==
86 +
87 +If an user tries to access a document for which she does not have the read right (for instance, after being mentioned inside the given document), an action should allow to require an access to the page.
88 +
89 +=== Messaging ===
90 +
91 +The most basic solution is to simply send a message to the user that triggered the mentions, asking for access to the page.
92 +
93 +=== Ad-hoc mechanism ===
94 +
95 +A more advance solution could be to present a button that would send a query to whoever has the right to set the read right for this page.
96 +
97 +
98 += Tasks =
99 +
100 +== Rich editor integration ==
101 +
102 +The rich editor must be integrated on every textarea supporting the xwiki syntax.
103 +
104 +* Comments
105 +* Annotations
106 +
107 +WARNING: other places ?
108 +
109 +== Adding an autocompletion on the rich editor ==
110 +
111 +Typing @ in the rich editor must present an autompletion of available users and groups and automatically insert the corresponding macro in the text.
112 +
113 +== Mention macro ==
114 +
115 +The mention macro must allow to declare a mention. This macro has one field pointing to a single user or group.
116 +
117 +The macro must be display in a distinctive and identifiable way.
118 +
119 +Mentions to the current user and/or a group in which the current is must be highlighted in specific colors.
120 +
121 +The text of the mention should be first name + last name, first name only or user login (the user defining the mention should be able to choose)
122 +
123 +== Mention macro settings ==
124 +
125 +Variations points of the mention macro must be configurable in the skins administration
126 +
127 +[[image:file:///home/mleduc/.config/Typora/typora-user-images/image-20200507110127020.png?lastModify=1588846637||alt="image-20200507110127020"]]
128 +
129 +== Mention in the syntax ==
130 +
131 +Mentions could be integrated as first-class entities in some syntaxes supported in the wiki, if those syntaxes has a build-in support for it.
132 +
133 +=== XWiki/2.2 ===
134 +
135 +In the specific context of xwiki/2.2, user mentions could be build around the notions of link to users, discussed in TODO, TODO and TODO.
136 +
137 +=== Other syntaxes ===
138 +
139 +TBD
140 +
141 +== Mentions history ==
142 +
143 +An user must not be notified of a mention several time for the same entity (document, comment, annotation...).
144 +
145 +A mapping between mentioned users (members of a group must be resolved to their individual users) and entities must be stored and used to identify the relevant notifications.
146 +
147 +Similarly, only members present in a group prior to the group mentions should be notified.
148 +
149 +A mapping between mentioned groups and entities must also be stored.
150 +
151 +A notification is only send to individual users that have not already be notified, and to groups that have not already been notified. Only group members who have not already been notified are notified.
152 +
153 +== Notifications settings ==
154 +
155 +integrate settings in the configuration to activate mentions at the level of the administration and at the level of individual users.
156 +
157 +[[image:file:///home/mleduc/.config/Typora/typora-user-images/image-20200507101630235.png?lastModify=1588846637||alt="image-20200507101630235"]]
158 +
159 +
160 +
7 7  == Existing discussions ==
8 8  
9 9  This section collects existing discussions that are relates to concerns of interest in the context of user mentions.
... ... @@ -28,5 +28,3 @@
28 28  |MediaWiki| | |Special link format (##~[~[User:Username]]##)
29 29  |Drupal|[[https:~~/~~/www.drupal.org/project/mentions>>https://www.drupal.org/project/mentions]]| |Special link format ([@userlogin]). Displayed with the user login prefixed with @
30 30  |Confluence|[[https:~~/~~/confluence.atlassian.com/doc/mentions-251725350.html>>https://confluence.atlassian.com/doc/mentions-251725350.html]]| |User login prefixed with @
31 -
32 -

 

https://forum.xwiki.org/t/user-mention-in-ck-editor/843

Description

Introduction

Mentions are a structured way to reference users in text (e.g., comments, annotations, documents).

They are usually visually distinguishable by an @ prefix followed by the identifier of an user, often in hypertext form (e.g., @mleduc).

    1. Introduction
    2. Mentions Integration
    3. Notifications
      1. Notifications rules
      2. Notifications content
      3. Notifications answer
      4. Notifications settings
    4. Extensibility
  1. Discussions
    1. Requesting view rights
      1. Messaging
      2. Ad-hoc mechanism
  2. Tasks
    1. Rich editor integration
    2. Adding an autocompletion on the rich editor
    3. Mention macro
    4. Mention macro settings
    5. Mention in the syntax
      1. XWiki/2.2
      2. Other syntaxes
    6. Mentions history
    7. Notifications settings
    8. Existing discussions
      1. Links extensibility
    9. Comparison matrix

Mentions Integration

It should be possible to add mentions to users or groups wherever xwiki syntaxes are supported.

A non comprehensive list includes:

  • documents body
  • comments (integrate rich editor)
  • annotations (integrate rich editor)
  • textarea fields in AWM (the rich editor is a user choice in the AWM settings)
  • WARNING: other places ?

In the rich editor it should be easy to include a mention using only the keyboard, and without having to use the macro section of the rich editor menu.

Mentions must be visually identifiable in the text, for instance the user name or group group could have a specific background color. Similarly, mentions to the current user and/or a group in which the current is must be highlighted in specific colors.

The default content of the display mention should be the first name + last name of the user. It should be possible to change it to it first name only, or to the login of the user. I don't know if it's a good idea to be able to allow to change the text of the mention for a free text (confusing, risk of link scamming...).

Mentions of removed users should still be display clearly, eventually identified visually that the user has been removed (which is not easy to identify in the context of AP for instance).

Notifications

Notifications rules

Mentioning a user of a group must trigger a even, eventually leading to the notification of the concerned users.

Nonetheless, user should not be notified several time for the same mention (e.g., when a document is edited and a mention was previously in the document).

Notifications content

The content of a notification must include as much content as possible regarding the context in which the mention occurred. This content must be as specific as possible according to the type of entity in which the mention occurred.

A non comprehensive list includes:

  • the user that made the mention
  • the type of entity in which the mention occurred
  • a direct link to the entity, e.g.,

    • the body of a document, ideally an anchor to the § where the mention occurs.
    • an anchor to a comment
    • an anchor to an annotation

Notifications answer

The most basic scenario is to click on the link in the notification and to interact with the wiki as usual

More advanced scenarios includes:

  • having a form to interact with the content directly in the content of the notification created by the mention (TODO: create task)
  • being able to answer directly to mail eventually received as a notification of a mention (TODO: create trask)

Notifications settings

Notifications of mentions should be integrated in the notifications settings of the wiki, using the notifications framework provided by XWiki.

Notifications must be activated by default to help users discover the new feature by receiving mentions.

image-20200507101357956

Extensibility

While the nominal scenario is the integration of mentions inside a xwiki instance (and its sub-wikis). The mentions features must be extensible to let extensions add new features on tops of the mentions.

The main use case of this is the integration of user mentions on ActivityPub (see https://design.xwiki.org/xwiki/bin/view/Proposal/ActivityPub).

The list of extension points should include:

  • users suggestions in the rich editor
  • an extension point on the notifications emission.

In addition, the core of the mentions must support unknown type of external users.

Discussions

Requesting view rights

If an user tries to access a document for which she does not have the read right (for instance, after being mentioned inside the given document), an action should allow to require an access to the page.

Messaging

The most basic solution is to simply send a message to the user that triggered the mentions, asking for access to the page.

Ad-hoc mechanism

A more advance solution could be to present a button that would send a query to whoever has the right to set the read right for this page.

Tasks

Rich editor integration

The rich editor must be integrated on every textarea supporting the xwiki syntax.

  • Comments
  • Annotations

WARNING: other places ?

Adding an autocompletion on the rich editor

Typing @ in the rich editor must present an autompletion of available users and groups and automatically insert the corresponding macro in the text.

Mention macro

The mention macro must allow to declare a mention. This macro has one field pointing to a single user or group.

The macro must be display in a distinctive and identifiable way.

Mentions to the current user and/or a group in which the current is must be highlighted in specific colors.

The text of the mention should be first name + last name, first name only or user login (the user defining the mention should be able to choose)

Mention macro settings

Variations points of the mention macro must be configurable in the skins administration

image-20200507110127020

Mention in the syntax

Mentions could be integrated as first-class entities in some syntaxes supported in the wiki, if those syntaxes has a build-in support for it.

XWiki/2.2

In the specific context of xwiki/2.2, user mentions could be build around the notions of link to users, discussed in TODO, TODO and TODO.

Other syntaxes

TBD

Mentions history

An user must not be notified of a mention several time for the same entity (document, comment, annotation...).

A mapping between mentioned users (members of a group must be resolved to their individual users) and entities must be stored and used to identify the relevant notifications.

Similarly, only members present in a group prior to the group mentions should be notified.

A mapping between mentioned groups and entities must also be stored.

A notification is only send to individual users that have not already be notified, and to groups that have not already been notified. Only group members who have not already been notified are notified.

Notifications settings

integrate settings in the configuration to activate mentions at the level of the administration and at the level of individual users.

image-20200507101630235

Existing discussions

This section collects existing discussions that are relates to concerns of interest in the context of user mentions.

Mentions in CKEditor https://forum.xwiki.org/t/user-mention-in-ck-editor/843

Links extensibility

Comparison matrix

ProductDocumentationActivityPub?Details
Mastodon yesWebfinger ids or user login for the local instance, prefixed with @.
Twitter noUser login prefixed with @
Wordpresshttps://wordpress.com/support/user-mentions/yes (by extension)User login prefixed with @
Discourse noUser login prefixed with @
Jira noUser login prefixed with @
MediaWiki  Special link format ([[User:Username]])
Drupalhttps://www.drupal.org/project/mentions Special link format ([@userlogin]). Displayed with the user login prefixed with @
Confluencehttps://confluence.atlassian.com/doc/mentions-251725350.html User login prefixed with @

 


 


 

Get Connected