On Oct 13, 10:49 pm, Robert C Corsaro <[EMAIL PROTECTED]> wrote: > I was wondering if I could have a branch to work on something like the > announcerplugin design as a core trac service. The code quality isn't > to good, so I hope to use most of the trac notification for the low > level impl, but the overall design like the announceplugin.
Robert, Thanks for your interest in helping out with this! Redoing notification is definately on the roadmap for the Trac project, and it should be much easier than today to reuse, extend and hook into it. This topic has been much discussed over the years, and there are also heaps of tickets related to improving and extending the notification "subsystem". What has been lacking is progress, and hopefully you can be able help us into the future here :-) I haven't looked at that particular plugin much, and likely I'm not alone in that I suppose. What I would like before work on a branch is started is a proposal with details on basic design, api, usage samples, references to related tickets and other related information - see http://trac.edgewall.org/wiki/TracDev/Proposals. We should document such major topics anyway, and it makes it easier to decide on "go" and review it as it makes progress. :::simon https://www.coderesort.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
