Update README.md (#42)

Author: IvanGoncharov

mentorship/2021/gsoc/README.md

@@ -34,11 +34,55 @@ As you develop ideas, please add them using this template:
 
 Good luck! If you have questions, please reach out to [[email protected]](mailto:[email protected]). You can also find us and ask questions to the mentors in the [#gsoc](https://graphql.slack.com/archives/CUB2DBYTF) channel on the [GraphQL Slack](https://graphql.slack.com). ([get an invite](https://slack-invite.graphql.org))
 
---
+### Make queries/SDL outputed by `graphql-js` compatible with `prettier` (Hard)
 
-Please add your ideas here.
+**Make GraphQL.js's print/printSchema functions format their output in way that is prettier compatible**
 
----
+`graphql-js` provide [print](https://github.com/graphql/graphql-js/blob/main/src/language/printer.js)/[printSchema](https://github.com/graphql/graphql-js/blob/main/src/utilities/printSchema.js) functions that output strings in GraphQL language format.
+Currently they are implemented in very simple manner so their output sometimes contains very long string or some other artifacts that look unpleasant.
+[Prettier](https://prettier.io/) becames de facto standard for formatting source code and it has support for GraphQL for years.
+So instead of reinventing the wheel we can make our implementation compatible with prettier.
+Also since prettier already using our `parse` function, as part of this project, we can collaborate with Prettier team to figure out if it possible for them to also use our `print` function.
+
+**Expected outcomes**
+
+* `print`/`printSchema` functions output is compatible with prettier
+* A lot of new test cases and 100% coverage for `print`/`printSchema` functions
+* Complited research project on switching Prettier to use GraphQL.js's `print` function
+
+**Skills required/preferred**
+
+* Strong knowledge of JavaScript/TypeScript
+* Experience with GraphQL
+* Experience with writing AST related code (Babel plugings, ESLint rules, etc.)
+
+**Mentors**
+
+* [IvanGoncharov](https://github.com/IvanGoncharov)
+
+### Integrate `graphql-relay-js` into `graphql-js`(Medium)
+
+**Move source code from `graphql-relay-js` into `graphql-js` repo to ease maintanance burden**
+
+Relay style pagination became popular standard in GraphQL world and we provide useful utils to make it easier to implement as part of [graphql/graphql-relay-js](https://github.com/graphql/graphql-relay-js) however maintaining it as separate repo significantly increase maintainance burden.
+Since `graphql-relay` package has zero dependencies (beyound `graphql`) we can easily integrate it into `graphql` package as subfolder.
+Biggest challenge would be to bring migrated code to TS and bring it up to `graphql-js` standards (test coverage, docs, etc.).
+
+**Expected outcomes**
+
+* All opened issues and PRs on `graphql-relay-js` are triaged and either fixed/closed or transfered to `graphql-js` repository.
+* All source code from [graphql/graphql-relay-js](https://github.com/graphql/graphql-relay-js) moved into [graphql/graphql-js](https://github.com/graphql/graphql-js) and released as part of [graphql]() package on NPM.
+* Migrated code is up to `graphql-js` is converted to TS, passing all checks and validations.
+
+**Skills required/preferred**
+
+* Strong knowledge of JavaScript/TypeScript
+* Experience with GraphQL and implementing Relay connection specification in particular
+* Refactoring skills
+
+**Mentors**
+
+* [IvanGoncharov](https://github.com/IvanGoncharov)
 
 ## Resources