Bug 1542241 - New repo for gluster-subvol
Summary: New repo for gluster-subvol
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-05 21:45 UTC by John Strunk
Modified: 2018-02-06 16:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-06 16:18:02 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)

Description John Strunk 2018-02-05 21:45:31 UTC
I currently maintain the gluster-subvol repo in my personal account: https://github.com/JohnStrunk/gluster-subvol

While this code has been created to service a very specific container storage use-case, it may be a useful starting point for others that have a need for large numbers of PVs in an openshift/kubernetes environment.

At Amar's suggestion, I propose moving this code under the gluster org so that others may more easily find, use, and contribute to the code.

Initial maintainer list: @JohnStrunk, @ShyamsundarR

Note:
- Licensing: This code is Apache-2.0. While it could potentially be changed to GPL, Apache is the standard license used for kubernetes code.
- There is a derivative being maintained by me in the OpenShift org for openshift.io, but will remain downstream of this repo
- I'm open to suggestions on how to make the repo transition... I can PR against the new repo or we could try and migrate my existing one.

Comment 1 Nigel Babu 2018-02-06 01:40:42 UTC
The easiest way is to transfer it to me (@nigelbabu) and I'll transfer it over to the gluster organization.

Comment 2 John Strunk 2018-02-06 15:32:36 UTC
Transfer to nigelbabu initiated.

Comment 3 Nigel Babu 2018-02-06 16:18:02 UTC
Transfer to gluster org complete. I've created a team that you both have maintainer access to and the team grants admin access to the repo.


Note You need to log in before you can comment on or make changes to this bug.