[b]Packaging, Patching, and Distribution Mgmt Community Forum Proposal[/b]
Creation and management of an OpenSolaris community forum focused on the what, 
how, and why of Solaris component software packaging, updating (patching), and 
product distribution initially providing the Sun-specified mechanisms, but then 
leveraging the community for new and improved mechanisms and processes.

[b]Audience[/b]
Typically, such work falls under the functional role of [i]release 
engineering[/i] which can cover the gambit of source code and binary 
configuration management, including building binaries from source, packaging 
the binaries into installable distribution units, assembling the component 
units into collective distributions, providing software life cycle management 
processes and tools, and overall product life cycle management.
This forum would be dedicated to helping individuals responsible for such 
functions.

[b]Goal[/b]
The intent of this forum is to provide the community the information needed to 
create an installable distribution image per the CDDL:

  [i]  3.5. Distribution of Executable Versions.
    You may distribute the Executable form of the Covered Software under the 
terms of this License or under the terms of a license of Your choice, which may 
contain terms different from this License, provided that You are in compliance 
with the terms of this License and that the license for the Executable form 
does not attempt to limit or alter the recipient's rights in the Source Code 
form from the rights set forth in this License. If You distribute the Covered 
Software in Executable form under a different license, You must make it 
absolutely clear that any terms which differ from this License are offered by 
You alone, not by the Initial Developer or Contributor. You hereby agree to 
indemnify the Initial Developer and every Contributor for any liability 
incurred by the Initial Developer or such Contributor as a result of any such 
terms You offer.

    3.6. Larger Works.
    You may create a Larger Work by combining Covered Software with other code 
not governed by the terms of this License and distribute the Larger Work as a 
single product. In such a case, You must make sure the requirements of this 
License are fulfilled for the Covered Software.[/i]
       [u] http://opensolaris.org/os/licensing/opensolaris_license/[/u]

[b]Scope[/b]
The set of material shall initially include all the specifications and process 
documentation necessary to assemble a bootable Solaris 
CD-ROM/DVD-ROM/netinstall image. This is all documented in the Solaris Source 
product documentation, but to even get to that point contributors have to know 
the rules for creating Solaris-compatible packages, what they need to build an 
installable image, etc.  All this information exists in Solaris Hardware 
Partners (SHWP) Program and Solaris Source Product docs, but it may need to be 
queued with everything else as to when it is supportable and ready for 
consumption for the community.
The forum community and Sun resources shall need to determine the extent to 
which processes and tools used in the production of Sun's Solaris releases will 
be provided to the community in either the form of source code and 
documentation or as Sun-provided services.

[b]Initial Community Leaders[/b]
Dave Miner, dminer
Rob Anderson, rander

[b]References[/b]
[]  OpenSolaris distributions and package managment
https://www.opensolaris.org/jive/thread.jspa?messageID=6758
[] The binary versions of the Solaris packaging tools are found @
[u]http://www.opensolaris.org/os/community/tools/pkgtools/[/u]
[]  Build a Solaris 10 distribution CD
https://www.opensolaris.org/jive/thread.jspa?messageID=12877
[]  Creating bootable DVD
https://www.opensolaris.org/jive/thread.jspa?messageID=17441
[] Community Proposals
   [i]New communities are created by sending a proposal describing the scope, 
goals, and initial core developers to the opensolaris-discuss mailing list. The 
proposal will be openly discussed and modified as necessary. Finally, the CAB 
will vote to either approve or deny creation of the community.

   Once a community is created on paper, the community has to create itself in 
reality. The first responsibility of a community is to clarify its own purpose 
and list of projects it intends to be working upon in the form of a mission 
statement and set of project records.[/i]
[u]http://www.opensolaris.org/os/community/cab/governance_proposal/#Communities[/u]
This message posted from opensolaris.org
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to