Fossil SCM
Updated change log and chat.md for the /chat switch to markdown.
Commit
32bd273ebf6d1008d49d8d52c8bfea64cb8add7e43880bd18a35c896b621067c
Parent
52d40548ed2a117…
2 files changed
+5
+10
-21
+5
| --- www/changes.wiki | ||
| +++ www/changes.wiki | ||
| @@ -39,10 +39,15 @@ | ||
| 39 | 39 | * The [/help?cmd=all|fossil all git status] command only shows reports for |
| 40 | 40 | the subset of repositories that have a configured Git export. |
| 41 | 41 | * Enhanced the [/help?cmd=/chat|/chat page] configuration and added the ability |
| 42 | 42 | for a repository administrator to [./chat.md#notifications|extend the |
| 43 | 43 | selection of notification sounds via unversioned files]. |
| 44 | + * The [/help?cmd=/chat|/chat] messages now use fossil's full complement of | |
| 45 | + markdown features, instead of the prior small subset of markup it | |
| 46 | + previously supported. This retroactively applies to all chat messages, | |
| 47 | + as they are markdown-processed when they are sent instead of when they | |
| 48 | + are saved. See [./chat.md#usage|the chat docs] for more details. | |
| 44 | 49 | |
| 45 | 50 | <h2 id='v2_16'>Changes for Version 2.16 (2021-07-02)</h2> |
| 46 | 51 | * <b>Security:</b> Fix the client-side TLS so that it verifies that the |
| 47 | 52 | server hostname matches its certificate. |
| 48 | 53 | * The default "ssh" command on Windows is changed to "ssh" instead of the |
| 49 | 54 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -39,10 +39,15 @@ | |
| 39 | * The [/help?cmd=all|fossil all git status] command only shows reports for |
| 40 | the subset of repositories that have a configured Git export. |
| 41 | * Enhanced the [/help?cmd=/chat|/chat page] configuration and added the ability |
| 42 | for a repository administrator to [./chat.md#notifications|extend the |
| 43 | selection of notification sounds via unversioned files]. |
| 44 | |
| 45 | <h2 id='v2_16'>Changes for Version 2.16 (2021-07-02)</h2> |
| 46 | * <b>Security:</b> Fix the client-side TLS so that it verifies that the |
| 47 | server hostname matches its certificate. |
| 48 | * The default "ssh" command on Windows is changed to "ssh" instead of the |
| 49 |
| --- www/changes.wiki | |
| +++ www/changes.wiki | |
| @@ -39,10 +39,15 @@ | |
| 39 | * The [/help?cmd=all|fossil all git status] command only shows reports for |
| 40 | the subset of repositories that have a configured Git export. |
| 41 | * Enhanced the [/help?cmd=/chat|/chat page] configuration and added the ability |
| 42 | for a repository administrator to [./chat.md#notifications|extend the |
| 43 | selection of notification sounds via unversioned files]. |
| 44 | * The [/help?cmd=/chat|/chat] messages now use fossil's full complement of |
| 45 | markdown features, instead of the prior small subset of markup it |
| 46 | previously supported. This retroactively applies to all chat messages, |
| 47 | as they are markdown-processed when they are sent instead of when they |
| 48 | are saved. See [./chat.md#usage|the chat docs] for more details. |
| 49 | |
| 50 | <h2 id='v2_16'>Changes for Version 2.16 (2021-07-02)</h2> |
| 51 | * <b>Security:</b> Fix the client-side TLS so that it verifies that the |
| 52 | server hostname matches its certificate. |
| 53 | * The default "ssh" command on Windows is changed to "ssh" instead of the |
| 54 |
+10
-21
| --- www/chat.md | ||
| +++ www/chat.md | ||
| @@ -4,15 +4,15 @@ | ||
| 4 | 4 | |
| 5 | 5 | As of version 2.14, |
| 6 | 6 | Fossil supports a developer chatroom feature. The chatroom provides an |
| 7 | 7 | ephemeral discussion venue for insiders. Design goals include: |
| 8 | 8 | |
| 9 | - * **Simple but functional** → Fossil chat is designed to provide a | |
| 10 | - convenient real-time communication mechanism for geographically | |
| 11 | - dispersed developers. Fossil chat is *not* intended | |
| 12 | - as a replacement or | |
| 13 | - competitor for IRC, Slack, Discord, Telegram, Google Hangouts, etc. | |
| 9 | + * **Simple but functional** → | |
| 10 | + Fossil chat is designed to provide a convenient real-time | |
| 11 | + communication mechanism for geographically dispersed developers. | |
| 12 | + Fossil chat is *not* intended as a replacement or competitor for | |
| 13 | + IRC, Slack, Discord, Telegram, Google Hangouts, etc. | |
| 14 | 14 | |
| 15 | 15 | * **Low administration** → |
| 16 | 16 | You can activate the chatroom in seconds without having to |
| 17 | 17 | mess with configuration files or install new software. |
| 18 | 18 | In an existing [server setup](./server/), |
| @@ -53,34 +53,23 @@ | ||
| 53 | 53 | behavior of chat, though the default settings are reasonable so in most |
| 54 | 54 | cases those settings can be ignored. The settings control things like |
| 55 | 55 | the amount of time that chat messages are retained before being purged |
| 56 | 56 | from the repository database. |
| 57 | 57 | |
| 58 | -## Usage | |
| 58 | +## <a id="usage"></a>Usage | |
| 59 | 59 | |
| 60 | 60 | For users with appropriate permissions, simply browse to the |
| 61 | 61 | [/chat](/help?cmd=/chat) to start up a chat session. The default |
| 62 | 62 | skin includes a "Chat" entry on the menu bar on wide screens for |
| 63 | 63 | people with chat privilege. There is also a "Chat" option on |
| 64 | 64 | the [Sitemap page](/sitemap), which means that chat will appear |
| 65 | 65 | as an option under the hamburger menu for many [skins](./customskin.md). |
| 66 | 66 | |
| 67 | -Message text is delivered verbatim. There is no markup. However, | |
| 68 | -the chat system does try to identify and tag hyperlinks, as follows: | |
| 69 | - | |
| 70 | - * Any word that begins with "http://" or "https://" is assumed | |
| 71 | - to be a hyperlink and is tagged. | |
| 72 | - | |
| 73 | - * Text within `[...]` is parsed, and it if is a valid hyperlink | |
| 74 | - target (according to the way that [Fossil Wiki](/wiki_rules) or | |
| 75 | - [Markdown](/md_rules) understand hyperlinks), then that text is | |
| 76 | - tagged. Note that only URLs and Fossil-internal constructs such | |
| 77 | - as checkin hashes and wiki pages names are recognized here, not | |
| 78 | - constructs such as `[URL | label]` or `[label](URL)`. | |
| 79 | - | |
| 80 | -Apart from adding hyperlink anchor tags to bits of text that look | |
| 81 | -like hyperlinks, no changes are made to the input text. | |
| 67 | +As of version 2.17, chat messages are subject to [fossil's | |
| 68 | +full range of markdown processing](/md_rules). Because chat messages are | |
| 69 | +stored as-is when they arrive from a client, this change applies | |
| 70 | +retroactively to messages stored by previous fossil versions. | |
| 82 | 71 | |
| 83 | 72 | Files may be sent via chat using the file selection element at the |
| 84 | 73 | bottom of the page. If the desktop environment system supports it, |
| 85 | 74 | files may be dragged and dropped onto that element. Files are not |
| 86 | 75 | automatically sent - selection of a file can be cancelled using the |
| 87 | 76 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -4,15 +4,15 @@ | |
| 4 | |
| 5 | As of version 2.14, |
| 6 | Fossil supports a developer chatroom feature. The chatroom provides an |
| 7 | ephemeral discussion venue for insiders. Design goals include: |
| 8 | |
| 9 | * **Simple but functional** → Fossil chat is designed to provide a |
| 10 | convenient real-time communication mechanism for geographically |
| 11 | dispersed developers. Fossil chat is *not* intended |
| 12 | as a replacement or |
| 13 | competitor for IRC, Slack, Discord, Telegram, Google Hangouts, etc. |
| 14 | |
| 15 | * **Low administration** → |
| 16 | You can activate the chatroom in seconds without having to |
| 17 | mess with configuration files or install new software. |
| 18 | In an existing [server setup](./server/), |
| @@ -53,34 +53,23 @@ | |
| 53 | behavior of chat, though the default settings are reasonable so in most |
| 54 | cases those settings can be ignored. The settings control things like |
| 55 | the amount of time that chat messages are retained before being purged |
| 56 | from the repository database. |
| 57 | |
| 58 | ## Usage |
| 59 | |
| 60 | For users with appropriate permissions, simply browse to the |
| 61 | [/chat](/help?cmd=/chat) to start up a chat session. The default |
| 62 | skin includes a "Chat" entry on the menu bar on wide screens for |
| 63 | people with chat privilege. There is also a "Chat" option on |
| 64 | the [Sitemap page](/sitemap), which means that chat will appear |
| 65 | as an option under the hamburger menu for many [skins](./customskin.md). |
| 66 | |
| 67 | Message text is delivered verbatim. There is no markup. However, |
| 68 | the chat system does try to identify and tag hyperlinks, as follows: |
| 69 | |
| 70 | * Any word that begins with "http://" or "https://" is assumed |
| 71 | to be a hyperlink and is tagged. |
| 72 | |
| 73 | * Text within `[...]` is parsed, and it if is a valid hyperlink |
| 74 | target (according to the way that [Fossil Wiki](/wiki_rules) or |
| 75 | [Markdown](/md_rules) understand hyperlinks), then that text is |
| 76 | tagged. Note that only URLs and Fossil-internal constructs such |
| 77 | as checkin hashes and wiki pages names are recognized here, not |
| 78 | constructs such as `[URL | label]` or `[label](URL)`. |
| 79 | |
| 80 | Apart from adding hyperlink anchor tags to bits of text that look |
| 81 | like hyperlinks, no changes are made to the input text. |
| 82 | |
| 83 | Files may be sent via chat using the file selection element at the |
| 84 | bottom of the page. If the desktop environment system supports it, |
| 85 | files may be dragged and dropped onto that element. Files are not |
| 86 | automatically sent - selection of a file can be cancelled using the |
| 87 |
| --- www/chat.md | |
| +++ www/chat.md | |
| @@ -4,15 +4,15 @@ | |
| 4 | |
| 5 | As of version 2.14, |
| 6 | Fossil supports a developer chatroom feature. The chatroom provides an |
| 7 | ephemeral discussion venue for insiders. Design goals include: |
| 8 | |
| 9 | * **Simple but functional** → |
| 10 | Fossil chat is designed to provide a convenient real-time |
| 11 | communication mechanism for geographically dispersed developers. |
| 12 | Fossil chat is *not* intended as a replacement or competitor for |
| 13 | IRC, Slack, Discord, Telegram, Google Hangouts, etc. |
| 14 | |
| 15 | * **Low administration** → |
| 16 | You can activate the chatroom in seconds without having to |
| 17 | mess with configuration files or install new software. |
| 18 | In an existing [server setup](./server/), |
| @@ -53,34 +53,23 @@ | |
| 53 | behavior of chat, though the default settings are reasonable so in most |
| 54 | cases those settings can be ignored. The settings control things like |
| 55 | the amount of time that chat messages are retained before being purged |
| 56 | from the repository database. |
| 57 | |
| 58 | ## <a id="usage"></a>Usage |
| 59 | |
| 60 | For users with appropriate permissions, simply browse to the |
| 61 | [/chat](/help?cmd=/chat) to start up a chat session. The default |
| 62 | skin includes a "Chat" entry on the menu bar on wide screens for |
| 63 | people with chat privilege. There is also a "Chat" option on |
| 64 | the [Sitemap page](/sitemap), which means that chat will appear |
| 65 | as an option under the hamburger menu for many [skins](./customskin.md). |
| 66 | |
| 67 | As of version 2.17, chat messages are subject to [fossil's |
| 68 | full range of markdown processing](/md_rules). Because chat messages are |
| 69 | stored as-is when they arrive from a client, this change applies |
| 70 | retroactively to messages stored by previous fossil versions. |
| 71 | |
| 72 | Files may be sent via chat using the file selection element at the |
| 73 | bottom of the page. If the desktop environment system supports it, |
| 74 | files may be dragged and dropped onto that element. Files are not |
| 75 | automatically sent - selection of a file can be cancelled using the |
| 76 |