Hello all, I would like to get the email invitation manager up and working again but I'm not sure how to do it. 1. Get the plugin working and write a small application as a front end for it. This is fast and reliable but the plugin system is deprecated and it wouldn't be that cool to be perpetuating dependency on a deprecated system. 2. Rewrite the invitation manager. I think this could be done within the 2.3 timeframe but I can't be sure of it. 2A. Rewrite as an application. This was my first thought, my reasons are because while sending email is a generic need deserving of an API, sending invitation mail is a specific need and if we are to include a public function for each need as specific as invitation email then we will surely end up with a monstrous and unmaintainable API. The problem with an application is that it is harder to maintain and keep clean, we have more systems in place such as checkstyle, advanced IDEs and the strict java compiler which are unavailable in groovy and especially unavailable in velocity. 2B. Rewrite as a module. This has the distinct advantage of the code being easier to manage, but carries the risk of bloated API. At the moment I can't think of any way to make the module available to the application/presentation end without adding to the API. How do you think this should be done? Any other options to avoid growing the api? Caleb