You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by Dave Birdsall <da...@esgyn.com> on 2015/07/14 02:17:39 UTC
Assignment of Trafodion JIRAs
Hi,
A question has come up concerning how JIRA works. I'm hoping perhaps one of
the mentors can advise.
I've heard that contributors can assign JIRAs to themselves in other Apache
projects (such as HBase). I think we would like to have the same ability in
Trafodion.
Looking at the set of JIRAs for Trafodion so far, most are unassigned. So I
am guessing that except for administrators folks are not able to assign
themselves to the JIRAs they write.
I've done a little looking into how to make it possible. There is a
Permissions page in JIRA that administrators can fiddle with. (Here it is,
but perhaps you have to be an administrator to see it:
https://issues.apache.org/jira/plugins/servlet/project-config/TRAFODION/permissions.)
On that page, I don't see an option for permitting folks to self-assign. I
do see one for allowing folks to assign to each other though and we could
solve the problem for Trafodion by simply adding all committers to that
list. Is this a good idea? (Mentors, please comment.)
So a question to the mentors: How do other projects work? Is it the case
that there is no separate privilege to self-assign?
A question to Trafodion contributors: Have any of you (besides
contributors) been able to self-assign?
And a more practical question: Are there any outstanding JIRAs that you'd
like to have assigned to you? If so, just reply to me and I can assign it
to you.
Thanks,
Dave
Re: Assignment of Trafodion JIRAs
Posted by Dave Birdsall <da...@esgyn.com>.
Right now the JIRA admins are: Stack, Alice Chen, Suresh, Steve Varnau and
me.
Dave
On Tue, Jul 14, 2015 at 8:53 AM, Sandhya Sundaresan <
sandhya.sundaresan@esgyn.com> wrote:
> That sounds reasonable Dave. As long as the contributor is able to mark it
> as "Fixed".
> Who are the admins who are able to close these ?
> Thanks
> Sandhya
>
> -----Original Message-----
> From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
> Sent: Tuesday, July 14, 2015 8:06 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Assignment of Trafodion JIRAs
>
> Hi Selva,
>
> Yes, I think only the creator or an admin can mark it resolved. Perhaps
> that is best? What do others think?
>
> Meantime, I'll continue to follow up on the assignment issue.
>
> Dave
>
> On Mon, Jul 13, 2015 at 7:02 PM, Selva Govindarajan <
> selva.govindarajan@esgyn.com> wrote:
>
> > Hi Dave,
> >
> > Trafodion contributors are not able to self-assign if the JIRA is
> > created by others. But, the committers were able to assign the JIRA to
> > the contributors. Suresh assigned one to me. However, I couldn't find
> > a way to mark the JIRA as resolved even when it is assigned to me. Can
> > only the creator mark it as resolved?
> >
> > On Mon, Jul 13, 2015 at 6:29 PM, Stack <st...@duboce.net> wrote:
> >
> > > On Mon, Jul 13, 2015 at 5:17 PM, Dave Birdsall
> > > <da...@esgyn.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > A question has come up concerning how JIRA works. I'm hoping
> > > > perhaps
> > one
> > > of
> > > > the mentors can advise.
> > > >
> > > > I've heard that contributors can assign JIRAs to themselves in
> > > > other
> > > Apache
> > > > projects (such as HBase). I think we would like to have the same
> > ability
> > > in
> > > > Trafodion.
> > > >
> > > > Looking at the set of JIRAs for Trafodion so far, most are
> unassigned.
> > > So I
> > > > am guessing that except for administrators folks are not able to
> > > > assign themselves to the JIRAs they write.
> > > >
> > > > I've done a little looking into how to make it possible. There is
> > > > a Permissions page in JIRA that administrators can fiddle with.
> > > > (Here it
> > > is,
> > > > but perhaps you have to be an administrator to see it:
> > > >
> > > >
> > >
> > https://issues.apache.org/jira/plugins/servlet/project-config/TRAFODIO
> > N/permissions
> > > > .)
> > > > On that page, I don't see an option for permitting folks to
> > self-assign.
> > > I
> > > > do see one for allowing folks to assign to each other though and
> > > > we
> > could
> > > > solve the problem for Trafodion by simply adding all committers to
> > > > that list. Is this a good idea? (Mentors, please comment.)
> > > >
> > > > So a question to the mentors: How do other projects work? Is it
> > > > the
> > case
> > > > that there is no separate privilege to self-assign?
> > > >
> > > > A question to Trafodion contributors: Have any of you (besides
> > > > contributors) been able to self-assign?
> > > >
> > > > And a more practical question: Are there any outstanding JIRAs
> > > > that
> > you'd
> > > > like to have assigned to you? If so, just reply to me and I can
> > > > assign
> > it
> > > > to you.
> > > >
> > > > Thanks,
> > > >
> > >
> > > (A version of what I wrote Dave offline)
> > >
> > > ...Need to make contrib friction-free as possible.
> > >
> > > Regards how it works in HBase, we inherited a 'template' for perms
> > > -- the hadoop 'permissions' template -- which had a bunch of this
> > > stuff setup
> > for
> > > us. We seem to have also taken other templates from hadoop including
> > > workflow (as best as I remember). To set HBase to use the Hadoop
> > template
> > > for JIRA, it was an INFRA ticket (But I can't find the ticket now
> > > which does not inspire confidence). It looks like we subsequently
> > > changed the template because ours is "hbase issue type schema".
> > > Trafodion might want
> > to
> > > take on the Hadoop template for schema or perms or evolve your own.
> > > You have 'Default Issue Type Scheme' now. Likely same for perms.
> > >
> > > I made you an administrator on the HBase JIRA so you can poke around
> > > and see how we are configured. See
> > >
> > >
> > https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/pe
> > rmissions
> > >
> > > Thanks for admining...
> > > St.Ack
> > >
> >
>
>
RE: Assignment of Trafodion JIRAs
Posted by Sandhya Sundaresan <sa...@esgyn.com>.
That sounds reasonable Dave. As long as the contributor is able to mark it as "Fixed".
Who are the admins who are able to close these ?
Thanks
Sandhya
-----Original Message-----
From: Dave Birdsall [mailto:dave.birdsall@esgyn.com]
Sent: Tuesday, July 14, 2015 8:06 AM
To: dev@trafodion.incubator.apache.org
Subject: Re: Assignment of Trafodion JIRAs
Hi Selva,
Yes, I think only the creator or an admin can mark it resolved. Perhaps that is best? What do others think?
Meantime, I'll continue to follow up on the assignment issue.
Dave
On Mon, Jul 13, 2015 at 7:02 PM, Selva Govindarajan < selva.govindarajan@esgyn.com> wrote:
> Hi Dave,
>
> Trafodion contributors are not able to self-assign if the JIRA is
> created by others. But, the committers were able to assign the JIRA to
> the contributors. Suresh assigned one to me. However, I couldn't find
> a way to mark the JIRA as resolved even when it is assigned to me. Can
> only the creator mark it as resolved?
>
> On Mon, Jul 13, 2015 at 6:29 PM, Stack <st...@duboce.net> wrote:
>
> > On Mon, Jul 13, 2015 at 5:17 PM, Dave Birdsall
> > <da...@esgyn.com>
> > wrote:
> >
> > > Hi,
> > >
> > > A question has come up concerning how JIRA works. I'm hoping
> > > perhaps
> one
> > of
> > > the mentors can advise.
> > >
> > > I've heard that contributors can assign JIRAs to themselves in
> > > other
> > Apache
> > > projects (such as HBase). I think we would like to have the same
> ability
> > in
> > > Trafodion.
> > >
> > > Looking at the set of JIRAs for Trafodion so far, most are unassigned.
> > So I
> > > am guessing that except for administrators folks are not able to
> > > assign themselves to the JIRAs they write.
> > >
> > > I've done a little looking into how to make it possible. There is
> > > a Permissions page in JIRA that administrators can fiddle with.
> > > (Here it
> > is,
> > > but perhaps you have to be an administrator to see it:
> > >
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/TRAFODIO
> N/permissions
> > > .)
> > > On that page, I don't see an option for permitting folks to
> self-assign.
> > I
> > > do see one for allowing folks to assign to each other though and
> > > we
> could
> > > solve the problem for Trafodion by simply adding all committers to
> > > that list. Is this a good idea? (Mentors, please comment.)
> > >
> > > So a question to the mentors: How do other projects work? Is it
> > > the
> case
> > > that there is no separate privilege to self-assign?
> > >
> > > A question to Trafodion contributors: Have any of you (besides
> > > contributors) been able to self-assign?
> > >
> > > And a more practical question: Are there any outstanding JIRAs
> > > that
> you'd
> > > like to have assigned to you? If so, just reply to me and I can
> > > assign
> it
> > > to you.
> > >
> > > Thanks,
> > >
> >
> > (A version of what I wrote Dave offline)
> >
> > ...Need to make contrib friction-free as possible.
> >
> > Regards how it works in HBase, we inherited a 'template' for perms
> > -- the hadoop 'permissions' template -- which had a bunch of this
> > stuff setup
> for
> > us. We seem to have also taken other templates from hadoop including
> > workflow (as best as I remember). To set HBase to use the Hadoop
> template
> > for JIRA, it was an INFRA ticket (But I can't find the ticket now
> > which does not inspire confidence). It looks like we subsequently
> > changed the template because ours is "hbase issue type schema".
> > Trafodion might want
> to
> > take on the Hadoop template for schema or perms or evolve your own.
> > You have 'Default Issue Type Scheme' now. Likely same for perms.
> >
> > I made you an administrator on the HBase JIRA so you can poke around
> > and see how we are configured. See
> >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/pe
> rmissions
> >
> > Thanks for admining...
> > St.Ack
> >
>
Re: Assignment of Trafodion JIRAs
Posted by Dave Birdsall <da...@esgyn.com>.
Hi Selva,
Yes, I think only the creator or an admin can mark it resolved. Perhaps
that is best? What do others think?
Meantime, I'll continue to follow up on the assignment issue.
Dave
On Mon, Jul 13, 2015 at 7:02 PM, Selva Govindarajan <
selva.govindarajan@esgyn.com> wrote:
> Hi Dave,
>
> Trafodion contributors are not able to self-assign if the JIRA is created
> by others. But, the committers were able to assign the JIRA to the
> contributors. Suresh assigned one to me. However, I couldn't find a way to
> mark the JIRA as resolved even when it is assigned to me. Can only the
> creator mark it as resolved?
>
> On Mon, Jul 13, 2015 at 6:29 PM, Stack <st...@duboce.net> wrote:
>
> > On Mon, Jul 13, 2015 at 5:17 PM, Dave Birdsall <da...@esgyn.com>
> > wrote:
> >
> > > Hi,
> > >
> > > A question has come up concerning how JIRA works. I'm hoping perhaps
> one
> > of
> > > the mentors can advise.
> > >
> > > I've heard that contributors can assign JIRAs to themselves in other
> > Apache
> > > projects (such as HBase). I think we would like to have the same
> ability
> > in
> > > Trafodion.
> > >
> > > Looking at the set of JIRAs for Trafodion so far, most are unassigned.
> > So I
> > > am guessing that except for administrators folks are not able to assign
> > > themselves to the JIRAs they write.
> > >
> > > I've done a little looking into how to make it possible. There is a
> > > Permissions page in JIRA that administrators can fiddle with. (Here it
> > is,
> > > but perhaps you have to be an administrator to see it:
> > >
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/TRAFODION/permissions
> > > .)
> > > On that page, I don't see an option for permitting folks to
> self-assign.
> > I
> > > do see one for allowing folks to assign to each other though and we
> could
> > > solve the problem for Trafodion by simply adding all committers to that
> > > list. Is this a good idea? (Mentors, please comment.)
> > >
> > > So a question to the mentors: How do other projects work? Is it the
> case
> > > that there is no separate privilege to self-assign?
> > >
> > > A question to Trafodion contributors: Have any of you (besides
> > > contributors) been able to self-assign?
> > >
> > > And a more practical question: Are there any outstanding JIRAs that
> you'd
> > > like to have assigned to you? If so, just reply to me and I can assign
> it
> > > to you.
> > >
> > > Thanks,
> > >
> >
> > (A version of what I wrote Dave offline)
> >
> > ...Need to make contrib friction-free as possible.
> >
> > Regards how it works in HBase, we inherited a 'template' for perms -- the
> > hadoop 'permissions' template -- which had a bunch of this stuff setup
> for
> > us. We seem to have also taken other templates from hadoop including
> > workflow (as best as I remember). To set HBase to use the Hadoop
> template
> > for JIRA, it was an INFRA ticket (But I can't find the ticket now which
> > does not inspire confidence). It looks like we subsequently changed the
> > template because ours is "hbase issue type schema". Trafodion might want
> to
> > take on the Hadoop template for schema or perms or evolve your own. You
> > have 'Default Issue Type Scheme' now. Likely same for perms.
> >
> > I made you an administrator on the HBase JIRA so you can poke around and
> > see how we are configured. See
> >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/permissions
> >
> > Thanks for admining...
> > St.Ack
> >
>
Re: Assignment of Trafodion JIRAs
Posted by Selva Govindarajan <se...@esgyn.com>.
Hi Dave,
Trafodion contributors are not able to self-assign if the JIRA is created
by others. But, the committers were able to assign the JIRA to the
contributors. Suresh assigned one to me. However, I couldn't find a way to
mark the JIRA as resolved even when it is assigned to me. Can only the
creator mark it as resolved?
On Mon, Jul 13, 2015 at 6:29 PM, Stack <st...@duboce.net> wrote:
> On Mon, Jul 13, 2015 at 5:17 PM, Dave Birdsall <da...@esgyn.com>
> wrote:
>
> > Hi,
> >
> > A question has come up concerning how JIRA works. I'm hoping perhaps one
> of
> > the mentors can advise.
> >
> > I've heard that contributors can assign JIRAs to themselves in other
> Apache
> > projects (such as HBase). I think we would like to have the same ability
> in
> > Trafodion.
> >
> > Looking at the set of JIRAs for Trafodion so far, most are unassigned.
> So I
> > am guessing that except for administrators folks are not able to assign
> > themselves to the JIRAs they write.
> >
> > I've done a little looking into how to make it possible. There is a
> > Permissions page in JIRA that administrators can fiddle with. (Here it
> is,
> > but perhaps you have to be an administrator to see it:
> >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/TRAFODION/permissions
> > .)
> > On that page, I don't see an option for permitting folks to self-assign.
> I
> > do see one for allowing folks to assign to each other though and we could
> > solve the problem for Trafodion by simply adding all committers to that
> > list. Is this a good idea? (Mentors, please comment.)
> >
> > So a question to the mentors: How do other projects work? Is it the case
> > that there is no separate privilege to self-assign?
> >
> > A question to Trafodion contributors: Have any of you (besides
> > contributors) been able to self-assign?
> >
> > And a more practical question: Are there any outstanding JIRAs that you'd
> > like to have assigned to you? If so, just reply to me and I can assign it
> > to you.
> >
> > Thanks,
> >
>
> (A version of what I wrote Dave offline)
>
> ...Need to make contrib friction-free as possible.
>
> Regards how it works in HBase, we inherited a 'template' for perms -- the
> hadoop 'permissions' template -- which had a bunch of this stuff setup for
> us. We seem to have also taken other templates from hadoop including
> workflow (as best as I remember). To set HBase to use the Hadoop template
> for JIRA, it was an INFRA ticket (But I can't find the ticket now which
> does not inspire confidence). It looks like we subsequently changed the
> template because ours is "hbase issue type schema". Trafodion might want to
> take on the Hadoop template for schema or perms or evolve your own. You
> have 'Default Issue Type Scheme' now. Likely same for perms.
>
> I made you an administrator on the HBase JIRA so you can poke around and
> see how we are configured. See
>
> https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/permissions
>
> Thanks for admining...
> St.Ack
>
Re: Assignment of Trafodion JIRAs
Posted by Stack <st...@duboce.net>.
On Mon, Jul 13, 2015 at 5:17 PM, Dave Birdsall <da...@esgyn.com>
wrote:
> Hi,
>
> A question has come up concerning how JIRA works. I'm hoping perhaps one of
> the mentors can advise.
>
> I've heard that contributors can assign JIRAs to themselves in other Apache
> projects (such as HBase). I think we would like to have the same ability in
> Trafodion.
>
> Looking at the set of JIRAs for Trafodion so far, most are unassigned. So I
> am guessing that except for administrators folks are not able to assign
> themselves to the JIRAs they write.
>
> I've done a little looking into how to make it possible. There is a
> Permissions page in JIRA that administrators can fiddle with. (Here it is,
> but perhaps you have to be an administrator to see it:
>
> https://issues.apache.org/jira/plugins/servlet/project-config/TRAFODION/permissions
> .)
> On that page, I don't see an option for permitting folks to self-assign. I
> do see one for allowing folks to assign to each other though and we could
> solve the problem for Trafodion by simply adding all committers to that
> list. Is this a good idea? (Mentors, please comment.)
>
> So a question to the mentors: How do other projects work? Is it the case
> that there is no separate privilege to self-assign?
>
> A question to Trafodion contributors: Have any of you (besides
> contributors) been able to self-assign?
>
> And a more practical question: Are there any outstanding JIRAs that you'd
> like to have assigned to you? If so, just reply to me and I can assign it
> to you.
>
> Thanks,
>
(A version of what I wrote Dave offline)
...Need to make contrib friction-free as possible.
Regards how it works in HBase, we inherited a 'template' for perms -- the
hadoop 'permissions' template -- which had a bunch of this stuff setup for
us. We seem to have also taken other templates from hadoop including
workflow (as best as I remember). To set HBase to use the Hadoop template
for JIRA, it was an INFRA ticket (But I can't find the ticket now which
does not inspire confidence). It looks like we subsequently changed the
template because ours is "hbase issue type schema". Trafodion might want to
take on the Hadoop template for schema or perms or evolve your own. You
have 'Default Issue Type Scheme' now. Likely same for perms.
I made you an administrator on the HBase JIRA so you can poke around and
see how we are configured. See
https://issues.apache.org/jira/plugins/servlet/project-config/HBASE/permissions
Thanks for admining...
St.Ack