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

Vijay Bellur vbellur at redhat.com
Wed Jun 24 10:54:51 UTC 2015

On Wednesday 24 June 2015 01:06 AM, Venky Shankar wrote:
> 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.

If we think that something is not ready to be merged, so let it be. We 
don't need to merge anything till the point that we think is good to be 
in the repository. non critical patches like the ones related to logging 
cannot be a blocker for any release.


More information about the maintainers mailing list