From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Greg KH <gregkh@linuxfoundation.org>,
Salah Triki <salah.triki@acm.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Richard Weinberger <richard@nod.at>,
linux-fsdevel@vger.kernel.org
Subject: Volunteering for BeFS maintainership
Date: Mon, 25 Jul 2016 18:21:19 +0100 [thread overview]
Message-ID: <57964A8F.2010104@osg.samsung.com> (raw)
Hi all,
Now that the 4.7 cycle is finished, I want to volunteer myself and Salah
Triki for maintainership of the BeFS filesystem.
Salah and myself have been cleaning up the code for the last few months,
and since the current status of it is Orphan, it would be great if we could
take care of it.
Personally, besides clean ups, I would like to add more documentation of how
the file system works, eg. including more function descriptions, so the Linux
implementation can be the ideal practical match to Dominic Giampaolo's free
book "Practical File System Design with the Be File System".
This book is the most in-depth I've found about any file system, which is
why I think having linux/fs/befs well documented would be very valuable to
eveybody learning about how file systems work.
I attach below what the change in MAINTAINERS would look like. If this is
approved I will send a proper formatted patch mail.
Thanks,
Luis
PD: I don't know if there is a formal process for maintainership in the Linux
kernel community. I am happy to follow that if it exists.
Also, if I'm missing anybody who should be in CC, please let me know.
---
MAINTAINERS | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 8c20323..7a62abc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2321,7 +2321,9 @@ S: Supported
F: drivers/media/platform/sti/bdisp
BEFS FILE SYSTEM
-S: Orphan
+M: Luis de Bethencourt <luisbg@osg.samsung.com>
+M: Salah Triki <salah.triki@acm.org>
+S: Mantained
F: Documentation/filesystems/befs.txt
F: fs/befs/
--
2.5.1
next reply other threads:[~2016-07-25 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:21 Luis de Bethencourt [this message]
2016-07-25 21:23 ` Volunteering for BeFS maintainership Greg KH
2016-07-25 23:16 ` Luis de Bethencourt
2016-07-26 17:56 ` Theodore Ts'o
2016-07-26 20:30 ` Luis de Bethencourt
2016-07-27 3:05 ` Theodore Ts'o
2016-07-27 11:45 ` Luis de Bethencourt
2016-07-27 13:23 ` Theodore Ts'o
2016-07-27 14:39 ` Luis de Bethencourt
2016-07-27 2:01 ` Salah Triki
2016-07-26 23:54 ` Salah Triki
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=57964A8F.2010104@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=salah.triki@acm.org \
--cc=viro@ZenIV.linux.org.uk \
/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).