I'll gladly take over http://trac-hacks.org/wiki/LoomingCloudsPlugin http://trac-hacks.org/wiki/SensitiveTicketsPlugin http://trac-hacks.org/wiki/RenameTracUsersScript http://trac-hacks.org/wiki/TicketSubmitPolicyPlugin
I can find a use for them. I won't be able to do any feature requests for a month or so (reasonably busy at the moment) but I can go through and fix bugs (and make sure they all work with 0.11.7). Let me know if you're ok with me taking of all/some of these. ~Rowan/Obs On Mar 11, 12:34 pm, Jeff Hammel <[email protected]> wrote: > Hi, > > I am the author and maintainer of the plugins > athttp://trac-hacks.org/wiki/k0s. These were mostly written for my previous > job at The Open Planning Project. While most of my Trac development of late > has not been officially supported, I have tried to be as prompt as I could > to fix bugs, particularly when patches and useful debugging information was > provided (*hint hint*). > > Now, I am no longer working at The Open Planning Project. While I still use > Trac for my own use, I will not have time to maintain all of my plugins. > So....I'm putting out the offer to either adopt out or co-maintain my > plugins, hopefully by people that still use them or are interested in. > > The first set are plugins I just won't use again, as they no longer fit the > Trac use cases I care about: > *http://trac-hacks.org/wiki/AutoQueryPlugin: this is already in Trac > core. Hopefully it will be in 0.12 when it is released. In any case, as > useful as it is, I don't care about maintaining it > *http://trac-hacks.org/wiki/ContactInfoPlugin: I don't really need this > for my personal Trac > *http://trac-hacks.org/wiki/CustomFieldProviderPlugin: probably should > never have written; provides custom ticket fields programmatically > *http://trac-hacks.org/wiki/LdapAuthStorePlugin: I don't use LDAP at > home; why would I? so I don't need this guy > *http://trac-hacks.org/wiki/LoomingCloudsPlugin: cute, but I don't really > use it > *http://trac-hacks.org/wiki/PdfRendererPlugin: again cute, but I'll just > avoid the issue by not putting up horrible PDFs on my Trac > *http://trac-hacks.org/wiki/RenameTracUsersScript > *http://trac-hacks.org/wiki/RepositoryHookSystemPlugin: its my > understanding that there is a pluggable hook infrastructure in 0.12; so I > don't really care about this guy > *http://trac-hacks.org/wiki/SharedCookieAuthPlugin: I don't care about > this at all right now > *http://trac-hacks.org/wiki/SimpleCaptchaPlugin > *http://trac-hacks.org/wiki/SvnChangeListenerPlugin: I don't use SVN > anymore > *http://trac-hacks.org/wiki/SvnUrlsPlugin: see above > *http://trac-hacks.org/wiki/TicketMoverPlugin > *http://trac-hacks.org/wiki/TracHoursPlugin > *http://trac-hacks.org/wiki/TracLdapAuthPlugin > *http://trac-hacks.org/wiki/TracOpenThreeOneOnePlugin > *http://trac-hacks.org/wiki/TracViewScript: cute, especially for > learning, but I don't care about it. > > The second set are plugins I care about, but would gladly adopt out or > co-maintain as I doubt I will have much time to maintain them: > *http://trac-hacks.org/wiki/AutoUpgradePlugin: I really hope this gets > fixed for real. Install a plugin should not re > *http://trac-hacks.org/wiki/AutocompleteUsersPlugin > *http://trac-hacks.org/wiki/CaptchaAuthPlugin > *http://trac-hacks.org/wiki/ComponentDependencyPlugin: an infrastructure > plugin I use in other plugins that have allow components to require other > components. Again, I'd love to see this in Trac core > *http://trac-hacks.org/wiki/CreatePluginScript: allows easy plugin > skeleton creation > *http://trac-hacks.org/wiki/IcalExporterPlugin > *http://trac-hacks.org/wiki/SensitiveTicketsPlugin: add a checkbox for > secure tickets; what most people think PrivateTicketsPlugin does > *http://trac-hacks.org/wiki/TicketSidebarProviderPlugin > *http://trac-hacks.org/wiki/TicketSubmitPolicyPlugin > *http://trac-hacks.org/wiki/TracPluginTemplateScript > *http://trac-hacks.org/wiki/TracSqlHelperScript: I really hate when the > backend sticks out in front. My admittedly horrible solution > > The third and last set of plugins I care about enough not to just give over > to someone. I would love co-maintainers, but I want to have some sort of > guided development, whereas the above I don't really care what happens to > them so long as they work (and work well with other plugins) and are > maintained: > *http://trac-hacks.org/wiki/GeoTicketPlugin: locate issues with tickets; > its a complicated plugin that I have some ideas how to improve, but have no > time right now > *http://trac-hacks.org/wiki/ImageTracPlugin: again, I'd love help, but > don't want to lose control of this one (yet, anyway) > *http://trac-hacks.org/wiki/MailToTracPlugin: pluggable alternative to > email2trac > *http://trac-hacks.org/wiki/TracLegosScript: I think this plugin could go > far. If only I had time to get it there > > The rest either don't need maintainence or are spoken for. If you have > interest in comaintaining or adopting any of these plugins contact me and > I'll mail otaku to set you up. For those that don't care, sorry for the > spam. > > Jeff Hammel > > _______________________________________________ > th-users mailing list > [email protected]https://lists.trac-hacks.org/mailman/listinfo/th-users _______________________________________________ th-users mailing list [email protected] https://lists.trac-hacks.org/mailman/listinfo/th-users
