On 10/23/15 11:09 PM, Eric Rescorla wrote: >> It may well be that having c-c code in m-c decreases friction overall, >> > since it saves time for the people that know they're allowed to break TB >> > but choose to help it anyway. However, the cost of redirected work for >> > contributors that _don't_ know they're allowed to break TB is real. That is >> > the tradeoff that needs to be weighed IMO. > > What Bobby said here seems very important. In the cost/benefit analysis, > the impact on Firefox needs to be weighted very heavily. In particular, > breaking TB should not cause failures either on try or on commit, and > changes to pieces of Gecko should not be held up on their impact on TB.
If we get this right on the tooling side, I don't think it will be a concern. For contributors that are regular Mozillians, I think it has been clearly communicated that making changes in Firefox and Toolkit does not require fixing Thunderbird/Seamonkey. New contributors will either have a mentor that knows and can communicate this fact, or will not see the changes when using a correctly configured dxr, which is likely linked in one of the contributor guides. Even if they do a grep and find code locally, they will be aware that Thunderbird and Firefox are separate products, and if they set out to fix a Firefox bug I don't think they'd immediately think they need to fix it in Thunderbird without asking questions. Personally I think they will either ignore Thunderbird outright, or ask someone if they need to take care of it. As per current policy, they will be told they do not have to. Philipp _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
