Re: email-ext plugin adoption

2018-10-11 Thread Tobias Gruetzmacher
Hi, On Wed, Oct 10, 2018 at 07:21:53PM +1030, David van Laatum wrote: > The next thing I was planning to do was rip a bunch of stuff out and > put it into a ext-notification plugin that is extendable to allow > multiple backend drivers ie email and slack. As I see most > notification style

Re: email-ext plugin adoption

2018-10-10 Thread Jesse Glick
On Wed, Oct 10, 2018 at 4:52 AM David van Laatum wrote: > most notification style plugins basically implementing the same thing and are > often quite limited unless you use pipelines My (old) thoughts in this area FWIW:

Re: email-ext plugin adoption

2018-10-10 Thread David van Laatum
Cool The next thing I was planning to do was rip a bunch of stuff out and put it into a ext-notification plugin that is extendable to allow multiple backend drivers ie email and slack. As I see most notification style plugins basically implementing the same thing and are often quite limited

Re: email-ext plugin adoption

2018-10-08 Thread Matt Sicker
I'd be interested in being a co-maintainer. On Mon, Oct 8, 2018 at 3:07 PM Slide wrote: > The email-ext plugin is currently up for adoption, looking for > co-maintainers. I used to be maintainer of this plugin and would like to > help again. I already have access to release in the repository

email-ext plugin adoption

2018-10-08 Thread Slide
The email-ext plugin is currently up for adoption, looking for co-maintainers. I used to be maintainer of this plugin and would like to help again. I already have access to release in the repository permissions stuff, and I am already part of the permissions groups on GitHub, but I wanted to