Skip to content

Adding contributing.md first draft #48

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

Merged
merged 4 commits into from
Jul 11, 2016
Merged

Adding contributing.md first draft #48

merged 4 commits into from
Jul 11, 2016

Conversation

graysonarts
Copy link
Contributor

Fixes #41
First draft of the contributing.md. Please feel free to comment on wording, improvements, etc.

@benlower
Copy link
Contributor

benlower commented Jul 7, 2016

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."

@lbrendanl
Copy link

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.

@t8y8
Copy link
Contributor

t8y8 commented Jul 8, 2016

Looks good to me

@graysonarts
Copy link
Contributor Author

@benlower I just saw your second comment about starting a conversation. I'll add something and send a new update real quick.

@benlower
Copy link
Contributor

benlower commented Jul 8, 2016

nice

@@ -27,3 +27,7 @@ the limitations that you are running into, and provide us with a use case to kno

For all other things, please submit a PR that includes the fix, documentation, or new code that you are trying to contribute. More information on
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to collectively

@graysonarts
Copy link
Contributor Author

yeah, I english good. Thanks @t8y8, fixed

@graysonarts
Copy link
Contributor Author

Anymore feedback on this one? Or is it good to merge?

@jdomingu
Copy link
Contributor

Ship it!

@benlower
Copy link
Contributor

LGTM

@graysonarts graysonarts merged commit d9f90f3 into tableau:development Jul 11, 2016
@graysonarts graysonarts deleted the contributing-file branch July 11, 2016 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy