What is the motivation between coupling DRF and Graphene Django?

Hi folks, hope you're all well!

I had a look at the PR that initially implemented the support for DRF [here](https://github.com/graphql-python/graphene-django/pull/186) but it doesn't have much context about the **motivation** behind of it.

I found a [comment](https://github.com/graphql-python/graphene-django/issues/594#issuecomment-474903689) from a maintainer indicating that he uses the DRF integration when he already has a serializer, otherwise he uses Django forms.

However, I'd like to understand more behind the motivation and intended usage/audience, and if this support was meant to only allow people developing in DRF to migrate more swiftly or if it is intended even for someone starting a project from scratch so that they gain from DRF abstractions.

Ultimately DRF is a nice library and I can see why re-using serializers could be beneficial during a migration from Rest to GraphQL, however I can't wrap my head around whether adding a DRF dependency in a greenfield project would be the go-for or if it would be unnecessary and/or troublesome.

Thanks for reading my mumbling speech, hope to get some feedback on that!