On Tue, May 9, 2017 at 8:21 PM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote: > People who respond on gluster-users do this already. Github issues is a > better tool to do this (Again IMHO). It is a bit easier to know what > questions are still open to be answered with github. Even after multiple > responses on gluster-users mail you won't be sure if it is answered or not, > so one has to go through the responses. Where as on github we can close it > once answered. So these kinds of things are the reason for asking this. Even with Github Issues, Gluster will not see a reduction of traffic to -users/-devel asking questions about the releases. What will happen for a (short?) while is that the project will have two inbound avenues to look for questions and respond to them. Over a period of time, if extreme focus and diligence is adopted, the traffic on mailing list *might* move over to Github issues. There are obvious advantages to using Issues. But there are also a small number of must-do things to manage this approach. -- sankarshan mukhopadhyay <https://about.me/sankarshan.mukhopadhyay> _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
