lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181002093619.nrmibtzouwraoyob@ws.net.home>
Date:   Tue, 2 Oct 2018 11:36:19 +0200
From:   Karel Zak <kzak@...hat.com>
To:     Richard Weinberger <richard.weinberger@...il.com>
Cc:     adilger@...ger.ca,
        Pali Rohár <pali.rohar@...il.com>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        util-linux@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
        andy.shevchenko@...il.com, aeb@...ian.org, andreas.bombe@...il.com
Subject: Re: Future of dosfstools project (FAT)

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@...ger.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@...hat.com>
 http://karelzak.blogspot.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ