From: Kari Argillander <firstname.lastname@example.org> To: Konstantin Komarov <email@example.com>, Linus Torvalds <firstname.lastname@example.org> Cc: "email@example.com" <firstname.lastname@example.org>, Theodore Ts'o <email@example.com>, Christoph Hellwig <firstname.lastname@example.org>, Matthew Wilcox <email@example.com>, Eric Biggers <firstname.lastname@example.org>, "Darrick J. Wong" <email@example.com>, Christian Brauner <firstname.lastname@example.org>, Al Viro <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org> Subject: Re: NTFS3 driver is orphan already. What we do? Date: Mon, 2 May 2022 23:49:23 +0300 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On 1.5.2022 20.13, Konstantin Komarov wrote: >> From: Linus Torvalds <email@example.com> >> Sent: Wednesday, April 27, 2022 7:47 PM >> To: Kari Argillander <firstname.lastname@example.org> >> Cc: Konstantin Komarov <email@example.com>; firstname.lastname@example.org; Theodore Ts'o <email@example.com>; >> Christoph Hellwig <firstname.lastname@example.org>; Matthew Wilcox <email@example.com>; Eric Biggers <firstname.lastname@example.org>; Darrick J. Wong >> <email@example.com>; Christian Brauner <firstname.lastname@example.org>; Al Viro <email@example.com>; Linux Kernel Mailing >> List <firstname.lastname@example.org> >> Subject: Re: NTFS3 driver is orphan already. What we do? >> >> [ Sad state of affairs mostly edited out ] >> >> On Tue, Apr 26, 2022 at 2:22 AM Kari Argillander >> <email@example.com> wrote: >>> >>> I also did suggest that I could co maintain this driver to take burden from >>> Konstantin, but haven't got any replay. >> >> If you are willing to maintain it (and maybe find other like-minded >> people to help you), I think that would certainly be a thing to try. >> >> And if we can find *nobody* that ends up caring and maintaining, then >> I guess we should remove it, rather than end up with *two* effectively >> unmaintained copies of NTFS drivers. >> >> Not that two unmaintained filesystems are much worse than one :-p >> >> Linus > > Hello Linus, Kari and all. Hello Konstantin and thanks for you answer. Happy to see that you are still in. > First and foremost I need to state that active work on NTFS3 driver has never stopped, > and it was never decided to "orphan" NTFS3. Currently we are still in the middle of the process > of getting the Kernel.org account. We need to sign our PGP key to move forward, but > the process is not so clear (will be grateful to get some process desciption), so it is going quite slow > trying to unravel the topic. Basically easiest route is some conference, but there is not so many as we are kinda middle of covid still. You can try to search some Germany kernel devs and contact them. Then you can meet them in person and proof who you are and then they will sign you key. I'm same situation my self right now and have meeting with some Finnish devs. > As for now, we can prepare patches/pull requests through the github, > and submit them right now (we have quite a bunch of fixes > for new Kernels support, bugfixes and fstests fixes) -- if Linus approves this approach > until we set up the proper git.kernel.org repo. It should not be problem to continue using Github. Kernel.org is of course nice in case example maintainership is transfer to others or there is multiple maintainers. > Also, to clarify this explicitly: in addition to the driver, we're working of ntfs3 utilities as well. Nice to hear :) > Overall, nevertheless the NTFS3 development pace has been slowed down a bit for previous couple > of months, its state is still the same as before: it is fully maintained and being developed. I have to disagree that it is fully maintained right now. Half year radio silence is not "fully maintained". But we can work this out so that this driver will be fully maintained. But the offer is still that you do not have to maintain this fully by yourself if this is too much work. There is many other subsystem where there are multiple maintainers. Also I would like to point once again that we really need to check that stable gets fixes also. But those are just what are fixes not new features. Also only merge window should be new code. Every other should should only contain fixes. This is why usually couple different branch is needed. If you have any questions please feel to always ask me or from mailing list. Argillander > And finally, we apologize for late reply; I allowed me short vacation after most restrictions because > of covid ended up this month in Germany. > > Thanks.
prev parent reply other threads:[~2022-05-02 20:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 9:22 Kari Argillander 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 [this message]
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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).