From 528ebad33f8ecbe8401ef779ce64648a7de0851a Mon Sep 17 00:00:00 2001 From: The HTTP Daemon Date: Thu, 16 Oct 2003 21:25:04 +0000 Subject: Initial data for the scons project --- www/index.html | 96 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 96 insertions(+) create mode 100644 www/index.html diff --git a/www/index.html b/www/index.html new file mode 100644 index 0000000..26f2a49 --- /dev/null +++ b/www/index.html @@ -0,0 +1,96 @@ + + + + + +

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. +

+ +

Until your project is approved, only you can view it and work on +it. +

+ +

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).
To edit this file, check out your project via CVS and edit www/index.html. + +
You can 'cvs add' and commit other files under the project's "www" +directory and they will published to your project web site.
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.
You can add a "Highlights:" line to the top of all web pages by adding a file www/project_highlights.html

+ + +

Mission

+ +

What is the goal of this project? +

+ +

What is the scope of this project? +

+ +

For example:

+ +

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

+ + +

What are high-level features you are sure to build? +

What would you write on a billboard about your project? Users +might only look for a few seconds.
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.

+ +

What are the high-level assumptions or ground rules for the project? +

+ +

For example: +

+ +

we will use programming language X on operating system Y for now. + +
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. + +
Try to keep this part short. +

+ + +

Related resources

+ +

Link to other stuff that you know about. It will help you +research requirements and provide a useful resource to potential +contributors.
Why reinvent the wheel? What is better about this wheel? Is there +any existing project that you can partner with or reuse?
Where would you go to try to find potential contibutors?

+ + + -- cgit v0.12