I have to agree with my namesake here. This is too complicated to design in a ML, without having some sort of reference point. It also makes is unrealistic to add new participants without the cliche "go read every post about this subject first". If nothing else we should have a wiki that contains at a high level:
a) general goals and requirements b) open items c) proposed design d) threat model These are living documents that should be evolving along with this discussion. Thanks! Lucas. On 3/11/2012 4:48 PM, Jonas Sicking wrote: > On Sat, Mar 10, 2012 at 1:41 PM, lkcl luke <luke.leigh...@gmail.com> wrote: >> this is all really good stuff, jim. but i have to reiterate: WHERE >> IS IT BEING FORMALLY DOCUMENTED? please don't say "in the mailing >> list". > Once we've had a bit more of a discussion here on the list, I think we > should document everything both as part of the OWA documentation, as > well as part of the general B2G documentation. But at this point I'm > not sure that there is enough consensus to start editing wikis. > > / Jonas > _______________________________________________ > dev-security mailing list > dev-security@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-security _______________________________________________ dev-security mailing list dev-security@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security
