Mike Christie wrote: [ .. ]
We really need to change how dm-multipath development works IMHO. Alasdair is just too overworked. It is not fair to him to have so much work piled on top of him and not fair to the community to have problems like this sit around for so long.
[ .. ]
With Alasdair having to maintain every driver that dm handles and those drivers increasing in complexity the work load is too large for one person and this makes coordination with other subsystems impossible. This is a large problem, when for something like dm-multipath it needs help from the block layer, and low levels like scsi. We really need a system like in the scsi layer where there are driver maintainers and then one core maintainer of the subsystem. The core maintainer has final (well ok community has final say I guess) say but trusts the low level driver maintainers to some extent. The low level driver maintainers still have to post patches for review to the community and maintainer but the core maintainer does not have to do a line by line review of the dm target module and learn all the lower level details of the sub-subsytem/lld/dm target module/transport/spec unless it affects dm core or it is a suspicious patch.
Totally agree. Of course, Alasdairs vote's the one that counts ... Cheers, Hannes -- Dr. Hannes Reinecke hare@xxxxxxx SuSE Linux Products GmbH S390 & zSeries Maxfeldstraße 5 +49 911 74053 688 90409 Nürnberg http://www.suse.de -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
