A number of folks have said that they've found videos and presentations that other engineers have done to be really helpful in terms of understanding how parts of the chrome codebase work. I'd love to see more explanatory talks and presentations to share knowledge in the compositor and gpu stack.
To that end, have there been parts of the compositor[*] that you went to work with and wish there had been a better explanation of? Is there an area you haven't touched and are curious how it works? Especially for external or new contributors, I'd love to know where our sharp corners are and which parts are particularly confusing.
Once we see what folks are particularly keen on hearing more about, then we can find folks interested in giving those talks. (If you are keen on talking about anything you're working on, please don't wait on me or this spreadsheet! Feel highly encouraged to just schedule something and give a talk whenever!)
[*] compositor and gpu defined super broadly here to be like anything through the current blink compositing and paint code, cc/ directory, display compositor, compositor scheduling, video integration, ui/cc glue, android/cc glue, animation, scrolling, compositor input, command buffer, gpu process, canvas integration, color, webgl, vulkan, &c &c &c
You received this message because you are subscribed to the Google Groups "paint-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
.
.