| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Let's get @lbrendanl and @jdomingu to weigh in too. I like this. Would be good to add something like "If you are considering adding a new feature, we suggest starting a conversation about it first to identify any potential design or scheduling issues before jumping in." |
Sorry, something went wrong.
|
Would it be worth just briefly mentioning that issues and feature requests are done through GH issues and all other fixes are done through PRs? I don't think it's uncommon for some to be unfamiliar with GitHub so it may be worth calling out. |
Sorry, something went wrong.
Based on feedback from @lbrendanl
|
Looks good to me |
Sorry, something went wrong.
|
@benlower I just saw your second comment about starting a conversation. I'll add something and send a new update real quick. |
Sorry, something went wrong.
based on feedback from @benlower
|
nice |
Sorry, something went wrong.
| creating a PR can be found in the [github documentation](https://help.github.com/articles/creating-a-pull-request/) | ||
|
|
||
| If the feature is complex or has multiple solutions that could be equally appropriate approaches, it would be helpful to file an issue to discuss the | ||
| design trade-offs of each solution before implementing, to allow us to collective arrive at the best solution, which most likely exists in the middle |
There was a problem hiding this comment.
to collectively
Sorry, something went wrong.
|
yeah, I english good. Thanks @t8y8, fixed |
Sorry, something went wrong.
|
Anymore feedback on this one? Or is it good to merge? |
Sorry, something went wrong.
|
Ship it! |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #41
First draft of the contributing.md. Please feel free to comment on wording, improvements, etc.