Hi all, I'm suggesting this topic for a while now, maybe if we finally get to talk about it in person something will improve :) The mm documentation is, well, not entirely up to date. We can opt for dropping the outdated parts, which would generate a nice negative diffstat, but identifying the outdated documentation requires nearly as much effort as updating it, so I think that making and keeping the docs up to date would be a better option. I'd like to discuss what can be done process-wise to improve the situation. Some points I had in mind: * Pay more attention to docs during review * Set an expectation level for docs accompanying a changeset * Spend some cycles to review and update the existing docs * Spend some more cycles to add new documentation * Participate in programs like Google Season of Docs I'd appreciate a discussion about how we can improve the existing memory management documentation so that a reader can get a coherent view of it, what are the gaps (although they are too many), and what would be the best way to close these gaps. -- Sincerely yours, Mike.
