-
Notifications
You must be signed in to change notification settings - Fork 3
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
forks to JuliaClimate org? #8
Comments
Hi @gaelforget , I did this on purpose but I understand how this is confusing. I'm still wondering where these 2 open source and community oriented repo should live. I know it shouldn't be my personal github account, but an organization. |
Thanks for the quick feedback. A few thoughts:
On the last one, this is basically what I do for JuliaClimate repos : fork them to my own account to do the dev / trial & error stuff using branches there, and PR back to the JuliaClimate repo if / when I feel it's ready for merge. I feel that this is a good way to avoid cluttering the main repo with a bunch of dev branches & so on. On the JuliaClimate org side I feel that we should clarify expectations, but in my view it's a place for the community to host and obtain original material from, not one to clutter with forks for doing one's dev and then PR'ing back to some other org. Wouldn't you agree? |
Thanks for the explanations @gaelforget ! I do agree. I am still a beginner at Git and GitHub and didn't know all the layers you explained. It makes sense. I will remove the forks. |
Cool. Welcome to GitHub and thanks for contributing OSS! In case that's useful, we did this doc aimed at new MIT students a couple years ago. Also I find that the github guides are a great resource and the stuff I suggested earlier is explained here incl on git <-> GitHub. Happy new year to you as well. Cheers, |
Hi @AlexisRenchon
was wondering whether you purposedly forked this repo and www.cupoftea.earth to JuliaClimate. Maybe you meant to transfer the repos to JuliaClimate, or to fork to your own GitHub account instead?
The text was updated successfully, but these errors were encountered: