Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations

[Django]

#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  Markus Holtermann  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Natalia Bidart):

 Replying to [comment:5 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.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cd4bb14c8-57657106-cad0-4488-ad69-cf453a596b30-00%40eu-central-1.amazonses.com.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations

[Django]

#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  Markus Holtermann  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by HAMA Barhamou):

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

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cd40fc7e8-06f30e85-8436-4fd3-bfe3-a8d91e7b9ccc-00%40eu-central-1.amazonses.com.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations

[Django]

#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  Markus Holtermann  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Mariusz Felisiak):

 * owner:  Markus Holtermann => (none)
 * status:  assigned => new


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.1275680be59bdf93ade0324d30e13335%40djangoproject.com.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations

[Django]

#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  MarkusH|Owner:  MarkusH
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by akki):

 Commenting to subscribe to this ticket.

 (Cannot add to cc as being detected as spam)

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.60f1aac80313f8e649a5550f3be49d3a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24989: Introduce contributor facing documentation for django.db.migrations (was: Introduce low-level documentation on Django's components)

[Django]

#24989: Introduce contributor facing documentation for django.db.migrations
---+
 Reporter:  MarkusH|Owner:  MarkusH
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by MarkusH):

 * owner:  nobody => MarkusH
 * status:  new => assigned
 * stage:  Unreviewed => Accepted


Old description:

> I first had the idea a Django: Under the Hood 2014, but abandoned it. A
> couple of days ago the idea came up in IRC again:
>
> 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.
>
> I.e. 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 proposed to add that documentation to `docs/internals/`. I'd put it
> into `docs/internals/api/`

New description:

 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.

--

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.5a9d34c7dcab72ce93328166d2dd8504%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.