Hi David, > I find it frustrating, from a CSR Group member perspective, that people > too often need someone else to tell them a CSR is, or is not, needed > rather than being able to evaluate that for themselves. Thinking about > the need for a CSR request should be on everyone's "checklist" before > proposing any new feature or significant change. And yes it should also > be part of the reviewer's review criteria. > > That said the only guaranteed additional exposure a CSR provides is to > the CSR Group lead - Joe - who will do the actual approval. Even CSR > Group members don't get notified of new CSRs - they are just JBS issues > and you have to watch the right component/subcomponent to get > notifications. So there is no guarantee that a CSR would have provoked > any detailed discussion at the time - unless Joe flagged it for some reason.
Thanks for the information. Speaking for myself, I guess I now have a better understanding of the CSR process than back in last December and would probably go for a CSR for such a change automatically. /Christoph
