On Mon, Aug 27, 2007 at 04:26:45PM -0700, Darren.Reed at Sun.COM wrote: > Will the changes to ntpd be offered back to www.ntp.org?
Consensus on what to do may only just be emerging. I'd imagine that we would contribute back any code changes, but shouldn't we first figure out just what we'll do? Heck, we could do something fairly different that does not involve modifying any NTP code. For example: Create a service that talks to the local NTP server to poll it for its time and estimated error/offset to UTC (IIRC that's available in NTP replies). Make this service be the one that others query for time status. Also, contributing changes back isn't necessarily what we should do in every case (the GPL, for example, doesn't require it -- it requires that modified source be made available). Just how to contribute the code back, whether very actively actively (cook up a patch, submit the target's bug tracking service) or more passively (send an e-mail pointing to OpenSolaris code), is something that might depend on the dynamics of the relevant open source communities and their relationship with the OpenSolaris community. I don't mean to get into a thread about proper open source code change contribution etiquette. Rather, I think it's too soon to be asking that question when the relevant changes that aren't even agreed to and might not materialize. Any discussion how we should approach open source code contributions from OpenSolaris to other communities should probably not take place on this list. Nico --
