-
Notifications
You must be signed in to change notification settings - Fork 1
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
Make repo public #5
Comments
Uhm, I think we should make sure we're doing the right things first. Then we could open source this. |
Done? |
As in ready to go public? |
I would say no, there's been discussion that this repo/gem should be renamed. https://github.com/twingly/zambezi/pull/84#issuecomment-36110788 |
I'm not sure yet. |
Yes |
@walro I'm curious, why do you think that? |
Because it will have things that are very Twingly specific and not much use to someone else? :) |
I think it's time! It would make life easier when deploying to Heroku, testing on Travis CI. Other than the biggest reason for me is, why not?. |
Will there be a release party? But even without a cake I think it can go public. |
We will definitely have cake. |
Don't think there's any reason to keep this repository private, right?
The text was updated successfully, but these errors were encountered: