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

How should we proceed for this repo? #1

Open
asgeirbirkis opened this issue May 7, 2015 · 1 comment
Open

How should we proceed for this repo? #1

asgeirbirkis opened this issue May 7, 2015 · 1 comment
Labels

Comments

@asgeirbirkis
Copy link

I have the first pieces of code ready to be put into this repo. Should we push directly to master or follow the master/development/branches model of the main repo? Should we have some review process in place, or simply push? I'd be interesting in hearing thoughts, I don't want to push to master until that has been decided.

@asgeirbirkis
Copy link
Author

I should add that my current thinking is that we should have some sort of review process in place, not as thorough as for the main repo, but perhaps we should create pull requests so that those interested can take a look before it gets merged, and assuming no one raises concerns within a week, the author him or herself can then merge (so that things don't get held up for multiple weeks due to lack of code reviewers).

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

1 participant