Introduce contributor facing documentation for django.db.migrations

[Markus Holtermann]

It would be helpful for new contributors as well as for other core devs not involved in certain parts of Django, to have documentation that outlines how these components work. Tim proposed to add that documentation to docs/internals/. I'd put it into docs/internals/api/

E.g. in migrations: you have a ModelState and to detect changes the autodetector takes all migrations and build the final model representation and then compares this ProjectState to the ProjectState constructed from all currently available models.

[Tim Graham]

I think the idea is accepted, but a ticket is needed for each thing you want to document, not all of them in one ticket. Do you want to retitle this one to cover migrations?

[Akshesh Doshi]

Commenting to subscribe to this ticket.

(Cannot add to cc as being detected as spam)

[HAMA Barhamou]

I think that this tiket should cover a broader need. ​https://forum.djangoproject.com/t/internal-organization-of-the-django-project/18490

[Natalia Bidart]

Replying to HAMA Barhamou:

I think that this tiket should cover a broader need. ​https://forum.djangoproject.com/t/internal-organization-of-the-django-project/18490

Hey HAMA Barhamou, thank you for your interest in making Django better, but please note that as mentioned in the first comment from Tim, this ticket is intentionally scoped to only documenting the database migrations machinery.