Skip to content
This repository was archived by the owner on Apr 1, 2025. It is now read-only.

Conversation

@patrickt
Copy link
Contributor

@patrickt patrickt commented Jun 7, 2019

We owe it to outside contributors to be clear about the process
involved in submitting a patch to Semantic, and the sad fact that we
won't be able to accept every proposed change.

Patrick Thomson added 3 commits June 7, 2019 11:07
We owe it to outside contributors to be clear about the process
involved in submitting a patch to Semantic, and the sad fact that we
won't be able to accept every proposed change.
@patrickt patrickt requested a review from dcreager June 7, 2019 17:43
@patrickt patrickt merged commit 072cedf into master Jun 7, 2019
Copy link
Contributor

@dcreager dcreager left a comment

Choose a reason for hiding this comment

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

Mostly good, just one thing to possibly change. Interested in your thoughts on it

- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).

Please be aware that contributions to Semantic may be sent through multiple cycles of code review—we are grateful for all community involvement, but because Semantic powers real systems, we must maintain a high standard of code quality. For reasons of compatibility with production Semantic uses within GitHub, we may also reject or require modifications to changes that would affect these systems. We may also reject patches that don't fit with our vision of the project; should this be the case, we encourage you to start your own fork, as a healthy fork ecosystem is a sign of a robust community with varying requirements.
Copy link
Contributor

Choose a reason for hiding this comment

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

“may be sent through” -> “may go through”

“production Semantic uses within” -> “production uses of Semantic within”

Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure about explicitly encouraging forks. How about just “when this happens, we will be clear about our rationale”?

@rewinfrey rewinfrey deleted the update-contributing branch June 7, 2019 21:34
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants