@(#)contract	1.8 @(#) /shared/sac/arc/ARC-Templates/contract [1.8 06/12/06]

	CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES

0.  Number: PSARC/2007/452 (extension to add the fassign() interface)

1.  This contract is between
	a SUPPLIER of INTERFACES and
	a CONSUMER of those INTERFACES,
    both of whom are entities within Sun Microsystems, Incorporated.

2.  The SUPPLIER (definer and/or implementor) is identified by the following:
    Product or Bundle: Solaris
    Consolidation: ON
    Department or Group: Solaris Core Technologies
    Bugster Product/Category/SubCategory: solaris/kernel/fs
    Responsible Manager: Don Traub

3.  The CONSUMER is identified by the following:
    Product or Bundle: Solaris Cluster
    Consolidation: Solaris Cluster
    Department or Group: Solaris Clustering RGM / APIs
    Bugster Product/Category/SubCategory: suncluster/suncluster/rgm
    Responsible Manager: Meenakshi Kaul-Basu

4.  The INTERFACES are:

    The following routine will be imported by Solaris Cluster modules
    from base Solaris kernel (this interface would be added in contract-1
    under PSARC/2007/452):

    INTERFACE	STABILITY

    fassign()	Project Private

5.  The ARC controlling these INTERFACES is:

    PSARC

6.  The CASE describing (Exporting) these INTERFACES is:

7.  The following SPECIAL ARRANGEMENTS are made which modify the rules
    imposed by the stability levels listed in section 4 above:
 
_N_ 7a. Although the stability level doesn't normally restrict it,
        SUPPLIER promises to only modify INTERFACES in an incompatible
	    way as follows:

		SUPPLIER agrees to only change the contracted interface
		in an incompatible manner in a new minor release.

_N_ 7b. Although the stability level doesn't normally allow it, CONSUMER will
        expose INTERFACES to a PARTNER, which is external to Sun, namely:
		Name of Company:
		Name of Department or Group within Company:
		Responsible Manager:

_Y_ 7c. Although the stability level doesn't normally allow it, CONSUMER will
        import INTERFACES from a separate consolidation.

        SUPPLIER will notify CONSUMER of any changes to the interface.

_Y_ 7d. If SUPPLIER decides to change (including replace or remove) any
	portion of the INTERFACES, SUPPLIER will notify CONSUMER of the
	proposed new version, no later than the application for ARC
	approval of the new version.
	If SUPPLIER and CONSUMER are contained in the same consolidation,
	they have the option of arranging for simultaneous conversion
	to the new interfaces.  If this is not possible, or if they are
	not in the same consolidation, then SUPPLIER will either make best
	effort to work with CONSUMER so that CONSUMER can detect which
	version of INTERFACES is being supplied, or else SUPPLIER will
	make best effort to supply both old and new versions of
	INTERFACES.

8. If CONSUMER requires changes in INTERFACES, SUPPLIER will make
   best effort to accommodate such changes, which shall then be
   treated in accordance with paragraph 7 above.

9. Notwithstanding paragraphs 7 and 8, a change to any portion
   of the INTERFACES shall be regarded as a completely new set of
   INTERFACES which require both ARC approval and execution of
   a new contract.

10. SUPPLIER and CONSUMER agree that evolution of INTERFACES shall be
    handled as follows:

    SUPPLIER will notify CONSUMER of any proposed changes to the 
    interface.
    
11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
    follows:

    CONSUMER shall file bugster change requests against the 
    interfaces under solaris/kernel/fs. SUPPLIER agrees to
    respond to these change requests according to the usual
    sustaining process.

12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
    follows:

    The interfaces are listed in the final case materials for 
    PSARC/2007/452. The documentation is consolidation-private
    and/or header files and/or implementation.

13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
    tested as follows:

    SUPPLIER agrees to test any changes to the interface as part of
    existing or updated test suites. CONSUMER agrees to test their
    use of these interface at the usual release intervals and when
    any changes are made to the implementation of the contracted 
    interface.

14. SUPPLIER and CONSUMER agree that this contract can be terminated as
    follows:

    Contract will be terminated by mutual agreement between the
    SUPPLIER and CONSUMER.

15. This contract is not valid until "signed" via agreement from the
    SUPPLIER and CONSUMER, and approved by the ARC CASE referenced by
    this contract.  E-mail agreement to the contract should be archived
    in the mail archive of CASE; verbal agreement to the contract
    should be noted in the meeting minutes.  This contract remains
    valid until superseded or invalidated.

For SUPPLIER: Don Traub				Date: 08/06/2007
For CONSUMER: Meenakshi Kaul-Basu	Date: 08/06/2007
For ARC: Charles Debaldareen		Date: 08/13/2007

    A copy of this contract shall be deposited in the CASE directory as
    "contract-1.txt".

16. (Not to be filled in until superseded or invalidated.)
    This contract was superseded or invalidated by CASE:
    For ARC:			Date: