On Wed, Mar 14, 2012 at 8:20 PM, Lucas Adamski <[email protected]> wrote: > I don't think the feature page should be the place for discussion, but it > should track the discussion. As issues are > raised, discussed & resolved, those would be mirrored in the feature page. > Otherwise, important issues will be lost, > and new participants will cannot synthesize a design from a huge fragmented > thread.
yes. i have already been criticised for "repeating myself", which is a clear sign that people are in fact overloaded and simply haven't got time to read 10,000 (and increasing) words before contributing. the wiki page should be subdivided into sections, and should represent and reflect the "latest up-to-speed decisions and ideas". it is even absolute madness to even expect the actual people who have been following this right from the beginning to be able to hold everything in their heads. if this could be subdivided into separate areas, and the tasks allocated to different working groups, it would be fine. you could even split it by mailing list. .... but you can't do that here, because this is _security_. there needs to be a clear understanding of the *entire* process (see previous message with over 12 sub-headings) and how each part contributes to the overall security. remember: this could turn out to be as big as android and the iphone. hundreds of millions of installations. you get that wrong, the consequences don't bear thinking about. it's not like PCs and web browsers. this is _phones_. the market is potentially 10x to 100x bigger. worst case is: they'll all come knocking on the mozilla foundation's door, some of them potentially with class action lawsuits. worse than that is the situation where you suddenly get 10 to 100x the number of bugreports on bugzilla. l. _______________________________________________ dev-security mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security
