Date: Wed, 10 Dec 2008 23:36:17 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Phillips <phillips@phunq.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, tux3@tux3.org
Subject: Re: Tux3 report: Tux3 by Christmas?
Message-Id: <20081210233617.ddb3fa30.akpm@linux-foundation.org>
In-Reply-To: <200812101435.40393.phillips@phunq.net>
References: <200812101435.40393.phillips@phunq.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1396
Lines: 39

On Wed, 10 Dec 2008 14:35:39 -0800 Daniel Phillips <phillips@phunq.net> wrote:

> The big goals for Christmas (this Christmas!) are:
> 
>    - SMP locking
>    - Atomic commit
>    - Posixly complete
>    - Rudimentary fsck
> 
> ...
> 
> Non-goals for Christmas include:
> 
>    - Versioning
>    - Directory indexing (PHTree)
>    - fsck repair

If it is your intention to submit this for a mainline merge then I
would encourage you to stop feature work at the earliest reasonable
stage and then move into the document, submit, review, merge, fixfixfix
phase.  That might take as long as several months.

Once things have stabilised and it's usable and performs respectably,
start thinking about features again.

Do NOT fall into the trap of adding more and more and more stuff to an
out-of-tree project.  It just makes it harder and harder to get it
merged.  There are many examples of this.


Also, don't feel that a merge would lock you into the current on-disk
layout.  I think it would be acceptable to emit a big printk("the
format of this fs will change without notice.  Do not yet store any
data on a tux3 fs") during mount().   For a while.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/