You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Kirk Lund <kl...@pivotal.io> on 2015/10/02 19:15:45 UTC
ASF Jira Project Roles and Groups
If I pull up a Jira ticket such as:
https://issues.apache.org/jira/browse/GEODE-189
I can add a comment or edit an existing comment and I notice there's an
option for locking the comment so that it's only readable by a specified
Project Role or Group.
At present there is only one Project Role "Committers" and one Group
"jira-users"
Is there a way we could add a custom Role or Group? Then we could add
comments that point back to non-public URLs to help the person working on
the ticket. Good idea, bad idea?
This is to avoid having to duplicate every single ticket on a private Jira
server just so we can add comments that reference Pivotal file system paths
for saved test runs and things like that. Engineers aren't going to be able
to fix most tickets unless they have more details including internal file
system paths.
-Kirk
Re: ASF Jira Project Roles and Groups
Posted by Kirk Lund <kl...@pivotal.io>.
I agree. And if the log files and stat files are valuable for working on
the bug shouldn't we make those available via a comment on a Jira ticket?
Even if some application that uses Geode isn't open sourced, but we have
logs and stats for it and that application hit a Geode bug for which we
file a Jira ticket for... then someone who's working on that ticket would
want to see the logs and stats even if they don't have access to the
application source code.
-Kirk
On Fri, Oct 2, 2015 at 11:07 AM, Dan Smith <ds...@pivotal.io> wrote:
> I agree with Anthony. There shouldn't be anything in geode that can't be
> picked up and worked on by any member of the community. Having bugs that
> can only be worked on by employees of Pivotal is contrary to being an open
> community.
>
> -Dan
>
> On Fri, Oct 2, 2015 at 10:54 AM, Kirk Lund <kl...@pivotal.io> wrote:
>
> > I'm all for making test results external as well. Can we open up our
> > servers so that the public can view our buglogs directories? That way we
> > can post comments pointing those invaluable results!
> >
> > If not then we need to replicate every ticket internally which is a
> > terrible idea.
> >
> > -Kirk
> >
> >
> > On Fri, Oct 2, 2015 at 10:45 AM, Anthony Baker <ab...@pivotal.io>
> wrote:
> >
> > > My belief is that Apache (and thus Geode) is an open community and
> > > everything about Geode should be open and collaborative. Private
> > comments
> > > on JIRA’s would distort that principle IMO. Perhaps we can find a way
> > over
> > > time to make internal test results and data less internal :-)
> > >
> > > Anthony
> > >
> > >
> > > > On Oct 2, 2015, at 7:15 PM, Kirk Lund <kl...@pivotal.io> wrote:
> > > >
> > > > If I pull up a Jira ticket such as:
> > > >
> > > > https://issues.apache.org/jira/browse/GEODE-189
> > > >
> > > > I can add a comment or edit an existing comment and I notice there's
> an
> > > > option for locking the comment so that it's only readable by a
> > specified
> > > > Project Role or Group.
> > > >
> > > > At present there is only one Project Role "Committers" and one Group
> > > > "jira-users"
> > > >
> > > > Is there a way we could add a custom Role or Group? Then we could add
> > > > comments that point back to non-public URLs to help the person
> working
> > on
> > > > the ticket. Good idea, bad idea?
> > > >
> > > > This is to avoid having to duplicate every single ticket on a private
> > > Jira
> > > > server just so we can add comments that reference Pivotal file system
> > > paths
> > > > for saved test runs and things like that. Engineers aren't going to
> be
> > > able
> > > > to fix most tickets unless they have more details including internal
> > file
> > > > system paths.
> > > >
> > > > -Kirk
> > >
> > >
> >
>
Re: ASF Jira Project Roles and Groups
Posted by Dan Smith <ds...@pivotal.io>.
I agree with Anthony. There shouldn't be anything in geode that can't be
picked up and worked on by any member of the community. Having bugs that
can only be worked on by employees of Pivotal is contrary to being an open
community.
-Dan
On Fri, Oct 2, 2015 at 10:54 AM, Kirk Lund <kl...@pivotal.io> wrote:
> I'm all for making test results external as well. Can we open up our
> servers so that the public can view our buglogs directories? That way we
> can post comments pointing those invaluable results!
>
> If not then we need to replicate every ticket internally which is a
> terrible idea.
>
> -Kirk
>
>
> On Fri, Oct 2, 2015 at 10:45 AM, Anthony Baker <ab...@pivotal.io> wrote:
>
> > My belief is that Apache (and thus Geode) is an open community and
> > everything about Geode should be open and collaborative. Private
> comments
> > on JIRA’s would distort that principle IMO. Perhaps we can find a way
> over
> > time to make internal test results and data less internal :-)
> >
> > Anthony
> >
> >
> > > On Oct 2, 2015, at 7:15 PM, Kirk Lund <kl...@pivotal.io> wrote:
> > >
> > > If I pull up a Jira ticket such as:
> > >
> > > https://issues.apache.org/jira/browse/GEODE-189
> > >
> > > I can add a comment or edit an existing comment and I notice there's an
> > > option for locking the comment so that it's only readable by a
> specified
> > > Project Role or Group.
> > >
> > > At present there is only one Project Role "Committers" and one Group
> > > "jira-users"
> > >
> > > Is there a way we could add a custom Role or Group? Then we could add
> > > comments that point back to non-public URLs to help the person working
> on
> > > the ticket. Good idea, bad idea?
> > >
> > > This is to avoid having to duplicate every single ticket on a private
> > Jira
> > > server just so we can add comments that reference Pivotal file system
> > paths
> > > for saved test runs and things like that. Engineers aren't going to be
> > able
> > > to fix most tickets unless they have more details including internal
> file
> > > system paths.
> > >
> > > -Kirk
> >
> >
>
Re: ASF Jira Project Roles and Groups
Posted by Kirk Lund <kl...@pivotal.io>.
I'm all for making test results external as well. Can we open up our
servers so that the public can view our buglogs directories? That way we
can post comments pointing those invaluable results!
If not then we need to replicate every ticket internally which is a
terrible idea.
-Kirk
On Fri, Oct 2, 2015 at 10:45 AM, Anthony Baker <ab...@pivotal.io> wrote:
> My belief is that Apache (and thus Geode) is an open community and
> everything about Geode should be open and collaborative. Private comments
> on JIRA’s would distort that principle IMO. Perhaps we can find a way over
> time to make internal test results and data less internal :-)
>
> Anthony
>
>
> > On Oct 2, 2015, at 7:15 PM, Kirk Lund <kl...@pivotal.io> wrote:
> >
> > If I pull up a Jira ticket such as:
> >
> > https://issues.apache.org/jira/browse/GEODE-189
> >
> > I can add a comment or edit an existing comment and I notice there's an
> > option for locking the comment so that it's only readable by a specified
> > Project Role or Group.
> >
> > At present there is only one Project Role "Committers" and one Group
> > "jira-users"
> >
> > Is there a way we could add a custom Role or Group? Then we could add
> > comments that point back to non-public URLs to help the person working on
> > the ticket. Good idea, bad idea?
> >
> > This is to avoid having to duplicate every single ticket on a private
> Jira
> > server just so we can add comments that reference Pivotal file system
> paths
> > for saved test runs and things like that. Engineers aren't going to be
> able
> > to fix most tickets unless they have more details including internal file
> > system paths.
> >
> > -Kirk
>
>
Re: ASF Jira Project Roles and Groups
Posted by Anthony Baker <ab...@pivotal.io>.
My belief is that Apache (and thus Geode) is an open community and everything about Geode should be open and collaborative. Private comments on JIRA’s would distort that principle IMO. Perhaps we can find a way over time to make internal test results and data less internal :-)
Anthony
> On Oct 2, 2015, at 7:15 PM, Kirk Lund <kl...@pivotal.io> wrote:
>
> If I pull up a Jira ticket such as:
>
> https://issues.apache.org/jira/browse/GEODE-189
>
> I can add a comment or edit an existing comment and I notice there's an
> option for locking the comment so that it's only readable by a specified
> Project Role or Group.
>
> At present there is only one Project Role "Committers" and one Group
> "jira-users"
>
> Is there a way we could add a custom Role or Group? Then we could add
> comments that point back to non-public URLs to help the person working on
> the ticket. Good idea, bad idea?
>
> This is to avoid having to duplicate every single ticket on a private Jira
> server just so we can add comments that reference Pivotal file system paths
> for saved test runs and things like that. Engineers aren't going to be able
> to fix most tickets unless they have more details including internal file
> system paths.
>
> -Kirk