From: Jaroslav Skarvada <jskarvad@redhat.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, util-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, mpluskal@suse.com,
base-system@gentoo.org,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Karel Zak <kzak@redhat.com>, Andreas Bombe <aeb@debian.org>,
Andreas Bombe <andreas.bombe@gmail.com>,
Andreas Dilger <adilger@dilger.ca>,
Richard Weinberger <richard.weinberger@gmail.com>
Subject: Re: Future of dosfstools project (FAT)
Date: Tue, 2 Oct 2018 04:44:10 -0400 (EDT) [thread overview]
Message-ID: <510499199.34825028.1538469850257.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181002081654.jxesr3kj62snzez5@pali>
----- Original Message -----
> On Monday 01 October 2018 22:13:41 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.
>
> Based on Richard's comment, I'm forwarding my original email (below) to
> the Fedora, Suse and Gentoo maintainers.
>
> On Saturday 29 September 2018 10:40:38 Pali Rohár wrote:
> > Hi!
> >
> > Last year I did some research how Windows and Linux tools handle FAT
> > labels (boot sector vs root directory) and proposed some unification.
> > More in thread: https://www.spinics.net/lists/kernel/msg2640891.html
> >
> > My proposed change for manipulating with FAT labels is now implemented
> > in util-linux v2.33, prepared new mtools version, and also in dosfstools
> > git (unreleased) https://www.spinics.net/lists/kernel/msg2645732.html
> >
> > Project dosfstools contains de-facto standard Linux userspace tools for
> > FAT filesystems (mkfs.fat, fsck.fat, fatlabel) and so it is quite
> > important because of high usage of FAT.
> >
> > But there was no new release of dosfstools since Jan 2017 and for more
> > then month I'm unsuccessfully try to contact maintainer of dosfstools
> > project (Andreas) about future of project itself.
> >
> > I do not know what happened, if either Andreas do not have time or
> > something else...
> >
> > So does somebody know what is state of dosfstools project?
> >
> > Also there are lot of proposed changes (with patches) for this project
> > https://github.com/dosfstools/dosfstools/pulls and also more reported
> > bugs https://github.com/dosfstools/dosfstools/issues
> >
> > If Andreas does not have time, can somebody else at least look at pull
> > requests and do some code review?
> >
> > I have some other unpublished/unfinished changes for dosfstools, but I
> > do not know now if it make sense to invest more time in this project
> > when maintainer does not respond... if this project is active or going
> > to be dead...
> >
> > If dosfstools is going to be inactive/dead, there is still mtools
> > project with provides FAT tools too and maintainer of it is now
> > preparing new bugfix version. So at least some alternative exists.
>
> --
> Pali Rohár
> pali.rohar@gmail.com
>
Hi,
I am downstream maintainer of dosfstools in Fedora/RHEL. My personal opinion
with such kind of projects is that one or two years without activity doesn't
mean the project is dead. I don't know what happened with Andreas, but
in case of no response my +1 for the GitHub fork. I think it's non offensive
solution which can be easily reverted if needed. Please let me know if you do it
thanks & regards
Jaroslav
next prev parent reply other threads:[~2018-10-02 8:44 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 [this message]
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
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=510499199.34825028.1538469850257.JavaMail.zimbra@redhat.com \
--to=jskarvad@redhat.com \
--cc=adilger@dilger.ca \
--cc=aeb@debian.org \
--cc=andreas.bombe@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=base-system@gentoo.org \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpluskal@suse.com \
--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).