Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20180929084038.an6pfhnsd6tblejl@pali> <404F3F76-402D-4E29-9957-429CB7D7ECFC@dilger.ca>
In-Reply-To: <404F3F76-402D-4E29-9957-429CB7D7ECFC@dilger.ca>
From:   Richard Weinberger <richard.weinberger@gmail.com>
Date:   Mon, 1 Oct 2018 22:13:41 +0200
Message-ID: <CAFLxGvxfegQFh0kvk81VLhLh0AkgvpT=hWMDCJz5FmgoTUNRqA@mail.gmail.com>
Subject: Re: Future of dosfstools project (FAT)
To:     adilger@dilger.ca
Cc:     =?UTF-8?Q?Pali_Roh=C3=A1r?= <pali.rohar@gmail.com>,
        linux-fsdevel <linux-fsdevel@vger.kernel.org>,
        util-linux@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
        andy.shevchenko@gmail.com, Karel Zak <kzak@redhat.com>,
        aeb@debian.org, andreas.bombe@gmail.com
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Oct 1, 2018 at 10:01 PM Andreas Dilger <adilger@dilger.ca> wrote:
> If the current dosfstools maintainer is non-responsive, you could always
> fork the project in GitHub, land the critical patches into your branch,
>  and make a release on your own.  If the maintainer surfaces again, then
> they can pull in your patches.  If not, then you are the new maintainer.

I also recommend talking to package maintainers of major distros.
Maybe one of them forked the project already and did what you plan to do.

In any case, let's try to avoid a drama like util-linux-ng was.

-- 
Thanks,
//richard