Changes between Version 82 and Version 83 of AnnouncerPlugin
- Timestamp:
- Aug 10, 2015, 9:46:17 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
AnnouncerPlugin
v82 v83 12 12 == Description 13 13 14 Th e AnnouncerPlugin provides an alternative notification system, that can be used to completelyreplace the default [t:wiki:TracNotification TracNotification].14 This plugin provides an alternative notification system, that can be used to replace the default [t:wiki:TracNotification TracNotification]. 15 15 16 16 === Improve '''users''' Trac experience 17 17 18 With growing number of both tickets and wiki pages, keeping yourself up-to-date on recent changes is a time consuming task and easy to miss important information. The bigger your Trac application and user base, the more important is a flexible announcement system. At the very least, it will allow users to receive ''notices about attachments'', and to ''opt-out from receiving messages'' due to the always_notify_(owner|reporter|updater) options. AnnouncerPlugin has ''wiki subscription'' capabilities ^[1]^ and provides each registered user with a large set of options to adapt change notifications to individual demand.18 With growing number of both tickets and wiki pages, keeping yourself up-to-date on recent changes is a time consuming task and easy to miss important information. The bigger your Trac application and user base, the more important is a flexible announcement system. At the very least, it will allow users to receive ''notices about attachments'', and to ''opt-out from receiving messages'' due to the always_notify_(owner|reporter|updater) options. AnnouncerPlugin has ''wiki subscription'' capabilities and provides each registered user with a large set of options to adapt change notifications to individual demand (see WikiNotificationPlugin for another approach). 19 19 20 20 === Get room for promising '''development''' … … 26 26 While sharing all knowledge is a great idea in a perfect world, real-world businesses commonly rely on tight informational restrictions, that customers can rely on. In professional communication cryptographically signed and encrypted email is essential. AnnouncerPlugin will become a building block of this new [t:wiki:TracDev/TrustedTrac Trusted Trac] information management. OpenPGP support is [wiki:AnnouncerPlugin/MessageEncryption on the way]. 27 27 28 ^[1]^ see WikiNotificationPlugin for another approach 29 30 AnnouncerPlugin extensions: 31 * QuietPlugin 28 AnnouncerPlugin extensions: QuietPlugin 32 29 33 30 == Installation and Configuration … … 36 33 37 34 * AnnouncerPlugin will only ever run on Trac 0.11b1 or later. 38 * While development is done with Trac 0.11 still in mind, i .e.to get full internationalization support you'll want to checkout from 'trunk' branch not before you have [http://babel.edgewall.org Babel] installed on your system.35 * While development is done with Trac 0.11 still in mind, ie to get full internationalization support you'll want to checkout from 'trunk' branch not before you have [http://babel.edgewall.org Babel] installed on your system. 39 36 Beware: This plugin may break notifications from other Trac plugins that use the default [t:wiki:TracNotification TracNotification] system. A plugin that sends notifications using the !TracNotification system needs to be modified to use the AnnouncerPlugin API. For example, see the aforementioned [AnnouncerPlugin/PluginSupport/FullBlogPlugin FullBlogPlugin]. 40 37 … … 50 47 As of r3107 (dubbed v0.2), the AnnouncerPlugin has been working in a basic way in our corporate Trac installation. This includes all the mentioned modules above, in particular the notification of Wiki additions/changes/deletions to anyone interested, 'watching' interesting resources, HTML ticket notifications, and such. 51 48 52 The email distribution is not as stable and complete as the default [t:wiki:TracNotification TracNotifications] yet; there are options that are not yet taken into account, and a lot of stuff particularly focused around codecs that are simplyignored right now. So while it could still work, there could be errors.49 The email distribution is not as stable and complete as the default [t:wiki:TracNotification TracNotifications] yet; there are options that are not yet taken into account, and a lot of stuff particularly focused around codecs that are ignored right now. So while it could still work, there could be errors. 53 50 54 51 === Installation … … 90 87 ==== Save on migration 91 88 92 If you configured the [t:wiki:TracNotification TracNotification] system before, another approach to Announcerconfiguration is to simply rename the `[notification]` section in your ''trac.ini'' to `[announcer]`. Where possible, the option names are the same. Additional options that may be available are specified above in the modules section.89 If you configured the [t:wiki:TracNotification TracNotification] system before, another approach to configuration is to simply rename the `[notification]` section in your ''trac.ini'' to `[announcer]`. Where possible, the option names are the same. Additional options that may be available are specified above in the modules section. 93 90 94 91 ==== Deep waters … … 127 124 === Modular per-user configuration 128 125 129 The plugin itself is very modular, and exactly what features you have will dependon which modules you enable. You select modules in the 'Plugins' page of the 'Admin' section of your Trac as stated the [#Centralconfiguration previous section].126 The plugin itself is very modular, and exactly what features you have depends on which modules you enable. You select modules in the 'Plugins' page of the 'Admin' section of your Trac as stated the [#Centralconfiguration previous section]. 130 127 131 128 ==== Legacy Modules … … 165 162 ==== General Wiki 166 163 167 If you would like to receive more general notice of wiki changes, you can use the ''!GeneralWikiSubscriber''. With it you may specify any number of patterns, and if they match a wiki page name, you'll receive a notice if that page is created, edited , deleted, or such.164 If you would like to receive more general notice of wiki changes, you can use the ''!GeneralWikiSubscriber''. With it you may specify any number of patterns, and if they match a wiki page name, you'll receive a notice if that page is created, edited or deleted. 168 165 169 166 In particular, you may use a pattern of '*' and you'll see any wiki changes that happen on the site. … … 179 176 The HTML formatter also sends out a plain text alternative for those email clients that may not support HTML email. 180 177 181 Ticket change messages are built from Genshi text template `ticket_email_plaintext.txt`. Additionally the following trac.inioptions are available to configure the ticket formatter:178 Ticket change messages are built from Genshi text template `ticket_email_plaintext.txt`. Additionally the following `trac.ini` options are available to configure the ticket formatter: 182 179 183 180 ticket_email_subject:: … … 190 187 ==== Distributors 191 188 192 Although the goal is to allow many kinds of distribution, at this point we're only delivering to email addresses. The ''!EmailDistributor'' uses the same options as the old trac notification, just (as above) in the ''announcer'' section and not the ''notification'' section.189 Although the goal is to allow many kinds of distribution, at this point we're only delivering to email addresses. The ''!EmailDistributor'' uses the same options as the old Trac notification, just (as above) in the ''announcer'' section and not the ''notification'' section. 193 190 194 191 There are a few additional ones: … … 201 198 Currently, the following resolvers can be configured to map usernames to email addresses: 202 199 203 * ''!DefaultDomainEmailResolver'': This will simplyblindly append the domain specified in [announcer] smtp_default_domain onto the end of the username.200 * ''!DefaultDomainEmailResolver'': This will blindly append the domain specified in [announcer] smtp_default_domain onto the end of the username. 204 201 * ''!SpecifiedEmailResolver'': This will allow the user to override the email address in Trac (or anywhere else) to demand all email be sent to a certain address specified in their user preferences (and separate from Trac's normal address) 205 202 * ''!SessionEmailResolver'': This will retrieve the email address associated with the username's Trac session. … … 273 270 }}} 274 271 1. Setup a virtualenv and install everything in it: 275 {{{ 276 #!sh 272 {{{#!sh 277 273 ~/src/th-announcer $ cd 278 274 ~ $ virtualenv th-announcer … … 313 309 python ./setup.py bdist_egg 314 310 }}} 315 Due to a know Trac issue Babel has to be installed prior to Trac, to get it all working as expected.[[BR]] 316 Again, for more details see the [t:wiki:CookBook/PluginL10N#Compileanduseit l10n cookbook page for Trac plugins].311 312 Due to a known Trac issue Babel has to be installed prior to Trac, to get it all working as expected. For more details see the [t:wiki:CookBook/PluginL10N#Compileanduseit l10n cookbook page for Trac plugins]. 317 313 318 314 === Email Configuration