@@ -9,15 +9,10 @@ No matter how you want to get involved, we ask that you first learn what’s
99expected of anyone who participates in the project by reading the Contribution
1010Guidelines and our [ Code of Conduct] [ coc ] .
1111
12- ** Please Note:** GitHub is for bug reports and contributions primarily -
13- if you have a support question head over to [ GoDaddy's Open Source
14- Software Slack channel] [ slack ] . You can request an invite
15- [ here] [ invite ] .
16-
1712## Answering Questions
1813
1914One of the most important and immediate ways you can support this project is
20- to answer questions on [ Slack ] [ slack ] or [ Github] [ issues ] . Whether you’re
15+ to answer questions on [ Github] [ issues ] . Whether you’re
2116helping a newcomer understand a feature or troubleshooting an edge case with a
2217seasoned developer, your knowledge and experience with a programming language
2318can go a long way to help others.
@@ -61,7 +56,7 @@ From a practical perspective, contributions are as simple as:
6156If you are interested in making a large change and feel unsure about its overall
6257effect, start with opening an Issue in the project's [ Issue Tracker] [ issues ]
6358with a high-level proposal and discuss it with the core contributors through
64- Github comments or in [ Slack ] [ slack ] . After reaching a consensus with core
59+ Github comments. After reaching a consensus with core
6560contributors about the change, discuss the best way to go about implementing it.
6661
6762> Tip: Keep your master branch pointing at the original repository and make
@@ -93,9 +88,6 @@ patches:
9388willing to do the same for you.
9489- Split your change into multiple smaller changes. The smaller your change,
9590the higher the probability that somebody will take a quick look at it.
96- - Mention the change on [Slack][slack]. If it is urgent, provide reasons why it
97- is important to get this change landed. Remember that you are asking for valuable
98- time from other professional developers.
9991
10092**Note that anyone is welcome to review and give feedback on a change, but only
10193people with commit access to the repository can approve it.**
@@ -119,6 +111,4 @@ guide with respect to patterns, naming, documentation and testing.
119111
120112[issues]: LINK_TO_PROJECTS_ISSUES_ON_GITHUB
121113[coc]: ./CODE_OF_CONDUCT.md
122- [slack]: https://godaddy-oss.slack.com/
123114[fork]: https://help.github.com/en/articles/fork-a-repo
124- [invite]: https://godaddy-oss-slack.herokuapp.com
0 commit comments