Commit | Line | Data |
---|---|---|
15637ed4 RG |
1 | |
2 | ||
3 | ||
4 | ||
5 | ||
6 | ||
7 | ||
8 | 386BSD RELEASE 0.1 | |
9 | SOFTWARE CONTRIBUTION FORM | |
10 | ||
11 | ||
12 | We are always pleased to look at enhancements, addi- | |
13 | tions or ports of public domain software for possible incor- | |
14 | poration into 386BSD releases. However, all contributed | |
15 | software must contain the following items: | |
16 | ||
17 | 1. The author's name, date, and copyright (if any). If a | |
18 | modification of a public-domain work, modification | |
19 | attribution and original author. | |
20 | ||
21 | 2. A brief description of the software module or item. | |
22 | ||
23 | 3. The following statement: "This software contains, to | |
24 | the best of my knowledge, no proprietary, trade secret, | |
25 | or otherwise encumbered code. I am making this | |
26 | software available for incorporation into 386BSD, | |
27 | understanding that 386BSD is a freely redistributable | |
28 | and modifiable system." | |
29 | ||
30 | In addition, the software should be in the following | |
31 | format: | |
32 | ||
33 | 1. Release number upon which generated (0.0, 0.1, etc). | |
34 | ||
35 | 2. Source code. Generated binary. | |
36 | ||
37 | 3. List of known bugs. | |
38 | ||
39 | 386BSD is a freely available work. All developers sub- | |
40 | mitting software for official 386BSD releases should be | |
41 | aware of this fact. Given the extremely wide distribution of | |
42 | this software, we cannot regulate or enforce specific usage, | |
43 | license, or proprietary restrictions, nor can we collect any | |
44 | monies or fees for use. Those developers who wish to | |
45 | encumber their software in this manner should find other | |
46 | mechanisms for distribution. | |
47 | ||
48 | We will not review or accept any code which is marked | |
49 | "proprietary" or "trade secret". | |
50 | ||
51 | We suggest that copyrights (or copylefts) not be made | |
52 | too "encumbering" in order to encourage usage, enhancements, | |
53 | and modifications of the submitted software. (For a sug- | |
54 | gested copyright format, we suggest the University of Cali- | |
55 | fornia copyright format.) | |
56 | ||
57 | Due to constraints on distribution size, research | |
58 | directions, and number of submissions, we cannot guarantee | |
59 | that any particular piece of software will be incorporated | |
60 | into the next release. However, we always encourage people | |
61 | ||
62 | ||
63 | 386BSD SOFTWARE.FORM 1 July 1992 | |
64 | ||
65 | ||
66 | ||
67 | ||
68 | ||
69 | ||
70 | ||
71 | ||
72 | ||
73 | ||
74 | to make their software available to other 386BSD Users via | |
75 | the network and user groups. That way, a large number of | |
76 | people can immediately benefit from your software and pro- | |
77 | vide critical feedback for enhancements and refinements. | |
78 | ||
79 | Please complete this software contribution form and | |
80 | return it along with your software contribution to: | |
81 | ||
82 | Lynne Greer Jolitz | |
83 | 386BSD User Registration | |
84 | 447 61ST Street | |
85 | Oakland, CA. 94609 USA | |
86 | ||
87 | +1-510-420-0174 FAX | |
88 | ljolitz@cardio.ucsf.edu | |
89 | CIS 76703,4266 | |
90 | ||
91 | ||
92 | ||
93 | ||
94 | ||
95 | ||
96 | ||
97 | ||
98 | ||
99 | ||
100 | ||
101 | ||
102 | ||
103 | ||
104 | ||
105 | ||
106 | ||
107 | ||
108 | ||
109 | ||
110 | ||
111 | ||
112 | ||
113 | ||
114 | ||
115 | ||
116 | ||
117 | ||
118 | ||
119 | ||
120 | ||
121 | ||
122 | ||
123 | ||
124 | ||
125 | ||
126 | ||
127 | ||
128 | 386BSD SOFTWARE.FORM 2 July 1992 | |
129 | ||
130 | ||
131 |