-
Notifications
You must be signed in to change notification settings - Fork 11
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
[DISQ-6] Add CONTRIBUTING and SUPPORT files. #15
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this suposed to be for the whole DISTQ-BIO community, or for only this repo?
CONTRIBUTING.md
Outdated
@@ -0,0 +1,9 @@ | |||
How to contribute to disq-bio |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be DISQ?
CONTRIBUTING.md
Outdated
How to contribute to disq-bio | ||
============================= | ||
|
||
Thank you in advance for contributing to disq-bio! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same
SUPPORT.md
Outdated
@@ -0,0 +1,20 @@ | |||
How to get support for disq-bio |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same
SUPPORT.md
Outdated
provide context for your issue. The [How to submit a contribution](https://opensource.guide/how-to-contribute/) | ||
Open Source Guide is very helpful in this regard. | ||
|
||
Thank you for contributing to disq-bio! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same
+1 |
CONTRIBUTING.md
Outdated
|
||
Thank you in advance for contributing to disq-bio! | ||
|
||
[todo] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realized that you added to every PR the [DISQ-{{issue_number}}]
and that should be documented somewhere, in addition to add the Fixes/Closes #{{issue_number}}
for cross-reference. On the other hand, what's about PRs without associated issue?
Maybe a good starting point to add something to this file?
d56dc7d
to
4d4ee84
Compare
Ping for review and merge. I realize these are a bit weak on content, but I'd rather get them in place now and add to them as things settle out. |
### Search the Github issue tracker and pull requests | ||
|
||
Before creating a new issue or pull request, please search the [Disq issue tracker](https://github.com/disq-bio/disq/issues) | ||
and [Disq open pull requests](https://github.com/disq-bio/disq/pulls) on Github. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe instead of repeat here the same as in SUPPORT.md
, it might be better to say where to find the support information (the other file) and link here with markdown.
@@ -0,0 +1,12 @@ | |||
How to contribute to Disq |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I mentioned in #13, I wouldadd a section about how to write distq in the project files (package names, java classes, markdown documentation, javadoc, etc.). That is a good point to start to set proper developmental guidelines...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I would add a PR-guidelines to setup naming conventions ([DISQ-#] Description
, as I can see in the current ones) and mentioning which issue is resolving. Also, it looks like each PR should point to an issue, and thus this should also be mentioned in the contributing guidelines...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created issue #39
and [Disq open pull requests](https://github.com/disq-bio/disq/pulls) on Github. | ||
|
||
|
||
### Create a new issue on Github |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe out of the scope of this PR, but it might be usefull to add a PR/issue template for github (and link it here too).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, created issue #38
I think that it is better to add some of the content that looks already assumed, as it is easier to track in a live document like the CONTRIBUTING.md file... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 to merging as-is and improving with follow-on PRs.
Created new issues to track suggestions made by @magicDGS, thanks! |
👍 |
Yes, this can be merged |
Thank you too! |
Thank you, @tomwhite |
Fixes #6.