I don't see anything wrong with publishing design docs on webkit-dev. Just don't proselytize :)
:DG< On Mon, Jun 29, 2009 at 11:40 AM, Jeremy Orlow<jor...@chromium.org> wrote: > On Mon, Jun 29, 2009 at 11:07 AM, David Levin <le...@chromium.org> wrote: >> >> It seems like if you are doing a significant change to an existing area or >> adding a feature, it is good to explain the change that you're planning to >> do (and hopefully get input from whoever had been working on that area >> recently the most). This explanation doesn't have to be >> a "design doc" though. >> For example from bug https://bugs.webkit.org/show_bug.cgi?id=25463, >> >> "The comments in the bug seem to show a lack of consensus as to whether we >> want >> this feature and whether the API is appropriate. These design issues >> should be >> hashed out (perhaps on the mailing list) before submitting a patch for >> code review." > > True. > > I guess WebKit guys have historically been pretty sensitive to us pushing > our ways upon them. Maybe we can continue circulating design docs for work > in WebKit on this mailing list, but keep them on the down low on the WebKit > mailing list? Maybe post links in bugs, but only bring them up on the > mailing list when there's specific issues to discuss? > > J > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
