Hi! 2009/4/12 Matteo Latini <[email protected]>: > Hi all, > I just discovered nilfs and I was wondering if there is some > way of getting involved in developing some code... > > thx, > Matteo Latini
Thanks. Any contribution is welcome. If you are interested in developing NILFS, please toy the source code. It's available from the following site with git: http://www.nilfs.org/git/ I'm also preparing for a repository of in-tree code in kernel.org. Until it gets available, Linus' tree is a quick reference. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git I'm now concentrating on bug hunting toward release of kernel 2.6.30, but I feel new feature development should be driven for later versions. At least, we have following todo items (these are listed in the current status page of our project), > * Checkpoint based remote replication > * Performance improvement (Better Block I/O submission) > * atime support > * Optimization for silicon disks (e.g. SSD) > * fsck > * Faster inode allocation > * Online resizing > * Online defrag > * filesystem freeze support > * Variety of Garbage Collection policies > * Design document and better developer support > * Better support of fsync, mmap, and direct I/O. > * Filesystem label support > * More backup copies of the super block > * Time-machine like browser extension (or Time slider) and we also need distro support; for example, Ubuntu or Fedora doesn't have good nilfs support though it's well supported in Debian. Documentation is another important problem. I'm not a native English writer, so all texts including comments, manpages, readme file have much room for improvement. If someone refine our manpages in util-package, I will take it in pretty certainly ;) Let's take it easy. Regards, Ryusuke Konishi _______________________________________________ users mailing list [email protected] https://www.nilfs.org/mailman/listinfo/users
