Login | Register
My pages Projects Community openCollabNet

Discussions > commits > svn commit: r2 - in trunk: . www

fsvs
Discussion topic

Hide all messages in topic

All messages in topic

svn commit: r2 - in trunk: . www

Author pmarek
Full name P.Marek
Date 2005-09-13 10:58:04 PDT
Message Author: pmarek
Date: Tue Sep 13 10:58:03 2005
New Revision: 2

Modified:
   trunk/ (props changed)
   trunk/www/index.html
Log:
 r4@flippy: flip | 2005-09-13 19:57:25 +0200
 first cut at index.html


Modified: trunk/www/index.html
Url: http://fsvs.tigris.o​rg/source/browse/fsv​s/trunk/www/index.ht​ml?view=diff&rev​=2&p1=trunk/www/​index.html&r1=1​&p2=trunk/www/ind​ex.html&r2=2
====================​====================​====================​==================
--- trunk/www/index.html (original)
+++ trunk/www/index.html Tue Sep 13 10:58:03 2005
@@ -1,106 +1,53 @@
-<html>
-<head>
- <style type="text/css">
-/* <![CDATA[ */
-@import "http://www.tigris.or​g/branding/css/tigri​s.css";
-@import "http://www.tigris.or​g/branding/css/inst.​css";
-/* ]]> */
- </style>
- <link rel="stylesheet" type="text/css" href="http://www.tigris.or​g/branding/css/print​.css" media="print" />
-<script src="http://www.tigris.or​g/branding/scripts/t​igris.js" type="text/javascript">
-</script>
- <title>Project Overview</title>
-</head>
-<body>
-
-<p>This is the initial web content for your project. Please customize
-this to fit your project. You don't need to answer 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 "Administer 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
-these 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>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<HTML>
+<HEAD>
+ <META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=iso-8859-1">
+ <TITLE>Project Overview</TITLE>
+ <META NAME="GENERATOR" CONTENT="OpenOffice.org 1.1.4 (Linux)">
+ <META NAME="CREATED" CONTENT="20050913;19455000">
+ <META NAME="CHANGED" CONTENT="20050913;19555800">
+ <SCRIPT SRC="http://www.tigris.or​g/branding/scripts/t​igris.js"></SCRIPT>
+</HEAD>
+<BODY LANG="en-US" DIR="LTR">
+<H1>FSVS</H1>
+<H2>Purpose</H2>
+<P>FSVS stands for &ldquo;Fast System VerSioning&rdquo;, &ldquo;File
+System VerSioning&rdquo; or &ldquo;Full System VerSioning&rdquo;. It
+aims to become a complete backup/restore tool for linux machines,
+with a subversion repository as the backend.</P>
+<H2>What is does currently</H2>
+<P>FSVS is still in development.<BR>Currently it does (in subversion
+speak)</P>
+<UL>
+ <LI>initialize itself for operation (define target URL)
+ <LI>commit to this URL (backup), with meta-data support (owner,
+ group, mode, devices, symlinks)</P>
+ <LI>update from this URL (restore), with meta-data support
+ <LI>use advanced ignore patterns, eg. to ignore all virtual
+ filesystems like /proc, /sys, /dev (if devfs), and so on.
+ PCRE-expressions and recursive ignore patterns are possible, too.
+</UL>
+<H2>What it needs to run</H2>
+<UL>
+ <LI>subversion-1.2 libraries
+ <LI>apr libraries
+ <LI>a linux machine
+ <LI>gcc to compile. No autoconf, automake or similar currently.
+</UL>
+<H2>What it needs for development</H2>
+<P>It still needs a small bit of polishing; but as of 2005-09-13 I
+believe it to be a good beta.<BR>First beta versions will soon appear
+on this website.</P>
+<P>Needed are</P>
+<UL>
+ <LI>users/testers
+ <LI>developers (a lot of features already planned &ndash; see
+ documentation)
+ <LI>native english speaker to translate my texts to something
+ readable :-)
+</UL>
+<H2>Statistic​s</H2>
+<P>It's released under the GPL; and has currently about 4000 lines of
+code, excluding comments and empty lines.</P>
+</BODY>
+</HTML>
Messages per page: