[Gluster-Maintainers] Community Transparency [Was: Responsibilities and expectations of our maintainers]

Venky Shankar vshankar at redhat.com
Wed Jun 24 05:06:30 UTC 2015

On 06/24/2015 10:09 AM, Krishnan Parthasarathi wrote:
>> Currently, we need more attention to the way of working, in and with,
>> the community and see how to increase the outreach of all the work we
>> are doing, else we may induce estrangement in this space.
> Yes. We could improve our engagement during design proposals. Oftentimes, there
> is an announcement style mail and then the commit.

..and more hangouts? Something like ceph developer summit (over 
hagnouts) would be good to have.

> We should improve the way we target features for a release. We must adopt a
> merge-window style of development (e.g linux-kernel). Jeff had some thoughts around
> this. Time shouldn't be an excuse for hurrying up features into a release.

Exactly. Something that's going on _now_ with the logging patches.

> More importantly, maintainers must be empowered to say _no_, when design/code
> submissions don't adhere to set expectations. Thoughts?
> _______________________________________________
> maintainers mailing list
> maintainers at gluster.org
> http://www.gluster.org/mailman/listinfo/maintainers

More information about the maintainers mailing list