survivejs/maintenance-book

Consider different viewpoints

bebraw opened this issue · 4 comments

bebraw commented

Two at least:

  • Legacy vs. modern - If you do only a modern build, you can forget about standalone dist bundles and UMD (a big win)
  • Maintainer vs. contributor vs. consumer views on different aspects.
sapegin commented

  1. The biggest question here is if you really can avoid that kind of stuff yet? If you can, we probably don't need a legacy version at all ;-)

  2. We cover some questions form the consumer point of view, like dependencies. Adding some chapters on how to be a good open source contributor would be awesome!

bebraw commented
  1. I was thinking of adding an explicit note (a tip?) mentioning about it if/when it's relevant.
  2. I think the point is to be more explicit about it. The book reads differently from different viewpoints and we can likely make it easier for the reader if we annotate the techniques somehow.
sapegin commented

  1. So far I'm not sure without any examples.

  2. Yeah, maybe we can describe different “paths” for different roles in the introduction. Like if you're a maintainer read these chapters?

bebraw commented
  1. seems more valuable. 1. is likely a warning here and there. Suggesting different paths to read is a good idea.