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

default settings in this repo #8

Open
rlidwka opened this issue Aug 20, 2014 · 4 comments
Open

default settings in this repo #8

rlidwka opened this issue Aug 20, 2014 · 4 comments
Labels

Comments

@rlidwka
Copy link
Member

rlidwka commented Aug 20, 2014

Okay, as I said in #1, I don't know what the default settings here should be.

For example, recently jshttp/http-utils repo was created, should we add it here or not? If yes, we'll essentially have two identical repos. If not, this repo will be just an outdated version of that one. Weird.

@Fishrock123
Copy link
Member

I think we should turn this into a module that just does some basic templating and generation. Right now the setup is just silly.

@rlidwka
Copy link
Member Author

rlidwka commented Aug 20, 2014

Right now you can change anything here. For example, you moved keywords to config file, but you could've just changed the template in your repos instead. Git will resolve merge conflicts by itself.

If you turn it to a generator, I'm afraid we'll lose that.

@jonathanong
Copy link
Contributor

i think what we have is fine. maybe remove all but one maintainer and one project.

@rlidwka
Copy link
Member Author

rlidwka commented Aug 20, 2014

yeah, just add this repo to make it self-contained :)

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

No branches or pull requests

3 participants