Pulp

+1 to doing this soon.

Either in this task, or another, we need docs about the rest of the pulp 3 code layout. Yesterday some of us were trying to understand the intent and expectation behind pulp.tasking, and it would have been very helpful to have that documented.

I added a blocking relationship on #2454, since the file plugin is effectively the proof of these docs. It's likely that any changes made in the review of that issue will affect what gets written into these docs, so I think we need #2454 to be MODIFIED or better before we can adequately review docs changes related to this issue.

#2454 is now MODIFIED, I'll be getting my docs PR up for review soon.

As mentioned in the PR, I ran into some issues with sphinx linking, particularly when sphinx is left to its own devices to create links, such as when generating a link to a given class's base class. I have some ideas about how to get sphinx playing along with the import strategy that we're using to organize things like models, serializers, and viewsets that are predicated on acceptance of my POSTed PR. I think it's possible to improve sphinx's crossref behavior a little bit to be smarter about the links it generates based on how our app is structure, and plan to capture those thoughts in a story if this goes MODIFIED in its current state.