3 karl 1.2 // Copyright (c) 2000, 2001, 2002 BMC Software; Hewlett-Packard Development
4 // Company, L.P.; IBM Corp.; The Open Group; Tivoli Systems.
5 // Copyright (c) 2003 BMC Software; Hewlett-Packard Development Company, L.P.;
6 // IBM Corp.; EMC Corporation, The Open Group.
7 // Copyright (c) 2004 BMC Software; Hewlett-Packard Development Company, L.P.;
8 // IBM Corp.; EMC Corporation; VERITAS Software Corporation; The Open Group.
9 // Copyright (c) 2005 Hewlett-Packard Development Company, L.P.; IBM Corp.;
10 // EMC Corporation; VERITAS Software Corporation; The Open Group.
11 // Copyright (c) 2006 Hewlett-Packard Development Company, L.P.; IBM Corp.;
12 // EMC Corporation; Symantec Corporation; The Open Group.
|
13 mday 1.1 //
14 // Permission is hereby granted, free of charge, to any person obtaining a copy
15 // of this software and associated documentation files (the "Software"), to
16 // deal in the Software without restriction, including without limitation the
17 // rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
18 // sell copies of the Software, and to permit persons to whom the Software is
19 // furnished to do so, subject to the following conditions:
20 //
21 // THE ABOVE COPYRIGHT NOTICE AND THIS PERMISSION NOTICE SHALL BE INCLUDED IN
22 // ALL COPIES OR SUBSTANTIAL PORTIONS OF THE SOFTWARE. THE SOFTWARE IS PROVIDED
23 // "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
24 // LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
25 // PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
26 // HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
27 // ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
28 // WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
29 //
30 //==============================================================================
|
47 mday 1.1 //
48 ////////////////////////////////////////////////////////////////////////////////
49
50 All copyright holders of a source file must submit it under this
51 license, and no other licenses may be asserted.
52
53 2) README
54
55 All submissions must include a README text file that documents the
56 purpose of the module and provides contact information for the
57 module's author.
58
59 3) INSTALL
60
61 All submissions must include an INSTALL file that documents the build,
62 install, and test procedures for the module.
63
64 4) TEST
65
66 All submissions should include a test subdirectory that contains
67 automated tests to verify the successful build of the source module.
68 mday 1.1
69 Directory Structure
70 ===================
71
72 Each submission to the Unsupported area of the CVS must be a
73 self-contained environment under its own root directory. For example,
74 a module Foo.cpp would have the following directory path in the CVS
75 repository:
76
77 $(PEGASUS_ROOT)/src/Unsupported/Foo/Foo.cpp
78
79 Alternatively, some modules will have a more structure environment:
80
81 $(PEGASUS_ROOT)/src/Unsupported/Foo/src/Foo.cpp
82 $(PEGASUS_ROOT)/src/Unsupported/Foo/test/Foo_test
83 $(PEGASUS_ROOT)/src/Unsupported/Foo/doc/Foo.html
84
85
86 Committing Modules to the Unsupported Area
87 ==========================================
88
89 mday 1.1 Although anyone may offer source code to the Unsupported area
90 (provided the above criteria are satisfied), only members of the
91 pegasus-cvs-writers group have authorization to commit source code to
92 the repository. Therefore, members of the general public need to
93 obtain steering commette sponsorship for any modules they want to
94 submit to the Unsupported area of the CVS.
95
|