This page is for collaborating to update the project goals and principles.
As a start, below are the goals and principles from the 2006 strategy paper.
h3.2006 Goals
# Create a competitive, inviting interactive installation experience
# Upgrade Solaris' automated installation capabilities to be the best in the industry
h3.2006 Principles
# The user's goal at installation is to place Solaris on the system as quickly as possible, so:
a) Only those tasks directly relevant to that goal for a significant percentage of users are included in the standard installation experience.
b) Task performance must be measured and optimized appropriately.
# Any configuration tasks the user performs during installation must also be available after the system is installed.
# Installation policies will favor and encourage Solaris best practices for installing and managing systems.
# Installation will leverage the best general-purpose technologies Solaris has available, we will avoid creating installation-specific mechanisms whenever possible.
Please add statements of suggested goals or principles to the list below. The more specific they are, the better at this point. We'll discuss these at a meeting in the near future to refine and classify them.
h3.2009 Goals and Principles
* Server components developed by the project should be portable across popular operating system platforms.
* Automated deployment technologies should scale from a small, homogeneous single-network environment to a large, heterogeneous wide-area network environment.
* Automated installation should provide compelling feature set and user experience
As a start, below are the goals and principles from the 2006 strategy paper.
h3.2006 Goals
# Create a competitive, inviting interactive installation experience
# Upgrade Solaris' automated installation capabilities to be the best in the industry
h3.2006 Principles
# The user's goal at installation is to place Solaris on the system as quickly as possible, so:
a) Only those tasks directly relevant to that goal for a significant percentage of users are included in the standard installation experience.
b) Task performance must be measured and optimized appropriately.
# Any configuration tasks the user performs during installation must also be available after the system is installed.
# Installation policies will favor and encourage Solaris best practices for installing and managing systems.
# Installation will leverage the best general-purpose technologies Solaris has available, we will avoid creating installation-specific mechanisms whenever possible.
Please add statements of suggested goals or principles to the list below. The more specific they are, the better at this point. We'll discuss these at a meeting in the near future to refine and classify them.
h3.2009 Goals and Principles
* Server components developed by the project should be portable across popular operating system platforms.
* Automated deployment technologies should scale from a small, homogeneous single-network environment to a large, heterogeneous wide-area network environment.
* Automated installation should provide compelling feature set and user experience