Anything can get out of date if it not in the code, but I think having a wiki with backlog should be good. I will add "closing inactive NFSv3 open files" to the list of things we should do.
Regards, Malahal. On Mon, Aug 1, 2016 at 12:01 PM, Frank Filz <ffilz...@mindspring.com> wrote: >> Hi all, >> I have contributed around 5 minor patches to NFS Ganesha and I plan to >> contribute more. I searched but could not find a TODO or wishlist of NFS >> Ganesha. There are many others like me I know of who would like to >> contribute but don't know what they should. Can we have a wishlist so that >> everyone who wish to contribute to NFS Ganesha knows which are the best >> areas to look at? > > I have various post-its with "todo" items on them. There is also /** @todo > comments in the code (and maybe some other tags to look at). I also have a > very old "punch list" e-mail. > > I probably should make some of that stuff more visible by creating a wiki > page... On the other hand, such things can easily become obsolete... > >> Some TODO I can think of: >> FSAL for some currently unsupported filesystems Add more tests to pynfs to >> test NFS Ganesha Deduplication/Compression/Backup support as a stackable >> FSAL layer > > What unsupported filesystems are you thinking of here? > > Frank > > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > > ------------------------------------------------------------------------------ > _______________________________________________ > Nfs-ganesha-devel mailing list > Nfs-ganesha-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel ------------------------------------------------------------------------------ _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel