ntfs3.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Kari Argillander <kari.argillander@stargateuniverse.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
	ntfs3@lists.linux.dev
Cc: Theodore Ts'o <tytso@mit.edu>, Christoph Hellwig <hch@lst.de>,
	Matthew Wilcox <willy@infradead.org>,
	Eric Biggers <ebiggers@kernel.org>,
	"Darrick J. Wong" <djwong@kernel.org>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: NTFS3 driver is orphan already. What we do?
Date: Tue, 26 Apr 2022 12:22:02 +0300	[thread overview]
Message-ID: <da20d32b-5185-f40b-48b8-2986922d8b25@stargateuniverse.net> (raw)

After ntfs3 got merged and 5.15 got released ntfs3 maintainer has kept total
radio silence. I have tried to contact him with personal mails with no 
luck. I
have chosen bunch of people to discuss what we should do this driver as 
this is
already orphan. Feel free to add more if you think it is necessary. There is
lot of bug reports which are ignored completely. Lot of patches which nobody
applies.

He did some work after 5.15, but has not send PR for those [1]. I did 
also ask
to use fix and next branches seperetly and tag stable fixes, but he did 
not do
that eater. I think Konstantin did not yet quite understand meaning of 
stable,
next and upstream and it is not ok to applied every patch to same tree 
for any
point.

Personally I did my best try to help Konstantin with maintainer things, 
but I
have to say that it was quite difficult as he mostly ignored emails and 
do many
things like he wanted. He did not suggest anything to anyone if someone send
patch. He just applied those or ignored. Also sometimes he just applied own
patch without sending it to review process. Of course new maintainer 
needs time
to learn things but just wanted to say these so everyone knows how 
things went
so far.

I also did suggest that I could co maintain this driver to take burden from
Konstantin, but haven't got any replay. I have worker towards better CI 
system
for myself for ntfs3 which of course will be public in some point if we 
solve
current situations. If we keep this driver we really need very good fstests
support. But we also do not have very good open source utilyes for ntfs.
Konstantin said that he will open source those as well, but here we are 
waiting
and we will probably have to wait long time.

Now is time to think what we should do. Should ntfs3 just be removed? As I
really wanted to see that ntfs3 will be big thing I have to say that I 
vote for
removing unless someone comes to rescue this catastrophe. Yes we break
userspace, but we might break it silently if nobody is maintaining this. 
I also
do not believe that if someone is just accepting patches that it is enough.
Ntfs3 is not so ready that we do not need some ntfs specialist to 
maintain it
imo. Really public CI might save something if we keep this in and I will 
work
towards that if we choose to keep this in.

And if Konstantin read this please come and join this conversation.

   Argillander

[1]: https://github.com/Paragon-Software-Group/linux-ntfs3/commits/devel

             reply	other threads:[~2022-04-26  9:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26  9:22 Kari Argillander [this message]
2022-04-27 17:47 ` Linus Torvalds
2022-04-28  0:47   ` Namjae Jeon
2022-04-29 16:45     ` Kari Argillander
2022-04-29 19:59       ` David Sterba
2022-04-28  9:38   ` Leonidas-Panagiotis Papadakos
2022-05-01 17:13   ` Konstantin Komarov
2022-05-02 20:49     ` Kari Argillander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=da20d32b-5185-f40b-48b8-2986922d8b25@stargateuniverse.net \
    --to=kari.argillander@stargateuniverse.net \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=djwong@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --subject='Re: NTFS3 driver is orphan already. What we do?' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).