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

Make repo public #5

Closed
dentarg opened this issue Feb 20, 2014 · 12 comments
Closed

Make repo public #5

dentarg opened this issue Feb 20, 2014 · 12 comments

Comments

@dentarg
Copy link
Collaborator

dentarg commented Feb 20, 2014

Don't think there's any reason to keep this repository private, right?

@jage
Copy link
Contributor

jage commented Feb 20, 2014

Uhm, I think we should make sure we're doing the right things first.
The README and code quality is too low at the moment.

Then we could open source this.

@dentarg
Copy link
Collaborator Author

dentarg commented Feb 26, 2014

Done?

@walro
Copy link
Contributor

walro commented Feb 26, 2014

Done?

As in ready to go public?

@jage
Copy link
Contributor

jage commented Feb 26, 2014

Done?

I would say no, there's been discussion that this repo/gem should be renamed.

https://github.com/twingly/zambezi/pull/84#issuecomment-36110788

@jage
Copy link
Contributor

jage commented Feb 26, 2014

Uhm, I think we should make sure we're doing the right things first.

I'm not sure yet.

@dentarg
Copy link
Collaborator Author

dentarg commented Feb 26, 2014

As in ready to go public?

Yes

@walro
Copy link
Contributor

walro commented Mar 10, 2014

I think we can safely say that this cannot go public if we do #6, so if you agree with #6 I think this can be closed.

@dentarg
Copy link
Collaborator Author

dentarg commented Mar 10, 2014

@walro I'm curious, why do you think that?

@walro
Copy link
Contributor

walro commented Mar 10, 2014

Because it will have things that are very Twingly specific and not much use to someone else? :)

@jage
Copy link
Contributor

jage commented Jul 16, 2014

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?.

@walro
Copy link
Contributor

walro commented Jul 16, 2014

Will there be a release party? But even without a cake I think it can go public.

@dentarg
Copy link
Collaborator Author

dentarg commented Jul 16, 2014

We will definitely have cake.

@jage jage closed this as completed Jul 16, 2014
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