Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project maintenance? #30

Open
aderyabin opened this issue Nov 10, 2014 · 3 comments
Open

Project maintenance? #30

aderyabin opened this issue Nov 10, 2014 · 3 comments

Comments

@aderyabin
Copy link

Hello, @j-mcnally.

My name is Andrey.
First of all, thank you. You've made a lot of work to create integration Capistrano with Slack. I enjoyed it very much on previous projects.

But in last few month project has not answered PR, outdated gems. It also does not support Capistrano 3 and new Slack API features and doesn't have tests.

So, do you have a plan to maintenance capistrano-slack and close above pointed bugs? If no, I'm ready to continue support and develop this gem because we use Capistrano and Slack in our projects actually.

@parkr
Copy link
Contributor

parkr commented Feb 7, 2015

Ditto to this. I have a PR in the works for the new Slack API.

@parkr
Copy link
Contributor

parkr commented Feb 7, 2015

Just released capistrano-slack-notify. https://github.com/parkr/capistrano-slack-notify

@j-mcnally
Copy link
Owner

Hey guys, Sorry for the absence, i've kind of deprecated this project, as other solutions have emerged since, that solve this problem better than this project. This project was started right when slack came out as more of an internal band-aid. it is a fork of capistrano-mountaintop which was what we were already using for campfire when we swtiched. Our team has since moved all our projects to Capistrano-3, Mina or Ansible so there is really little motivation to continue development of the project. I invite people to find a replacement or fork the project and take it over, I wont be mad.

If you use capistrano 3, i highly recommend slackistrano, its what we use internally now with our Cap3 projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants