> - GitHub... don't message me on GitHub. None of the Lift committer will > pull from your repository. The Lift IP is clean which means that unless > you > are a committer and you have written the code yourself, it doesn't get into > Lift. This allows businesses to use Lift knowing what the provenance of > the > code is.
Sorry if I'm being dense, but does this include patches for small enhancements and bug fixes? For example, I posted a message on the list about some limitations in the Mailer configuration. I made some small modifications to the class so that it works better in shared vm environments, but I'd like to see those changes (or at least similar functionality) make it back into Lift because 1) I think it would be useful to other people, and 2) maintaining my own Mailer for all my projects causes a maintenance penalty that I'm interested in not paying in the long term. What is the best thing I can do to help make that happen? In most communities I've been involved with in the past, the answer is "Submit a patch!", but it appears that may not be the case here. And FYI - the Mailer issue isn't really that critical, I'm just using it as an example. Thanks, - Spencer --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
