PSARC contract for 2008/482: NWAM Phase 0.5 (picea)

[Leontine Binchy]

I aprrove

James Carlson wrote:
> In order to share a private library between ON and the GUI for NWAM,
> we need to have an ARC contract specifying how it'll be used.  I've
> drafted one below based on the information in the PSARC case and
> information from bugster.
>
> It should be fairly straightforward.  Please look it over and either:
>
>   - Reply to the message with a simple "I agree" message.  Note that
>     I've set "Reply-to" on this message to psarc-ext at sac.sfbay.
>
>   - Reply directly to me with questions or comments or concerns about
>     the contract, and I'll update it if necessary.
>
>
>
> @(#)contract	1.8 @(#) /shared/sac/arc/ARC-Templates/contract [1.8 06/12/06]
>
> 	CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES
>
> 0.  Number: PSARC/2008/482-01
>
> 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 Networking
>     Bugster Product/Category/SubCategory: solaris/network/config
>     Responsible Manager:		Victor Nelson
>
> 3.  The CONSUMER is identified by the following:
>     Product or Bundle:			JDS
>     Consolidation:			GNOME
>     Department or Group:		Desktop Development
>     Bugster Product/Category/SubCategory: jds/gnome/applets
>     Responsible Manager:		Leo Binchy
>
> 4.  The INTERFACES are:
>
> 	<libnwam.h>		Project Private
> 	/lib/libnwam.so.1	Project Private
>
> 5.  The ARC controlling these INTERFACES is: PSARC
>
> 6.  The CASE describing (Exporting) these INTERFACES is: 2008/482
>
> 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:
>
> _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.
>
> _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.
> 	If SUPPLIER cannot make both versions of INTERFACES available,
> 	and SUPPLIER and CONSUMER cannot devise a method whereby
> 	CONSUMER can detect which version of INTERFACES is being
> 	supplied, and the old version of CONSUMER will not run with the
> 	new version of SUPPLIER, then either the EOL process must be
> 	followed by SUPPLIER, or else a major release of SUPPLIER will
> 	be required, or the change will not be allowed.
>
> 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 obtain approval for changes from CONSUMER.  CONSUMER
>     will use bugster or informal communication to request changes from
>     SUPPLIER.  Technical coordination will be accomplished using this
>     mailing list:
>
> 	nwam-discuss at opensolaris.org
>
> 11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
>     follows:
>
>     CONSUMER will file bugs using bugster or request changes
>     informally, as needed.
>
> 12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
>     follows:
>
>     Design document (archived with case materials and delivered
>     privately to GUI team) is the only documentation.
>
> 13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
>     tested as follows:
>
>     SUPPLIER will test interfaces using stand-alone application to
>     exercise components.  CONSUMER and SUPPLER will both test
>     combination of GUI and library on a variety of systems.
>
> 14. SUPPLIER and CONSUMER agree that this contract can be terminated as
>     follows:
>
>     Contract will expire when NWAM Phase 1 (PSARC 2008/532) has been
>     delivered, or by mutual agreement at any earlier date.
>
> 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:			Date:
> For CONSUMER:			Date:
> For ARC:			Date:
>
>     A copy of this contract shall be deposited in the CASE directory as
>     "contract-<digits>" or in a "contracts" subdirectory.
>
> 16. (Not to be filled in until superseded or invalidated.)
>     This contract was superseded or invalidated by CASE:
>     For ARC:			Date:
>
>