Hello! On Tue 16-04-24 14:04:14, Josef Bacik wrote: > I would like to propose we organize ourselves more akin to the other large > subsystems. We are one of the few where everybody sends their own PR to Linus, > so oftentimes the first time we're testing eachothers code is when we all rebase > our respective trees onto -rc1. I think we could benefit from getting more > organized amongst ourselves, having a single tree we all flow into, and then > have that tree flow into Linus. > > I'm also not a fan of single maintainers in general, much less for this large of > an undertaking. I would also propose that we have a maintainership group where > we rotate the responsibilities of the mechanics of running a tree like this. > I'm nothing if not unreliable so I wouldn't be part of this group per se, but I > don't think we should just make Christian do it. This would be a big job, and > it would need to be shared. > > I would also propose that along with this single tree and group maintainership > we organize some guidelines about the above problems and all collectively agree > on how we're going to address them. Having clear guidelines for adding new file > systems, clear guidelines for removing them. Giving developers the ability to > make big API changes outside of the individual file systems trees to make it > easier to get things merged instead of having to base against 4 or 5 different > trees. Develop some guidelines about how we want patches to look, how we want > testing to be done, etc. so people can move through our different communities > and not have drastically different experiences. > > This is a massive proposal, and not one that we're going to be able to nail down > and implement quickly or easily. But I think in the long term it'll make > working in our community simpler, more predictable, and less frustrating for > everybody. Thanks, I think this is good discussion for the FS track. I'd be certainly interested in this. Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
