You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafodion.apache.org by "Marton, Roberta S" <ro...@hp.com> on 2015/06/25 18:29:20 UTC
Question on JIRA's
I have created my first JIRA this morning. A little confusion with the CREATE button but got that resolved.
Looking at the current set of Trafodion JIRA's I see that they are all unassigned. I looked around a bit and could not figure out how to assign them.
Perusing the internet, it looks like there is an administrator that can assign JIRA's.
How should we be handling assigning Trafodion JIRAs? Can I just assign a JIRA to myself without any special privilege?
And Pierre, great job in putting together the Trafodion wiki page.
Roberta
Re: Question on JIRA's
Posted by Stack <st...@duboce.net>.
You are an administrator now too Dave,
St.Ack
On Wed, Jul 8, 2015 at 4:56 PM, Dave Birdsall <da...@esgyn.com>
wrote:
> Hi Stack,
>
> FYI: My JIRA account is "DaveBirdsall".
>
> Dave
>
> On Wed, Jul 8, 2015 at 1:53 PM, Stack <st...@duboce.net> wrote:
>
> > On Thu, Jun 25, 2015 at 9:43 AM, Chen, Alice (Trafodion) <
> > alice.chen@hp.com>
> > wrote:
> >
> > > Hello Roberta,
> > >
> > > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701
> .
> > > Our project was created but no administrator has been assigned nor has
> > our
> > > old LP bugs been imported yet.
> > >
> > >
> >
> > INFRA just made me administrator. I made Alice, Steve, and Suresh
> > administrator's too (Dave, I cannot find an account for you in JIRA).
> >
> > One of you might want to go through the admin page and do a few tweaks
> > adding home page, description, and logo. Would advise not messing with
> the
> > 'flow' or doing other drastic change until you all have a better idea on
> > how it currently works.
> >
> > St.Ack
> >
> >
> >
> > > Cheers,
> > > Alice
> > >
> > > -----Original Message-----
> > > From: Marton, Roberta S
> > > Sent: Thursday, June 25, 2015 9:29 AM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: Question on JIRA's
> > >
> > > I have created my first JIRA this morning. A little confusion with the
> > > CREATE button but got that resolved.
> > >
> > > Looking at the current set of Trafodion JIRA's I see that they are all
> > > unassigned. I looked around a bit and could not figure out how to
> assign
> > > them.
> > > Perusing the internet, it looks like there is an administrator that can
> > > assign JIRA's.
> > > How should we be handling assigning Trafodion JIRAs? Can I just
> assign a
> > > JIRA to myself without any special privilege?
> > >
> > > And Pierre, great job in putting together the Trafodion wiki page.
> > >
> > > Roberta
> > >
> >
>
Re: Question on JIRA's
Posted by Dave Birdsall <da...@esgyn.com>.
Hi Stack,
FYI: My JIRA account is "DaveBirdsall".
Dave
On Wed, Jul 8, 2015 at 1:53 PM, Stack <st...@duboce.net> wrote:
> On Thu, Jun 25, 2015 at 9:43 AM, Chen, Alice (Trafodion) <
> alice.chen@hp.com>
> wrote:
>
> > Hello Roberta,
> >
> > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 .
> > Our project was created but no administrator has been assigned nor has
> our
> > old LP bugs been imported yet.
> >
> >
>
> INFRA just made me administrator. I made Alice, Steve, and Suresh
> administrator's too (Dave, I cannot find an account for you in JIRA).
>
> One of you might want to go through the admin page and do a few tweaks
> adding home page, description, and logo. Would advise not messing with the
> 'flow' or doing other drastic change until you all have a better idea on
> how it currently works.
>
> St.Ack
>
>
>
> > Cheers,
> > Alice
> >
> > -----Original Message-----
> > From: Marton, Roberta S
> > Sent: Thursday, June 25, 2015 9:29 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Question on JIRA's
> >
> > I have created my first JIRA this morning. A little confusion with the
> > CREATE button but got that resolved.
> >
> > Looking at the current set of Trafodion JIRA's I see that they are all
> > unassigned. I looked around a bit and could not figure out how to assign
> > them.
> > Perusing the internet, it looks like there is an administrator that can
> > assign JIRA's.
> > How should we be handling assigning Trafodion JIRAs? Can I just assign a
> > JIRA to myself without any special privilege?
> >
> > And Pierre, great job in putting together the Trafodion wiki page.
> >
> > Roberta
> >
>
Re: Question on JIRA's
Posted by Stack <st...@duboce.net>.
On Thu, Jun 25, 2015 at 9:43 AM, Chen, Alice (Trafodion) <al...@hp.com>
wrote:
> Hello Roberta,
>
> We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 .
> Our project was created but no administrator has been assigned nor has our
> old LP bugs been imported yet.
>
>
INFRA just made me administrator. I made Alice, Steve, and Suresh
administrator's too (Dave, I cannot find an account for you in JIRA).
One of you might want to go through the admin page and do a few tweaks
adding home page, description, and logo. Would advise not messing with the
'flow' or doing other drastic change until you all have a better idea on
how it currently works.
St.Ack
> Cheers,
> Alice
>
> -----Original Message-----
> From: Marton, Roberta S
> Sent: Thursday, June 25, 2015 9:29 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Question on JIRA's
>
> I have created my first JIRA this morning. A little confusion with the
> CREATE button but got that resolved.
>
> Looking at the current set of Trafodion JIRA's I see that they are all
> unassigned. I looked around a bit and could not figure out how to assign
> them.
> Perusing the internet, it looks like there is an administrator that can
> assign JIRA's.
> How should we be handling assigning Trafodion JIRAs? Can I just assign a
> JIRA to myself without any special privilege?
>
> And Pierre, great job in putting together the Trafodion wiki page.
>
> Roberta
>
RE: Question on JIRA's
Posted by "Varnau, Steve (Trafodion)" <st...@hp.com>.
Makes sense to me. We are already in that state where we have a bunch of contributors that are not committers, and we want to encourage more participation.
-Steve
> -----Original Message-----
> From: Pierre Smits [mailto:pierre.smits@gmail.com]
> Sent: Friday, June 26, 2015 00:42
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Question on JIRA's
>
> Roberta, All,
>
> Are you sure you want this project to have a methodology for 'assigning'
> to other contributors? What I have learned over the years within a few
> Apache projects is that when there is a restrictive scheme for the
> greatest group of contributors (those without privileges) involvement is
> of the lowest kind possible. Non-privileged contributors just register
> issues (or don't at all), because they don't feel ownership as they only
> have limited means to influence those with privileges.
> Nothing hampers community growth more than restrictions on contributor
> permissions. And within each Apache project there are already a
> multitude of permissions schemes to consider and work with (from a
> managerial point of view), as the underlying tools don't use an
> integrated Authentication & Authorisation solution (e.g. JIRA vs
> Confluence).
>
> A solution to this predicament regarding JIRA issues could be the
> following: in stead of opting where only contributors with privileges
> (committers) have the permission to do issue assignment, let us opt for
> the 'Default plus Contributor Assign Permission Scheme' as described in
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Author
> ization
> .
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> <ro...@hp.com>
> wrote:
>
> > Thanks Alice. I knew this was needed to move over Lauchpad but missed
> > the assigning of JIRA bugs.
> >
> > Roberta
> >
> > -----Original Message-----
> > From: Chen, Alice (Trafodion)
> > Sent: Thursday, June 25, 2015 9:44 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Question on JIRA's
> >
> > Hello Roberta,
> >
> > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701
> .
> > Our project was created but no administrator has been assigned nor has
> > our old LP bugs been imported yet.
> >
> > Cheers,
> > Alice
> >
> > -----Original Message-----
> > From: Marton, Roberta S
> > Sent: Thursday, June 25, 2015 9:29 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Question on JIRA's
> >
> > I have created my first JIRA this morning. A little confusion with
> > the CREATE button but got that resolved.
> >
> > Looking at the current set of Trafodion JIRA's I see that they are all
> > unassigned. I looked around a bit and could not figure out how to
> > assign them.
> > Perusing the internet, it looks like there is an administrator that
> > can assign JIRA's.
> > How should we be handling assigning Trafodion JIRAs? Can I just
> > assign a JIRA to myself without any special privilege?
> >
> > And Pierre, great job in putting together the Trafodion wiki page.
> >
> > Roberta
> >
Re: Question on JIRA's
Posted by Andrew Purtell <ap...@apache.org>.
Thanks for the clarification, as you can see I was looking at the INFRA
wiki and not getting a clear sense of that.
In my experience on several projects, occasionally someone does reassign an
issue unexpectedly. I've seen newcomers do that accidentally. It prompts a
brief discussion on the JIRA and a correction. Even experienced committers
do it from time to time, but they typically catch the mistake and fix it
right away. I've not seen this abused in 7 years.
On Sat, Jul 4, 2015 at 3:44 PM, Pierre Smits <pi...@gmail.com> wrote:
> To be accurate, the 'Default plus Contributor Assign Permission Scheme' for
> JIRA applicable to the project or podling allows any contributor (even
> those without commit-privileges) to assign issues to themselves, but also
> to others. However, it should be frowned upon if such happens. As this
> would go against the aspect of common decency amongst volunteers in an open
> source project. Of course a contributor can suggest and ask in a comment on
> the issue who would be the most suitable contributor to address and further
> the issue to resolvement and closure.
>
> Though the technical setup of the scheme is very liberal, we can - of
> course - limit how this podling and if anything goes well during incubation
> upon graduation to TLP the project will apply such by incorporating it in
> its bylaws.
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Sat, Jul 4, 2015 at 1:17 AM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > > but they cannot reassign issues to themselves which are already
> assigned
> > to others.
> >
> > Pardon, they might be able to reassign to themselves but not to others.
> I'm
> > not clear on which alternative is correct and have no way to test right
> > now. Worst case, if someone accidentally or improperly assigns something
> > to themselves, someone with Committer role or better can fix it.
> >
> >
> > On Fri, Jul 3, 2015 at 3:12 PM, Andrew Purtell <ap...@apache.org>
> > wrote:
> >
> > > For our project we authorize the role "jira-users" as a contributor.
> See
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> > > for what the Contributors role allows. Anyone signed up with an account
> > on
> > > ASF JIRA can assign themselves unassigned issues, but they cannot
> > reassign
> > > issues to themselves which are already assigned to others.
> > >
> > > > With this model an interested contributor could create a JIRA and
> > assign
> > > it to herself/himself if they feel it is appropriate.
> > >
> > > Yes.
> > >
> > > It also lets you do things like create a number of issues good for
> > > beginners, perhaps identified with a label like "beginner". Then later
> an
> > > interested beginner will be able assign such issues to themselves and
> get
> > > going, presumably with guidance once committers notice the email from
> > JIRA
> > > that the issue was assigned.
> > >
> > >
> > > On Sat, Jun 27, 2015 at 1:56 PM, Subbiah, Suresh <
> Suresh.Subbiah@hp.com>
> > > wrote:
> > >
> > >> +1 For JIRA assignment privileges being granted to any registered
> JIRA
> > >> User. With this model an interested contributor could create a JIRA
> and
> > >> assign it to herself/himself if they feel it is appropriate.
> > >> As I understand it this would extend JIRA assignment privileges beyond
> > >> what is provided in the link given in Pierre's message below.
> > >> Andrew did I understand correctly that for the HBase project the
> project
> > >> administrator does "not" grant assignment priv on a case by case
> basis,
> > but
> > >> rather all registered JIRA users by default have JIRA assignment
> privs?
> > >>
> > >> Thank you
> > >> Suresh
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Andrew Purtell [mailto:apurtell@apache.org]
> > >> Sent: Friday, June 26, 2015 4:21 PM
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: Re: Question on JIRA's
> > >>
> > >> Once the INFRA issue is sorted out the project administrator can grant
> > >> assignment perms to any JIRA user. Many projects operate like this.
> > We're
> > >> doing this over on HBase now. +1 on assignment being a good
> contributor
> > >> motivator, I believe this. At least, I'll admit it would work on me.
> It
> > >> certainly doesn't hurt.
> > >>
> > >> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <
> pierre.smits@gmail.com>
> > >> wrote:
> > >>
> > >> > Roberta, All,
> > >> >
> > >> > Are you sure you want this project to have a methodology for
> > >> > 'assigning' to other contributors? What I have learned over the
> years
> > >> > within a few Apache projects is that when there is a restrictive
> > >> > scheme for the greatest group of contributors (those without
> > >> > privileges) involvement is of the lowest kind possible.
> Non-privileged
> > >> > contributors just register issues (or don't at all), because they
> > >> > don't feel ownership as they only have limited means to influence
> > those
> > >> with privileges.
> > >> > Nothing hampers community growth more than restrictions on
> contributor
> > >> > permissions. And within each Apache project there are already a
> > >> > multitude of permissions schemes to consider and work with (from a
> > >> > managerial point of view), as the underlying tools don't use an
> > >> > integrated Authentication & Authorisation solution (e.g. JIRA vs
> > >> Confluence).
> > >> >
> > >> > A solution to this predicament regarding JIRA issues could be the
> > >> > following: in stead of opting where only contributors with
> privileges
> > >> > (committers) have the permission to do issue assignment, let us opt
> > >> > for the 'Default plus Contributor Assign Permission Scheme' as
> > >> > described in
> > >> >
> > >> >
> > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > >> > orization
> > >> > .
> > >> >
> > >> > Best regards,
> > >> >
> > >> > Pierre Smits
> > >> >
> > >> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > >> > Services & Solutions for Cloud-
> > >> > Based Manufacturing, Professional
> > >> > Services and Retail & Trade
> > >> > http://www.orrtiz.com
> > >> >
> > >> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > >> > <ro...@hp.com>
> > >> > wrote:
> > >> >
> > >> > > Thanks Alice. I knew this was needed to move over Lauchpad but
> > >> > > missed
> > >> > the
> > >> > > assigning of JIRA bugs.
> > >> > >
> > >> > > Roberta
> > >> > >
> > >> > > -----Original Message-----
> > >> > > From: Chen, Alice (Trafodion)
> > >> > > Sent: Thursday, June 25, 2015 9:44 AM
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: RE: Question on JIRA's
> > >> > >
> > >> > > Hello Roberta,
> > >> > >
> > >> > > We are blocked due to
> > >> https://issues.apache.org/jira/browse/INFRA-9701 .
> > >> > > Our project was created but no administrator has been assigned nor
> > >> > > has
> > >> > our
> > >> > > old LP bugs been imported yet.
> > >> > >
> > >> > > Cheers,
> > >> > > Alice
> > >> > >
> > >> > > -----Original Message-----
> > >> > > From: Marton, Roberta S
> > >> > > Sent: Thursday, June 25, 2015 9:29 AM
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: Question on JIRA's
> > >> > >
> > >> > > I have created my first JIRA this morning. A little confusion
> with
> > >> > > the CREATE button but got that resolved.
> > >> > >
> > >> > > Looking at the current set of Trafodion JIRA's I see that they are
> > >> > > all unassigned. I looked around a bit and could not figure out
> how
> > >> > > to assign them.
> > >> > > Perusing the internet, it looks like there is an administrator
> that
> > >> > > can assign JIRA's.
> > >> > > How should we be handling assigning Trafodion JIRAs? Can I just
> > >> > > assign a JIRA to myself without any special privilege?
> > >> > >
> > >> > > And Pierre, great job in putting together the Trafodion wiki page.
> > >> > >
> > >> > > Roberta
> > >> > >
> > >> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Question on JIRA's
Posted by Pierre Smits <pi...@gmail.com>.
The best suggestion to 'speed along INFRA-9701' I can give is:
poke the right person with the right poker at the right place and time!
That will get someone coming into action. You could consider one of the
PPMCs, mentors, or INFRA.
On the other hand, these reappearing postings referencing INFRA-9701 should
be trigger enough...
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Mon, Jul 6, 2015 at 5:44 PM, Suresh Subbiah <su...@gmail.com>
wrote:
> I am eager to try all this out. Does anyone have suggestions on what we can
> we do speed along
> https://issues.apache.org/jira/browse/INFRA-9701 ?
>
> Thanks
> Suresh
>
> On Sat, Jul 4, 2015 at 5:44 PM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > To be accurate, the 'Default plus Contributor Assign Permission Scheme'
> for
> > JIRA applicable to the project or podling allows any contributor (even
> > those without commit-privileges) to assign issues to themselves, but also
> > to others. However, it should be frowned upon if such happens. As this
> > would go against the aspect of common decency amongst volunteers in an
> open
> > source project. Of course a contributor can suggest and ask in a comment
> on
> > the issue who would be the most suitable contributor to address and
> further
> > the issue to resolvement and closure.
> >
> > Though the technical setup of the scheme is very liberal, we can - of
> > course - limit how this podling and if anything goes well during
> incubation
> > upon graduation to TLP the project will apply such by incorporating it in
> > its bylaws.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > Services & Solutions for Cloud-
> > Based Manufacturing, Professional
> > Services and Retail & Trade
> > http://www.orrtiz.com
> >
> > On Sat, Jul 4, 2015 at 1:17 AM, Andrew Purtell <ap...@apache.org>
> > wrote:
> >
> > > > but they cannot reassign issues to themselves which are already
> > assigned
> > > to others.
> > >
> > > Pardon, they might be able to reassign to themselves but not to others.
> > I'm
> > > not clear on which alternative is correct and have no way to test right
> > > now. Worst case, if someone accidentally or improperly assigns
> something
> > > to themselves, someone with Committer role or better can fix it.
> > >
> > >
> > > On Fri, Jul 3, 2015 at 3:12 PM, Andrew Purtell <ap...@apache.org>
> > > wrote:
> > >
> > > > For our project we authorize the role "jira-users" as a contributor.
> > See
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> > > > for what the Contributors role allows. Anyone signed up with an
> account
> > > on
> > > > ASF JIRA can assign themselves unassigned issues, but they cannot
> > > reassign
> > > > issues to themselves which are already assigned to others.
> > > >
> > > > > With this model an interested contributor could create a JIRA and
> > > assign
> > > > it to herself/himself if they feel it is appropriate.
> > > >
> > > > Yes.
> > > >
> > > > It also lets you do things like create a number of issues good for
> > > > beginners, perhaps identified with a label like "beginner". Then
> later
> > an
> > > > interested beginner will be able assign such issues to themselves and
> > get
> > > > going, presumably with guidance once committers notice the email from
> > > JIRA
> > > > that the issue was assigned.
> > > >
> > > >
> > > > On Sat, Jun 27, 2015 at 1:56 PM, Subbiah, Suresh <
> > Suresh.Subbiah@hp.com>
> > > > wrote:
> > > >
> > > >> +1 For JIRA assignment privileges being granted to any registered
> > JIRA
> > > >> User. With this model an interested contributor could create a JIRA
> > and
> > > >> assign it to herself/himself if they feel it is appropriate.
> > > >> As I understand it this would extend JIRA assignment privileges
> beyond
> > > >> what is provided in the link given in Pierre's message below.
> > > >> Andrew did I understand correctly that for the HBase project the
> > project
> > > >> administrator does "not" grant assignment priv on a case by case
> > basis,
> > > but
> > > >> rather all registered JIRA users by default have JIRA assignment
> > privs?
> > > >>
> > > >> Thank you
> > > >> Suresh
> > > >>
> > > >>
> > > >>
> > > >> -----Original Message-----
> > > >> From: Andrew Purtell [mailto:apurtell@apache.org]
> > > >> Sent: Friday, June 26, 2015 4:21 PM
> > > >> To: dev@trafodion.incubator.apache.org
> > > >> Subject: Re: Question on JIRA's
> > > >>
> > > >> Once the INFRA issue is sorted out the project administrator can
> grant
> > > >> assignment perms to any JIRA user. Many projects operate like this.
> > > We're
> > > >> doing this over on HBase now. +1 on assignment being a good
> > contributor
> > > >> motivator, I believe this. At least, I'll admit it would work on me.
> > It
> > > >> certainly doesn't hurt.
> > > >>
> > > >> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <
> > pierre.smits@gmail.com>
> > > >> wrote:
> > > >>
> > > >> > Roberta, All,
> > > >> >
> > > >> > Are you sure you want this project to have a methodology for
> > > >> > 'assigning' to other contributors? What I have learned over the
> > years
> > > >> > within a few Apache projects is that when there is a restrictive
> > > >> > scheme for the greatest group of contributors (those without
> > > >> > privileges) involvement is of the lowest kind possible.
> > Non-privileged
> > > >> > contributors just register issues (or don't at all), because they
> > > >> > don't feel ownership as they only have limited means to influence
> > > those
> > > >> with privileges.
> > > >> > Nothing hampers community growth more than restrictions on
> > contributor
> > > >> > permissions. And within each Apache project there are already a
> > > >> > multitude of permissions schemes to consider and work with (from a
> > > >> > managerial point of view), as the underlying tools don't use an
> > > >> > integrated Authentication & Authorisation solution (e.g. JIRA vs
> > > >> Confluence).
> > > >> >
> > > >> > A solution to this predicament regarding JIRA issues could be the
> > > >> > following: in stead of opting where only contributors with
> > privileges
> > > >> > (committers) have the permission to do issue assignment, let us
> opt
> > > >> > for the 'Default plus Contributor Assign Permission Scheme' as
> > > >> > described in
> > > >> >
> > > >> >
> > > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > > >> > orization
> > > >> > .
> > > >> >
> > > >> > Best regards,
> > > >> >
> > > >> > Pierre Smits
> > > >> >
> > > >> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > > >> > Services & Solutions for Cloud-
> > > >> > Based Manufacturing, Professional
> > > >> > Services and Retail & Trade
> > > >> > http://www.orrtiz.com
> > > >> >
> > > >> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > > >> > <ro...@hp.com>
> > > >> > wrote:
> > > >> >
> > > >> > > Thanks Alice. I knew this was needed to move over Lauchpad but
> > > >> > > missed
> > > >> > the
> > > >> > > assigning of JIRA bugs.
> > > >> > >
> > > >> > > Roberta
> > > >> > >
> > > >> > > -----Original Message-----
> > > >> > > From: Chen, Alice (Trafodion)
> > > >> > > Sent: Thursday, June 25, 2015 9:44 AM
> > > >> > > To: dev@trafodion.incubator.apache.org
> > > >> > > Subject: RE: Question on JIRA's
> > > >> > >
> > > >> > > Hello Roberta,
> > > >> > >
> > > >> > > We are blocked due to
> > > >> https://issues.apache.org/jira/browse/INFRA-9701 .
> > > >> > > Our project was created but no administrator has been assigned
> nor
> > > >> > > has
> > > >> > our
> > > >> > > old LP bugs been imported yet.
> > > >> > >
> > > >> > > Cheers,
> > > >> > > Alice
> > > >> > >
> > > >> > > -----Original Message-----
> > > >> > > From: Marton, Roberta S
> > > >> > > Sent: Thursday, June 25, 2015 9:29 AM
> > > >> > > To: dev@trafodion.incubator.apache.org
> > > >> > > Subject: Question on JIRA's
> > > >> > >
> > > >> > > I have created my first JIRA this morning. A little confusion
> > with
> > > >> > > the CREATE button but got that resolved.
> > > >> > >
> > > >> > > Looking at the current set of Trafodion JIRA's I see that they
> are
> > > >> > > all unassigned. I looked around a bit and could not figure out
> > how
> > > >> > > to assign them.
> > > >> > > Perusing the internet, it looks like there is an administrator
> > that
> > > >> > > can assign JIRA's.
> > > >> > > How should we be handling assigning Trafodion JIRAs? Can I just
> > > >> > > assign a JIRA to myself without any special privilege?
> > > >> > >
> > > >> > > And Pierre, great job in putting together the Trafodion wiki
> page.
> > > >> > >
> > > >> > > Roberta
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Best regards,
> > > >>
> > > >> - Andy
> > > >>
> > > >> Problems worthy of attack prove their worth by hitting back. - Piet
> > Hein
> > > >> (via Tom White)
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > >
> > > > - Andy
> > > >
> > > > Problems worthy of attack prove their worth by hitting back. - Piet
> > Hein
> > > > (via Tom White)
> > > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > > - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
>
Re: Question on JIRA's
Posted by Suresh Subbiah <su...@gmail.com>.
I am eager to try all this out. Does anyone have suggestions on what we can
we do speed along
https://issues.apache.org/jira/browse/INFRA-9701 ?
Thanks
Suresh
On Sat, Jul 4, 2015 at 5:44 PM, Pierre Smits <pi...@gmail.com> wrote:
> To be accurate, the 'Default plus Contributor Assign Permission Scheme' for
> JIRA applicable to the project or podling allows any contributor (even
> those without commit-privileges) to assign issues to themselves, but also
> to others. However, it should be frowned upon if such happens. As this
> would go against the aspect of common decency amongst volunteers in an open
> source project. Of course a contributor can suggest and ask in a comment on
> the issue who would be the most suitable contributor to address and further
> the issue to resolvement and closure.
>
> Though the technical setup of the scheme is very liberal, we can - of
> course - limit how this podling and if anything goes well during incubation
> upon graduation to TLP the project will apply such by incorporating it in
> its bylaws.
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Sat, Jul 4, 2015 at 1:17 AM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > > but they cannot reassign issues to themselves which are already
> assigned
> > to others.
> >
> > Pardon, they might be able to reassign to themselves but not to others.
> I'm
> > not clear on which alternative is correct and have no way to test right
> > now. Worst case, if someone accidentally or improperly assigns something
> > to themselves, someone with Committer role or better can fix it.
> >
> >
> > On Fri, Jul 3, 2015 at 3:12 PM, Andrew Purtell <ap...@apache.org>
> > wrote:
> >
> > > For our project we authorize the role "jira-users" as a contributor.
> See
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> > > for what the Contributors role allows. Anyone signed up with an account
> > on
> > > ASF JIRA can assign themselves unassigned issues, but they cannot
> > reassign
> > > issues to themselves which are already assigned to others.
> > >
> > > > With this model an interested contributor could create a JIRA and
> > assign
> > > it to herself/himself if they feel it is appropriate.
> > >
> > > Yes.
> > >
> > > It also lets you do things like create a number of issues good for
> > > beginners, perhaps identified with a label like "beginner". Then later
> an
> > > interested beginner will be able assign such issues to themselves and
> get
> > > going, presumably with guidance once committers notice the email from
> > JIRA
> > > that the issue was assigned.
> > >
> > >
> > > On Sat, Jun 27, 2015 at 1:56 PM, Subbiah, Suresh <
> Suresh.Subbiah@hp.com>
> > > wrote:
> > >
> > >> +1 For JIRA assignment privileges being granted to any registered
> JIRA
> > >> User. With this model an interested contributor could create a JIRA
> and
> > >> assign it to herself/himself if they feel it is appropriate.
> > >> As I understand it this would extend JIRA assignment privileges beyond
> > >> what is provided in the link given in Pierre's message below.
> > >> Andrew did I understand correctly that for the HBase project the
> project
> > >> administrator does "not" grant assignment priv on a case by case
> basis,
> > but
> > >> rather all registered JIRA users by default have JIRA assignment
> privs?
> > >>
> > >> Thank you
> > >> Suresh
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Andrew Purtell [mailto:apurtell@apache.org]
> > >> Sent: Friday, June 26, 2015 4:21 PM
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: Re: Question on JIRA's
> > >>
> > >> Once the INFRA issue is sorted out the project administrator can grant
> > >> assignment perms to any JIRA user. Many projects operate like this.
> > We're
> > >> doing this over on HBase now. +1 on assignment being a good
> contributor
> > >> motivator, I believe this. At least, I'll admit it would work on me.
> It
> > >> certainly doesn't hurt.
> > >>
> > >> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <
> pierre.smits@gmail.com>
> > >> wrote:
> > >>
> > >> > Roberta, All,
> > >> >
> > >> > Are you sure you want this project to have a methodology for
> > >> > 'assigning' to other contributors? What I have learned over the
> years
> > >> > within a few Apache projects is that when there is a restrictive
> > >> > scheme for the greatest group of contributors (those without
> > >> > privileges) involvement is of the lowest kind possible.
> Non-privileged
> > >> > contributors just register issues (or don't at all), because they
> > >> > don't feel ownership as they only have limited means to influence
> > those
> > >> with privileges.
> > >> > Nothing hampers community growth more than restrictions on
> contributor
> > >> > permissions. And within each Apache project there are already a
> > >> > multitude of permissions schemes to consider and work with (from a
> > >> > managerial point of view), as the underlying tools don't use an
> > >> > integrated Authentication & Authorisation solution (e.g. JIRA vs
> > >> Confluence).
> > >> >
> > >> > A solution to this predicament regarding JIRA issues could be the
> > >> > following: in stead of opting where only contributors with
> privileges
> > >> > (committers) have the permission to do issue assignment, let us opt
> > >> > for the 'Default plus Contributor Assign Permission Scheme' as
> > >> > described in
> > >> >
> > >> >
> > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > >> > orization
> > >> > .
> > >> >
> > >> > Best regards,
> > >> >
> > >> > Pierre Smits
> > >> >
> > >> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > >> > Services & Solutions for Cloud-
> > >> > Based Manufacturing, Professional
> > >> > Services and Retail & Trade
> > >> > http://www.orrtiz.com
> > >> >
> > >> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > >> > <ro...@hp.com>
> > >> > wrote:
> > >> >
> > >> > > Thanks Alice. I knew this was needed to move over Lauchpad but
> > >> > > missed
> > >> > the
> > >> > > assigning of JIRA bugs.
> > >> > >
> > >> > > Roberta
> > >> > >
> > >> > > -----Original Message-----
> > >> > > From: Chen, Alice (Trafodion)
> > >> > > Sent: Thursday, June 25, 2015 9:44 AM
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: RE: Question on JIRA's
> > >> > >
> > >> > > Hello Roberta,
> > >> > >
> > >> > > We are blocked due to
> > >> https://issues.apache.org/jira/browse/INFRA-9701 .
> > >> > > Our project was created but no administrator has been assigned nor
> > >> > > has
> > >> > our
> > >> > > old LP bugs been imported yet.
> > >> > >
> > >> > > Cheers,
> > >> > > Alice
> > >> > >
> > >> > > -----Original Message-----
> > >> > > From: Marton, Roberta S
> > >> > > Sent: Thursday, June 25, 2015 9:29 AM
> > >> > > To: dev@trafodion.incubator.apache.org
> > >> > > Subject: Question on JIRA's
> > >> > >
> > >> > > I have created my first JIRA this morning. A little confusion
> with
> > >> > > the CREATE button but got that resolved.
> > >> > >
> > >> > > Looking at the current set of Trafodion JIRA's I see that they are
> > >> > > all unassigned. I looked around a bit and could not figure out
> how
> > >> > > to assign them.
> > >> > > Perusing the internet, it looks like there is an administrator
> that
> > >> > > can assign JIRA's.
> > >> > > How should we be handling assigning Trafodion JIRAs? Can I just
> > >> > > assign a JIRA to myself without any special privilege?
> > >> > >
> > >> > > And Pierre, great job in putting together the Trafodion wiki page.
> > >> > >
> > >> > > Roberta
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Best regards,
> > >>
> > >> - Andy
> > >>
> > >> Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > >> (via Tom White)
> > >>
> > >
> > >
> > >
> > > --
> > > Best regards,
> > >
> > > - Andy
> > >
> > > Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > > (via Tom White)
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
Re: Question on JIRA's
Posted by Pierre Smits <pi...@gmail.com>.
To be accurate, the 'Default plus Contributor Assign Permission Scheme' for
JIRA applicable to the project or podling allows any contributor (even
those without commit-privileges) to assign issues to themselves, but also
to others. However, it should be frowned upon if such happens. As this
would go against the aspect of common decency amongst volunteers in an open
source project. Of course a contributor can suggest and ask in a comment on
the issue who would be the most suitable contributor to address and further
the issue to resolvement and closure.
Though the technical setup of the scheme is very liberal, we can - of
course - limit how this podling and if anything goes well during incubation
upon graduation to TLP the project will apply such by incorporating it in
its bylaws.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Sat, Jul 4, 2015 at 1:17 AM, Andrew Purtell <ap...@apache.org> wrote:
> > but they cannot reassign issues to themselves which are already assigned
> to others.
>
> Pardon, they might be able to reassign to themselves but not to others. I'm
> not clear on which alternative is correct and have no way to test right
> now. Worst case, if someone accidentally or improperly assigns something
> to themselves, someone with Committer role or better can fix it.
>
>
> On Fri, Jul 3, 2015 at 3:12 PM, Andrew Purtell <ap...@apache.org>
> wrote:
>
> > For our project we authorize the role "jira-users" as a contributor. See
> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> > for what the Contributors role allows. Anyone signed up with an account
> on
> > ASF JIRA can assign themselves unassigned issues, but they cannot
> reassign
> > issues to themselves which are already assigned to others.
> >
> > > With this model an interested contributor could create a JIRA and
> assign
> > it to herself/himself if they feel it is appropriate.
> >
> > Yes.
> >
> > It also lets you do things like create a number of issues good for
> > beginners, perhaps identified with a label like "beginner". Then later an
> > interested beginner will be able assign such issues to themselves and get
> > going, presumably with guidance once committers notice the email from
> JIRA
> > that the issue was assigned.
> >
> >
> > On Sat, Jun 27, 2015 at 1:56 PM, Subbiah, Suresh <Su...@hp.com>
> > wrote:
> >
> >> +1 For JIRA assignment privileges being granted to any registered JIRA
> >> User. With this model an interested contributor could create a JIRA and
> >> assign it to herself/himself if they feel it is appropriate.
> >> As I understand it this would extend JIRA assignment privileges beyond
> >> what is provided in the link given in Pierre's message below.
> >> Andrew did I understand correctly that for the HBase project the project
> >> administrator does "not" grant assignment priv on a case by case basis,
> but
> >> rather all registered JIRA users by default have JIRA assignment privs?
> >>
> >> Thank you
> >> Suresh
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Andrew Purtell [mailto:apurtell@apache.org]
> >> Sent: Friday, June 26, 2015 4:21 PM
> >> To: dev@trafodion.incubator.apache.org
> >> Subject: Re: Question on JIRA's
> >>
> >> Once the INFRA issue is sorted out the project administrator can grant
> >> assignment perms to any JIRA user. Many projects operate like this.
> We're
> >> doing this over on HBase now. +1 on assignment being a good contributor
> >> motivator, I believe this. At least, I'll admit it would work on me. It
> >> certainly doesn't hurt.
> >>
> >> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
> >> wrote:
> >>
> >> > Roberta, All,
> >> >
> >> > Are you sure you want this project to have a methodology for
> >> > 'assigning' to other contributors? What I have learned over the years
> >> > within a few Apache projects is that when there is a restrictive
> >> > scheme for the greatest group of contributors (those without
> >> > privileges) involvement is of the lowest kind possible. Non-privileged
> >> > contributors just register issues (or don't at all), because they
> >> > don't feel ownership as they only have limited means to influence
> those
> >> with privileges.
> >> > Nothing hampers community growth more than restrictions on contributor
> >> > permissions. And within each Apache project there are already a
> >> > multitude of permissions schemes to consider and work with (from a
> >> > managerial point of view), as the underlying tools don't use an
> >> > integrated Authentication & Authorisation solution (e.g. JIRA vs
> >> Confluence).
> >> >
> >> > A solution to this predicament regarding JIRA issues could be the
> >> > following: in stead of opting where only contributors with privileges
> >> > (committers) have the permission to do issue assignment, let us opt
> >> > for the 'Default plus Contributor Assign Permission Scheme' as
> >> > described in
> >> >
> >> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> >> > orization
> >> > .
> >> >
> >> > Best regards,
> >> >
> >> > Pierre Smits
> >> >
> >> > *ORRTIZ.COM <http://www.orrtiz.com>*
> >> > Services & Solutions for Cloud-
> >> > Based Manufacturing, Professional
> >> > Services and Retail & Trade
> >> > http://www.orrtiz.com
> >> >
> >> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> >> > <ro...@hp.com>
> >> > wrote:
> >> >
> >> > > Thanks Alice. I knew this was needed to move over Lauchpad but
> >> > > missed
> >> > the
> >> > > assigning of JIRA bugs.
> >> > >
> >> > > Roberta
> >> > >
> >> > > -----Original Message-----
> >> > > From: Chen, Alice (Trafodion)
> >> > > Sent: Thursday, June 25, 2015 9:44 AM
> >> > > To: dev@trafodion.incubator.apache.org
> >> > > Subject: RE: Question on JIRA's
> >> > >
> >> > > Hello Roberta,
> >> > >
> >> > > We are blocked due to
> >> https://issues.apache.org/jira/browse/INFRA-9701 .
> >> > > Our project was created but no administrator has been assigned nor
> >> > > has
> >> > our
> >> > > old LP bugs been imported yet.
> >> > >
> >> > > Cheers,
> >> > > Alice
> >> > >
> >> > > -----Original Message-----
> >> > > From: Marton, Roberta S
> >> > > Sent: Thursday, June 25, 2015 9:29 AM
> >> > > To: dev@trafodion.incubator.apache.org
> >> > > Subject: Question on JIRA's
> >> > >
> >> > > I have created my first JIRA this morning. A little confusion with
> >> > > the CREATE button but got that resolved.
> >> > >
> >> > > Looking at the current set of Trafodion JIRA's I see that they are
> >> > > all unassigned. I looked around a bit and could not figure out how
> >> > > to assign them.
> >> > > Perusing the internet, it looks like there is an administrator that
> >> > > can assign JIRA's.
> >> > > How should we be handling assigning Trafodion JIRAs? Can I just
> >> > > assign a JIRA to myself without any special privilege?
> >> > >
> >> > > And Pierre, great job in putting together the Trafodion wiki page.
> >> > >
> >> > > Roberta
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Best regards,
> >>
> >> - Andy
> >>
> >> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> >> (via Tom White)
> >>
> >
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
Re: Question on JIRA's
Posted by Andrew Purtell <ap...@apache.org>.
> but they cannot reassign issues to themselves which are already assigned
to others.
Pardon, they might be able to reassign to themselves but not to others. I'm
not clear on which alternative is correct and have no way to test right
now. Worst case, if someone accidentally or improperly assigns something
to themselves, someone with Committer role or better can fix it.
On Fri, Jul 3, 2015 at 3:12 PM, Andrew Purtell <ap...@apache.org> wrote:
> For our project we authorize the role "jira-users" as a contributor. See
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> for what the Contributors role allows. Anyone signed up with an account on
> ASF JIRA can assign themselves unassigned issues, but they cannot reassign
> issues to themselves which are already assigned to others.
>
> > With this model an interested contributor could create a JIRA and assign
> it to herself/himself if they feel it is appropriate.
>
> Yes.
>
> It also lets you do things like create a number of issues good for
> beginners, perhaps identified with a label like "beginner". Then later an
> interested beginner will be able assign such issues to themselves and get
> going, presumably with guidance once committers notice the email from JIRA
> that the issue was assigned.
>
>
> On Sat, Jun 27, 2015 at 1:56 PM, Subbiah, Suresh <Su...@hp.com>
> wrote:
>
>> +1 For JIRA assignment privileges being granted to any registered JIRA
>> User. With this model an interested contributor could create a JIRA and
>> assign it to herself/himself if they feel it is appropriate.
>> As I understand it this would extend JIRA assignment privileges beyond
>> what is provided in the link given in Pierre's message below.
>> Andrew did I understand correctly that for the HBase project the project
>> administrator does "not" grant assignment priv on a case by case basis, but
>> rather all registered JIRA users by default have JIRA assignment privs?
>>
>> Thank you
>> Suresh
>>
>>
>>
>> -----Original Message-----
>> From: Andrew Purtell [mailto:apurtell@apache.org]
>> Sent: Friday, June 26, 2015 4:21 PM
>> To: dev@trafodion.incubator.apache.org
>> Subject: Re: Question on JIRA's
>>
>> Once the INFRA issue is sorted out the project administrator can grant
>> assignment perms to any JIRA user. Many projects operate like this. We're
>> doing this over on HBase now. +1 on assignment being a good contributor
>> motivator, I believe this. At least, I'll admit it would work on me. It
>> certainly doesn't hurt.
>>
>> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
>> wrote:
>>
>> > Roberta, All,
>> >
>> > Are you sure you want this project to have a methodology for
>> > 'assigning' to other contributors? What I have learned over the years
>> > within a few Apache projects is that when there is a restrictive
>> > scheme for the greatest group of contributors (those without
>> > privileges) involvement is of the lowest kind possible. Non-privileged
>> > contributors just register issues (or don't at all), because they
>> > don't feel ownership as they only have limited means to influence those
>> with privileges.
>> > Nothing hampers community growth more than restrictions on contributor
>> > permissions. And within each Apache project there are already a
>> > multitude of permissions schemes to consider and work with (from a
>> > managerial point of view), as the underlying tools don't use an
>> > integrated Authentication & Authorisation solution (e.g. JIRA vs
>> Confluence).
>> >
>> > A solution to this predicament regarding JIRA issues could be the
>> > following: in stead of opting where only contributors with privileges
>> > (committers) have the permission to do issue assignment, let us opt
>> > for the 'Default plus Contributor Assign Permission Scheme' as
>> > described in
>> >
>> > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
>> > orization
>> > .
>> >
>> > Best regards,
>> >
>> > Pierre Smits
>> >
>> > *ORRTIZ.COM <http://www.orrtiz.com>*
>> > Services & Solutions for Cloud-
>> > Based Manufacturing, Professional
>> > Services and Retail & Trade
>> > http://www.orrtiz.com
>> >
>> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
>> > <ro...@hp.com>
>> > wrote:
>> >
>> > > Thanks Alice. I knew this was needed to move over Lauchpad but
>> > > missed
>> > the
>> > > assigning of JIRA bugs.
>> > >
>> > > Roberta
>> > >
>> > > -----Original Message-----
>> > > From: Chen, Alice (Trafodion)
>> > > Sent: Thursday, June 25, 2015 9:44 AM
>> > > To: dev@trafodion.incubator.apache.org
>> > > Subject: RE: Question on JIRA's
>> > >
>> > > Hello Roberta,
>> > >
>> > > We are blocked due to
>> https://issues.apache.org/jira/browse/INFRA-9701 .
>> > > Our project was created but no administrator has been assigned nor
>> > > has
>> > our
>> > > old LP bugs been imported yet.
>> > >
>> > > Cheers,
>> > > Alice
>> > >
>> > > -----Original Message-----
>> > > From: Marton, Roberta S
>> > > Sent: Thursday, June 25, 2015 9:29 AM
>> > > To: dev@trafodion.incubator.apache.org
>> > > Subject: Question on JIRA's
>> > >
>> > > I have created my first JIRA this morning. A little confusion with
>> > > the CREATE button but got that resolved.
>> > >
>> > > Looking at the current set of Trafodion JIRA's I see that they are
>> > > all unassigned. I looked around a bit and could not figure out how
>> > > to assign them.
>> > > Perusing the internet, it looks like there is an administrator that
>> > > can assign JIRA's.
>> > > How should we be handling assigning Trafodion JIRAs? Can I just
>> > > assign a JIRA to myself without any special privilege?
>> > >
>> > > And Pierre, great job in putting together the Trafodion wiki page.
>> > >
>> > > Roberta
>> > >
>> >
>>
>>
>>
>> --
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Question on JIRA's
Posted by Andrew Purtell <ap...@apache.org>.
For our project we authorize the role "jira-users" as a contributor. See
https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
for what the Contributors role allows. Anyone signed up with an account on
ASF JIRA can assign themselves unassigned issues, but they cannot reassign
issues to themselves which are already assigned to others.
> With this model an interested contributor could create a JIRA and assign
it to herself/himself if they feel it is appropriate.
Yes.
It also lets you do things like create a number of issues good for
beginners, perhaps identified with a label like "beginner". Then later an
interested beginner will be able assign such issues to themselves and get
going, presumably with guidance once committers notice the email from JIRA
that the issue was assigned.
On Sat, Jun 27, 2015 at 1:56 PM, Subbiah, Suresh <Su...@hp.com>
wrote:
> +1 For JIRA assignment privileges being granted to any registered JIRA
> User. With this model an interested contributor could create a JIRA and
> assign it to herself/himself if they feel it is appropriate.
> As I understand it this would extend JIRA assignment privileges beyond
> what is provided in the link given in Pierre's message below.
> Andrew did I understand correctly that for the HBase project the project
> administrator does "not" grant assignment priv on a case by case basis, but
> rather all registered JIRA users by default have JIRA assignment privs?
>
> Thank you
> Suresh
>
>
>
> -----Original Message-----
> From: Andrew Purtell [mailto:apurtell@apache.org]
> Sent: Friday, June 26, 2015 4:21 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Question on JIRA's
>
> Once the INFRA issue is sorted out the project administrator can grant
> assignment perms to any JIRA user. Many projects operate like this. We're
> doing this over on HBase now. +1 on assignment being a good contributor
> motivator, I believe this. At least, I'll admit it would work on me. It
> certainly doesn't hurt.
>
> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > Roberta, All,
> >
> > Are you sure you want this project to have a methodology for
> > 'assigning' to other contributors? What I have learned over the years
> > within a few Apache projects is that when there is a restrictive
> > scheme for the greatest group of contributors (those without
> > privileges) involvement is of the lowest kind possible. Non-privileged
> > contributors just register issues (or don't at all), because they
> > don't feel ownership as they only have limited means to influence those
> with privileges.
> > Nothing hampers community growth more than restrictions on contributor
> > permissions. And within each Apache project there are already a
> > multitude of permissions schemes to consider and work with (from a
> > managerial point of view), as the underlying tools don't use an
> > integrated Authentication & Authorisation solution (e.g. JIRA vs
> Confluence).
> >
> > A solution to this predicament regarding JIRA issues could be the
> > following: in stead of opting where only contributors with privileges
> > (committers) have the permission to do issue assignment, let us opt
> > for the 'Default plus Contributor Assign Permission Scheme' as
> > described in
> >
> > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > orization
> > .
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > Services & Solutions for Cloud-
> > Based Manufacturing, Professional
> > Services and Retail & Trade
> > http://www.orrtiz.com
> >
> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > <ro...@hp.com>
> > wrote:
> >
> > > Thanks Alice. I knew this was needed to move over Lauchpad but
> > > missed
> > the
> > > assigning of JIRA bugs.
> > >
> > > Roberta
> > >
> > > -----Original Message-----
> > > From: Chen, Alice (Trafodion)
> > > Sent: Thursday, June 25, 2015 9:44 AM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: RE: Question on JIRA's
> > >
> > > Hello Roberta,
> > >
> > > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701
> .
> > > Our project was created but no administrator has been assigned nor
> > > has
> > our
> > > old LP bugs been imported yet.
> > >
> > > Cheers,
> > > Alice
> > >
> > > -----Original Message-----
> > > From: Marton, Roberta S
> > > Sent: Thursday, June 25, 2015 9:29 AM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: Question on JIRA's
> > >
> > > I have created my first JIRA this morning. A little confusion with
> > > the CREATE button but got that resolved.
> > >
> > > Looking at the current set of Trafodion JIRA's I see that they are
> > > all unassigned. I looked around a bit and could not figure out how
> > > to assign them.
> > > Perusing the internet, it looks like there is an administrator that
> > > can assign JIRA's.
> > > How should we be handling assigning Trafodion JIRAs? Can I just
> > > assign a JIRA to myself without any special privilege?
> > >
> > > And Pierre, great job in putting together the Trafodion wiki page.
> > >
> > > Roberta
> > >
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Question on JIRA's
Posted by Pierre Smits <pi...@gmail.com>.
Hi Selva,
I found the following (albeit somewhat dated), that may shed some light:
https://issues.apache.org/jira/browse/INFRA-2205
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Wed, Jul 1, 2015 at 7:14 PM, Selva Govindarajan <
selva.govindarajan@esgyn.com> wrote:
> Trafodion was using gerrit before it become a apache incubator project.
> Does github have a mechanism to vote for a commit as +2, +1 or -1.like
> gerrit had? If not, how should the reviewers communicate this to the
> committers.
>
>
> Selva
>
> On Wed, Jul 1, 2015 at 7:02 AM, Moran, Amanda <am...@hp.com>
> wrote:
>
> > Pierre-
> >
> > Thanks for the guidance. I know my group (we work on the installer) has
> > worked from the commit then review type of way so it's good to know this
> > information (since I would have continued to do it that way). Thanks
> again!
> >
> > Amanda
> >
> > Sent from my iPhone
> >
> > > On Jul 1, 2015, at 12:11 AM, "Pierre Smits" <pi...@gmail.com>
> > wrote:
> > >
> > > Assigning a JIRA ticket to someone else than yourself should only be
> done
> > > with the explicit consent of the (potential) assignee. Please remember
> > that
> > > communication is the glue that holds a project (or podling) together
> and
> > > happy. Doing a lot of work and then seeing it rejected (or reverted)
> > > without the buy-in from the community can lead to that. Every
> contributor
> > > always needs to keep in mind that, when it comes to code changes,
> > consensus
> > > is required. A single -1 (from a contributor with binding privileges)
> can
> > > have the whole work reverted.
> > >
> > > Especially with improvements (biggies, as opposed to smaller ones like
> > > inproving a comment) should always go through a RTC process (review
> then
> > > commit) in stead of CTR (commit then review) before stuff gets
> persisted
> > > in code repositories.
> > >
> > > Best regards,
> > >
> > > Pierre Smits
> > >
> > > *ORRTIZ.COM <http://www.orrtiz.com>*
> > > Services & Solutions for Cloud-
> > > Based Manufacturing, Professional
> > > Services and Retail & Trade
> > > http://www.orrtiz.com
> > >
> > > On Tue, Jun 30, 2015 at 11:58 PM, Birdsall, Dave <dave.birdsall@hp.com
> >
> > > wrote:
> > >
> > >> I'm +1 at least for the set of privileges that Pierre mentions (
> > >>
> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> > >> ).
> > >>
> > >> The question of whether anyone should be able to assign a JIRA
> (perhaps
> > >> restricted to themselves?) seems at root to be a question of how much
> > >> control and when that committers wish to exercise. If anyone can
> assign
> > to
> > >> themselves, then they might do a lot of work and then get rejected
> when
> > it
> > >> is time to commit. If folks have to wait for a committer to assign
> > >> something to them, they might get feedback earlier. On the other hand
> it
> > >> would be a bottleneck that would tend to stop work rather than
> > encouraging
> > >> it.
> > >>
> > >> I'd like to hear more from Andrew about the specifics of how it is
> done
> > in
> > >> the HBase world.
> > >>
> > >> -----Original Message-----
> > >> From: Subbiah, Suresh
> > >> Sent: Saturday, June 27, 2015 1:56 PM
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: RE: Question on JIRA's
> > >>
> > >> +1 For JIRA assignment privileges being granted to any registered
> JIRA
> > >> User. With this model an interested contributor could create a JIRA
> and
> > >> assign it to herself/himself if they feel it is appropriate.
> > >> As I understand it this would extend JIRA assignment privileges beyond
> > >> what is provided in the link given in Pierre's message below.
> > >> Andrew did I understand correctly that for the HBase project the
> project
> > >> administrator does "not" grant assignment priv on a case by case
> basis,
> > but
> > >> rather all registered JIRA users by default have JIRA assignment
> privs?
> > >>
> > >> Thank you
> > >> Suresh
> > >>
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Andrew Purtell [mailto:apurtell@apache.org]
> > >> Sent: Friday, June 26, 2015 4:21 PM
> > >> To: dev@trafodion.incubator.apache.org
> > >> Subject: Re: Question on JIRA's
> > >>
> > >> Once the INFRA issue is sorted out the project administrator can grant
> > >> assignment perms to any JIRA user. Many projects operate like this.
> > We're
> > >> doing this over on HBase now. +1 on assignment being a good
> contributor
> > >> motivator, I believe this. At least, I'll admit it would work on me.
> It
> > >> certainly doesn't hurt.
> > >>
> > >> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <
> pierre.smits@gmail.com>
> > >> wrote:
> > >>
> > >>> Roberta, All,
> > >>>
> > >>> Are you sure you want this project to have a methodology for
> > >>> 'assigning' to other contributors? What I have learned over the years
> > >>> within a few Apache projects is that when there is a restrictive
> > >>> scheme for the greatest group of contributors (those without
> > >>> privileges) involvement is of the lowest kind possible.
> Non-privileged
> > >>> contributors just register issues (or don't at all), because they
> > >>> don't feel ownership as they only have limited means to influence
> those
> > >> with privileges.
> > >>> Nothing hampers community growth more than restrictions on
> contributor
> > >>> permissions. And within each Apache project there are already a
> > >>> multitude of permissions schemes to consider and work with (from a
> > >>> managerial point of view), as the underlying tools don't use an
> > >>> integrated Authentication & Authorisation solution (e.g. JIRA vs
> > >> Confluence).
> > >>>
> > >>> A solution to this predicament regarding JIRA issues could be the
> > >>> following: in stead of opting where only contributors with privileges
> > >>> (committers) have the permission to do issue assignment, let us opt
> > >>> for the 'Default plus Contributor Assign Permission Scheme' as
> > >>> described in
> > >>>
> > >>>
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > >>> orization
> > >>> .
> > >>>
> > >>> Best regards,
> > >>>
> > >>> Pierre Smits
> > >>>
> > >>> *ORRTIZ.COM <http://www.orrtiz.com>*
> > >>> Services & Solutions for Cloud-
> > >>> Based Manufacturing, Professional
> > >>> Services and Retail & Trade
> > >>> http://www.orrtiz.com
> > >>>
> > >>> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > >>> <ro...@hp.com>
> > >>> wrote:
> > >>>
> > >>>> Thanks Alice. I knew this was needed to move over Lauchpad but
> > >>>> missed
> > >>> the
> > >>>> assigning of JIRA bugs.
> > >>>>
> > >>>> Roberta
> > >>>>
> > >>>> -----Original Message-----
> > >>>> From: Chen, Alice (Trafodion)
> > >>>> Sent: Thursday, June 25, 2015 9:44 AM
> > >>>> To: dev@trafodion.incubator.apache.org
> > >>>> Subject: RE: Question on JIRA's
> > >>>>
> > >>>> Hello Roberta,
> > >>>>
> > >>>> We are blocked due to
> > https://issues.apache.org/jira/browse/INFRA-9701
> > >> .
> > >>>> Our project was created but no administrator has been assigned nor
> > >>>> has
> > >>> our
> > >>>> old LP bugs been imported yet.
> > >>>>
> > >>>> Cheers,
> > >>>> Alice
> > >>>>
> > >>>> -----Original Message-----
> > >>>> From: Marton, Roberta S
> > >>>> Sent: Thursday, June 25, 2015 9:29 AM
> > >>>> To: dev@trafodion.incubator.apache.org
> > >>>> Subject: Question on JIRA's
> > >>>>
> > >>>> I have created my first JIRA this morning. A little confusion with
> > >>>> the CREATE button but got that resolved.
> > >>>>
> > >>>> Looking at the current set of Trafodion JIRA's I see that they are
> > >>>> all unassigned. I looked around a bit and could not figure out how
> > >>>> to assign them.
> > >>>> Perusing the internet, it looks like there is an administrator that
> > >>>> can assign JIRA's.
> > >>>> How should we be handling assigning Trafodion JIRAs? Can I just
> > >>>> assign a JIRA to myself without any special privilege?
> > >>>>
> > >>>> And Pierre, great job in putting together the Trafodion wiki page.
> > >>>>
> > >>>> Roberta
> > >>
> > >>
> > >>
> > >> --
> > >> Best regards,
> > >>
> > >> - Andy
> > >>
> > >> Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> > >> (via Tom White)
> > >>
> >
>
Re: Question on JIRA's
Posted by Selva Govindarajan <se...@esgyn.com>.
Trafodion was using gerrit before it become a apache incubator project.
Does github have a mechanism to vote for a commit as +2, +1 or -1.like
gerrit had? If not, how should the reviewers communicate this to the
committers.
Selva
On Wed, Jul 1, 2015 at 7:02 AM, Moran, Amanda <am...@hp.com>
wrote:
> Pierre-
>
> Thanks for the guidance. I know my group (we work on the installer) has
> worked from the commit then review type of way so it's good to know this
> information (since I would have continued to do it that way). Thanks again!
>
> Amanda
>
> Sent from my iPhone
>
> > On Jul 1, 2015, at 12:11 AM, "Pierre Smits" <pi...@gmail.com>
> wrote:
> >
> > Assigning a JIRA ticket to someone else than yourself should only be done
> > with the explicit consent of the (potential) assignee. Please remember
> that
> > communication is the glue that holds a project (or podling) together and
> > happy. Doing a lot of work and then seeing it rejected (or reverted)
> > without the buy-in from the community can lead to that. Every contributor
> > always needs to keep in mind that, when it comes to code changes,
> consensus
> > is required. A single -1 (from a contributor with binding privileges) can
> > have the whole work reverted.
> >
> > Especially with improvements (biggies, as opposed to smaller ones like
> > inproving a comment) should always go through a RTC process (review then
> > commit) in stead of CTR (commit then review) before stuff gets persisted
> > in code repositories.
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > Services & Solutions for Cloud-
> > Based Manufacturing, Professional
> > Services and Retail & Trade
> > http://www.orrtiz.com
> >
> > On Tue, Jun 30, 2015 at 11:58 PM, Birdsall, Dave <da...@hp.com>
> > wrote:
> >
> >> I'm +1 at least for the set of privileges that Pierre mentions (
> >>
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> >> ).
> >>
> >> The question of whether anyone should be able to assign a JIRA (perhaps
> >> restricted to themselves?) seems at root to be a question of how much
> >> control and when that committers wish to exercise. If anyone can assign
> to
> >> themselves, then they might do a lot of work and then get rejected when
> it
> >> is time to commit. If folks have to wait for a committer to assign
> >> something to them, they might get feedback earlier. On the other hand it
> >> would be a bottleneck that would tend to stop work rather than
> encouraging
> >> it.
> >>
> >> I'd like to hear more from Andrew about the specifics of how it is done
> in
> >> the HBase world.
> >>
> >> -----Original Message-----
> >> From: Subbiah, Suresh
> >> Sent: Saturday, June 27, 2015 1:56 PM
> >> To: dev@trafodion.incubator.apache.org
> >> Subject: RE: Question on JIRA's
> >>
> >> +1 For JIRA assignment privileges being granted to any registered JIRA
> >> User. With this model an interested contributor could create a JIRA and
> >> assign it to herself/himself if they feel it is appropriate.
> >> As I understand it this would extend JIRA assignment privileges beyond
> >> what is provided in the link given in Pierre's message below.
> >> Andrew did I understand correctly that for the HBase project the project
> >> administrator does "not" grant assignment priv on a case by case basis,
> but
> >> rather all registered JIRA users by default have JIRA assignment privs?
> >>
> >> Thank you
> >> Suresh
> >>
> >>
> >>
> >> -----Original Message-----
> >> From: Andrew Purtell [mailto:apurtell@apache.org]
> >> Sent: Friday, June 26, 2015 4:21 PM
> >> To: dev@trafodion.incubator.apache.org
> >> Subject: Re: Question on JIRA's
> >>
> >> Once the INFRA issue is sorted out the project administrator can grant
> >> assignment perms to any JIRA user. Many projects operate like this.
> We're
> >> doing this over on HBase now. +1 on assignment being a good contributor
> >> motivator, I believe this. At least, I'll admit it would work on me. It
> >> certainly doesn't hurt.
> >>
> >> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
> >> wrote:
> >>
> >>> Roberta, All,
> >>>
> >>> Are you sure you want this project to have a methodology for
> >>> 'assigning' to other contributors? What I have learned over the years
> >>> within a few Apache projects is that when there is a restrictive
> >>> scheme for the greatest group of contributors (those without
> >>> privileges) involvement is of the lowest kind possible. Non-privileged
> >>> contributors just register issues (or don't at all), because they
> >>> don't feel ownership as they only have limited means to influence those
> >> with privileges.
> >>> Nothing hampers community growth more than restrictions on contributor
> >>> permissions. And within each Apache project there are already a
> >>> multitude of permissions schemes to consider and work with (from a
> >>> managerial point of view), as the underlying tools don't use an
> >>> integrated Authentication & Authorisation solution (e.g. JIRA vs
> >> Confluence).
> >>>
> >>> A solution to this predicament regarding JIRA issues could be the
> >>> following: in stead of opting where only contributors with privileges
> >>> (committers) have the permission to do issue assignment, let us opt
> >>> for the 'Default plus Contributor Assign Permission Scheme' as
> >>> described in
> >>>
> >>> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> >>> orization
> >>> .
> >>>
> >>> Best regards,
> >>>
> >>> Pierre Smits
> >>>
> >>> *ORRTIZ.COM <http://www.orrtiz.com>*
> >>> Services & Solutions for Cloud-
> >>> Based Manufacturing, Professional
> >>> Services and Retail & Trade
> >>> http://www.orrtiz.com
> >>>
> >>> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> >>> <ro...@hp.com>
> >>> wrote:
> >>>
> >>>> Thanks Alice. I knew this was needed to move over Lauchpad but
> >>>> missed
> >>> the
> >>>> assigning of JIRA bugs.
> >>>>
> >>>> Roberta
> >>>>
> >>>> -----Original Message-----
> >>>> From: Chen, Alice (Trafodion)
> >>>> Sent: Thursday, June 25, 2015 9:44 AM
> >>>> To: dev@trafodion.incubator.apache.org
> >>>> Subject: RE: Question on JIRA's
> >>>>
> >>>> Hello Roberta,
> >>>>
> >>>> We are blocked due to
> https://issues.apache.org/jira/browse/INFRA-9701
> >> .
> >>>> Our project was created but no administrator has been assigned nor
> >>>> has
> >>> our
> >>>> old LP bugs been imported yet.
> >>>>
> >>>> Cheers,
> >>>> Alice
> >>>>
> >>>> -----Original Message-----
> >>>> From: Marton, Roberta S
> >>>> Sent: Thursday, June 25, 2015 9:29 AM
> >>>> To: dev@trafodion.incubator.apache.org
> >>>> Subject: Question on JIRA's
> >>>>
> >>>> I have created my first JIRA this morning. A little confusion with
> >>>> the CREATE button but got that resolved.
> >>>>
> >>>> Looking at the current set of Trafodion JIRA's I see that they are
> >>>> all unassigned. I looked around a bit and could not figure out how
> >>>> to assign them.
> >>>> Perusing the internet, it looks like there is an administrator that
> >>>> can assign JIRA's.
> >>>> How should we be handling assigning Trafodion JIRAs? Can I just
> >>>> assign a JIRA to myself without any special privilege?
> >>>>
> >>>> And Pierre, great job in putting together the Trafodion wiki page.
> >>>>
> >>>> Roberta
> >>
> >>
> >>
> >> --
> >> Best regards,
> >>
> >> - Andy
> >>
> >> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> >> (via Tom White)
> >>
>
Re: Question on JIRA's
Posted by "Moran, Amanda" <am...@hp.com>.
Pierre-
Thanks for the guidance. I know my group (we work on the installer) has worked from the commit then review type of way so it's good to know this information (since I would have continued to do it that way). Thanks again!
Amanda
Sent from my iPhone
> On Jul 1, 2015, at 12:11 AM, "Pierre Smits" <pi...@gmail.com> wrote:
>
> Assigning a JIRA ticket to someone else than yourself should only be done
> with the explicit consent of the (potential) assignee. Please remember that
> communication is the glue that holds a project (or podling) together and
> happy. Doing a lot of work and then seeing it rejected (or reverted)
> without the buy-in from the community can lead to that. Every contributor
> always needs to keep in mind that, when it comes to code changes, consensus
> is required. A single -1 (from a contributor with binding privileges) can
> have the whole work reverted.
>
> Especially with improvements (biggies, as opposed to smaller ones like
> inproving a comment) should always go through a RTC process (review then
> commit) in stead of CTR (commit then review) before stuff gets persisted
> in code repositories.
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Tue, Jun 30, 2015 at 11:58 PM, Birdsall, Dave <da...@hp.com>
> wrote:
>
>> I'm +1 at least for the set of privileges that Pierre mentions (
>> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
>> ).
>>
>> The question of whether anyone should be able to assign a JIRA (perhaps
>> restricted to themselves?) seems at root to be a question of how much
>> control and when that committers wish to exercise. If anyone can assign to
>> themselves, then they might do a lot of work and then get rejected when it
>> is time to commit. If folks have to wait for a committer to assign
>> something to them, they might get feedback earlier. On the other hand it
>> would be a bottleneck that would tend to stop work rather than encouraging
>> it.
>>
>> I'd like to hear more from Andrew about the specifics of how it is done in
>> the HBase world.
>>
>> -----Original Message-----
>> From: Subbiah, Suresh
>> Sent: Saturday, June 27, 2015 1:56 PM
>> To: dev@trafodion.incubator.apache.org
>> Subject: RE: Question on JIRA's
>>
>> +1 For JIRA assignment privileges being granted to any registered JIRA
>> User. With this model an interested contributor could create a JIRA and
>> assign it to herself/himself if they feel it is appropriate.
>> As I understand it this would extend JIRA assignment privileges beyond
>> what is provided in the link given in Pierre's message below.
>> Andrew did I understand correctly that for the HBase project the project
>> administrator does "not" grant assignment priv on a case by case basis, but
>> rather all registered JIRA users by default have JIRA assignment privs?
>>
>> Thank you
>> Suresh
>>
>>
>>
>> -----Original Message-----
>> From: Andrew Purtell [mailto:apurtell@apache.org]
>> Sent: Friday, June 26, 2015 4:21 PM
>> To: dev@trafodion.incubator.apache.org
>> Subject: Re: Question on JIRA's
>>
>> Once the INFRA issue is sorted out the project administrator can grant
>> assignment perms to any JIRA user. Many projects operate like this. We're
>> doing this over on HBase now. +1 on assignment being a good contributor
>> motivator, I believe this. At least, I'll admit it would work on me. It
>> certainly doesn't hurt.
>>
>> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
>> wrote:
>>
>>> Roberta, All,
>>>
>>> Are you sure you want this project to have a methodology for
>>> 'assigning' to other contributors? What I have learned over the years
>>> within a few Apache projects is that when there is a restrictive
>>> scheme for the greatest group of contributors (those without
>>> privileges) involvement is of the lowest kind possible. Non-privileged
>>> contributors just register issues (or don't at all), because they
>>> don't feel ownership as they only have limited means to influence those
>> with privileges.
>>> Nothing hampers community growth more than restrictions on contributor
>>> permissions. And within each Apache project there are already a
>>> multitude of permissions schemes to consider and work with (from a
>>> managerial point of view), as the underlying tools don't use an
>>> integrated Authentication & Authorisation solution (e.g. JIRA vs
>> Confluence).
>>>
>>> A solution to this predicament regarding JIRA issues could be the
>>> following: in stead of opting where only contributors with privileges
>>> (committers) have the permission to do issue assignment, let us opt
>>> for the 'Default plus Contributor Assign Permission Scheme' as
>>> described in
>>>
>>> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
>>> orization
>>> .
>>>
>>> Best regards,
>>>
>>> Pierre Smits
>>>
>>> *ORRTIZ.COM <http://www.orrtiz.com>*
>>> Services & Solutions for Cloud-
>>> Based Manufacturing, Professional
>>> Services and Retail & Trade
>>> http://www.orrtiz.com
>>>
>>> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
>>> <ro...@hp.com>
>>> wrote:
>>>
>>>> Thanks Alice. I knew this was needed to move over Lauchpad but
>>>> missed
>>> the
>>>> assigning of JIRA bugs.
>>>>
>>>> Roberta
>>>>
>>>> -----Original Message-----
>>>> From: Chen, Alice (Trafodion)
>>>> Sent: Thursday, June 25, 2015 9:44 AM
>>>> To: dev@trafodion.incubator.apache.org
>>>> Subject: RE: Question on JIRA's
>>>>
>>>> Hello Roberta,
>>>>
>>>> We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701
>> .
>>>> Our project was created but no administrator has been assigned nor
>>>> has
>>> our
>>>> old LP bugs been imported yet.
>>>>
>>>> Cheers,
>>>> Alice
>>>>
>>>> -----Original Message-----
>>>> From: Marton, Roberta S
>>>> Sent: Thursday, June 25, 2015 9:29 AM
>>>> To: dev@trafodion.incubator.apache.org
>>>> Subject: Question on JIRA's
>>>>
>>>> I have created my first JIRA this morning. A little confusion with
>>>> the CREATE button but got that resolved.
>>>>
>>>> Looking at the current set of Trafodion JIRA's I see that they are
>>>> all unassigned. I looked around a bit and could not figure out how
>>>> to assign them.
>>>> Perusing the internet, it looks like there is an administrator that
>>>> can assign JIRA's.
>>>> How should we be handling assigning Trafodion JIRAs? Can I just
>>>> assign a JIRA to myself without any special privilege?
>>>>
>>>> And Pierre, great job in putting together the Trafodion wiki page.
>>>>
>>>> Roberta
>>
>>
>>
>> --
>> Best regards,
>>
>> - Andy
>>
>> Problems worthy of attack prove their worth by hitting back. - Piet Hein
>> (via Tom White)
>>
Re: Question on JIRA's
Posted by Andrew Purtell <ap...@apache.org>.
+1, it's a good idea not to reassign a JIRA without consent of the current
assignee, or if the current assignee doesn't respond to an inquiry on the
JIRA after a reasonable amount of time. Helps prevent misunderstandings and
hurt feelings.
On Wed, Jul 1, 2015 at 12:10 AM, Pierre Smits <pi...@gmail.com>
wrote:
> Assigning a JIRA ticket to someone else than yourself should only be done
> with the explicit consent of the (potential) assignee. Please remember that
> communication is the glue that holds a project (or podling) together and
> happy. Doing a lot of work and then seeing it rejected (or reverted)
> without the buy-in from the community can lead to that. Every contributor
> always needs to keep in mind that, when it comes to code changes, consensus
> is required. A single -1 (from a contributor with binding privileges) can
> have the whole work reverted.
>
> Especially with improvements (biggies, as opposed to smaller ones like
> inproving a comment) should always go through a RTC process (review then
> commit) in stead of CTR (commit then review) before stuff gets persisted
> in code repositories.
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Tue, Jun 30, 2015 at 11:58 PM, Birdsall, Dave <da...@hp.com>
> wrote:
>
> > I'm +1 at least for the set of privileges that Pierre mentions (
> >
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> > ).
> >
> > The question of whether anyone should be able to assign a JIRA (perhaps
> > restricted to themselves?) seems at root to be a question of how much
> > control and when that committers wish to exercise. If anyone can assign
> to
> > themselves, then they might do a lot of work and then get rejected when
> it
> > is time to commit. If folks have to wait for a committer to assign
> > something to them, they might get feedback earlier. On the other hand it
> > would be a bottleneck that would tend to stop work rather than
> encouraging
> > it.
> >
> > I'd like to hear more from Andrew about the specifics of how it is done
> in
> > the HBase world.
> >
> > -----Original Message-----
> > From: Subbiah, Suresh
> > Sent: Saturday, June 27, 2015 1:56 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Question on JIRA's
> >
> > +1 For JIRA assignment privileges being granted to any registered JIRA
> > User. With this model an interested contributor could create a JIRA and
> > assign it to herself/himself if they feel it is appropriate.
> > As I understand it this would extend JIRA assignment privileges beyond
> > what is provided in the link given in Pierre's message below.
> > Andrew did I understand correctly that for the HBase project the project
> > administrator does "not" grant assignment priv on a case by case basis,
> but
> > rather all registered JIRA users by default have JIRA assignment privs?
> >
> > Thank you
> > Suresh
> >
> >
> >
> > -----Original Message-----
> > From: Andrew Purtell [mailto:apurtell@apache.org]
> > Sent: Friday, June 26, 2015 4:21 PM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Re: Question on JIRA's
> >
> > Once the INFRA issue is sorted out the project administrator can grant
> > assignment perms to any JIRA user. Many projects operate like this. We're
> > doing this over on HBase now. +1 on assignment being a good contributor
> > motivator, I believe this. At least, I'll admit it would work on me. It
> > certainly doesn't hurt.
> >
> > On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
> > wrote:
> >
> > > Roberta, All,
> > >
> > > Are you sure you want this project to have a methodology for
> > > 'assigning' to other contributors? What I have learned over the years
> > > within a few Apache projects is that when there is a restrictive
> > > scheme for the greatest group of contributors (those without
> > > privileges) involvement is of the lowest kind possible. Non-privileged
> > > contributors just register issues (or don't at all), because they
> > > don't feel ownership as they only have limited means to influence those
> > with privileges.
> > > Nothing hampers community growth more than restrictions on contributor
> > > permissions. And within each Apache project there are already a
> > > multitude of permissions schemes to consider and work with (from a
> > > managerial point of view), as the underlying tools don't use an
> > > integrated Authentication & Authorisation solution (e.g. JIRA vs
> > Confluence).
> > >
> > > A solution to this predicament regarding JIRA issues could be the
> > > following: in stead of opting where only contributors with privileges
> > > (committers) have the permission to do issue assignment, let us opt
> > > for the 'Default plus Contributor Assign Permission Scheme' as
> > > described in
> > >
> > > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > > orization
> > > .
> > >
> > > Best regards,
> > >
> > > Pierre Smits
> > >
> > > *ORRTIZ.COM <http://www.orrtiz.com>*
> > > Services & Solutions for Cloud-
> > > Based Manufacturing, Professional
> > > Services and Retail & Trade
> > > http://www.orrtiz.com
> > >
> > > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > > <ro...@hp.com>
> > > wrote:
> > >
> > > > Thanks Alice. I knew this was needed to move over Lauchpad but
> > > > missed
> > > the
> > > > assigning of JIRA bugs.
> > > >
> > > > Roberta
> > > >
> > > > -----Original Message-----
> > > > From: Chen, Alice (Trafodion)
> > > > Sent: Thursday, June 25, 2015 9:44 AM
> > > > To: dev@trafodion.incubator.apache.org
> > > > Subject: RE: Question on JIRA's
> > > >
> > > > Hello Roberta,
> > > >
> > > > We are blocked due to
> https://issues.apache.org/jira/browse/INFRA-9701
> > .
> > > > Our project was created but no administrator has been assigned nor
> > > > has
> > > our
> > > > old LP bugs been imported yet.
> > > >
> > > > Cheers,
> > > > Alice
> > > >
> > > > -----Original Message-----
> > > > From: Marton, Roberta S
> > > > Sent: Thursday, June 25, 2015 9:29 AM
> > > > To: dev@trafodion.incubator.apache.org
> > > > Subject: Question on JIRA's
> > > >
> > > > I have created my first JIRA this morning. A little confusion with
> > > > the CREATE button but got that resolved.
> > > >
> > > > Looking at the current set of Trafodion JIRA's I see that they are
> > > > all unassigned. I looked around a bit and could not figure out how
> > > > to assign them.
> > > > Perusing the internet, it looks like there is an administrator that
> > > > can assign JIRA's.
> > > > How should we be handling assigning Trafodion JIRAs? Can I just
> > > > assign a JIRA to myself without any special privilege?
> > > >
> > > > And Pierre, great job in putting together the Trafodion wiki page.
> > > >
> > > > Roberta
> > > >
> > >
> >
> >
> >
> > --
> > Best regards,
> >
> > - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Question on JIRA's
Posted by Pierre Smits <pi...@gmail.com>.
Assigning a JIRA ticket to someone else than yourself should only be done
with the explicit consent of the (potential) assignee. Please remember that
communication is the glue that holds a project (or podling) together and
happy. Doing a lot of work and then seeing it rejected (or reverted)
without the buy-in from the community can lead to that. Every contributor
always needs to keep in mind that, when it comes to code changes, consensus
is required. A single -1 (from a contributor with binding privileges) can
have the whole work reverted.
Especially with improvements (biggies, as opposed to smaller ones like
inproving a comment) should always go through a RTC process (review then
commit) in stead of CTR (commit then review) before stuff gets persisted
in code repositories.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Tue, Jun 30, 2015 at 11:58 PM, Birdsall, Dave <da...@hp.com>
wrote:
> I'm +1 at least for the set of privileges that Pierre mentions (
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> ).
>
> The question of whether anyone should be able to assign a JIRA (perhaps
> restricted to themselves?) seems at root to be a question of how much
> control and when that committers wish to exercise. If anyone can assign to
> themselves, then they might do a lot of work and then get rejected when it
> is time to commit. If folks have to wait for a committer to assign
> something to them, they might get feedback earlier. On the other hand it
> would be a bottleneck that would tend to stop work rather than encouraging
> it.
>
> I'd like to hear more from Andrew about the specifics of how it is done in
> the HBase world.
>
> -----Original Message-----
> From: Subbiah, Suresh
> Sent: Saturday, June 27, 2015 1:56 PM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Question on JIRA's
>
> +1 For JIRA assignment privileges being granted to any registered JIRA
> User. With this model an interested contributor could create a JIRA and
> assign it to herself/himself if they feel it is appropriate.
> As I understand it this would extend JIRA assignment privileges beyond
> what is provided in the link given in Pierre's message below.
> Andrew did I understand correctly that for the HBase project the project
> administrator does "not" grant assignment priv on a case by case basis, but
> rather all registered JIRA users by default have JIRA assignment privs?
>
> Thank you
> Suresh
>
>
>
> -----Original Message-----
> From: Andrew Purtell [mailto:apurtell@apache.org]
> Sent: Friday, June 26, 2015 4:21 PM
> To: dev@trafodion.incubator.apache.org
> Subject: Re: Question on JIRA's
>
> Once the INFRA issue is sorted out the project administrator can grant
> assignment perms to any JIRA user. Many projects operate like this. We're
> doing this over on HBase now. +1 on assignment being a good contributor
> motivator, I believe this. At least, I'll admit it would work on me. It
> certainly doesn't hurt.
>
> On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
> wrote:
>
> > Roberta, All,
> >
> > Are you sure you want this project to have a methodology for
> > 'assigning' to other contributors? What I have learned over the years
> > within a few Apache projects is that when there is a restrictive
> > scheme for the greatest group of contributors (those without
> > privileges) involvement is of the lowest kind possible. Non-privileged
> > contributors just register issues (or don't at all), because they
> > don't feel ownership as they only have limited means to influence those
> with privileges.
> > Nothing hampers community growth more than restrictions on contributor
> > permissions. And within each Apache project there are already a
> > multitude of permissions schemes to consider and work with (from a
> > managerial point of view), as the underlying tools don't use an
> > integrated Authentication & Authorisation solution (e.g. JIRA vs
> Confluence).
> >
> > A solution to this predicament regarding JIRA issues could be the
> > following: in stead of opting where only contributors with privileges
> > (committers) have the permission to do issue assignment, let us opt
> > for the 'Default plus Contributor Assign Permission Scheme' as
> > described in
> >
> > https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> > orization
> > .
> >
> > Best regards,
> >
> > Pierre Smits
> >
> > *ORRTIZ.COM <http://www.orrtiz.com>*
> > Services & Solutions for Cloud-
> > Based Manufacturing, Professional
> > Services and Retail & Trade
> > http://www.orrtiz.com
> >
> > On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> > <ro...@hp.com>
> > wrote:
> >
> > > Thanks Alice. I knew this was needed to move over Lauchpad but
> > > missed
> > the
> > > assigning of JIRA bugs.
> > >
> > > Roberta
> > >
> > > -----Original Message-----
> > > From: Chen, Alice (Trafodion)
> > > Sent: Thursday, June 25, 2015 9:44 AM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: RE: Question on JIRA's
> > >
> > > Hello Roberta,
> > >
> > > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701
> .
> > > Our project was created but no administrator has been assigned nor
> > > has
> > our
> > > old LP bugs been imported yet.
> > >
> > > Cheers,
> > > Alice
> > >
> > > -----Original Message-----
> > > From: Marton, Roberta S
> > > Sent: Thursday, June 25, 2015 9:29 AM
> > > To: dev@trafodion.incubator.apache.org
> > > Subject: Question on JIRA's
> > >
> > > I have created my first JIRA this morning. A little confusion with
> > > the CREATE button but got that resolved.
> > >
> > > Looking at the current set of Trafodion JIRA's I see that they are
> > > all unassigned. I looked around a bit and could not figure out how
> > > to assign them.
> > > Perusing the internet, it looks like there is an administrator that
> > > can assign JIRA's.
> > > How should we be handling assigning Trafodion JIRAs? Can I just
> > > assign a JIRA to myself without any special privilege?
> > >
> > > And Pierre, great job in putting together the Trafodion wiki page.
> > >
> > > Roberta
> > >
> >
>
>
>
> --
> Best regards,
>
> - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
RE: Question on JIRA's
Posted by "Birdsall, Dave" <da...@hp.com>.
I'm +1 at least for the set of privileges that Pierre mentions (https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization).
The question of whether anyone should be able to assign a JIRA (perhaps restricted to themselves?) seems at root to be a question of how much control and when that committers wish to exercise. If anyone can assign to themselves, then they might do a lot of work and then get rejected when it is time to commit. If folks have to wait for a committer to assign something to them, they might get feedback earlier. On the other hand it would be a bottleneck that would tend to stop work rather than encouraging it.
I'd like to hear more from Andrew about the specifics of how it is done in the HBase world.
-----Original Message-----
From: Subbiah, Suresh
Sent: Saturday, June 27, 2015 1:56 PM
To: dev@trafodion.incubator.apache.org
Subject: RE: Question on JIRA's
+1 For JIRA assignment privileges being granted to any registered JIRA User. With this model an interested contributor could create a JIRA and assign it to herself/himself if they feel it is appropriate.
As I understand it this would extend JIRA assignment privileges beyond what is provided in the link given in Pierre's message below.
Andrew did I understand correctly that for the HBase project the project administrator does "not" grant assignment priv on a case by case basis, but rather all registered JIRA users by default have JIRA assignment privs?
Thank you
Suresh
-----Original Message-----
From: Andrew Purtell [mailto:apurtell@apache.org]
Sent: Friday, June 26, 2015 4:21 PM
To: dev@trafodion.incubator.apache.org
Subject: Re: Question on JIRA's
Once the INFRA issue is sorted out the project administrator can grant assignment perms to any JIRA user. Many projects operate like this. We're doing this over on HBase now. +1 on assignment being a good contributor motivator, I believe this. At least, I'll admit it would work on me. It certainly doesn't hurt.
On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
wrote:
> Roberta, All,
>
> Are you sure you want this project to have a methodology for
> 'assigning' to other contributors? What I have learned over the years
> within a few Apache projects is that when there is a restrictive
> scheme for the greatest group of contributors (those without
> privileges) involvement is of the lowest kind possible. Non-privileged
> contributors just register issues (or don't at all), because they
> don't feel ownership as they only have limited means to influence those with privileges.
> Nothing hampers community growth more than restrictions on contributor
> permissions. And within each Apache project there are already a
> multitude of permissions schemes to consider and work with (from a
> managerial point of view), as the underlying tools don't use an
> integrated Authentication & Authorisation solution (e.g. JIRA vs Confluence).
>
> A solution to this predicament regarding JIRA issues could be the
> following: in stead of opting where only contributors with privileges
> (committers) have the permission to do issue assignment, let us opt
> for the 'Default plus Contributor Assign Permission Scheme' as
> described in
>
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> orization
> .
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> <ro...@hp.com>
> wrote:
>
> > Thanks Alice. I knew this was needed to move over Lauchpad but
> > missed
> the
> > assigning of JIRA bugs.
> >
> > Roberta
> >
> > -----Original Message-----
> > From: Chen, Alice (Trafodion)
> > Sent: Thursday, June 25, 2015 9:44 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Question on JIRA's
> >
> > Hello Roberta,
> >
> > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 .
> > Our project was created but no administrator has been assigned nor
> > has
> our
> > old LP bugs been imported yet.
> >
> > Cheers,
> > Alice
> >
> > -----Original Message-----
> > From: Marton, Roberta S
> > Sent: Thursday, June 25, 2015 9:29 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Question on JIRA's
> >
> > I have created my first JIRA this morning. A little confusion with
> > the CREATE button but got that resolved.
> >
> > Looking at the current set of Trafodion JIRA's I see that they are
> > all unassigned. I looked around a bit and could not figure out how
> > to assign them.
> > Perusing the internet, it looks like there is an administrator that
> > can assign JIRA's.
> > How should we be handling assigning Trafodion JIRAs? Can I just
> > assign a JIRA to myself without any special privilege?
> >
> > And Pierre, great job in putting together the Trafodion wiki page.
> >
> > Roberta
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
RE: Question on JIRA's
Posted by "Subbiah, Suresh" <Su...@hp.com>.
+1 For JIRA assignment privileges being granted to any registered JIRA User. With this model an interested contributor could create a JIRA and assign it to herself/himself if they feel it is appropriate.
As I understand it this would extend JIRA assignment privileges beyond what is provided in the link given in Pierre's message below.
Andrew did I understand correctly that for the HBase project the project administrator does "not" grant assignment priv on a case by case basis, but rather all registered JIRA users by default have JIRA assignment privs?
Thank you
Suresh
-----Original Message-----
From: Andrew Purtell [mailto:apurtell@apache.org]
Sent: Friday, June 26, 2015 4:21 PM
To: dev@trafodion.incubator.apache.org
Subject: Re: Question on JIRA's
Once the INFRA issue is sorted out the project administrator can grant assignment perms to any JIRA user. Many projects operate like this. We're doing this over on HBase now. +1 on assignment being a good contributor motivator, I believe this. At least, I'll admit it would work on me. It certainly doesn't hurt.
On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
wrote:
> Roberta, All,
>
> Are you sure you want this project to have a methodology for
> 'assigning' to other contributors? What I have learned over the years
> within a few Apache projects is that when there is a restrictive
> scheme for the greatest group of contributors (those without
> privileges) involvement is of the lowest kind possible. Non-privileged
> contributors just register issues (or don't at all), because they
> don't feel ownership as they only have limited means to influence those with privileges.
> Nothing hampers community growth more than restrictions on contributor
> permissions. And within each Apache project there are already a
> multitude of permissions schemes to consider and work with (from a
> managerial point of view), as the underlying tools don't use an
> integrated Authentication & Authorisation solution (e.g. JIRA vs Confluence).
>
> A solution to this predicament regarding JIRA issues could be the
> following: in stead of opting where only contributors with privileges
> (committers) have the permission to do issue assignment, let us opt
> for the 'Default plus Contributor Assign Permission Scheme' as
> described in
>
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Auth
> orization
> .
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S
> <ro...@hp.com>
> wrote:
>
> > Thanks Alice. I knew this was needed to move over Lauchpad but
> > missed
> the
> > assigning of JIRA bugs.
> >
> > Roberta
> >
> > -----Original Message-----
> > From: Chen, Alice (Trafodion)
> > Sent: Thursday, June 25, 2015 9:44 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Question on JIRA's
> >
> > Hello Roberta,
> >
> > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 .
> > Our project was created but no administrator has been assigned nor
> > has
> our
> > old LP bugs been imported yet.
> >
> > Cheers,
> > Alice
> >
> > -----Original Message-----
> > From: Marton, Roberta S
> > Sent: Thursday, June 25, 2015 9:29 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Question on JIRA's
> >
> > I have created my first JIRA this morning. A little confusion with
> > the CREATE button but got that resolved.
> >
> > Looking at the current set of Trafodion JIRA's I see that they are
> > all unassigned. I looked around a bit and could not figure out how
> > to assign them.
> > Perusing the internet, it looks like there is an administrator that
> > can assign JIRA's.
> > How should we be handling assigning Trafodion JIRAs? Can I just
> > assign a JIRA to myself without any special privilege?
> >
> > And Pierre, great job in putting together the Trafodion wiki page.
> >
> > Roberta
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
Re: Question on JIRA's
Posted by Andrew Purtell <ap...@apache.org>.
Once the INFRA issue is sorted out the project administrator can grant
assignment perms to any JIRA user. Many projects operate like this. We're
doing this over on HBase now. +1 on assignment being a good contributor
motivator, I believe this. At least, I'll admit it would work on me. It
certainly doesn't hurt.
On Fri, Jun 26, 2015 at 12:41 AM, Pierre Smits <pi...@gmail.com>
wrote:
> Roberta, All,
>
> Are you sure you want this project to have a methodology for 'assigning' to
> other contributors? What I have learned over the years within a few Apache
> projects is that when there is a restrictive scheme for the greatest group
> of contributors (those without privileges) involvement is of the lowest
> kind possible. Non-privileged contributors just register issues (or don't
> at all), because they don't feel ownership as they only have limited means
> to influence those with privileges.
> Nothing hampers community growth more than restrictions on contributor
> permissions. And within each Apache project there are already a multitude
> of permissions schemes to consider and work with (from a managerial point
> of view), as the underlying tools don't use an integrated Authentication &
> Authorisation solution (e.g. JIRA vs Confluence).
>
> A solution to this predicament regarding JIRA issues could be the
> following: in stead of opting where only contributors with privileges
> (committers) have the permission to do issue assignment, let us opt for the
> 'Default plus Contributor Assign Permission Scheme' as described in
>
> https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
> .
>
> Best regards,
>
> Pierre Smits
>
> *ORRTIZ.COM <http://www.orrtiz.com>*
> Services & Solutions for Cloud-
> Based Manufacturing, Professional
> Services and Retail & Trade
> http://www.orrtiz.com
>
> On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S <ro...@hp.com>
> wrote:
>
> > Thanks Alice. I knew this was needed to move over Lauchpad but missed
> the
> > assigning of JIRA bugs.
> >
> > Roberta
> >
> > -----Original Message-----
> > From: Chen, Alice (Trafodion)
> > Sent: Thursday, June 25, 2015 9:44 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: RE: Question on JIRA's
> >
> > Hello Roberta,
> >
> > We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 .
> > Our project was created but no administrator has been assigned nor has
> our
> > old LP bugs been imported yet.
> >
> > Cheers,
> > Alice
> >
> > -----Original Message-----
> > From: Marton, Roberta S
> > Sent: Thursday, June 25, 2015 9:29 AM
> > To: dev@trafodion.incubator.apache.org
> > Subject: Question on JIRA's
> >
> > I have created my first JIRA this morning. A little confusion with the
> > CREATE button but got that resolved.
> >
> > Looking at the current set of Trafodion JIRA's I see that they are all
> > unassigned. I looked around a bit and could not figure out how to assign
> > them.
> > Perusing the internet, it looks like there is an administrator that can
> > assign JIRA's.
> > How should we be handling assigning Trafodion JIRAs? Can I just assign a
> > JIRA to myself without any special privilege?
> >
> > And Pierre, great job in putting together the Trafodion wiki page.
> >
> > Roberta
> >
>
--
Best regards,
- Andy
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)
Re: Question on JIRA's
Posted by Pierre Smits <pi...@gmail.com>.
Roberta, All,
Are you sure you want this project to have a methodology for 'assigning' to
other contributors? What I have learned over the years within a few Apache
projects is that when there is a restrictive scheme for the greatest group
of contributors (those without privileges) involvement is of the lowest
kind possible. Non-privileged contributors just register issues (or don't
at all), because they don't feel ownership as they only have limited means
to influence those with privileges.
Nothing hampers community growth more than restrictions on contributor
permissions. And within each Apache project there are already a multitude
of permissions schemes to consider and work with (from a managerial point
of view), as the underlying tools don't use an integrated Authentication &
Authorisation solution (e.g. JIRA vs Confluence).
A solution to this predicament regarding JIRA issues could be the
following: in stead of opting where only contributors with privileges
(committers) have the permission to do issue assignment, let us opt for the
'Default plus Contributor Assign Permission Scheme' as described in
https://cwiki.apache.org/confluence/display/INFRA/Role+Based+JIRA+Authorization
.
Best regards,
Pierre Smits
*ORRTIZ.COM <http://www.orrtiz.com>*
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com
On Thu, Jun 25, 2015 at 7:09 PM, Marton, Roberta S <ro...@hp.com>
wrote:
> Thanks Alice. I knew this was needed to move over Lauchpad but missed the
> assigning of JIRA bugs.
>
> Roberta
>
> -----Original Message-----
> From: Chen, Alice (Trafodion)
> Sent: Thursday, June 25, 2015 9:44 AM
> To: dev@trafodion.incubator.apache.org
> Subject: RE: Question on JIRA's
>
> Hello Roberta,
>
> We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 .
> Our project was created but no administrator has been assigned nor has our
> old LP bugs been imported yet.
>
> Cheers,
> Alice
>
> -----Original Message-----
> From: Marton, Roberta S
> Sent: Thursday, June 25, 2015 9:29 AM
> To: dev@trafodion.incubator.apache.org
> Subject: Question on JIRA's
>
> I have created my first JIRA this morning. A little confusion with the
> CREATE button but got that resolved.
>
> Looking at the current set of Trafodion JIRA's I see that they are all
> unassigned. I looked around a bit and could not figure out how to assign
> them.
> Perusing the internet, it looks like there is an administrator that can
> assign JIRA's.
> How should we be handling assigning Trafodion JIRAs? Can I just assign a
> JIRA to myself without any special privilege?
>
> And Pierre, great job in putting together the Trafodion wiki page.
>
> Roberta
>
RE: Question on JIRA's
Posted by "Marton, Roberta S" <ro...@hp.com>.
Thanks Alice. I knew this was needed to move over Lauchpad but missed the assigning of JIRA bugs.
Roberta
-----Original Message-----
From: Chen, Alice (Trafodion)
Sent: Thursday, June 25, 2015 9:44 AM
To: dev@trafodion.incubator.apache.org
Subject: RE: Question on JIRA's
Hello Roberta,
We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 . Our project was created but no administrator has been assigned nor has our old LP bugs been imported yet.
Cheers,
Alice
-----Original Message-----
From: Marton, Roberta S
Sent: Thursday, June 25, 2015 9:29 AM
To: dev@trafodion.incubator.apache.org
Subject: Question on JIRA's
I have created my first JIRA this morning. A little confusion with the CREATE button but got that resolved.
Looking at the current set of Trafodion JIRA's I see that they are all unassigned. I looked around a bit and could not figure out how to assign them.
Perusing the internet, it looks like there is an administrator that can assign JIRA's.
How should we be handling assigning Trafodion JIRAs? Can I just assign a JIRA to myself without any special privilege?
And Pierre, great job in putting together the Trafodion wiki page.
Roberta
RE: Question on JIRA's
Posted by "Chen, Alice (Trafodion)" <al...@hp.com>.
Hello Roberta,
We are blocked due to https://issues.apache.org/jira/browse/INFRA-9701 . Our project was created but no administrator has been assigned nor has our old LP bugs been imported yet.
Cheers,
Alice
-----Original Message-----
From: Marton, Roberta S
Sent: Thursday, June 25, 2015 9:29 AM
To: dev@trafodion.incubator.apache.org
Subject: Question on JIRA's
I have created my first JIRA this morning. A little confusion with the CREATE button but got that resolved.
Looking at the current set of Trafodion JIRA's I see that they are all unassigned. I looked around a bit and could not figure out how to assign them.
Perusing the internet, it looks like there is an administrator that can assign JIRA's.
How should we be handling assigning Trafodion JIRAs? Can I just assign a JIRA to myself without any special privilege?
And Pierre, great job in putting together the Trafodion wiki page.
Roberta