www/index.html


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96

<html>
<head>
</head>
<body>

<p>This is the initial web content for your project.  Please customize
this to fit your project.  You dont need to anwser all these questions
or follow this exact format, but we do like to see this kind of
information before we approve projects for public viewing.
</p>

<p>Until your project is approved, only you can view it and work on
it.
</p>

<ul>
<li>This index.html will be used if and only if you have the "Use
Project Home Page" option checked on the "Adminster Project" page
(click the "Admin" tab).</li>

<li>To edit this file, check out your project via CVS and edit www/index.html.

<li>You can 'cvs add' and commit other files under the project's "www"
directory and they will published to your project web site.</li>

<li>Also, consider starting a thread in the "dev" mailing list to get
thes discussion started.  A good one is an "introduction" thread where
people post messages about themselves and their interest in the
project.</li>

<li>You can add a "Highlights:" line to the top of all web pages by adding a file www/project_highlights.html </li>
</ul>


<h3>Mission</h3>

<p>What is the goal of this project?
</p>

<p>What is the scope of this project?
</p>

<p>For example:</p>

<ul>
<li>Develop just enough functionality to scratch a particular itch</li>
<li>Build a tool just like XYZ, but less broken</li>
<li>Build the best XYZ-tool ever!</li>
</ul>


<p>What are high-level features you are sure to build?
</p>
<ul>

<li>What would you write on a billboard about your project? Users
might only look for a few seconds.</li>

<li>Use the issue tracker to track features and enhancement
requests. It is not just for bugs, pre-populate it with feature
descriptions so that potential contributors know what you would like them
to work on.</li>
</ul>

<p>What are the high-level assumptions or ground rules for the project?
</p>

<p>For example:
</p>

<ul>
<li> we will use programming language X on operating system Y for now.

<li>We will, or will not, consider certain functional areas like
internationalization, high security, concurrency, etc.  The list of
functional areas will depend on what you are trying to do.

<li>Try to keep this part short.
</ul>


<h3>Related resources</h3>

<ul>
<li>Link to other stuff that you know about.  It will help you
research requirements and provide a useful resource to potential
contributors.</li>

<li>Why reinvent the wheel? What is better about this wheel?  Is there
any existing project that you can partner with or reuse?</li>

<li>Where would you go to try to find potential contibutors?</li>
</ul>

</body>
</html>