On Mon, Aug 27, 2007 at 05:10:09PM -0700, Darren.Reed at sun.com wrote: > The NTP daemon is a 3rd party application. Local changes > increase the difficulty of bringing in updates from the origin > (www.ntp.org) if they aren't fed back.
As Nico said, this isn't the right place to have this conversation. There are ongoing discussions on the OGB list about high-level policies for consolidation management; suggestions for minimising the maintenance burden while still meeting our obligations are best communicated there. In any event, worries about where a set of changes is sent are entirely orthogonal to what those changes will be; whether or how our changes propagate beyond the codebase for which we are responsible do not affect the technical correctness of a design decision. If a correctly-designed and properly-implemented change increases our maintenance burden because "ntp.org" won't integrate it, that tells us only that our historical strategy for maintaining NTP in our source base is the wrong one. It does not affect the correctness of that change, the development of which is the actual topic here. -- Keith M Wesolowski "Sir, we're surrounded!" FishWorks "Excellent; we can attack in any direction!"
