Wednesday June 01, 2005
Change And it ought to be remembered that there is nothing more difficult to take in hand, more perilous to conduct, or more uncertain in its success, than to take the lead in the introduction of a new order of things. Because the innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may do well under the new. This coolness arises partly from fear of the opponents, who have the laws on their side, and partly from the incredulity of men, who do not readily believe in new things until they have had a long experience of them.
Thus, it happens that wheneever those who are hostile have the opportunity to attack they do it like partisans, whilst the others defend lukewarmly...
The Prince, Chapter 6 by Niccolo Machiavelli
Sun's involvement in community development projects such as OpenSolaris, Gnome and Mozilla is all about change - both process changes and code changes.
In the spirit of trying to avoid the above fate, I will be using this space to present and discuss some of the processes that Sun uses to identify and manage such change.
Technorati Tag: OpenSolarisTechnorati Tag: Solaris
( Jun 01 2005, 01:20:00 PM PDT ) Permalink Comments [2]
This is a personal weblog, I do not speak for my employer.
My experience with change managemet systems like those are on par with Remedy, and (more) frequently custom tools, email, or groupware. But, I still don't know what (or exactly how) Sun does it ... Is it as simple as sending a free formed email to the ARC? Are there standards or templates? How do these changes get communicated to *all* components dependent on an interface? What if you don't know if a component is dependent?
Posted by Joseph Tingiris on July 27, 2005 at 10:43 AM PDT #
Posted by John Plocher on September 14, 2006 at 03:13 PM PDT #