Bug 1456349 - Request for a new GitHub repository called "integration"
Summary: Request for a new GitHub repository called "integration"
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2017-05-29 07:44 UTC by Niels de Vos
Modified: 2017-06-04 04:48 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-06-04 04:48:16 UTC
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:

Attachments (Terms of Use)

Description Niels de Vos 2017-05-29 07:44:28 UTC
We would like to have a new GitHub repository called "integration" that be used as landing repository for the "Gluster Experience & Integration for Developers" (the people behind integration@gluster.org). By using our own repository, we can use the GitHub project planning instead of our current Trello board. This will make the work that is done for Gluster integrations with other projects more visible in the community.

Contributions will be sent through Pull Requests (not Gerrit), so that it is easier for non-Gluster developers to send their scripts and tools.

Please make Sahina and me an admin (usernames "sabose" and "nixpanic") of the repository, so that we can approve and merge Pull Requests and add other maintainers (permissions are needed for the project management part).

Comment 1 Shyamsundar 2017-05-29 14:17:46 UTC
I have only one comment: Please make sure your planning is aptly reflected in the glusterfs "focus area" planning project as well, i.e have those lanes populated as well as your own project, reflecting work done/tobe done on glusterfs. Instead of pointing to another repo to the users community for (say) gfapi enhancements planned and such.

Comment 2 Nigel Babu 2017-06-04 04:48:16 UTC
This is done.

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