# Build Instructions and Communication **URL:** \ **Category:** Google Summer of Code\ **Created:** [February 14, 2018, 10:02am UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761 "2018-02-14T10:02:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mr1holmes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mr1holmes/32/27720_2.png) [@mr1holmes](https://discuss.elastic.co/u/mr1holmes)\ **Post date:** [February 14, 2018, 10:02am UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/1 "2018-02-14T10:02:10Z")
I'm interested to work on [Speed up Highlighting](https://github.com/elastic/gsoc#elasticsearch_highlighting_order) idea for GSoC 2018. Where can I find the build instructions? And is the #elasticsearch channel on freenode is correct medium to discuss this project or is there a mailing list or slack? ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [February 15, 2018, 3:53am UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/2 "2018-02-15T03:53:34Z")
Hey, You mean build instructions for Elasticsearch? The best starting point should be [https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase](https://github.com/elastic/elasticsearch/blob/master/CONTRIBUTING.md#contributing-to-the-elasticsearch-codebase) For general Elasticsearch questions the #elasticsearch IRC channel on Freenode is great. If you have a specific question about Elasticsearch then [https://discuss.elastic.co/c/elasticsearch](https://discuss.elastic.co/c/elasticsearch) is the best place (it's kind of our mailing list by now). And please keep any GSoC specific questions in [https://discuss.elastic.co/c/elastic-community/elastic-gsoc](https://discuss.elastic.co/c/elastic-community/elastic-gsoc). Hope that helps 🙂 ---
**Author:** ![refactormyself](https://avatars.discourse-cdn.com/v4/letter/r/2acd7d/32.png) [@refactormyself](https://discuss.elastic.co/u/refactormyself)\ **Post date:** [March 17, 2018, 8:42pm UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/3 "2018-03-17T20:42:16Z")
Hello. I made a PR and it failed because I did not sign the license. I have later done that. But I don't know what to do. It is still marked failed ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [March 17, 2018, 9:01pm UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/4 "2018-03-17T21:01:04Z")
Do you have a link to the PR? This is something we should get fixed, but it doesn't make a real difference for the GSoC application — we can still judge your abstract and PR, so don't worry too much about it. ---
**Author:** ![refactormyself](https://avatars.discourse-cdn.com/v4/letter/r/2acd7d/32.png) [@refactormyself](https://discuss.elastic.co/u/refactormyself)\ **Post date:** [March 17, 2018, 9:03pm UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/5 "2018-03-17T21:03:07Z")
> ---
**Author:** ![xeraa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xeraa/32/48181_2.png) [@xeraa](https://discuss.elastic.co/u/xeraa)\ **Post date:** [March 17, 2018, 9:46pm UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/6 "2018-03-17T21:46:17Z")
Generally PRs should always be against master and we'll backport the relevant branches; with the obvious exception that something only needs fixing in a specific branch, but that's not the case for this doc fix. IMO the easiest approach would be to close this PR and open a new one against master. Then the CLA check should also pass (if you are using the same email address for the commit). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 4, 2022, 5:13am UTC](https://discuss.elastic.co/t/build-instructions-and-communication/119761/7 "2022-11-04T05:13:52Z")