Re: [Gluster-devel] Questions on github

[Pranith Kumar Karampuri]

On Tue, May 9, 2017 at 9:01 PM, Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:

> On Tue, May 9, 2017 at 8:50 PM, Niels de Vos  wrote:
>
> [much snipping]
>
> > A but related to this, but is Stack Overflow not *the* place to ask and
> > answer questions? There even is a "glusterfs" tag, and questions and
> > answers can be marked even better than with GitHub (imho):
> >
> > https://stackoverflow.com/questions/tagged/glusterfs
> >
>
> Alright. The intended outcome (from how I comprehend this conversation
> thread) is that developers/maintainers desire to respond more
> (quickly/efficiently) to queries from users in the community. The way
> this outcome is achieved is when the
> developers/maintainers/those-who-know respond more often. The tooling
> or, medium is not what is the crucial part here. However, it becomes
> critical when there are far too many of avenues and too little
> attention on a regular basis. *That* is a far from ideal situation.
>

Yeah, if maintainers are expected to be active on github, then answering
questions which are right there is just a step away.


>
> --
> sankarshan mukhopadhyay
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Sankarshan Mukhopadhyay]

On Tue, May 9, 2017 at 8:50 PM, Niels de Vos  wrote:

[much snipping]

> A but related to this, but is Stack Overflow not *the* place to ask and
> answer questions? There even is a "glusterfs" tag, and questions and
> answers can be marked even better than with GitHub (imho):
>
> https://stackoverflow.com/questions/tagged/glusterfs
>

Alright. The intended outcome (from how I comprehend this conversation
thread) is that developers/maintainers desire to respond more
(quickly/efficiently) to queries from users in the community. The way
this outcome is achieved is when the
developers/maintainers/those-who-know respond more often. The tooling
or, medium is not what is the crucial part here. However, it becomes
critical when there are far too many of avenues and too little
attention on a regular basis. *That* is a far from ideal situation.

-- 
sankarshan mukhopadhyay

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Shyam]

On 05/09/2017 10:51 AM, Pranith Kumar Karampuri wrote:



On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay
> wrote:

On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri
> wrote:
>
>
> On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay
> > wrote:
>>
>> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi > wrote:
>> > I personally prefer github questions than mailing list, because a valid
>> > question can later become a reason for a new feature. Also, as you 
said,
>> > we
>> > can 'assignee' a question and if we start with bug triage we can also
>> > make
>> > sure at least we respond to questions which is pending.
>>
>> Is the on-going discussion in this thread about using
>> > as a method to have
>> questions and responses from the community?
>
>
> yeah, this is something users have started doing. It seems better than 
mail
> (at least to me).
>

There is a trend of projects who are moving to Github Issues as a
medium/platform for responding to queries. As Amar mentions earlier in
the thread and Shyam implies - this requires constant (ie. daily)
vigil and attention. If those are in place, it is a practical move.


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.

Shyam,
  I started being more active on github because of the user
questions. So may be different people take different paths to be more
active on github.com/gluster . Some people
may not be as active on github even after we wait for a long time just
like in gluster-users so may be we should start using it for questions
sooner? Thoughts? It will only encourage more developers to be active on
github.


I want *maintainers* to be fully active on github issues for features, 
and also to maintain the project boards for the focus areas and 
respective components. Further (as others have stated) we need triage 
setup for github. Once such action is seen and executed, moving to 
github becomes more real for other purposes.


The original intention was to move to github for bugs as well, if you 
recollect. There was always a question about ML vs github for the same, 
yes github is more useful, but to repeat, let's get better at managing 
feature, component, focus area and release scope via github and then 
take it to a larger group.


Currently disrupting the users ML and asking them to move to github 
issues (in addition to the ML?), will create noise for what we intend to 
achieve with github projects and issues. If we can handle what we 
started out with better over time, then we can take on the additional 
noise and handle the same, till then we may just set ourselves up for 
failure.




___
Gluster-devel mailing list
Gluster-devel@gluster.org 
http://lists.gluster.org/mailman/listinfo/gluster-devel





--
Pranith


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Niels de Vos]

On Tue, May 09, 2017 at 08:21:54PM +0530, Pranith Kumar Karampuri wrote:
> On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay <
> sankarshan.mukhopadh...@gmail.com> wrote:
> 
> > On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri
> >  wrote:
> > >
> > >
> > > On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay
> > >  wrote:
> > >>
> > >> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi 
> > wrote:
> > >> > I personally prefer github questions than mailing list, because a
> > valid
> > >> > question can later become a reason for a new feature. Also, as you
> > said,
> > >> > we
> > >> > can 'assignee' a question and if we start with bug triage we can also
> > >> > make
> > >> > sure at least we respond to questions which is pending.
> > >>
> > >> Is the on-going discussion in this thread about using
> > >>  as a method to have
> > >> questions and responses from the community?
> > >
> > >
> > > yeah, this is something users have started doing. It seems better than
> > mail
> > > (at least to me).
> > >
> >
> > There is a trend of projects who are moving to Github Issues as a
> > medium/platform for responding to queries. As Amar mentions earlier in
> > the thread and Shyam implies - this requires constant (ie. daily)
> > vigil and attention. If those are in place, it is a practical move.
> >
> 
> 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.
> 
> Shyam,
>   I started being more active on github because of the user questions.
> So may be different people take different paths to be more active on
> github.com/gluster. Some people may not be as active on github even after
> we wait for a long time just like in gluster-users so may be we should
> start using it for questions sooner? Thoughts? It will only encourage more
> developers to be active on github.

A but related to this, but is Stack Overflow not *the* place to ask and
answer questions? There even is a "glusterfs" tag, and questions and
answers can be marked even better than with GitHub (imho):

https://stackoverflow.com/questions/tagged/glusterfs

From a quick look, users are asking more questions there than in the
gluster/glusterfs repository. For users it should not need to matter
what repository contains the sources (glusterfs, glusterfs-coreutils,
heketi, gluster-block, ...), which is something they need to understand
for GitHub Issues (or get ignored or ping-ponged around?).

Thanks,
Niels


signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Sankarshan Mukhopadhyay]

On Tue, May 9, 2017 at 8:21 PM, Pranith Kumar Karampuri
 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

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Pranith Kumar Karampuri]

On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:

> On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri
>  wrote:
> >
> >
> > On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay
> >  wrote:
> >>
> >> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi 
> wrote:
> >> > I personally prefer github questions than mailing list, because a
> valid
> >> > question can later become a reason for a new feature. Also, as you
> said,
> >> > we
> >> > can 'assignee' a question and if we start with bug triage we can also
> >> > make
> >> > sure at least we respond to questions which is pending.
> >>
> >> Is the on-going discussion in this thread about using
> >>  as a method to have
> >> questions and responses from the community?
> >
> >
> > yeah, this is something users have started doing. It seems better than
> mail
> > (at least to me).
> >
>
> There is a trend of projects who are moving to Github Issues as a
> medium/platform for responding to queries. As Amar mentions earlier in
> the thread and Shyam implies - this requires constant (ie. daily)
> vigil and attention. If those are in place, it is a practical move.
>

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.

Shyam,
  I started being more active on github because of the user questions.
So may be different people take different paths to be more active on
github.com/gluster. Some people may not be as active on github even after
we wait for a long time just like in gluster-users so may be we should
start using it for questions sooner? Thoughts? It will only encourage more
developers to be active on github.

___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Sankarshan Mukhopadhyay]

On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri
 wrote:
>
>
> On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay
>  wrote:
>>
>> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi  wrote:
>> > I personally prefer github questions than mailing list, because a valid
>> > question can later become a reason for a new feature. Also, as you said,
>> > we
>> > can 'assignee' a question and if we start with bug triage we can also
>> > make
>> > sure at least we respond to questions which is pending.
>>
>> Is the on-going discussion in this thread about using
>>  as a method to have
>> questions and responses from the community?
>
>
> yeah, this is something users have started doing. It seems better than mail
> (at least to me).
>

There is a trend of projects who are moving to Github Issues as a
medium/platform for responding to queries. As Amar mentions earlier in
the thread and Shyam implies - this requires constant (ie. daily)
vigil and attention. If those are in place, it is a practical move.
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Pranith Kumar Karampuri]

On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:

> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi  wrote:
> > I personally prefer github questions than mailing list, because a valid
> > question can later become a reason for a new feature. Also, as you said,
> we
> > can 'assignee' a question and if we start with bug triage we can also
> make
> > sure at least we respond to questions which is pending.
>
> Is the on-going discussion in this thread about using
>  as a method to have
> questions and responses from the community?
>

yeah, this is something users have started doing. It seems better than mail
(at least to me).


>
>
>
> --
> sankarshan mukhopadhyay
> 
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Sankarshan Mukhopadhyay]

On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi  wrote:
> I personally prefer github questions than mailing list, because a valid
> question can later become a reason for a new feature. Also, as you said, we
> can 'assignee' a question and if we start with bug triage we can also make
> sure at least we respond to questions which is pending.

Is the on-going discussion in this thread about using
 as a method to have
questions and responses from the community?



-- 
sankarshan mukhopadhyay

___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Pranith Kumar Karampuri]

On Tue, May 9, 2017 at 4:43 PM, Shyam  wrote:

> Hi,
>
> I would first like to see the habit of developers filing github issues for
> features that they are working on and are also thinking about in the near
> future.
>
> When we have that practice in place, taking it forward for bugs, and
> questions would work better.
>
> Currently we are still on the gaining mindshare for the former. If, as
> maintainers, we can do this better, taking up the latter is easier.
>

Hmm... based on experience, even when quite a few maintainers are there on
gluster-users/gluster-devel, quite a few times the questions pertaining to
a component won't get answered may be because they are busy with something
else. It is a bit cumbersome to find out what are the questions that still
need to be answered with the existing model.

So at least for questions it seems like a good idea to participate on
github, so that if a question doesn't get answered we would at least know
at some point and answer it.


> Shyam
>
> On 05/09/2017 05:27 AM, Pranith Kumar Karampuri wrote:
>
>> hi,
>> Wanted to know what people feel about asking/answering questions on
>> github.com , at the moment we are only using github
>> for RFEs, I am wondering if it would be fine to open it for questions
>> too. Main benefit I see is that it is easier to see open-questions at a
>> glance and easy to direct someone to the question/answer in future. It
>> is a bit cumbersome to browse through the thread on mailing list
>> compared to github IMHO.
>>
>> --
>> Pranith
>>
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>>


-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Niels de Vos]

On Tue, May 09, 2017 at 03:30:43PM +0530, Pranith Kumar Karampuri wrote:
> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi  wrote:
> 
> > I personally prefer github questions than mailing list, because a valid
> > question can later become a reason for a new feature. Also, as you said, we
> > can 'assignee' a question and if we start with bug triage we can also make
> > sure at least we respond to questions which is pending.
> >
> > A note of caution, i would like to keep github for more code / feature
> > related questions than that of setup related questions.
> >
> 
> Yeah, I was thinking for feature related questions which can turn into
> bugs/features/documentation we can take this route. We can always encourage
> them to post on gluster-users and close the question if it doesn't fall in
> the category.

At the moment very few developers seems to triage newly reported bugs.
Eventhough we have a good description and ways to get notifications on a
per component base. Since last week (new) 17 bugs were not triaged and
the few that handle this fallthrough in the Bug Triage meeting try to
take care of those.

I am not sure if adding GitHub issues for anything else as features
would help with the resonsiveness. Could there be an email to
b...@gluster.org when a new GitHub issue is reported? Users, developers
and maintainers can then (hopefully) filter on the components of their
interest.

In any case, the description that is shown when a new GitHub issue is
reported should be very clear on what kind of questions/problems go
where.

Thanks,
Niels

> 
> 
> >
> >
> > Regards,
> > Amar
> >
> > On Tue, May 9, 2017 at 2:57 PM, Pranith Kumar Karampuri <
> > pkara...@redhat.com> wrote:
> >
> >> hi,
> >> Wanted to know what people feel about asking/answering questions on
> >> github.com, at the moment we are only using github for RFEs, I am
> >> wondering if it would be fine to open it for questions too. Main benefit I
> >> see is that it is easier to see open-questions at a glance and easy to
> >> direct someone to the question/answer in future. It is a bit cumbersome to
> >> browse through the thread on mailing list compared to github IMHO.
> >>
> >> --
> >> Pranith
> >>
> >> ___
> >> Gluster-devel mailing list
> >> Gluster-devel@gluster.org
> >> http://lists.gluster.org/mailman/listinfo/gluster-devel
> >>
> >
> >
> >
> > --
> > Amar Tumballi (amarts)
> >
> 
> 
> 
> -- 
> Pranith

> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel



signature.asc
Description: PGP signature
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Shyam]

Hi,

I would first like to see the habit of developers filing github issues 
for features that they are working on and are also thinking about in the 
near future.


When we have that practice in place, taking it forward for bugs, and 
questions would work better.


Currently we are still on the gaining mindshare for the former. If, as 
maintainers, we can do this better, taking up the latter is easier.


Shyam

On 05/09/2017 05:27 AM, Pranith Kumar Karampuri wrote:

hi,
Wanted to know what people feel about asking/answering questions on
github.com , at the moment we are only using github
for RFEs, I am wondering if it would be fine to open it for questions
too. Main benefit I see is that it is easier to see open-questions at a
glance and easy to direct someone to the question/answer in future. It
is a bit cumbersome to browse through the thread on mailing list
compared to github IMHO.

--
Pranith


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel


___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Pranith Kumar Karampuri]

On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi  wrote:

> I personally prefer github questions than mailing list, because a valid
> question can later become a reason for a new feature. Also, as you said, we
> can 'assignee' a question and if we start with bug triage we can also make
> sure at least we respond to questions which is pending.
>
> A note of caution, i would like to keep github for more code / feature
> related questions than that of setup related questions.
>

Yeah, I was thinking for feature related questions which can turn into
bugs/features/documentation we can take this route. We can always encourage
them to post on gluster-users and close the question if it doesn't fall in
the category.


>
>
> Regards,
> Amar
>
> On Tue, May 9, 2017 at 2:57 PM, Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> hi,
>> Wanted to know what people feel about asking/answering questions on
>> github.com, at the moment we are only using github for RFEs, I am
>> wondering if it would be fine to open it for questions too. Main benefit I
>> see is that it is easier to see open-questions at a glance and easy to
>> direct someone to the question/answer in future. It is a bit cumbersome to
>> browse through the thread on mailing list compared to github IMHO.
>>
>> --
>> Pranith
>>
>> ___
>> Gluster-devel mailing list
>> Gluster-devel@gluster.org
>> http://lists.gluster.org/mailman/listinfo/gluster-devel
>>
>
>
>
> --
> Amar Tumballi (amarts)
>



-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

Re: [Gluster-devel] Questions on github

[Amar Tumballi]

I personally prefer github questions than mailing list, because a valid
question can later become a reason for a new feature. Also, as you said, we
can 'assignee' a question and if we start with bug triage we can also make
sure at least we respond to questions which is pending.

A note of caution, i would like to keep github for more code / feature
related questions than that of setup related questions.


Regards,
Amar

On Tue, May 9, 2017 at 2:57 PM, Pranith Kumar Karampuri  wrote:

> hi,
> Wanted to know what people feel about asking/answering questions on
> github.com, at the moment we are only using github for RFEs, I am
> wondering if it would be fine to open it for questions too. Main benefit I
> see is that it is easier to see open-questions at a glance and easy to
> direct someone to the question/answer in future. It is a bit cumbersome to
> browse through the thread on mailing list compared to github IMHO.
>
> --
> Pranith
>
> ___
> Gluster-devel mailing list
> Gluster-devel@gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
>



-- 
Amar Tumballi (amarts)
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel

[Gluster-devel] Questions on github

[Pranith Kumar Karampuri]

hi,
Wanted to know what people feel about asking/answering questions on
github.com, at the moment we are only using github for RFEs, I am wondering
if it would be fine to open it for questions too. Main benefit I see is
that it is easier to see open-questions at a glance and easy to direct
someone to the question/answer in future. It is a bit cumbersome to browse
through the thread on mailing list compared to github IMHO.

-- 
Pranith
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-devel