I see your point. but this would not be simply adding functionality really. more like rewriting the whole Notifications plugin and then integrating its http/tcp/udp publishers into the new code. take a look at the source code of both plugins.
I totally see value in what is in Notifications plugin now (like HTTP/UDP/TCP publishers). I would probably want that in my new plugin (even though I personally don't need this now). who is the "gatekeeper" for that plugin? who would approve/reject changes in it? would those authors be okay with those massive changes (which would essentially produce a completely new plugin)? On Monday, July 13, 2015 at 2:03:30 PM UTC-7, Oleg Nenashev wrote: > > IMO it would be better to merge the functionality into the Notifications > plugin. > Both mentioned cases can be addressed in the existing plugin, which may be > helpful for the current plugin users. > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2dfe2b00-b542-4b09-92df-69d2adcdaa7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
