-
Notifications
You must be signed in to change notification settings - Fork 28
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
Add a CONTRIBUTING file #31
Comments
@jywarren what do you think about this one? |
Well, I think the README can be quite long before this is needed, and it's great for it to be all in one place. So maybe we could wait on this until the README gets really really long? |
@jywarren sure, sounds good. |
@jywarren @ryzokuken can I work on this as my first contribution to PublicLab |
Sure! Please feel free to go ahead.
…On Sun 18 Feb, 2018, 1:50 PM Amit singh, ***@***.***> wrote:
@jywarren <https://github.com/jywarren> @ryzokuken
<https://github.com/ryzokuken> can I work on this as my first
contribution to PublicLab
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMg3Mt3Z5c464QwCWy4MKHHhCIu6Xk8mks5tV91igaJpZM4N2dCh>
.
|
@ryzokuken what I understand from the issue is that we need to create a CONTRIBUTING .md file. but what things I have to write in the file. |
Try looking at a few CONTRIBUTING.md files, especially the one we use at plots2. We'd basically need resources for new contributors in there. Make a PR with a dummy file and we could discuss the specifics inside that PR. Thanks. |
@ryzokuken could you please review the PR #94 |
@ryzokuken @jywarren can I close this one as #94 seems to solve this issue? Thanks! |
Add a CONTRIBUTING markdown file, shift the current contribution information from the README to this file, add information about how to name branches and everything, general guidelines regarding contributing to the project. Also, this file would be the most appropriate place to include the content to be added under #11.
Link this file to the README.
The text was updated successfully, but these errors were encountered: