-
Notifications
You must be signed in to change notification settings - Fork 0
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
Dumping everyones code? #3
Comments
if people want to put their projects under the org that is totally fine, but i think it's also totally fine for them to keep ownership as long as they are open to cooperation and they don't become a roadblock |
yea they could include their license under their folder? I mean is it not the same to say pull out relevant snippets of code, and include a license. Vs including their whole project? Also if their project is GNU License I think we cant use it with Apache License, so in that case they would just have to willingly offer snippets with no license. I think keeping ownership will be too cumbersome to make changes, every contribution should be equally owned by everyone. |
i don't think beam-http should own any code, personally. i want to support other projects and encourage cooperation between them, not take them over |
Can a project like that be included in erlang/OTP then? I mean encouraging other projects then makes this a non-code repo, maybe its better to open a Wiki then instead of a github repo? |
What if we dump our relevent code from projects under the project it came from / user if that is not avail?
Then we have 1 central place where we collaborate and pull from all the different sources we have.
For example I put my websocket implemention under websocket_vans163/ and websocket/ folder could be the central collaboration location.
I pushed an example.
The text was updated successfully, but these errors were encountered: