xing/cap_gun

Super simple capistrano deployment notifications. Forked from relevance/cap_gun.

cap_gun's Issues

Commit list may contain unpushed changes

The commit log is being built locally. This may lead to commits being mentioned in the email that are not available in the remote repository, and therefore were not really deployed.

Allow server-side sending of email

Currently, the deployment email is being sent from the machine of the deploying user.
But some users don't have a working smtp server or sendmail setup.

In this case, sending the email on the server side (which usually has a working mail setup) could be an option.

cap_gun should therefore allow a server-side sending of the email. My initial idea is to wrap the email sending in a rake task, which can then be called via cap.

License missing from gemspec

RubyGems.org doesn't report a license for your gem. This is because it is not specified in the gemspec of your last release.

via e.g.

spec.license = 'MIT'
# or
spec.licenses = ['MIT', 'GPL-2']

Including a license in your gemspec is an easy way for rubygems.org and other tools to check how your gem is licensed. As you can image, scanning your repository for a LICENSE file or parsing the README, and then attempting to identify the license or licenses is much more difficult and more error prone. So, even for projects that already specify a license, including a license in your gemspec is a good practice. See, for example, how rubygems.org uses the gemspec to display the rails gem license.

There is even a License Finder gem to help companies/individuals ensure all gems they use meet their licensing needs. This tool depends on license information being available in the gemspec. This is an important enough issue that even Bundler now generates gems with a default 'MIT' license.

I hope you'll consider specifying a license in your gemspec. If not, please just close the issue with a nice message. In either case, I'll follow up. Thanks for your time!

Appendix:

If you need help choosing a license (sorry, I haven't checked your readme or looked for a license file), GitHub has created a license picker tool. Code without a license specified defaults to 'All rights reserved'-- denying others all rights to use of the code.
Here's a list of the license names I've found and their frequencies

p.s. In case you're wondering how I found you and why I made this issue, it's because I'm collecting stats on gems (I was originally looking for download data) and decided to collect license metadata,too, and make issues for gemspecs not specifying a license as a public service :). See the previous link or my blog post about this project for more information.

[Feature request] HTML formatted E-Mails

Kinda weird that I ever request a feature for E-Mails in HTML format, but I think this would be a nice addition. Then you'd be able to link the branch or commit hashes properly for example instead of only providing a simple link to the repository.

Cheers,
Mike