A new path for GraphQL Import - help us decide on the roadmap!

Hi everyone!

I'm @urigo the founder of [The Guild](http://the-guild.dev).

As recently [been announced](https://www.prisma.io/blog/the-guild-takes-over-oss-libraries-vvluy2i4uevs) on the Prisma blog, we are taking over the maintenance of this library going forward.
I've expressed it in the blog post in more details but I would like to start by thanking Prisma for conceiving, creating and maintaining this library so far and also for doing the selfless act of providing it with fresh life by handing over the maintenance to us.

We already have a certain plan in mind going forward, some of it we've specified in the blog post, but we want you, the users and community of the library to be part of influencing the roadmap going forward.

One thing to note about [The Guild](http://the-guild.dev) - We place all the open source packages we maintain under individual person's Github profile instead of under a GitHub org or a company.
That is part of our philosophy - it puts more accountability on the maintainer and it also lowers the barrier of creating successful competing forks.
So we will transfer that repository from under Prisma as part of the transition.

I'm looking forward to start the discussion here below.
Please share how and why you use the library today, what are your biggest pain points today and ideas and features you would like to see in the future.

I will add points into the description here as we go.

Let's make this happen!

The issue names no file, test, or entry point and asks for roadmap feedback rather than a defined change. Read the issue discussion and linked announcement first; there is no concrete completion condition until the maintainers turn a roadmap decision into a scoped task.

Written by the indexing model from the issue text.