<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, 23 Aug 2019, 9:13 Amar Tumballi <<a href="mailto:amarts@gmail.com">amarts@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi developers,<div><br></div><div>With this email, I want to understand what is the general feeling around this topic.</div><div><br></div><div>We from gluster org (in <a href="http://github.com/gluster" target="_blank" rel="noreferrer">github.com/gluster</a>) have many projects which follow complete github workflow, where as there are few, specially the main one 'glusterfs', which uses 'Gerrit'.</div><div><br></div><div>While this has worked all these years, currently, there is a huge set of brain-share on github workflow as many other top projects, and similar projects use only github as the place to develop, track and run tests etc. As it is possible to have all of the tools required for this project in github itself (code, PR, issues, CI/CD, docs), lets look at how we are structured today:</div><div><br></div><div>Gerrit - glusterfs code + Review system</div><div>Bugzilla - For bugs</div><div>Github - For feature requests</div><div>Trello - (not very much used) for tracking project development.</div><div>CI/CD - CentOS-ci / Jenkins, etc but maintained from different repo.</div><div>Docs - glusterdocs - different repo.</div><div>Metrics - Nothing (other than github itself tracking contributors).</div><div><br></div><div>While it may cause a minor glitch for many long time developers who are used to the flow, moving to github would bring all these in single place, makes getting new users easy, and uniform development practices for all gluster org repositories.</div><div><br></div><div>As it is just the proposal, I would like to hear people's thought on this, and conclude on this another month, so by glusterfs-8 development time, we are clear about this.</div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I don't like mixed mode, but I also dislike Github's code review tools, so I'd like to remind the option of using <a href="http://gerrithub.io/">http://gerrithub.io/</a> for code review. </div><div dir="auto">Other than that, I'm in favor of moving over. </div><div dir="auto">Y. </div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>Can we decide on this before September 30th? Please voice your concerns.</div><div><br></div><div>Regards,</div><div>Amar</div><div><br></div><div><br></div><div><br></div></div>
_______________________________________________<br>
<br>
Community Meeting Calendar:<br>
<br>
APAC Schedule -<br>
Every 2nd and 4th Tuesday at 11:30 AM IST<br>
Bridge: <a href="https://bluejeans.com/836554017" rel="noreferrer noreferrer" target="_blank">https://bluejeans.com/836554017</a><br>
<br>
NA/EMEA Schedule -<br>
Every 1st and 3rd Tuesday at 01:00 PM EDT<br>
Bridge: <a href="https://bluejeans.com/486278655" rel="noreferrer noreferrer" target="_blank">https://bluejeans.com/486278655</a><br>
<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank" rel="noreferrer">Gluster-devel@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-devel</a><br>
<br>
</blockquote></div></div></div>