Bug 1608684

Summary:	Change glusto ownership to reflect current reality
Product:	[Community] GlusterFS	Reporter:	Nigel Babu <nigelb>
Component:	tests	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:15:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nigel Babu 2018-07-26 07:19:21 UTC

Currently the bulk of the work in Glusto is being done by Vijay and Akarsha. Therefore, promoting them to peers. I was only a maintainer as a stand-in until new maintainers were ready to take over. I believe they are now ready, so I'm moving back to peer.

Shwetha has moved from working on Gluster. I have checked with her to confirm and remove her from peer status.

Comment 1 Worker Ant 2018-07-26 07:35:26 UTC

REVIEW: https://review.gluster.org/20566 (maintainers: change in glusto ownership) posted (#1) for review on master by Nigel Babu

Comment 2 Worker Ant 2018-07-26 08:45:57 UTC

COMMIT: https://review.gluster.org/20566 committed in master by "Nigel Babu" <nigelb> with a commit message- maintainers: change in glusto ownership

As the project has matured, Vijay and Akarsha have stepped up
significantly. Nigel is stepping down to peer now that there are capable
people who will be actively focusing on Glusto.

Shwetha is no longer actively contributing and has therefore agreed to
step down from peer.

Change-Id: I089eb02857d2ea353e811cb8bdf71edda96fa041
Fixes: bz#1608684

Comment 3 Shyamsundar 2018-10-23 15:15:30 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/