WANTED new maintainer for Linux/md (and mdadm)

WANTED new maintainer for Linux/md (and mdadm)

[NeilBrown]

[-- Attachment #1: Type: text/plain, Size: 4527 bytes --]


hi,
 I became maintainer for md (Linux Software RAID) in late 2001 and on
 the whole it has been fun and a valuable experience.  But I have been
 losing interest in recent years (https://lwn.net/Articles/511073/) and
 as was mentioned at the kernel summit, I would like to resign.  Some
 years ago I managed to hand over nfsd to the excellent Bruce Fields,
 but I do not seem to have the gift that Linus has of attracting
 maintainers.  While there are a number of people who know quite a bit
 about md and/or have contributed to development, there is no obvious
 candidate for replacement maintainer - no one who has already been
 doing significant parts of the maintainer role.

 So I have decided to fall back on the mechanism by which I ended up
 being maintainer in the first place.  I will create a vacuum and hope
 someone fills it (yes: I was sucked-in....).  So as of 1st February
 2016 I will be resigning.

 At the kernel summit in October Linus talked about the value of
 maintainership teams (https://lwn.net/Articles/662979/).  I think it
 would be great if a (small) team formed to continue to oversee md
 rather than just a single individual (or maybe the dm team could extend
 to include md??).  If I had managed to be part of a team rather than
 "going it alone" for so long, I might feel less tired of the whole
 thing now.

 I don't see it as my place to appoint that team or any individuals, or
 even to nominate any candidates.  A very important attribute of a
 maintainer is that they need to care about the code and the subsystem
 and I cannot tell other people to care (or even know if they do).  It
 is really up to individuals to volunteer.  A few people have been
 mentioned to me in earlier less-public conversations.  Any of them may
 well be suitable, but I would rather they named themselves if
 interested.

 So I'm hoping to get one or more volunteers to be maintainer:
   - to gather and manage patches and outstanding issues,
   - to review patches or get them reviewed
   - to follow up bug reports and get them resolved
   - to feed patches upstream, maybe directly to Linus,
     maybe through some other maintainer, depending on what
     relationships already exist or can be formed,
   - to guide the longer term direction (saying "no" is important
     sometimes),
   - to care,
 but also to be aware that maintainership takes real effort and time, as
 does anything that is really worthwhile.

 This all applies to mdadm as well as md (except you would ultimately
 *be* upstream for mdadm, not needing to send it anywhere).  Even if a
 clear team doesn't form it would be great if different people
 maintained mdadm and md.

 One part of the job that I have put a lot of time in to is following
 the linux-raid@vger.kernel.org list and providing support.  This makes
 people feel good about md and so more adventurous in using it.
 Consequently I tend to hear about bugs and usability issues nice and
 early (well before paying customers hit them in most cases) and that is
 a big win.
 In recent times I've been doing less of this and have been absolutely
 thrilled that the gap has been more than filled by other very competent
 community members.  Not developers particular but a number of md users
 have been providing excellent support.  I'd particularly like to
 high-light Phil Turmel who is very forthcoming with excellent advice,
 but he is certainly not the only one who deserves a lot of thanks.
 So "Thank you" to everyone who answers questions on linux-raid.

 This would be a good place for any future maintainer to hang out to
 receive wisdom as well as to provide support.

 I will still be around.  I can certainly help out in some sort of
 mentor role, and can probably be convinced to review patches and
 comment on designs.  But I really want to head towards spending less
 time on md (there are so many other interesting things to learn about).

 So: if anyone is interested - please announce yourself, ask questions
 and start doing things.  I have no clear idea about how a transition
 will happen.  That is really up to you (plural). Take the bull by the
 horns and start *being* a maintainer(team).  I won't get in your way
 and I'll help where I can.

Thanks,
NeilBrown

P.S. I'm committed to continue to work with the raid5-journal effort
From Facebook and the raid1-cluster effort from SUSE and the
line-in-the-sand of 1st February won't affect my support for those.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

WANTED new maintainer for Linux/md (and mdadm)

[NeilBrown]

[-- Attachment #1: Type: text/plain, Size: 4527 bytes --]


hi,
 I became maintainer for md (Linux Software RAID) in late 2001 and on
 the whole it has been fun and a valuable experience.  But I have been
 losing interest in recent years (https://lwn.net/Articles/511073/) and
 as was mentioned at the kernel summit, I would like to resign.  Some
 years ago I managed to hand over nfsd to the excellent Bruce Fields,
 but I do not seem to have the gift that Linus has of attracting
 maintainers.  While there are a number of people who know quite a bit
 about md and/or have contributed to development, there is no obvious
 candidate for replacement maintainer - no one who has already been
 doing significant parts of the maintainer role.

 So I have decided to fall back on the mechanism by which I ended up
 being maintainer in the first place.  I will create a vacuum and hope
 someone fills it (yes: I was sucked-in....).  So as of 1st February
 2016 I will be resigning.

 At the kernel summit in October Linus talked about the value of
 maintainership teams (https://lwn.net/Articles/662979/).  I think it
 would be great if a (small) team formed to continue to oversee md
 rather than just a single individual (or maybe the dm team could extend
 to include md??).  If I had managed to be part of a team rather than
 "going it alone" for so long, I might feel less tired of the whole
 thing now.

 I don't see it as my place to appoint that team or any individuals, or
 even to nominate any candidates.  A very important attribute of a
 maintainer is that they need to care about the code and the subsystem
 and I cannot tell other people to care (or even know if they do).  It
 is really up to individuals to volunteer.  A few people have been
 mentioned to me in earlier less-public conversations.  Any of them may
 well be suitable, but I would rather they named themselves if
 interested.

 So I'm hoping to get one or more volunteers to be maintainer:
   - to gather and manage patches and outstanding issues,
   - to review patches or get them reviewed
   - to follow up bug reports and get them resolved
   - to feed patches upstream, maybe directly to Linus,
     maybe through some other maintainer, depending on what
     relationships already exist or can be formed,
   - to guide the longer term direction (saying "no" is important
     sometimes),
   - to care,
 but also to be aware that maintainership takes real effort and time, as
 does anything that is really worthwhile.

 This all applies to mdadm as well as md (except you would ultimately
 *be* upstream for mdadm, not needing to send it anywhere).  Even if a
 clear team doesn't form it would be great if different people
 maintained mdadm and md.

 One part of the job that I have put a lot of time in to is following
 the linux-raid@vger.kernel.org list and providing support.  This makes
 people feel good about md and so more adventurous in using it.
 Consequently I tend to hear about bugs and usability issues nice and
 early (well before paying customers hit them in most cases) and that is
 a big win.
 In recent times I've been doing less of this and have been absolutely
 thrilled that the gap has been more than filled by other very competent
 community members.  Not developers particular but a number of md users
 have been providing excellent support.  I'd particularly like to
 high-light Phil Turmel who is very forthcoming with excellent advice,
 but he is certainly not the only one who deserves a lot of thanks.
 So "Thank you" to everyone who answers questions on linux-raid.

 This would be a good place for any future maintainer to hang out to
 receive wisdom as well as to provide support.

 I will still be around.  I can certainly help out in some sort of
 mentor role, and can probably be convinced to review patches and
 comment on designs.  But I really want to head towards spending less
 time on md (there are so many other interesting things to learn about).

 So: if anyone is interested - please announce yourself, ask questions
 and start doing things.  I have no clear idea about how a transition
 will happen.  That is really up to you (plural). Take the bull by the
 horns and start *being* a maintainer(team).  I won't get in your way
 and I'll help where I can.

Thanks,
NeilBrown

P.S. I'm committed to continue to work with the raid5-journal effort
From Facebook and the raid1-cluster effort from SUSE and the
line-in-the-sand of 1st February won't affect my support for those.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Re: WANTED new maintainer for Linux/md (and mdadm)

[Phil Turmel]

On 12/21/2015 01:10 AM, NeilBrown wrote:

>  In recent times I've been doing less of this and have been absolutely
>  thrilled that the gap has been more than filled by other very competent
>  community members.  Not developers particular but a number of md users
>  have been providing excellent support.  I'd particularly like to
>  high-light Phil Turmel who is very forthcoming with excellent advice,
>  but he is certainly not the only one who deserves a lot of thanks.
>  So "Thank you" to everyone who answers questions on linux-raid.

You are very welcome.  I may just have to polish my kernel coding skills
to earn a place in a maintainership team.

Phil Turmel

Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)

[Sebastian Parschauer]

On 21.12.2015 07:10, NeilBrown wrote:
> 
> hi,
>  I became maintainer for md (Linux Software RAID) in late 2001 and on
>  the whole it has been fun and a valuable experience.  But I have been
>  losing interest in recent years (https://lwn.net/Articles/511073/) and
>  as was mentioned at the kernel summit, I would like to resign.  Some
>  years ago I managed to hand over nfsd to the excellent Bruce Fields,
>  but I do not seem to have the gift that Linus has of attracting
>  maintainers.  While there are a number of people who know quite a bit
>  about md and/or have contributed to development, there is no obvious
>  candidate for replacement maintainer - no one who has already been
>  doing significant parts of the maintainer role.
> 
>  So I have decided to fall back on the mechanism by which I ended up
>  being maintainer in the first place.  I will create a vacuum and hope
>  someone fills it (yes: I was sucked-in....).  So as of 1st February
>  2016 I will be resigning.
> 
>  At the kernel summit in October Linus talked about the value of
>  maintainership teams (https://lwn.net/Articles/662979/).  I think it
>  would be great if a (small) team formed to continue to oversee md
>  rather than just a single individual (or maybe the dm team could extend
>  to include md??).  If I had managed to be part of a team rather than
>  "going it alone" for so long, I might feel less tired of the whole
>  thing now.
> 
>  I don't see it as my place to appoint that team or any individuals, or
>  even to nominate any candidates.  A very important attribute of a
>  maintainer is that they need to care about the code and the subsystem
>  and I cannot tell other people to care (or even know if they do).  It
>  is really up to individuals to volunteer.  A few people have been
>  mentioned to me in earlier less-public conversations.  Any of them may
>  well be suitable, but I would rather they named themselves if
>  interested.
> 
>  So I'm hoping to get one or more volunteers to be maintainer:
>    - to gather and manage patches and outstanding issues,
>    - to review patches or get them reviewed
>    - to follow up bug reports and get them resolved
>    - to feed patches upstream, maybe directly to Linus,
>      maybe through some other maintainer, depending on what
>      relationships already exist or can be formed,
>    - to guide the longer term direction (saying "no" is important
>      sometimes),
>    - to care,
>  but also to be aware that maintainership takes real effort and time, as
>  does anything that is really worthwhile.
> 
>  This all applies to mdadm as well as md (except you would ultimately
>  *be* upstream for mdadm, not needing to send it anywhere).  Even if a
>  clear team doesn't form it would be great if different people
>  maintained mdadm and md.
> 
>  One part of the job that I have put a lot of time in to is following
>  the linux-raid@vger.kernel.org list and providing support.  This makes
>  people feel good about md and so more adventurous in using it.
>  Consequently I tend to hear about bugs and usability issues nice and
>  early (well before paying customers hit them in most cases) and that is
>  a big win.
>  In recent times I've been doing less of this and have been absolutely
>  thrilled that the gap has been more than filled by other very competent
>  community members.  Not developers particular but a number of md users
>  have been providing excellent support.  I'd particularly like to
>  high-light Phil Turmel who is very forthcoming with excellent advice,
>  but he is certainly not the only one who deserves a lot of thanks.
>  So "Thank you" to everyone who answers questions on linux-raid.
> 
>  This would be a good place for any future maintainer to hang out to
>  receive wisdom as well as to provide support.
> 
>  I will still be around.  I can certainly help out in some sort of
>  mentor role, and can probably be convinced to review patches and
>  comment on designs.  But I really want to head towards spending less
>  time on md (there are so many other interesting things to learn about).
> 
>  So: if anyone is interested - please announce yourself, ask questions
>  and start doing things.  I have no clear idea about how a transition
>  will happen.  That is really up to you (plural). Take the bull by the
>  horns and start *being* a maintainer(team).  I won't get in your way
>  and I'll help where I can.
> 
> Thanks,
> NeilBrown
> 
> P.S. I'm committed to continue to work with the raid5-journal effort
> From Facebook and the raid1-cluster effort from SUSE and the
> line-in-the-sand of 1st February won't affect my support for those.
> 


Hi Neil,

I've been maintaining the custom Linux kernels, custom MD and custom
mdadm since more than 4 years at ProfitBricks now. I've learned a lot
from you. Thank you very much for all the efforts! I will definitely
miss you in the MD/mdadm maintainer role. I especially like that you
care for all Linux distributions/kernel versions. That's what a real
upstream is about. I wish you all the best for the future!

Unfortunately my public activity has been very limited as company
interests always have priority. I would really like to help maintaining
MD/mdadm upstream but I would need an employer who pays me for that and
provides access to the required hardware.

In my leisure time I already maintain the upstream Linux memory scanner
project scanmem/GameConqueror.

Cheers,
Sebastian

Re: WANTED new maintainer for Linux/md (and mdadm)

[Shaohua Li]

On Mon, Dec 21, 2015 at 05:10:06PM +1100, NeilBrown wrote:
> 
> hi,
>  I became maintainer for md (Linux Software RAID) in late 2001 and on
>  the whole it has been fun and a valuable experience.  But I have been
>  losing interest in recent years (https://lwn.net/Articles/511073/) and
>  as was mentioned at the kernel summit, I would like to resign.  Some
>  years ago I managed to hand over nfsd to the excellent Bruce Fields,
>  but I do not seem to have the gift that Linus has of attracting
>  maintainers.  While there are a number of people who know quite a bit
>  about md and/or have contributed to development, there is no obvious
>  candidate for replacement maintainer - no one who has already been
>  doing significant parts of the maintainer role.
> 
>  So I have decided to fall back on the mechanism by which I ended up
>  being maintainer in the first place.  I will create a vacuum and hope
>  someone fills it (yes: I was sucked-in....).  So as of 1st February
>  2016 I will be resigning.
> 
>  At the kernel summit in October Linus talked about the value of
>  maintainership teams (https://lwn.net/Articles/662979/).  I think it
>  would be great if a (small) team formed to continue to oversee md
>  rather than just a single individual (or maybe the dm team could extend
>  to include md??).  If I had managed to be part of a team rather than
>  "going it alone" for so long, I might feel less tired of the whole
>  thing now.
> 
>  I don't see it as my place to appoint that team or any individuals, or
>  even to nominate any candidates.  A very important attribute of a
>  maintainer is that they need to care about the code and the subsystem
>  and I cannot tell other people to care (or even know if they do).  It
>  is really up to individuals to volunteer.  A few people have been
>  mentioned to me in earlier less-public conversations.  Any of them may
>  well be suitable, but I would rather they named themselves if
>  interested.
> 
>  So I'm hoping to get one or more volunteers to be maintainer:
>    - to gather and manage patches and outstanding issues,
>    - to review patches or get them reviewed
>    - to follow up bug reports and get them resolved
>    - to feed patches upstream, maybe directly to Linus,
>      maybe through some other maintainer, depending on what
>      relationships already exist or can be formed,
>    - to guide the longer term direction (saying "no" is important
>      sometimes),
>    - to care,
>  but also to be aware that maintainership takes real effort and time, as
>  does anything that is really worthwhile.
> 
>  This all applies to mdadm as well as md (except you would ultimately
>  *be* upstream for mdadm, not needing to send it anywhere).  Even if a
>  clear team doesn't form it would be great if different people
>  maintained mdadm and md.
> 
>  One part of the job that I have put a lot of time in to is following
>  the linux-raid@vger.kernel.org list and providing support.  This makes
>  people feel good about md and so more adventurous in using it.
>  Consequently I tend to hear about bugs and usability issues nice and
>  early (well before paying customers hit them in most cases) and that is
>  a big win.
>  In recent times I've been doing less of this and have been absolutely
>  thrilled that the gap has been more than filled by other very competent
>  community members.  Not developers particular but a number of md users
>  have been providing excellent support.  I'd particularly like to
>  high-light Phil Turmel who is very forthcoming with excellent advice,
>  but he is certainly not the only one who deserves a lot of thanks.
>  So "Thank you" to everyone who answers questions on linux-raid.
> 
>  This would be a good place for any future maintainer to hang out to
>  receive wisdom as well as to provide support.
> 
>  I will still be around.  I can certainly help out in some sort of
>  mentor role, and can probably be convinced to review patches and
>  comment on designs.  But I really want to head towards spending less
>  time on md (there are so many other interesting things to learn about).
> 
>  So: if anyone is interested - please announce yourself, ask questions
>  and start doing things.  I have no clear idea about how a transition
>  will happen.  That is really up to you (plural). Take the bull by the
>  horns and start *being* a maintainer(team).  I won't get in your way
>  and I'll help where I can.
> 
> Thanks,
> NeilBrown
> 
> P.S. I'm committed to continue to work with the raid5-journal effort
> From Facebook and the raid1-cluster effort from SUSE and the
> line-in-the-sand of 1st February won't affect my support for those.

Hi Neil,

Thanks for all the efforts! We will definitely miss you and fortunately you
won't completely quit from MD :). I'm very interested in helping maintain MD. I
have been working on MD for several years. My employer (facebook) supports me,
so I have time being a maintainer too.

Thanks,
Shaohua

Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)

[Brassow Jonathan]

Many thanks Neil for all the work you’ve done and the help you gave me while working on the DM/MD interactions bits.  I’m happy you are sticking around for the raid1-cluster and raid5-journal bits and I’m interested to see what comes out of those.

I know there are a number of folks around Red Hat who are capable and possibly interested to share the load.  They should be back from PTO soon and we’ll make sure they know about the opportunity.

thanks,
 brassow

> On Dec 21, 2015, at 12:10 AM, NeilBrown <neilb@suse.com> wrote:
> 
> 
> hi,
> I became maintainer for md (Linux Software RAID) in late 2001 and on
> the whole it has been fun and a valuable experience.  But I have been
> losing interest in recent years (https://lwn.net/Articles/511073/) and
> as was mentioned at the kernel summit, I would like to resign.  Some
> years ago I managed to hand over nfsd to the excellent Bruce Fields,
> but I do not seem to have the gift that Linus has of attracting
> maintainers.  While there are a number of people who know quite a bit
> about md and/or have contributed to development, there is no obvious
> candidate for replacement maintainer - no one who has already been
> doing significant parts of the maintainer role.
> 
> So I have decided to fall back on the mechanism by which I ended up
> being maintainer in the first place.  I will create a vacuum and hope
> someone fills it (yes: I was sucked-in....).  So as of 1st February
> 2016 I will be resigning.
> 
> At the kernel summit in October Linus talked about the value of
> maintainership teams (https://lwn.net/Articles/662979/).  I think it
> would be great if a (small) team formed to continue to oversee md
> rather than just a single individual (or maybe the dm team could extend
> to include md??).  If I had managed to be part of a team rather than
> "going it alone" for so long, I might feel less tired of the whole
> thing now.
> 
> I don't see it as my place to appoint that team or any individuals, or
> even to nominate any candidates.  A very important attribute of a
> maintainer is that they need to care about the code and the subsystem
> and I cannot tell other people to care (or even know if they do).  It
> is really up to individuals to volunteer.  A few people have been
> mentioned to me in earlier less-public conversations.  Any of them may
> well be suitable, but I would rather they named themselves if
> interested.
> 
> So I'm hoping to get one or more volunteers to be maintainer:
>   - to gather and manage patches and outstanding issues,
>   - to review patches or get them reviewed
>   - to follow up bug reports and get them resolved
>   - to feed patches upstream, maybe directly to Linus,
>     maybe through some other maintainer, depending on what
>     relationships already exist or can be formed,
>   - to guide the longer term direction (saying "no" is important
>     sometimes),
>   - to care,
> but also to be aware that maintainership takes real effort and time, as
> does anything that is really worthwhile.
> 
> This all applies to mdadm as well as md (except you would ultimately
> *be* upstream for mdadm, not needing to send it anywhere).  Even if a
> clear team doesn't form it would be great if different people
> maintained mdadm and md.
> 
> One part of the job that I have put a lot of time in to is following
> the linux-raid@vger.kernel.org list and providing support.  This makes
> people feel good about md and so more adventurous in using it.
> Consequently I tend to hear about bugs and usability issues nice and
> early (well before paying customers hit them in most cases) and that is
> a big win.
> In recent times I've been doing less of this and have been absolutely
> thrilled that the gap has been more than filled by other very competent
> community members.  Not developers particular but a number of md users
> have been providing excellent support.  I'd particularly like to
> high-light Phil Turmel who is very forthcoming with excellent advice,
> but he is certainly not the only one who deserves a lot of thanks.
> So "Thank you" to everyone who answers questions on linux-raid.
> 
> This would be a good place for any future maintainer to hang out to
> receive wisdom as well as to provide support.
> 
> I will still be around.  I can certainly help out in some sort of
> mentor role, and can probably be convinced to review patches and
> comment on designs.  But I really want to head towards spending less
> time on md (there are so many other interesting things to learn about).
> 
> So: if anyone is interested - please announce yourself, ask questions
> and start doing things.  I have no clear idea about how a transition
> will happen.  That is really up to you (plural). Take the bull by the
> horns and start *being* a maintainer(team).  I won't get in your way
> and I'll help where I can.
> 
> Thanks,
> NeilBrown
> 
> P.S. I'm committed to continue to work with the raid5-journal effort
> From Facebook and the raid1-cluster effort from SUSE and the
> line-in-the-sand of 1st February won't affect my support for those.
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel

Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)

[Jes Sorensen]

Brassow Jonathan <jbrassow@redhat.com> writes:
> Many thanks Neil for all the work you’ve done and the help you gave me
> while working on the DM/MD interactions bits.  I’m happy you are
> sticking around for the raid1-cluster and raid5-journal bits and I’m
> interested to see what comes out of those.
>
> I know there are a number of folks around Red Hat who are capable and
> possibly interested to share the load.  They should be back from PTO
> soon and we’ll make sure they know about the opportunity.

Thanks Neil!

I mentioned to Neil last year that I could probably be convinced,
bribed, shamed, into maintaining mdadm.

The kernel MD stack I think really needs a team to run it. There is just
too much internal knowledge sitting in Neil's head and I personally am a
little scared of taking on that. Shaohua Li would be a good candidate
for that team IMHO.

Cheers,
Jes


> thanks,
>  brassow
>
>> On Dec 21, 2015, at 12:10 AM, NeilBrown <neilb@suse.com> wrote:
>> 
>> 
>> hi,
>> I became maintainer for md (Linux Software RAID) in late 2001 and on
>> the whole it has been fun and a valuable experience.  But I have been
>> losing interest in recent years (https://lwn.net/Articles/511073/) and
>> as was mentioned at the kernel summit, I would like to resign.  Some
>> years ago I managed to hand over nfsd to the excellent Bruce Fields,
>> but I do not seem to have the gift that Linus has of attracting
>> maintainers.  While there are a number of people who know quite a bit
>> about md and/or have contributed to development, there is no obvious
>> candidate for replacement maintainer - no one who has already been
>> doing significant parts of the maintainer role.
>> 
>> So I have decided to fall back on the mechanism by which I ended up
>> being maintainer in the first place.  I will create a vacuum and hope
>> someone fills it (yes: I was sucked-in....).  So as of 1st February
>> 2016 I will be resigning.
>> 
>> At the kernel summit in October Linus talked about the value of
>> maintainership teams (https://lwn.net/Articles/662979/).  I think it
>> would be great if a (small) team formed to continue to oversee md
>> rather than just a single individual (or maybe the dm team could extend
>> to include md??).  If I had managed to be part of a team rather than
>> "going it alone" for so long, I might feel less tired of the whole
>> thing now.
>> 
>> I don't see it as my place to appoint that team or any individuals, or
>> even to nominate any candidates.  A very important attribute of a
>> maintainer is that they need to care about the code and the subsystem
>> and I cannot tell other people to care (or even know if they do).  It
>> is really up to individuals to volunteer.  A few people have been
>> mentioned to me in earlier less-public conversations.  Any of them may
>> well be suitable, but I would rather they named themselves if
>> interested.
>> 
>> So I'm hoping to get one or more volunteers to be maintainer:
>>   - to gather and manage patches and outstanding issues,
>>   - to review patches or get them reviewed
>>   - to follow up bug reports and get them resolved
>>   - to feed patches upstream, maybe directly to Linus,
>>     maybe through some other maintainer, depending on what
>>     relationships already exist or can be formed,
>>   - to guide the longer term direction (saying "no" is important
>>     sometimes),
>>   - to care,
>> but also to be aware that maintainership takes real effort and time, as
>> does anything that is really worthwhile.
>> 
>> This all applies to mdadm as well as md (except you would ultimately
>> *be* upstream for mdadm, not needing to send it anywhere).  Even if a
>> clear team doesn't form it would be great if different people
>> maintained mdadm and md.
>> 
>> One part of the job that I have put a lot of time in to is following
>> the linux-raid@vger.kernel.org list and providing support.  This makes
>> people feel good about md and so more adventurous in using it.
>> Consequently I tend to hear about bugs and usability issues nice and
>> early (well before paying customers hit them in most cases) and that is
>> a big win.
>> In recent times I've been doing less of this and have been absolutely
>> thrilled that the gap has been more than filled by other very competent
>> community members.  Not developers particular but a number of md users
>> have been providing excellent support.  I'd particularly like to
>> high-light Phil Turmel who is very forthcoming with excellent advice,
>> but he is certainly not the only one who deserves a lot of thanks.
>> So "Thank you" to everyone who answers questions on linux-raid.
>> 
>> This would be a good place for any future maintainer to hang out to
>> receive wisdom as well as to provide support.
>> 
>> I will still be around.  I can certainly help out in some sort of
>> mentor role, and can probably be convinced to review patches and
>> comment on designs.  But I really want to head towards spending less
>> time on md (there are so many other interesting things to learn about).
>> 
>> So: if anyone is interested - please announce yourself, ask questions
>> and start doing things.  I have no clear idea about how a transition
>> will happen.  That is really up to you (plural). Take the bull by the
>> horns and start *being* a maintainer(team).  I won't get in your way
>> and I'll help where I can.
>> 
>> Thanks,
>> NeilBrown
>> 
>> P.S. I'm committed to continue to work with the raid5-journal effort
>> From Facebook and the raid1-cluster effort from SUSE and the
>> line-in-the-sand of 1st February won't affect my support for those.
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)

[NeilBrown]

[-- Attachment #1: Type: text/plain, Size: 7112 bytes --]

On Thu, Jan 07 2016, Jes Sorensen wrote:

> Brassow Jonathan <jbrassow@redhat.com> writes:
>> Many thanks Neil for all the work you’ve done and the help you gave me
>> while working on the DM/MD interactions bits.  I’m happy you are
>> sticking around for the raid1-cluster and raid5-journal bits and I’m
>> interested to see what comes out of those.
>>
>> I know there are a number of folks around Red Hat who are capable and
>> possibly interested to share the load.  They should be back from PTO
>> soon and we’ll make sure they know about the opportunity.
>
> Thanks Neil!
>
> I mentioned to Neil last year that I could probably be convinced,
> bribed, shamed, into maintaining mdadm.

I realise that is somewhat tongue-in-cheek, but I am certainly not
looking for someone who needs to be convinced, bribed, or shamed.
I'm hoping for someone who will weigh the pros and cons, decide this is
a contribution they are willing (and maybe even eager) to make, and will
step up and do so.
And I suspect that behind that facade of reluctance, that is what you
are really offering.  Thanks.

I propose to make one last release of mdadm either next week or the last
week of January.  I plan to call it "3.4" in acknowledgment of the new
cluster and raid5-journal functionality.
If you were to take it from there, I would be grateful.

Thanks,
NeilBrown

>
> The kernel MD stack I think really needs a team to run it. There is just
> too much internal knowledge sitting in Neil's head and I personally am a
> little scared of taking on that. Shaohua Li would be a good candidate
> for that team IMHO.
>
> Cheers,
> Jes
>
>
>> thanks,
>>  brassow
>>
>>> On Dec 21, 2015, at 12:10 AM, NeilBrown <neilb@suse.com> wrote:
>>> 
>>> 
>>> hi,
>>> I became maintainer for md (Linux Software RAID) in late 2001 and on
>>> the whole it has been fun and a valuable experience.  But I have been
>>> losing interest in recent years (https://lwn.net/Articles/511073/) and
>>> as was mentioned at the kernel summit, I would like to resign.  Some
>>> years ago I managed to hand over nfsd to the excellent Bruce Fields,
>>> but I do not seem to have the gift that Linus has of attracting
>>> maintainers.  While there are a number of people who know quite a bit
>>> about md and/or have contributed to development, there is no obvious
>>> candidate for replacement maintainer - no one who has already been
>>> doing significant parts of the maintainer role.
>>> 
>>> So I have decided to fall back on the mechanism by which I ended up
>>> being maintainer in the first place.  I will create a vacuum and hope
>>> someone fills it (yes: I was sucked-in....).  So as of 1st February
>>> 2016 I will be resigning.
>>> 
>>> At the kernel summit in October Linus talked about the value of
>>> maintainership teams (https://lwn.net/Articles/662979/).  I think it
>>> would be great if a (small) team formed to continue to oversee md
>>> rather than just a single individual (or maybe the dm team could extend
>>> to include md??).  If I had managed to be part of a team rather than
>>> "going it alone" for so long, I might feel less tired of the whole
>>> thing now.
>>> 
>>> I don't see it as my place to appoint that team or any individuals, or
>>> even to nominate any candidates.  A very important attribute of a
>>> maintainer is that they need to care about the code and the subsystem
>>> and I cannot tell other people to care (or even know if they do).  It
>>> is really up to individuals to volunteer.  A few people have been
>>> mentioned to me in earlier less-public conversations.  Any of them may
>>> well be suitable, but I would rather they named themselves if
>>> interested.
>>> 
>>> So I'm hoping to get one or more volunteers to be maintainer:
>>>   - to gather and manage patches and outstanding issues,
>>>   - to review patches or get them reviewed
>>>   - to follow up bug reports and get them resolved
>>>   - to feed patches upstream, maybe directly to Linus,
>>>     maybe through some other maintainer, depending on what
>>>     relationships already exist or can be formed,
>>>   - to guide the longer term direction (saying "no" is important
>>>     sometimes),
>>>   - to care,
>>> but also to be aware that maintainership takes real effort and time, as
>>> does anything that is really worthwhile.
>>> 
>>> This all applies to mdadm as well as md (except you would ultimately
>>> *be* upstream for mdadm, not needing to send it anywhere).  Even if a
>>> clear team doesn't form it would be great if different people
>>> maintained mdadm and md.
>>> 
>>> One part of the job that I have put a lot of time in to is following
>>> the linux-raid@vger.kernel.org list and providing support.  This makes
>>> people feel good about md and so more adventurous in using it.
>>> Consequently I tend to hear about bugs and usability issues nice and
>>> early (well before paying customers hit them in most cases) and that is
>>> a big win.
>>> In recent times I've been doing less of this and have been absolutely
>>> thrilled that the gap has been more than filled by other very competent
>>> community members.  Not developers particular but a number of md users
>>> have been providing excellent support.  I'd particularly like to
>>> high-light Phil Turmel who is very forthcoming with excellent advice,
>>> but he is certainly not the only one who deserves a lot of thanks.
>>> So "Thank you" to everyone who answers questions on linux-raid.
>>> 
>>> This would be a good place for any future maintainer to hang out to
>>> receive wisdom as well as to provide support.
>>> 
>>> I will still be around.  I can certainly help out in some sort of
>>> mentor role, and can probably be convinced to review patches and
>>> comment on designs.  But I really want to head towards spending less
>>> time on md (there are so many other interesting things to learn about).
>>> 
>>> So: if anyone is interested - please announce yourself, ask questions
>>> and start doing things.  I have no clear idea about how a transition
>>> will happen.  That is really up to you (plural). Take the bull by the
>>> horns and start *being* a maintainer(team).  I won't get in your way
>>> and I'll help where I can.
>>> 
>>> Thanks,
>>> NeilBrown
>>> 
>>> P.S. I'm committed to continue to work with the raid5-journal effort
>>> From Facebook and the raid1-cluster effort from SUSE and the
>>> line-in-the-sand of 1st February won't affect my support for those.
>>> --
>>> dm-devel mailing list
>>> dm-devel@redhat.com
>>> https://www.redhat.com/mailman/listinfo/dm-devel
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Re: WANTED new maintainer for Linux/md (and mdadm)

[NeilBrown]

[-- Attachment #1: Type: text/plain, Size: 1712 bytes --]

On Tue, Jan 05 2016, Shaohua Li wrote:

>
> Hi Neil,
>
> Thanks for all the efforts! We will definitely miss you and fortunately you
> won't completely quit from MD :). I'm very interested in helping maintain MD. I
> have been working on MD for several years. My employer (facebook) supports me,
> so I have time being a maintainer too.

Hi Shaohua,
 as you are one of the more active developers of MD at the moment, this
 probably affects you more than many others and your willingness to
 contribute more is certainly welcome.

 The first question is where do you send your patches to get the
 appropriate review and upstream acceptance.  Alasdair or Mike (DM),
 Jens (Block), Andrew Morton (anything) and Linus (everything) are all
 defensible choices for upstreaming (I've submitted through Andrew in
 the past, but through Linus exclusively once I figured out git).  That
 is really something you and they would need to negotiate though.

 I plan to submit a pull request to Linus for the 4.5 merge window
 and then stop queuing patches.  I will still review your journaling
 patches but will likely reply with "Reviewed-by" rather than "applied,
 thanks".
 My intention is to only look at other patches if they already have an
 independent "Reviewed-by", but it remains to be seen how strongly I
 stick to that intention.

 If you have specific questions about anything (md internals, git
 work-flows, whatever) do feel free to ask.
 I am trying to write some comprehensive documentation on the internals
 of MD - though it is slow going.  Once that is mostly done I'll make it
 available and it should at least serve as a good structure in which to
 place answers to further questions.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Re: [dm-devel] WANTED new maintainer for Linux/md (and mdadm)

[Jes Sorensen]

NeilBrown <neilb@suse.de> writes:
> On Thu, Jan 07 2016, Jes Sorensen wrote:
>
>> Brassow Jonathan <jbrassow@redhat.com> writes:
>>> Many thanks Neil for all the work you’ve done and the help you gave me
>>> while working on the DM/MD interactions bits.  I’m happy you are
>>> sticking around for the raid1-cluster and raid5-journal bits and I’m
>>> interested to see what comes out of those.
>>>
>>> I know there are a number of folks around Red Hat who are capable and
>>> possibly interested to share the load.  They should be back from PTO
>>> soon and we’ll make sure they know about the opportunity.
>>
>> Thanks Neil!
>>
>> I mentioned to Neil last year that I could probably be convinced,
>> bribed, shamed, into maintaining mdadm.
>
> I realise that is somewhat tongue-in-cheek, but I am certainly not
> looking for someone who needs to be convinced, bribed, or shamed.  I'm
> hoping for someone who will weigh the pros and cons, decide this is a
> contribution they are willing (and maybe even eager) to make, and will
> step up and do so.  And I suspect that behind that facade of
> reluctance, that is what you are really offering.  Thanks.
>
> I propose to make one last release of mdadm either next week or the last
> week of January.  I plan to call it "3.4" in acknowledgment of the new
> cluster and raid5-journal functionality.
> If you were to take it from there, I would be grateful.

Hi Neil,

I wouldn't have offered to take on mdadm if I hadn't meant it, even if I
like making the wording sound silly :) I feel I can do a decent job at
it and the task should be reasonable in scope. If someone is dying to
take it on, I am not going to stand in their way, but I feel mdadm needs
a maintainer and it's a worthy effort.

We'll have to figure out the logistics, and I'd like to coordinate with
who takes on drivers/md

Cheers,
Jes

>
> Thanks,
> NeilBrown
>
>>
>> The kernel MD stack I think really needs a team to run it. There is just
>> too much internal knowledge sitting in Neil's head and I personally am a
>> little scared of taking on that. Shaohua Li would be a good candidate
>> for that team IMHO.
>>
>> Cheers,
>> Jes
>>
>>
>>> thanks,
>>>  brassow
>>>
>>>> On Dec 21, 2015, at 12:10 AM, NeilBrown <neilb@suse.com> wrote:
>>>> 
>>>> 
>>>> hi,
>>>> I became maintainer for md (Linux Software RAID) in late 2001 and on
>>>> the whole it has been fun and a valuable experience.  But I have been
>>>> losing interest in recent years (https://lwn.net/Articles/511073/) and
>>>> as was mentioned at the kernel summit, I would like to resign.  Some
>>>> years ago I managed to hand over nfsd to the excellent Bruce Fields,
>>>> but I do not seem to have the gift that Linus has of attracting
>>>> maintainers.  While there are a number of people who know quite a bit
>>>> about md and/or have contributed to development, there is no obvious
>>>> candidate for replacement maintainer - no one who has already been
>>>> doing significant parts of the maintainer role.
>>>> 
>>>> So I have decided to fall back on the mechanism by which I ended up
>>>> being maintainer in the first place.  I will create a vacuum and hope
>>>> someone fills it (yes: I was sucked-in....).  So as of 1st February
>>>> 2016 I will be resigning.
>>>> 
>>>> At the kernel summit in October Linus talked about the value of
>>>> maintainership teams (https://lwn.net/Articles/662979/).  I think it
>>>> would be great if a (small) team formed to continue to oversee md
>>>> rather than just a single individual (or maybe the dm team could extend
>>>> to include md??).  If I had managed to be part of a team rather than
>>>> "going it alone" for so long, I might feel less tired of the whole
>>>> thing now.
>>>> 
>>>> I don't see it as my place to appoint that team or any individuals, or
>>>> even to nominate any candidates.  A very important attribute of a
>>>> maintainer is that they need to care about the code and the subsystem
>>>> and I cannot tell other people to care (or even know if they do).  It
>>>> is really up to individuals to volunteer.  A few people have been
>>>> mentioned to me in earlier less-public conversations.  Any of them may
>>>> well be suitable, but I would rather they named themselves if
>>>> interested.
>>>> 
>>>> So I'm hoping to get one or more volunteers to be maintainer:
>>>>   - to gather and manage patches and outstanding issues,
>>>>   - to review patches or get them reviewed
>>>>   - to follow up bug reports and get them resolved
>>>>   - to feed patches upstream, maybe directly to Linus,
>>>>     maybe through some other maintainer, depending on what
>>>>     relationships already exist or can be formed,
>>>>   - to guide the longer term direction (saying "no" is important
>>>>     sometimes),
>>>>   - to care,
>>>> but also to be aware that maintainership takes real effort and time, as
>>>> does anything that is really worthwhile.
>>>> 
>>>> This all applies to mdadm as well as md (except you would ultimately
>>>> *be* upstream for mdadm, not needing to send it anywhere).  Even if a
>>>> clear team doesn't form it would be great if different people
>>>> maintained mdadm and md.
>>>> 
>>>> One part of the job that I have put a lot of time in to is following
>>>> the linux-raid@vger.kernel.org list and providing support.  This makes
>>>> people feel good about md and so more adventurous in using it.
>>>> Consequently I tend to hear about bugs and usability issues nice and
>>>> early (well before paying customers hit them in most cases) and that is
>>>> a big win.
>>>> In recent times I've been doing less of this and have been absolutely
>>>> thrilled that the gap has been more than filled by other very competent
>>>> community members.  Not developers particular but a number of md users
>>>> have been providing excellent support.  I'd particularly like to
>>>> high-light Phil Turmel who is very forthcoming with excellent advice,
>>>> but he is certainly not the only one who deserves a lot of thanks.
>>>> So "Thank you" to everyone who answers questions on linux-raid.
>>>> 
>>>> This would be a good place for any future maintainer to hang out to
>>>> receive wisdom as well as to provide support.
>>>> 
>>>> I will still be around.  I can certainly help out in some sort of
>>>> mentor role, and can probably be convinced to review patches and
>>>> comment on designs.  But I really want to head towards spending less
>>>> time on md (there are so many other interesting things to learn about).
>>>> 
>>>> So: if anyone is interested - please announce yourself, ask questions
>>>> and start doing things.  I have no clear idea about how a transition
>>>> will happen.  That is really up to you (plural). Take the bull by the
>>>> horns and start *being* a maintainer(team).  I won't get in your way
>>>> and I'll help where I can.
>>>> 
>>>> Thanks,
>>>> NeilBrown
>>>> 
>>>> P.S. I'm committed to continue to work with the raid5-journal effort
>>>> From Facebook and the raid1-cluster effort from SUSE and the
>>>> line-in-the-sand of 1st February won't affect my support for those.
>>>> --
>>>> dm-devel mailing list
>>>> dm-devel@redhat.com
>>>> https://www.redhat.com/mailman/listinfo/dm-devel
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: WANTED new maintainer for Linux/md (and mdadm)

[Artur Paszkiewicz]

On 12/21/2015 07:10 AM, NeilBrown wrote:
> 
> hi,
>  I became maintainer for md (Linux Software RAID) in late 2001 and on
>  the whole it has been fun and a valuable experience.  But I have been
>  losing interest in recent years (https://lwn.net/Articles/511073/) and
>  as was mentioned at the kernel summit, I would like to resign.  Some
>  years ago I managed to hand over nfsd to the excellent Bruce Fields,
>  but I do not seem to have the gift that Linus has of attracting
>  maintainers.  While there are a number of people who know quite a bit
>  about md and/or have contributed to development, there is no obvious
>  candidate for replacement maintainer - no one who has already been
>  doing significant parts of the maintainer role.
> 
>  So I have decided to fall back on the mechanism by which I ended up
>  being maintainer in the first place.  I will create a vacuum and hope
>  someone fills it (yes: I was sucked-in....).  So as of 1st February
>  2016 I will be resigning.
> 
>  At the kernel summit in October Linus talked about the value of
>  maintainership teams (https://lwn.net/Articles/662979/).  I think it
>  would be great if a (small) team formed to continue to oversee md
>  rather than just a single individual (or maybe the dm team could extend
>  to include md??).  If I had managed to be part of a team rather than
>  "going it alone" for so long, I might feel less tired of the whole
>  thing now.
> 
>  I don't see it as my place to appoint that team or any individuals, or
>  even to nominate any candidates.  A very important attribute of a
>  maintainer is that they need to care about the code and the subsystem
>  and I cannot tell other people to care (or even know if they do).  It
>  is really up to individuals to volunteer.  A few people have been
>  mentioned to me in earlier less-public conversations.  Any of them may
>  well be suitable, but I would rather they named themselves if
>  interested.
> 
>  So I'm hoping to get one or more volunteers to be maintainer:
>    - to gather and manage patches and outstanding issues,
>    - to review patches or get them reviewed
>    - to follow up bug reports and get them resolved
>    - to feed patches upstream, maybe directly to Linus,
>      maybe through some other maintainer, depending on what
>      relationships already exist or can be formed,
>    - to guide the longer term direction (saying "no" is important
>      sometimes),
>    - to care,
>  but also to be aware that maintainership takes real effort and time, as
>  does anything that is really worthwhile.
> 
>  This all applies to mdadm as well as md (except you would ultimately
>  *be* upstream for mdadm, not needing to send it anywhere).  Even if a
>  clear team doesn't form it would be great if different people
>  maintained mdadm and md.
> 
>  One part of the job that I have put a lot of time in to is following
>  the linux-raid@vger.kernel.org list and providing support.  This makes
>  people feel good about md and so more adventurous in using it.
>  Consequently I tend to hear about bugs and usability issues nice and
>  early (well before paying customers hit them in most cases) and that is
>  a big win.
>  In recent times I've been doing less of this and have been absolutely
>  thrilled that the gap has been more than filled by other very competent
>  community members.  Not developers particular but a number of md users
>  have been providing excellent support.  I'd particularly like to
>  high-light Phil Turmel who is very forthcoming with excellent advice,
>  but he is certainly not the only one who deserves a lot of thanks.
>  So "Thank you" to everyone who answers questions on linux-raid.
> 
>  This would be a good place for any future maintainer to hang out to
>  receive wisdom as well as to provide support.
> 
>  I will still be around.  I can certainly help out in some sort of
>  mentor role, and can probably be convinced to review patches and
>  comment on designs.  But I really want to head towards spending less
>  time on md (there are so many other interesting things to learn about).
> 
>  So: if anyone is interested - please announce yourself, ask questions
>  and start doing things.  I have no clear idea about how a transition
>  will happen.  That is really up to you (plural). Take the bull by the
>  horns and start *being* a maintainer(team).  I won't get in your way
>  and I'll help where I can.
> 
> Thanks,
> NeilBrown
> 
> P.S. I'm committed to continue to work with the raid5-journal effort
> From Facebook and the raid1-cluster effort from SUSE and the
> line-in-the-sand of 1st February won't affect my support for those.
> 

Hi Neil,

Thank you for your work and time spent on maintaining MD/mdadm. I would also
like to offer help for the emerging maintainership team. I've been working with
MD RAID for more than 4 years, mostly testing and developing the IMSM-related
parts on behalf of my employer - Intel. I realize that I was not very visible
on this mailing list, but I think I have a pretty good knowledge about mdadm
and the MD drivers. Now I have Intel's approval to take on maintaining MD RAID
as part of my job, not focusing primarily on IMSM. I definitely feel more
confident with maintaining mdadm, but I would certainly like to learn more
about the kernel MD stack and help with it as much as I can.

Regards,
Artur

Re: WANTED new maintainer for Linux/md (and mdadm)

[NeilBrown]

[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]

On Wed, Jan 20 2016, Artur Paszkiewicz wrote:
>
> Hi Neil,
>
> Thank you for your work and time spent on maintaining MD/mdadm. I would also
> like to offer help for the emerging maintainership team. I've been working with
> MD RAID for more than 4 years, mostly testing and developing the IMSM-related
> parts on behalf of my employer - Intel. I realize that I was not very visible
> on this mailing list, but I think I have a pretty good knowledge about mdadm
> and the MD drivers. Now I have Intel's approval to take on maintaining MD RAID
> as part of my job, not focusing primarily on IMSM. I definitely feel more
> confident with maintaining mdadm, but I would certainly like to learn more
> about the kernel MD stack and help with it as much as I can.

Hi Arthur,
 thanks for all your IMSM work over the years!  It is great that you can
 continue contributing and do so more broadly.

 For the moment Jes Serensen will be co-ordinating mdadm (once I make a
 release ... tomorrow?) and Shaohua Li will be looking after the
 kernel/md side.  I'm sure there is plenty of room for you too though.
 Only one person (at a time) can queue patches, but several can
 collaborate at development and support and bug fixing and testing and
 ....
 I suggest you find ways to co-ordinate with them.

 This:
     https://bugzilla.kernel.org/show_bug.cgi?id=108741
 is currently most important in my mind, but there are other things to
 do.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

Re: WANTED new maintainer for Linux/md (and mdadm)

[Jes Sorensen]

NeilBrown <neilb@suse.com> writes:
> On Wed, Jan 20 2016, Artur Paszkiewicz wrote:
>>
>> Hi Neil,
>>
>> Thank you for your work and time spent on maintaining MD/mdadm. I would also
>> like to offer help for the emerging maintainership team. I've been
>> working with
>> MD RAID for more than 4 years, mostly testing and developing the IMSM-related
>> parts on behalf of my employer - Intel. I realize that I was not very visible
>> on this mailing list, but I think I have a pretty good knowledge about mdadm
>> and the MD drivers. Now I have Intel's approval to take on maintaining MD RAID
>> as part of my job, not focusing primarily on IMSM. I definitely feel more
>> confident with maintaining mdadm, but I would certainly like to learn more
>> about the kernel MD stack and help with it as much as I can.
>
> Hi Arthur,
>  thanks for all your IMSM work over the years!  It is great that you can
>  continue contributing and do so more broadly.
>
>  For the moment Jes Serensen will be co-ordinating mdadm (once I make a
>  release ... tomorrow?) and Shaohua Li will be looking after the
>  kernel/md side.  I'm sure there is plenty of room for you too though.
>  Only one person (at a time) can queue patches, but several can
>  collaborate at development and support and bug fixing and testing and
>  ....
>  I suggest you find ways to co-ordinate with them.
>
>  This:
>      https://bugzilla.kernel.org/show_bug.cgi?id=108741
>  is currently most important in my mind, but there are other things to
>  do.

Hi Arthur,

I have setup a git repository for mdadm here:
git://git.kernel.org/pub/scm/utils/mdadm/mdadm.git

I'll be relying heavily on your contributions in managing this now that
Neil is leaving it to us. I'll do my best to maintain it in a similar
manner to Neil, albeit I am probably going to screw up a lot more often.

Please fire away those patches and do not be afraid to yell at me if I
get something wrong!

Cheers,
Jes