Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp1055128imm; Tue, 2 Oct 2018 01:46:46 -0700 (PDT) X-Google-Smtp-Source: ACcGV61SlqL+Avr2DMfJRMNhxyqgYHT0JTLhvdV31z875STlYFGeRSTsNDv1ayzi25BNpZ91Sg4H X-Received: by 2002:a17:902:30a3:: with SMTP id v32-v6mr267481plb.277.1538470005965; Tue, 02 Oct 2018 01:46:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538470005; cv=none; d=google.com; s=arc-20160816; b=VMuAVRGyoscTiSdTbHe3stZxGeZ8JBERMndj32wrDNdIweFr0eAgSGy1Wrtx95A6Ej j1TM+UZAj9w9hyvthVu3w/QlURCbzLzGKcI3X2HQ0CU0ZjxBj+6xFhn49XciZisqV9T6 ZSw8gNpCAURcxUfHsC/+AhiCZAdjKVu7jQuUZ9k2WeVuFYjDJC74cxZsyIH+V3AUQ39y Mc4N/OYXsmM5ZslyILme4EWYYhoqXlYRjdP28HozOoCHT0muLiWSehHtw30dnKGdUh55 maE8rejGR3Dmo92oVWk+ZZ38aN4zs0ybXwL74SXjDdyt01imtgJXNNI6+7DBN5fUCX6l y3hQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:thread-index:thread-topic :content-transfer-encoding:mime-version:subject:references :in-reply-to:message-id:cc:to:from:date; bh=Yaa3rWlJorBBa2TqZuGz2ScAkaDdHRXJL4a8CS4YB7M=; b=oQNtJhibSEiv2BmhkF3D/lhgbMdIX3o2a3moyJAvby243zcQM7fMhZtt+VHpWbTYKn XDF7HQZMlKfaKlSMzDu64MU5DnXaMklWMLiWRRptBgsbcKcSPmwHoGvTeuytH30sv9qV bJf+N8azS7eLBDMxvg88odNtH3DddXV5OV+Rc+Z7azRwZXLe7t7v7kU0iMpcEQZ9cRBL b6GmNwWMZ9Af3dyg583pdlEM27FWNrRE3uszWcSf1Cu80K1R7kWN/Gokm30/gAfOpup2 5nzfb8CjkNrwCYKO40QFZk1rdBGps3WkMCTSaQ9S+JutkvQ5qz9UPdhRdU6YsxLb4NYy aiaw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h1-v6si13607065pgs.493.2018.10.02.01.46.30; Tue, 02 Oct 2018 01:46:45 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727388AbeJBP0U convert rfc822-to-8bit (ORCPT + 99 others); Tue, 2 Oct 2018 11:26:20 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51518 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726508AbeJBP0U (ORCPT ); Tue, 2 Oct 2018 11:26:20 -0400 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id CE942308212C; Tue, 2 Oct 2018 08:44:10 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id AB57C2010CEF; Tue, 2 Oct 2018 08:44:10 +0000 (UTC) Received: from zmail22.collab.prod.int.phx2.redhat.com (zmail22.collab.prod.int.phx2.redhat.com [10.5.83.26]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 7CED81809546; Tue, 2 Oct 2018 08:44:10 +0000 (UTC) Date: Tue, 2 Oct 2018 04:44:10 -0400 (EDT) From: Jaroslav Skarvada To: Pali =?utf-8?Q?Roh=C3=A1r?= 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 , Karel Zak , Andreas Bombe , Andreas Bombe , Andreas Dilger , Richard Weinberger Message-ID: <510499199.34825028.1538469850257.JavaMail.zimbra@redhat.com> In-Reply-To: <20181002081654.jxesr3kj62snzez5@pali> References: <20180929084038.an6pfhnsd6tblejl@pali> <20181002081654.jxesr3kj62snzez5@pali> Subject: Re: Future of dosfstools project (FAT) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Originating-IP: [10.43.7.166, 10.4.195.20] Thread-Topic: Future of dosfstools project (FAT) Thread-Index: sjMSYP9oasQnW4UnwK55WDa9X3Hb4w== X-Scanned-By: MIMEDefang 2.84 on 10.5.11.25 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.42]); Tue, 02 Oct 2018 08:44:10 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ----- > On Monday 01 October 2018 22:13:41 Richard Weinberger wrote: > > On Mon, Oct 1, 2018 at 10:01 PM Andreas Dilger 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