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

Discussion: Same repo for all? or separate? #42

Open
krishnadasmallya opened this issue Mar 9, 2016 · 2 comments
Open

Discussion: Same repo for all? or separate? #42

krishnadasmallya opened this issue Mar 9, 2016 · 2 comments

Comments

@krishnadasmallya
Copy link

Are we planning to use the same repo for all kind of code say for instance for #12 are we planning to manage it in the same repo?

I would suggest the owner of the same can create a separate repo and others following the task could contribute to it, this will give more among us an opportunity to own a repo.

@sujeshchirackkal
Copy link

It is going to be separate repo tasks like these. But an issue is raised here as it has to be tested using upswing. I have created one for Scalding already. Can create more based on the context.

@krishnadasmallya
Copy link
Author

I would suggest let owner of the task do that themselves so they have a repo to their name, thoughts?

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
@sujeshchirackkal @krishnadasmallya and others