From: Karel Zak <kzak@redhat.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: adilger@dilger.ca, "Pali Rohár" <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, aeb@debian.org,
andreas.bombe@gmail.com
Subject: Re: Future of dosfstools project (FAT)
Date: Tue, 2 Oct 2018 11:36:19 +0200 [thread overview]
Message-ID: <20181002093619.nrmibtzouwraoyob@ws.net.home> (raw)
In-Reply-To: <CAFLxGvxfegQFh0kvk81VLhLh0AkgvpT=hWMDCJz5FmgoTUNRqA@mail.gmail.com>
On Mon, Oct 01, 2018 at 10:13:41PM +0200, Richard Weinberger wrote:
> 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.
Drama? :-) We had confirmed support from all mainstream distros before
the fork and rename. It was really not ad hoc solution. The project
has been renamed back to util-linux after confirmation from the
original maintainer.
Sometimes fork open source project is a good thing. The another
example is mutt -> mutt-kz -> neomutt ;-)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2018-10-02 9:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 8:40 Future of dosfstools project (FAT) Pali Rohár
2018-10-01 20:00 ` Andreas Dilger
2018-10-01 20:13 ` Richard Weinberger
2018-10-02 8:16 ` Pali Rohár
2018-10-02 8:44 ` Jaroslav Skarvada
2018-10-12 9:19 ` Andreas Henriksson
2018-10-12 12:40 ` Pali Rohár
2018-10-12 14:35 ` Doug Goldstein
2018-11-14 11:33 ` Pali Rohár
[not found] ` <CAPXf_qN66-Mi+o+9ENGqCDe-_2tHaf9uM3moRcCGNvmxwH3ExQ@mail.gmail.com>
2018-12-06 8:38 ` Pali Rohár
2018-12-12 13:57 ` Pali Rohár
2018-12-17 9:50 ` Pali Rohár
2018-12-27 22:17 ` Pali Rohár
2019-01-08 15:32 ` Andy Shevchenko
2019-01-08 15:39 ` Richard Weinberger
2019-01-14 15:17 ` Pali Rohár
2019-01-14 15:19 ` Richard Weinberger
2019-02-09 15:40 ` Pali Rohár
2019-02-15 20:04 ` Andy Shevchenko
2018-10-02 9:36 ` Karel Zak [this message]
2018-10-01 20:14 ` Pali Rohár
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=20181002093619.nrmibtzouwraoyob@ws.net.home \
--to=kzak@redhat.com \
--cc=adilger@dilger.ca \
--cc=aeb@debian.org \
--cc=andreas.bombe@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=richard.weinberger@gmail.com \
--cc=util-linux@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).