Mail Plugin
Locked
Mail Plugin
 
|
I have a few questions about the Mail Plugin:
* Is it being deprecated in favor of a different plugin? Assuming no... * Looking at the github pull requests, it appears this plugin requires some TLC. I've run into a couple annoying bugs myself. Is SpringSource looking for a community owner? Assuming yes...
* What is SpringSource looking for in such a person? Thanks, Nathan Wells
|
Re: Mail Plugin
|
|
Should I be asking this question on the grails dev list? I understand that everyone's busy making such an awesome framework. It's just that I hate to keep patching up my production plugin instances to workaround issues.
I imagine I could just fork the plugin, or do something similarly drastic, but I'd like to reduce, rather than expand the entropy in the universe.
Nathan Wells On Fri, Jun 15, 2012 at 11:33 AM, Nathan Wells <[hidden email]> wrote: I have a few questions about the Mail Plugin: |
|
Forking a plugin isn't expanding entropy, it's just standard working
practice in the open source ecosystem. You fork the plugin, you make the requisite fixes (with tests) and then you submit pull requests - then, the plugin owner (currently Peter Ledbrook I believe) approve them and release a new version. When you're done, you can delete your fork. Voila. What is it that the plugin lacks, in your opinion? I'm (eventually) re-working my sendgrid plugin to integrate more nicely with the mail plugin, so it'd be nice to know what features people are looking for. Cheers, Antony On 18 June 2012 20:57, Nathan Wells <[hidden email]> wrote: > Should I be asking this question on the grails dev list? I understand that > everyone's busy making such an awesome framework. It's just that I hate to > keep patching up my production plugin instances to workaround issues. > > I imagine I could just fork the plugin, or do something similarly drastic, > but I'd like to reduce, rather than expand the entropy in the universe. > > Nathan Wells > > > > On Fri, Jun 15, 2012 at 11:33 AM, Nathan Wells <[hidden email]> wrote: >> >> I have a few questions about the Mail Plugin: >> >> * Is it being deprecated in favor of a different plugin? Assuming no... >> * Looking at the github pull requests, it appears this plugin requires >> some TLC. I've run into a couple annoying bugs myself. Is SpringSource >> looking for a community owner? Assuming yes... >> * What is SpringSource looking for in such a person? >> >> Thanks, >> Nathan Wells > > -- ________________________________ ꜽ . antony jones . http://www.enzy.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Re: Mail Plugin
|
|
Sorry, when I said fork, that was probably incorrect terminology. I mean fork the source, but also start releasing fixes under a new plugin name.
The reasoning for this is that the owner (either Graeme - JIRA or Peter) has been apparently unable to work on it. I'm guessing this is probably because they have many other things to do which are a higher priority.
So, should I fork the project and start a new "Email" grails plugins? Or can I help contribute to the existing plugin in some way (either pull requests, or managing the plugin itself)? I much prefer this second one.
Nathan Wells On Mon, Jun 18, 2012 at 4:49 PM, Antony Jones <[hidden email]> wrote: Forking a plugin isn't expanding entropy, it's just standard working |
Re: Mail Plugin
|
We've been negligent in applying pull requests but please don't create a new plugin that's very similar to this one. That will force users to have to figure out which one to use. If there's a good reason to create a similar plugin that's incompatible (e.g. Shiro vs Spring Security) then that's cool - competition is good. But two similar plugins will just be confusing.
Fork the plugin in the Github sense, i.e. that it's intended to be modified but pulled into the main repo. Keep sending pull requests and be noisy about them. They'll get applied eventually :) Burt
|
Re: Mail Plugin
|
|
Sweet! Hardcore forking action here I come!
Nathan Wells On Mon, Jun 18, 2012 at 8:02 PM, burtbeckwith <[hidden email]> wrote: We've been negligent in applying pull requests but please don't create a new |
Re: Mail Plugin
|
|
So, I submitted my pull request. Please merge at your earliest convenience:
Nathan Wells On Tue, Jun 19, 2012 at 4:08 AM, Nathan Wells <[hidden email]> wrote: Sweet! Hardcore forking action here I come! |
Re: Mail Plugin
|
|
Burt,
Is this the best forum to be noisy about pull requests, or should I do it on the grails-dev list? Nathan Wells On Tue, Jun 19, 2012 at 10:21 AM, Nathan Wells <[hidden email]> wrote: So, I submitted my pull request. Please merge at your earliest convenience: |
Re: Mail Plugin
|
|
OK, grails-dev it is.
Nathan Wells On Wed, Jun 20, 2012 at 12:58 PM, Nathan Wells <[hidden email]> wrote: Burt, |
«
Return to Grails - user
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |