You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@training.apache.org by Lars Francke <la...@gmail.com> on 2019/02/22 22:23:42 UTC
Jira // Bug tracker
We don't have any code yet but I'm 100% sure that we want some way to track
issues soon. My vote is for Jira but Bugzilla would still be a theoretical
option I believe?
As far as I know Github issues are not an option because the content is not
owned by the ASF.
So, if there are no objections I'll request a Jira project soon.
But we can discuss here - or elsewhere later - what kind of components we
want/need etc. and I'm sure this will also emerge while we work on it.
I'd like to avoid spamming the dev@ list with Jira notifications. What
works for other projects is something like this:
PR and issue creation -> dev@
PR and issue comments/close -> issues@
Git commit -> commits@
But some projects also don't receive Git(hub) mails directly but instead
they are added to relevant Jiras as "Worklogs". I'm not sure exactly what
the options are but I'd try to keep it simple at first and then refine if
needed.
Opinions?
Re: Jira // Bug tracker
Posted by Dmitriy Pavlov <dp...@apache.org>.
+1 for JIRA.
вс, 24 февр. 2019 г. в 03:43, Lars Francke <la...@gmail.com>:
> I'm also +1 on Jira.
>
> On Sat, Feb 23, 2019 at 10:58 PM Christofer Dutz <
> christofer.dutz@c-ware.de>
> wrote:
>
> > And all of these projects adopting github issues and. PRs usually end up
> > flooding every mailbox with thousands of useless emails and makes it
> > impossible to sensibly file the project.
> >
> > I would also favor jira.
> >
> > Chris
> >
> > Outlook für Android<https://aka.ms/ghei36> herunterladen
> >
> > ________________________________
> > From: Furkan KAMACI <fu...@gmail.com>
> > Sent: Saturday, February 23, 2019 9:17:45 PM
> > To: dev@training.apache.org
> > Subject: Re: Jira // Bug tracker
> >
> > Hi,
> >
> > > Out of curiosity: Can you point at one or two? I assume it's mostly the
> > > newer ones.
> >
> > Yes, mostly new podlings uses Github for such purpose as like Justin
> > pointed i.e. https://github.com/apache/incubator-druid/issues
> >
> > My vote is for Jira too. It is more flexible and powerful i.e. if we want
> > to decide to use Confluence and integrate it with Jira.
> >
> > Kind Regards,
> > Furkan KAMACI
> >
> > On Sat, Feb 23, 2019 at 9:50 PM Sharan Foga <sh...@apache.org> wrote:
> >
> > > Hi
> > >
> > > I'd prefer Jira too especially if it's going to be easier for anyone to
> > > contribute.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2019/02/23 04:21:44, Kenneth Knowles <ke...@apache.org> wrote:
> > > > > > One thing I've encountered on GitHub is that you can only assign
> a
> > PR
> > > > > > review to a member of the `apache` organization. Is that also
> true
> > > for
> > > > > > issues?
> > > > >
> > > > > Most likely but I don’t know. Because of GitHib's poor granularity
> of
> > > it's
> > > > > permission system INFRA have locked it down and a lot of things
> > > projects
> > > > > can do in the wild can’t be done at Apache.
> > > > >
> > > >
> > > > If this is true, I prefer Jira so non-committers can take issues.
> What
> > do
> > > > you do on echarts? Do you know what they do on royale-asjs?
> > > >
> > > > Kenn
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
I'm also +1 on Jira.
On Sat, Feb 23, 2019 at 10:58 PM Christofer Dutz <ch...@c-ware.de>
wrote:
> And all of these projects adopting github issues and. PRs usually end up
> flooding every mailbox with thousands of useless emails and makes it
> impossible to sensibly file the project.
>
> I would also favor jira.
>
> Chris
>
> Outlook für Android<https://aka.ms/ghei36> herunterladen
>
> ________________________________
> From: Furkan KAMACI <fu...@gmail.com>
> Sent: Saturday, February 23, 2019 9:17:45 PM
> To: dev@training.apache.org
> Subject: Re: Jira // Bug tracker
>
> Hi,
>
> > Out of curiosity: Can you point at one or two? I assume it's mostly the
> > newer ones.
>
> Yes, mostly new podlings uses Github for such purpose as like Justin
> pointed i.e. https://github.com/apache/incubator-druid/issues
>
> My vote is for Jira too. It is more flexible and powerful i.e. if we want
> to decide to use Confluence and integrate it with Jira.
>
> Kind Regards,
> Furkan KAMACI
>
> On Sat, Feb 23, 2019 at 9:50 PM Sharan Foga <sh...@apache.org> wrote:
>
> > Hi
> >
> > I'd prefer Jira too especially if it's going to be easier for anyone to
> > contribute.
> >
> > Thanks
> > Sharan
> >
> > On 2019/02/23 04:21:44, Kenneth Knowles <ke...@apache.org> wrote:
> > > > > One thing I've encountered on GitHub is that you can only assign a
> PR
> > > > > review to a member of the `apache` organization. Is that also true
> > for
> > > > > issues?
> > > >
> > > > Most likely but I don’t know. Because of GitHib's poor granularity of
> > it's
> > > > permission system INFRA have locked it down and a lot of things
> > projects
> > > > can do in the wild can’t be done at Apache.
> > > >
> > >
> > > If this is true, I prefer Jira so non-committers can take issues. What
> do
> > > you do on echarts? Do you know what they do on royale-asjs?
> > >
> > > Kenn
> > >
> >
>
Re: Jira // Bug tracker
Posted by Christofer Dutz <ch...@c-ware.de>.
And all of these projects adopting github issues and. PRs usually end up flooding every mailbox with thousands of useless emails and makes it impossible to sensibly file the project.
I would also favor jira.
Chris
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Furkan KAMACI <fu...@gmail.com>
Sent: Saturday, February 23, 2019 9:17:45 PM
To: dev@training.apache.org
Subject: Re: Jira // Bug tracker
Hi,
> Out of curiosity: Can you point at one or two? I assume it's mostly the
> newer ones.
Yes, mostly new podlings uses Github for such purpose as like Justin
pointed i.e. https://github.com/apache/incubator-druid/issues
My vote is for Jira too. It is more flexible and powerful i.e. if we want
to decide to use Confluence and integrate it with Jira.
Kind Regards,
Furkan KAMACI
On Sat, Feb 23, 2019 at 9:50 PM Sharan Foga <sh...@apache.org> wrote:
> Hi
>
> I'd prefer Jira too especially if it's going to be easier for anyone to
> contribute.
>
> Thanks
> Sharan
>
> On 2019/02/23 04:21:44, Kenneth Knowles <ke...@apache.org> wrote:
> > > > One thing I've encountered on GitHub is that you can only assign a PR
> > > > review to a member of the `apache` organization. Is that also true
> for
> > > > issues?
> > >
> > > Most likely but I don’t know. Because of GitHib's poor granularity of
> it's
> > > permission system INFRA have locked it down and a lot of things
> projects
> > > can do in the wild can’t be done at Apache.
> > >
> >
> > If this is true, I prefer Jira so non-committers can take issues. What do
> > you do on echarts? Do you know what they do on royale-asjs?
> >
> > Kenn
> >
>
Re: Jira // Bug tracker
Posted by Furkan KAMACI <fu...@gmail.com>.
Hi,
> Out of curiosity: Can you point at one or two? I assume it's mostly the
> newer ones.
Yes, mostly new podlings uses Github for such purpose as like Justin
pointed i.e. https://github.com/apache/incubator-druid/issues
My vote is for Jira too. It is more flexible and powerful i.e. if we want
to decide to use Confluence and integrate it with Jira.
Kind Regards,
Furkan KAMACI
On Sat, Feb 23, 2019 at 9:50 PM Sharan Foga <sh...@apache.org> wrote:
> Hi
>
> I'd prefer Jira too especially if it's going to be easier for anyone to
> contribute.
>
> Thanks
> Sharan
>
> On 2019/02/23 04:21:44, Kenneth Knowles <ke...@apache.org> wrote:
> > > > One thing I've encountered on GitHub is that you can only assign a PR
> > > > review to a member of the `apache` organization. Is that also true
> for
> > > > issues?
> > >
> > > Most likely but I don’t know. Because of GitHib's poor granularity of
> it's
> > > permission system INFRA have locked it down and a lot of things
> projects
> > > can do in the wild can’t be done at Apache.
> > >
> >
> > If this is true, I prefer Jira so non-committers can take issues. What do
> > you do on echarts? Do you know what they do on royale-asjs?
> >
> > Kenn
> >
>
Re: Jira // Bug tracker
Posted by Mirko Kämpf <mi...@gmail.com>.
+1 for JIRA
Sharan Foga <sh...@apache.org> schrieb am Sa., 23. Feb. 2019, 10:50:
> Hi
>
> I'd prefer Jira too especially if it's going to be easier for anyone to
> contribute.
>
> Thanks
> Sharan
>
> On 2019/02/23 04:21:44, Kenneth Knowles <ke...@apache.org> wrote:
> > > > One thing I've encountered on GitHub is that you can only assign a PR
> > > > review to a member of the `apache` organization. Is that also true
> for
> > > > issues?
> > >
> > > Most likely but I don’t know. Because of GitHib's poor granularity of
> it's
> > > permission system INFRA have locked it down and a lot of things
> projects
> > > can do in the wild can’t be done at Apache.
> > >
> >
> > If this is true, I prefer Jira so non-committers can take issues. What do
> > you do on echarts? Do you know what they do on royale-asjs?
> >
> > Kenn
> >
>
Re: Jira // Bug tracker
Posted by Sharan Foga <sh...@apache.org>.
Hi
I'd prefer Jira too especially if it's going to be easier for anyone to contribute.
Thanks
Sharan
On 2019/02/23 04:21:44, Kenneth Knowles <ke...@apache.org> wrote:
> > > One thing I've encountered on GitHub is that you can only assign a PR
> > > review to a member of the `apache` organization. Is that also true for
> > > issues?
> >
> > Most likely but I don’t know. Because of GitHib's poor granularity of it's
> > permission system INFRA have locked it down and a lot of things projects
> > can do in the wild can’t be done at Apache.
> >
>
> If this is true, I prefer Jira so non-committers can take issues. What do
> you do on echarts? Do you know what they do on royale-asjs?
>
> Kenn
>
Re: Jira // Bug tracker
Posted by Kenneth Knowles <ke...@apache.org>.
> > One thing I've encountered on GitHub is that you can only assign a PR
> > review to a member of the `apache` organization. Is that also true for
> > issues?
>
> Most likely but I don’t know. Because of GitHib's poor granularity of it's
> permission system INFRA have locked it down and a lot of things projects
> can do in the wild can’t be done at Apache.
>
If this is true, I prefer Jira so non-committers can take issues. What do
you do on echarts? Do you know what they do on royale-asjs?
Kenn
Re: Jira // Bug tracker
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> One thing I've encountered on GitHub is that you can only assign a PR
> review to a member of the `apache` organization. Is that also true for
> issues?
Most likely but I don’t know. Because of GitHib's poor granularity of it's permission system INFRA have locked it down and a lot of things projects can do in the wild can’t be done at Apache.
Thanks,
Justin
Re: Jira // Bug tracker
Posted by Kenneth Knowles <ke...@apache.org>.
One thing I've encountered on GitHub is that you can only assign a PR
review to a member of the `apache` organization. Is that also true for
issues?
Kenn
On Fri, Feb 22, 2019 at 3:36 PM Sönke Liebau
<so...@opencore.com.invalid> wrote:
> Heyho,
>
> in the case of jira vs github issues I am in favor of jira.
> Github issues just feel .. "off" to me somehow as well as simply having
> less functionality.
>
> Best regards,
> Sönke
>
>
> Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <ju...@classsoftware.com>
> geschrieben:
>
> > Hi,
> >
> > > Out of curiosity: Can you point at one or two? I assume it's mostly the
> > > newer ones.
> >
> > Yes mostly newer podlings but then that’s what I mostly work with for
> > instance [1] (9,500+ issues), but there’s at least one TLP I also know
> that
> > uses it. [2]
> >
> > This is not to say these projects are exemplar in any way or we should
> > copy what they do. :-)
> >
> > > Not really. There's one thread that comes to mind[1]
> >
> > Yep it would seem that GitHub issues may be a bit of a grey area here.
> >
> > BTW I'm fine with JIRA but if people want to use GitHub issues I’m also
> > fine with that. I guess it come down to what is our audience most likely
> > to want to use, being more the technical trainer types they may be
> familiar
> > with a GitHub workflow rather than a JIRA one? But I’m not really sure.
> >
> > Thanks,
> > Justin
> >
> > 1. https://github.com/apache/incubator-echarts/issues
> > 2. https://github.com/apache/royale-asjs/issues
> >
> >
>
Re: Jira // Bug tracker
Posted by Dmitriy Pavlov <dp...@apache.org>.
I absolutely agree with this redirect to a separate list - all actions for
PR/Issues forwarding on the dev will make this list too busy.
JIRA login is dpavlov.
пн, 25 февр. 2019 г. в 23:32, Lars Francke <la...@gmail.com>:
> Okay. I'll go ahead and request it.
>
> Similar to Confluence it would be good to have at least one or two more
> administrators. If you give me your JIRA username I'll add you.
> I'll have all notifications sent to dev@training.apache.org for now but
> I'm
> very much in favor of having this separated out like this:
>
> PR and issue creation -> dev@
> PR and issue comments/close -> issues@
> Git commit -> commits@
>
> Not urgent for now but if you have an opinion on this let me know.
>
> On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <collin.rogowski@inovex.de
> >
> wrote:
>
> > +1 for Jira
> >
> > cr
> >
> >
> > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de> wrote:
> >
> > > I would also favor Jira.
> > >
> > > Kind regards,
> > > Hans-Peter
> > >
> > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > soenke.liebau@opencore.com
> > > .INVALID>:
> > > >
> > > > Heyho,
> > > >
> > > > in the case of jira vs github issues I am in favor of jira.
> > > > Github issues just feel .. "off" to me somehow as well as simply
> having
> > > > less functionality.
> > > >
> > > > Best regards,
> > > > Sönke
> > > >
> > > >
> > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > justin@classsoftware.com
> > > >
> > > > geschrieben:
> > > >
> > > >> Hi,
> > > >>
> > > >>> Out of curiosity: Can you point at one or two? I assume it's mostly
> > the
> > > >>> newer ones.
> > > >>
> > > >> Yes mostly newer podlings but then that’s what I mostly work with
> for
> > > >> instance [1] (9,500+ issues), but there’s at least one TLP I also
> know
> > > that
> > > >> uses it. [2]
> > > >>
> > > >> This is not to say these projects are exemplar in any way or we
> should
> > > >> copy what they do. :-)
> > > >>
> > > >>> Not really. There's one thread that comes to mind[1]
> > > >>
> > > >> Yep it would seem that GitHub issues may be a bit of a grey area
> here.
> > > >>
> > > >> BTW I'm fine with JIRA but if people want to use GitHub issues I’m
> > also
> > > >> fine with that. I guess it come down to what is our audience most
> > > likely
> > > >> to want to use, being more the technical trainer types they may be
> > > familiar
> > > >> with a GitHub workflow rather than a JIRA one? But I’m not really
> > sure.
> > > >>
> > > >> Thanks,
> > > >> Justin
> > > >>
> > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > >> 2. https://github.com/apache/royale-asjs/issues
> > > >>
> > > >>
> > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
I found it very useful to have the creation messages on dev@ - the traffic
is not that high compared to all other messages and they are actually
pretty nice to see.
On Mon, Feb 25, 2019 at 10:52 PM Kenneth Knowles <ke...@apache.org> wrote:
> +1000 to separating issues@. Interesting idea having creation messages
> show
> up on dev@.
>
> I'd be happy to help administer. I do quite a bit of Jira. Username is
> kenn.
>
> Kenn
>
> On Mon, Feb 25, 2019 at 1:27 PM Sharan Foga <sh...@apache.org> wrote:
>
> > Hi Lars
> >
> > I can help with Jira admin too - my JIra login is sharan.
> >
> > Thanks
> > Sharan
> >
> > On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > > Okay. I'll go ahead and request it.
> > >
> > > Similar to Confluence it would be good to have at least one or two more
> > > administrators. If you give me your JIRA username I'll add you.
> > > I'll have all notifications sent to dev@training.apache.org for now
> but
> > I'm
> > > very much in favor of having this separated out like this:
> > >
> > > PR and issue creation -> dev@
> > > PR and issue comments/close -> issues@
> > > Git commit -> commits@
> > >
> > > Not urgent for now but if you have an opinion on this let me know.
> > >
> > > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> > collin.rogowski@inovex.de>
> > > wrote:
> > >
> > > > +1 for Jira
> > > >
> > > > cr
> > > >
> > > >
> > > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> > wrote:
> > > >
> > > > > I would also favor Jira.
> > > > >
> > > > > Kind regards,
> > > > > Hans-Peter
> > > > >
> > > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > > soenke.liebau@opencore.com
> > > > > .INVALID>:
> > > > > >
> > > > > > Heyho,
> > > > > >
> > > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > > Github issues just feel .. "off" to me somehow as well as simply
> > having
> > > > > > less functionality.
> > > > > >
> > > > > > Best regards,
> > > > > > Sönke
> > > > > >
> > > > > >
> > > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > > justin@classsoftware.com
> > > > > >
> > > > > > geschrieben:
> > > > > >
> > > > > >> Hi,
> > > > > >>
> > > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> > mostly
> > > > the
> > > > > >>> newer ones.
> > > > > >>
> > > > > >> Yes mostly newer podlings but then that’s what I mostly work
> with
> > for
> > > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I
> also
> > know
> > > > > that
> > > > > >> uses it. [2]
> > > > > >>
> > > > > >> This is not to say these projects are exemplar in any way or we
> > should
> > > > > >> copy what they do. :-)
> > > > > >>
> > > > > >>> Not really. There's one thread that comes to mind[1]
> > > > > >>
> > > > > >> Yep it would seem that GitHub issues may be a bit of a grey area
> > here.
> > > > > >>
> > > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues
> I’m
> > > > also
> > > > > >> fine with that. I guess it come down to what is our audience
> most
> > > > > likely
> > > > > >> to want to use, being more the technical trainer types they may
> be
> > > > > familiar
> > > > > >> with a GitHub workflow rather than a JIRA one? But I’m not
> really
> > > > sure.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Justin
> > > > > >>
> > > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Kenneth Knowles <ke...@apache.org>.
+1000 to separating issues@. Interesting idea having creation messages show
up on dev@.
I'd be happy to help administer. I do quite a bit of Jira. Username is kenn.
Kenn
On Mon, Feb 25, 2019 at 1:27 PM Sharan Foga <sh...@apache.org> wrote:
> Hi Lars
>
> I can help with Jira admin too - my JIra login is sharan.
>
> Thanks
> Sharan
>
> On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > Okay. I'll go ahead and request it.
> >
> > Similar to Confluence it would be good to have at least one or two more
> > administrators. If you give me your JIRA username I'll add you.
> > I'll have all notifications sent to dev@training.apache.org for now but
> I'm
> > very much in favor of having this separated out like this:
> >
> > PR and issue creation -> dev@
> > PR and issue comments/close -> issues@
> > Git commit -> commits@
> >
> > Not urgent for now but if you have an opinion on this let me know.
> >
> > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> collin.rogowski@inovex.de>
> > wrote:
> >
> > > +1 for Jira
> > >
> > > cr
> > >
> > >
> > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> wrote:
> > >
> > > > I would also favor Jira.
> > > >
> > > > Kind regards,
> > > > Hans-Peter
> > > >
> > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > soenke.liebau@opencore.com
> > > > .INVALID>:
> > > > >
> > > > > Heyho,
> > > > >
> > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > Github issues just feel .. "off" to me somehow as well as simply
> having
> > > > > less functionality.
> > > > >
> > > > > Best regards,
> > > > > Sönke
> > > > >
> > > > >
> > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > justin@classsoftware.com
> > > > >
> > > > > geschrieben:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> mostly
> > > the
> > > > >>> newer ones.
> > > > >>
> > > > >> Yes mostly newer podlings but then that’s what I mostly work with
> for
> > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I also
> know
> > > > that
> > > > >> uses it. [2]
> > > > >>
> > > > >> This is not to say these projects are exemplar in any way or we
> should
> > > > >> copy what they do. :-)
> > > > >>
> > > > >>> Not really. There's one thread that comes to mind[1]
> > > > >>
> > > > >> Yep it would seem that GitHub issues may be a bit of a grey area
> here.
> > > > >>
> > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues I’m
> > > also
> > > > >> fine with that. I guess it come down to what is our audience most
> > > > likely
> > > > >> to want to use, being more the technical trainer types they may be
> > > > familiar
> > > > >> with a GitHub workflow rather than a JIRA one? But I’m not really
> > > sure.
> > > > >>
> > > > >> Thanks,
> > > > >> Justin
> > > > >>
> > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
I was reminded that I never actually posted the URL :)
<https://issues.apache.org/jira/browse/TRAINING>
We also have an issues@training.apache.org mailing list now and Jira things
(other than issue created) will be sent there.
On Tue, Feb 26, 2019 at 8:16 AM Lars Francke <la...@gmail.com> wrote:
> That was Jira. It worked in Confluence. I can try again tonight
>
> @Furkan: I can add you tonight (unless one of the others jumps in before
> that)
>
> On Mon, Feb 25, 2019 at 11:51 PM Sharan F <sh...@apache.org> wrote:
>
>> On Mon, 25 Feb 2019, 23:33 Lars Francke, <la...@gmail.com> wrote:
>>
>> > Hi Sharan,
>> >
>> > for some reason I get this error when I try to add you: "We can't find
>> > 'sharan' in any accessible user directory. Check they're still active
>> and
>> > available, and try again." Any idea what's going on?
>> >
>>
>> Nope. Was that confluence or jira?
>>
>> I logged in confluence and jira to check my username before I responded.
>> Let me ask someone from infra
>>
>> Thanks
>> Sharan
>>
>> Kenneth, Dmitriy and Sönke worked just fine.
>> >
>> > On Mon, Feb 25, 2019 at 10:27 PM Sharan Foga <sh...@apache.org> wrote:
>> >
>> > > Hi Lars
>> > >
>> > > I can help with Jira admin too - my JIra login is sharan.
>> > >
>> > > Thanks
>> > > Sharan
>> > >
>> > > On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
>> > > > Okay. I'll go ahead and request it.
>> > > >
>> > > > Similar to Confluence it would be good to have at least one or two
>> more
>> > > > administrators. If you give me your JIRA username I'll add you.
>> > > > I'll have all notifications sent to dev@training.apache.org for now
>> > but
>> > > I'm
>> > > > very much in favor of having this separated out like this:
>> > > >
>> > > > PR and issue creation -> dev@
>> > > > PR and issue comments/close -> issues@
>> > > > Git commit -> commits@
>> > > >
>> > > > Not urgent for now but if you have an opinion on this let me know.
>> > > >
>> > > > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
>> > > collin.rogowski@inovex.de>
>> > > > wrote:
>> > > >
>> > > > > +1 for Jira
>> > > > >
>> > > > > cr
>> > > > >
>> > > > >
>> > > > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
>> > > wrote:
>> > > > >
>> > > > > > I would also favor Jira.
>> > > > > >
>> > > > > > Kind regards,
>> > > > > > Hans-Peter
>> > > > > >
>> > > > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
>> > > > > soenke.liebau@opencore.com
>> > > > > > .INVALID>:
>> > > > > > >
>> > > > > > > Heyho,
>> > > > > > >
>> > > > > > > in the case of jira vs github issues I am in favor of jira.
>> > > > > > > Github issues just feel .. "off" to me somehow as well as
>> simply
>> > > having
>> > > > > > > less functionality.
>> > > > > > >
>> > > > > > > Best regards,
>> > > > > > > Sönke
>> > > > > > >
>> > > > > > >
>> > > > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
>> > > > > justin@classsoftware.com
>> > > > > > >
>> > > > > > > geschrieben:
>> > > > > > >
>> > > > > > >> Hi,
>> > > > > > >>
>> > > > > > >>> Out of curiosity: Can you point at one or two? I assume it's
>> > > mostly
>> > > > > the
>> > > > > > >>> newer ones.
>> > > > > > >>
>> > > > > > >> Yes mostly newer podlings but then that’s what I mostly work
>> > with
>> > > for
>> > > > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I
>> > also
>> > > know
>> > > > > > that
>> > > > > > >> uses it. [2]
>> > > > > > >>
>> > > > > > >> This is not to say these projects are exemplar in any way or
>> we
>> > > should
>> > > > > > >> copy what they do. :-)
>> > > > > > >>
>> > > > > > >>> Not really. There's one thread that comes to mind[1]
>> > > > > > >>
>> > > > > > >> Yep it would seem that GitHub issues may be a bit of a grey
>> area
>> > > here.
>> > > > > > >>
>> > > > > > >> BTW I'm fine with JIRA but if people want to use GitHub
>> issues
>> > I’m
>> > > > > also
>> > > > > > >> fine with that. I guess it come down to what is our audience
>> > most
>> > > > > > likely
>> > > > > > >> to want to use, being more the technical trainer types they
>> may
>> > be
>> > > > > > familiar
>> > > > > > >> with a GitHub workflow rather than a JIRA one? But I’m not
>> > really
>> > > > > sure.
>> > > > > > >>
>> > > > > > >> Thanks,
>> > > > > > >> Justin
>> > > > > > >>
>> > > > > > >> 1. https://github.com/apache/incubator-echarts/issues
>> > > > > > >> 2. https://github.com/apache/royale-asjs/issues
>> > > > > > >>
>> > > > > > >>
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: Jira // Bug tracker
Posted by Sharan Foga <sh...@apache.org>.
Hi Lars
Gavin from infra set me up on the Jira. My username has a bit of history that I thought had been fixed but was still in the database.
Anyway it's fine now.
Thanks
Sharan
On 2019/02/26 07:16:11, Lars Francke <la...@gmail.com> wrote:
> That was Jira. It worked in Confluence. I can try again tonight
>
> @Furkan: I can add you tonight (unless one of the others jumps in before
> that)
>
> On Mon, Feb 25, 2019 at 11:51 PM Sharan F <sh...@apache.org> wrote:
>
> > On Mon, 25 Feb 2019, 23:33 Lars Francke, <la...@gmail.com> wrote:
> >
> > > Hi Sharan,
> > >
> > > for some reason I get this error when I try to add you: "We can't find
> > > 'sharan' in any accessible user directory. Check they're still active and
> > > available, and try again." Any idea what's going on?
> > >
> >
> > Nope. Was that confluence or jira?
> >
> > I logged in confluence and jira to check my username before I responded.
> > Let me ask someone from infra
> >
> > Thanks
> > Sharan
> >
> > Kenneth, Dmitriy and Sönke worked just fine.
> > >
> > > On Mon, Feb 25, 2019 at 10:27 PM Sharan Foga <sh...@apache.org> wrote:
> > >
> > > > Hi Lars
> > > >
> > > > I can help with Jira admin too - my JIra login is sharan.
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > > On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > > > > Okay. I'll go ahead and request it.
> > > > >
> > > > > Similar to Confluence it would be good to have at least one or two
> > more
> > > > > administrators. If you give me your JIRA username I'll add you.
> > > > > I'll have all notifications sent to dev@training.apache.org for now
> > > but
> > > > I'm
> > > > > very much in favor of having this separated out like this:
> > > > >
> > > > > PR and issue creation -> dev@
> > > > > PR and issue comments/close -> issues@
> > > > > Git commit -> commits@
> > > > >
> > > > > Not urgent for now but if you have an opinion on this let me know.
> > > > >
> > > > > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> > > > collin.rogowski@inovex.de>
> > > > > wrote:
> > > > >
> > > > > > +1 for Jira
> > > > > >
> > > > > > cr
> > > > > >
> > > > > >
> > > > > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> > > > wrote:
> > > > > >
> > > > > > > I would also favor Jira.
> > > > > > >
> > > > > > > Kind regards,
> > > > > > > Hans-Peter
> > > > > > >
> > > > > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > > > > soenke.liebau@opencore.com
> > > > > > > .INVALID>:
> > > > > > > >
> > > > > > > > Heyho,
> > > > > > > >
> > > > > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > > > > Github issues just feel .. "off" to me somehow as well as
> > simply
> > > > having
> > > > > > > > less functionality.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > > Sönke
> > > > > > > >
> > > > > > > >
> > > > > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > > > > justin@classsoftware.com
> > > > > > > >
> > > > > > > > geschrieben:
> > > > > > > >
> > > > > > > >> Hi,
> > > > > > > >>
> > > > > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> > > > mostly
> > > > > > the
> > > > > > > >>> newer ones.
> > > > > > > >>
> > > > > > > >> Yes mostly newer podlings but then that’s what I mostly work
> > > with
> > > > for
> > > > > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I
> > > also
> > > > know
> > > > > > > that
> > > > > > > >> uses it. [2]
> > > > > > > >>
> > > > > > > >> This is not to say these projects are exemplar in any way or
> > we
> > > > should
> > > > > > > >> copy what they do. :-)
> > > > > > > >>
> > > > > > > >>> Not really. There's one thread that comes to mind[1]
> > > > > > > >>
> > > > > > > >> Yep it would seem that GitHub issues may be a bit of a grey
> > area
> > > > here.
> > > > > > > >>
> > > > > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues
> > > I’m
> > > > > > also
> > > > > > > >> fine with that. I guess it come down to what is our audience
> > > most
> > > > > > > likely
> > > > > > > >> to want to use, being more the technical trainer types they
> > may
> > > be
> > > > > > > familiar
> > > > > > > >> with a GitHub workflow rather than a JIRA one? But I’m not
> > > really
> > > > > > sure.
> > > > > > > >>
> > > > > > > >> Thanks,
> > > > > > > >> Justin
> > > > > > > >>
> > > > > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > > > > >>
> > > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
That was Jira. It worked in Confluence. I can try again tonight
@Furkan: I can add you tonight (unless one of the others jumps in before
that)
On Mon, Feb 25, 2019 at 11:51 PM Sharan F <sh...@apache.org> wrote:
> On Mon, 25 Feb 2019, 23:33 Lars Francke, <la...@gmail.com> wrote:
>
> > Hi Sharan,
> >
> > for some reason I get this error when I try to add you: "We can't find
> > 'sharan' in any accessible user directory. Check they're still active and
> > available, and try again." Any idea what's going on?
> >
>
> Nope. Was that confluence or jira?
>
> I logged in confluence and jira to check my username before I responded.
> Let me ask someone from infra
>
> Thanks
> Sharan
>
> Kenneth, Dmitriy and Sönke worked just fine.
> >
> > On Mon, Feb 25, 2019 at 10:27 PM Sharan Foga <sh...@apache.org> wrote:
> >
> > > Hi Lars
> > >
> > > I can help with Jira admin too - my JIra login is sharan.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > > > Okay. I'll go ahead and request it.
> > > >
> > > > Similar to Confluence it would be good to have at least one or two
> more
> > > > administrators. If you give me your JIRA username I'll add you.
> > > > I'll have all notifications sent to dev@training.apache.org for now
> > but
> > > I'm
> > > > very much in favor of having this separated out like this:
> > > >
> > > > PR and issue creation -> dev@
> > > > PR and issue comments/close -> issues@
> > > > Git commit -> commits@
> > > >
> > > > Not urgent for now but if you have an opinion on this let me know.
> > > >
> > > > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> > > collin.rogowski@inovex.de>
> > > > wrote:
> > > >
> > > > > +1 for Jira
> > > > >
> > > > > cr
> > > > >
> > > > >
> > > > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> > > wrote:
> > > > >
> > > > > > I would also favor Jira.
> > > > > >
> > > > > > Kind regards,
> > > > > > Hans-Peter
> > > > > >
> > > > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > > > soenke.liebau@opencore.com
> > > > > > .INVALID>:
> > > > > > >
> > > > > > > Heyho,
> > > > > > >
> > > > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > > > Github issues just feel .. "off" to me somehow as well as
> simply
> > > having
> > > > > > > less functionality.
> > > > > > >
> > > > > > > Best regards,
> > > > > > > Sönke
> > > > > > >
> > > > > > >
> > > > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > > > justin@classsoftware.com
> > > > > > >
> > > > > > > geschrieben:
> > > > > > >
> > > > > > >> Hi,
> > > > > > >>
> > > > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> > > mostly
> > > > > the
> > > > > > >>> newer ones.
> > > > > > >>
> > > > > > >> Yes mostly newer podlings but then that’s what I mostly work
> > with
> > > for
> > > > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I
> > also
> > > know
> > > > > > that
> > > > > > >> uses it. [2]
> > > > > > >>
> > > > > > >> This is not to say these projects are exemplar in any way or
> we
> > > should
> > > > > > >> copy what they do. :-)
> > > > > > >>
> > > > > > >>> Not really. There's one thread that comes to mind[1]
> > > > > > >>
> > > > > > >> Yep it would seem that GitHub issues may be a bit of a grey
> area
> > > here.
> > > > > > >>
> > > > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues
> > I’m
> > > > > also
> > > > > > >> fine with that. I guess it come down to what is our audience
> > most
> > > > > > likely
> > > > > > >> to want to use, being more the technical trainer types they
> may
> > be
> > > > > > familiar
> > > > > > >> with a GitHub workflow rather than a JIRA one? But I’m not
> > really
> > > > > sure.
> > > > > > >>
> > > > > > >> Thanks,
> > > > > > >> Justin
> > > > > > >>
> > > > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Sharan F <sh...@apache.org>.
On Mon, 25 Feb 2019, 23:33 Lars Francke, <la...@gmail.com> wrote:
> Hi Sharan,
>
> for some reason I get this error when I try to add you: "We can't find
> 'sharan' in any accessible user directory. Check they're still active and
> available, and try again." Any idea what's going on?
>
Nope. Was that confluence or jira?
I logged in confluence and jira to check my username before I responded.
Let me ask someone from infra
Thanks
Sharan
Kenneth, Dmitriy and Sönke worked just fine.
>
> On Mon, Feb 25, 2019 at 10:27 PM Sharan Foga <sh...@apache.org> wrote:
>
> > Hi Lars
> >
> > I can help with Jira admin too - my JIra login is sharan.
> >
> > Thanks
> > Sharan
> >
> > On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > > Okay. I'll go ahead and request it.
> > >
> > > Similar to Confluence it would be good to have at least one or two more
> > > administrators. If you give me your JIRA username I'll add you.
> > > I'll have all notifications sent to dev@training.apache.org for now
> but
> > I'm
> > > very much in favor of having this separated out like this:
> > >
> > > PR and issue creation -> dev@
> > > PR and issue comments/close -> issues@
> > > Git commit -> commits@
> > >
> > > Not urgent for now but if you have an opinion on this let me know.
> > >
> > > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> > collin.rogowski@inovex.de>
> > > wrote:
> > >
> > > > +1 for Jira
> > > >
> > > > cr
> > > >
> > > >
> > > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> > wrote:
> > > >
> > > > > I would also favor Jira.
> > > > >
> > > > > Kind regards,
> > > > > Hans-Peter
> > > > >
> > > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > > soenke.liebau@opencore.com
> > > > > .INVALID>:
> > > > > >
> > > > > > Heyho,
> > > > > >
> > > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > > Github issues just feel .. "off" to me somehow as well as simply
> > having
> > > > > > less functionality.
> > > > > >
> > > > > > Best regards,
> > > > > > Sönke
> > > > > >
> > > > > >
> > > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > > justin@classsoftware.com
> > > > > >
> > > > > > geschrieben:
> > > > > >
> > > > > >> Hi,
> > > > > >>
> > > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> > mostly
> > > > the
> > > > > >>> newer ones.
> > > > > >>
> > > > > >> Yes mostly newer podlings but then that’s what I mostly work
> with
> > for
> > > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I
> also
> > know
> > > > > that
> > > > > >> uses it. [2]
> > > > > >>
> > > > > >> This is not to say these projects are exemplar in any way or we
> > should
> > > > > >> copy what they do. :-)
> > > > > >>
> > > > > >>> Not really. There's one thread that comes to mind[1]
> > > > > >>
> > > > > >> Yep it would seem that GitHub issues may be a bit of a grey area
> > here.
> > > > > >>
> > > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues
> I’m
> > > > also
> > > > > >> fine with that. I guess it come down to what is our audience
> most
> > > > > likely
> > > > > >> to want to use, being more the technical trainer types they may
> be
> > > > > familiar
> > > > > >> with a GitHub workflow rather than a JIRA one? But I’m not
> really
> > > > sure.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Justin
> > > > > >>
> > > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Furkan KAMACI <fu...@gmail.com>.
Hi Lars,
My ASF JIRA username is *kamaci*
I can help as a JIRA admin too.
Kind Regards,
Furkan KAMACI
On Tue, Feb 26, 2019 at 1:33 AM Lars Francke <la...@gmail.com> wrote:
> Hi Sharan,
>
> for some reason I get this error when I try to add you: "We can't find
> 'sharan' in any accessible user directory. Check they're still active and
> available, and try again." Any idea what's going on?
>
> Kenneth, Dmitriy and Sönke worked just fine.
>
> On Mon, Feb 25, 2019 at 10:27 PM Sharan Foga <sh...@apache.org> wrote:
>
> > Hi Lars
> >
> > I can help with Jira admin too - my JIra login is sharan.
> >
> > Thanks
> > Sharan
> >
> > On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > > Okay. I'll go ahead and request it.
> > >
> > > Similar to Confluence it would be good to have at least one or two more
> > > administrators. If you give me your JIRA username I'll add you.
> > > I'll have all notifications sent to dev@training.apache.org for now
> but
> > I'm
> > > very much in favor of having this separated out like this:
> > >
> > > PR and issue creation -> dev@
> > > PR and issue comments/close -> issues@
> > > Git commit -> commits@
> > >
> > > Not urgent for now but if you have an opinion on this let me know.
> > >
> > > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> > collin.rogowski@inovex.de>
> > > wrote:
> > >
> > > > +1 for Jira
> > > >
> > > > cr
> > > >
> > > >
> > > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> > wrote:
> > > >
> > > > > I would also favor Jira.
> > > > >
> > > > > Kind regards,
> > > > > Hans-Peter
> > > > >
> > > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > > soenke.liebau@opencore.com
> > > > > .INVALID>:
> > > > > >
> > > > > > Heyho,
> > > > > >
> > > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > > Github issues just feel .. "off" to me somehow as well as simply
> > having
> > > > > > less functionality.
> > > > > >
> > > > > > Best regards,
> > > > > > Sönke
> > > > > >
> > > > > >
> > > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > > justin@classsoftware.com
> > > > > >
> > > > > > geschrieben:
> > > > > >
> > > > > >> Hi,
> > > > > >>
> > > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> > mostly
> > > > the
> > > > > >>> newer ones.
> > > > > >>
> > > > > >> Yes mostly newer podlings but then that’s what I mostly work
> with
> > for
> > > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I
> also
> > know
> > > > > that
> > > > > >> uses it. [2]
> > > > > >>
> > > > > >> This is not to say these projects are exemplar in any way or we
> > should
> > > > > >> copy what they do. :-)
> > > > > >>
> > > > > >>> Not really. There's one thread that comes to mind[1]
> > > > > >>
> > > > > >> Yep it would seem that GitHub issues may be a bit of a grey area
> > here.
> > > > > >>
> > > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues
> I’m
> > > > also
> > > > > >> fine with that. I guess it come down to what is our audience
> most
> > > > > likely
> > > > > >> to want to use, being more the technical trainer types they may
> be
> > > > > familiar
> > > > > >> with a GitHub workflow rather than a JIRA one? But I’m not
> really
> > > > sure.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> Justin
> > > > > >>
> > > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
Hi Sharan,
for some reason I get this error when I try to add you: "We can't find
'sharan' in any accessible user directory. Check they're still active and
available, and try again." Any idea what's going on?
Kenneth, Dmitriy and Sönke worked just fine.
On Mon, Feb 25, 2019 at 10:27 PM Sharan Foga <sh...@apache.org> wrote:
> Hi Lars
>
> I can help with Jira admin too - my JIra login is sharan.
>
> Thanks
> Sharan
>
> On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> > Okay. I'll go ahead and request it.
> >
> > Similar to Confluence it would be good to have at least one or two more
> > administrators. If you give me your JIRA username I'll add you.
> > I'll have all notifications sent to dev@training.apache.org for now but
> I'm
> > very much in favor of having this separated out like this:
> >
> > PR and issue creation -> dev@
> > PR and issue comments/close -> issues@
> > Git commit -> commits@
> >
> > Not urgent for now but if you have an opinion on this let me know.
> >
> > On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <
> collin.rogowski@inovex.de>
> > wrote:
> >
> > > +1 for Jira
> > >
> > > cr
> > >
> > >
> > > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de>
> wrote:
> > >
> > > > I would also favor Jira.
> > > >
> > > > Kind regards,
> > > > Hans-Peter
> > > >
> > > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > > soenke.liebau@opencore.com
> > > > .INVALID>:
> > > > >
> > > > > Heyho,
> > > > >
> > > > > in the case of jira vs github issues I am in favor of jira.
> > > > > Github issues just feel .. "off" to me somehow as well as simply
> having
> > > > > less functionality.
> > > > >
> > > > > Best regards,
> > > > > Sönke
> > > > >
> > > > >
> > > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > > justin@classsoftware.com
> > > > >
> > > > > geschrieben:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >>> Out of curiosity: Can you point at one or two? I assume it's
> mostly
> > > the
> > > > >>> newer ones.
> > > > >>
> > > > >> Yes mostly newer podlings but then that’s what I mostly work with
> for
> > > > >> instance [1] (9,500+ issues), but there’s at least one TLP I also
> know
> > > > that
> > > > >> uses it. [2]
> > > > >>
> > > > >> This is not to say these projects are exemplar in any way or we
> should
> > > > >> copy what they do. :-)
> > > > >>
> > > > >>> Not really. There's one thread that comes to mind[1]
> > > > >>
> > > > >> Yep it would seem that GitHub issues may be a bit of a grey area
> here.
> > > > >>
> > > > >> BTW I'm fine with JIRA but if people want to use GitHub issues I’m
> > > also
> > > > >> fine with that. I guess it come down to what is our audience most
> > > > likely
> > > > >> to want to use, being more the technical trainer types they may be
> > > > familiar
> > > > >> with a GitHub workflow rather than a JIRA one? But I’m not really
> > > sure.
> > > > >>
> > > > >> Thanks,
> > > > >> Justin
> > > > >>
> > > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > > >> 2. https://github.com/apache/royale-asjs/issues
> > > > >>
> > > > >>
> > > >
> > > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Sharan Foga <sh...@apache.org>.
Hi Lars
I can help with Jira admin too - my JIra login is sharan.
Thanks
Sharan
On 2019/02/25 20:32:04, Lars Francke <la...@gmail.com> wrote:
> Okay. I'll go ahead and request it.
>
> Similar to Confluence it would be good to have at least one or two more
> administrators. If you give me your JIRA username I'll add you.
> I'll have all notifications sent to dev@training.apache.org for now but I'm
> very much in favor of having this separated out like this:
>
> PR and issue creation -> dev@
> PR and issue comments/close -> issues@
> Git commit -> commits@
>
> Not urgent for now but if you have an opinion on this let me know.
>
> On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <co...@inovex.de>
> wrote:
>
> > +1 for Jira
> >
> > cr
> >
> >
> > On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de> wrote:
> >
> > > I would also favor Jira.
> > >
> > > Kind regards,
> > > Hans-Peter
> > >
> > > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> > soenke.liebau@opencore.com
> > > .INVALID>:
> > > >
> > > > Heyho,
> > > >
> > > > in the case of jira vs github issues I am in favor of jira.
> > > > Github issues just feel .. "off" to me somehow as well as simply having
> > > > less functionality.
> > > >
> > > > Best regards,
> > > > Sönke
> > > >
> > > >
> > > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> > justin@classsoftware.com
> > > >
> > > > geschrieben:
> > > >
> > > >> Hi,
> > > >>
> > > >>> Out of curiosity: Can you point at one or two? I assume it's mostly
> > the
> > > >>> newer ones.
> > > >>
> > > >> Yes mostly newer podlings but then that’s what I mostly work with for
> > > >> instance [1] (9,500+ issues), but there’s at least one TLP I also know
> > > that
> > > >> uses it. [2]
> > > >>
> > > >> This is not to say these projects are exemplar in any way or we should
> > > >> copy what they do. :-)
> > > >>
> > > >>> Not really. There's one thread that comes to mind[1]
> > > >>
> > > >> Yep it would seem that GitHub issues may be a bit of a grey area here.
> > > >>
> > > >> BTW I'm fine with JIRA but if people want to use GitHub issues I’m
> > also
> > > >> fine with that. I guess it come down to what is our audience most
> > > likely
> > > >> to want to use, being more the technical trainer types they may be
> > > familiar
> > > >> with a GitHub workflow rather than a JIRA one? But I’m not really
> > sure.
> > > >>
> > > >> Thanks,
> > > >> Justin
> > > >>
> > > >> 1. https://github.com/apache/incubator-echarts/issues
> > > >> 2. https://github.com/apache/royale-asjs/issues
> > > >>
> > > >>
> > >
> > >
> >
>
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
Okay. I'll go ahead and request it.
Similar to Confluence it would be good to have at least one or two more
administrators. If you give me your JIRA username I'll add you.
I'll have all notifications sent to dev@training.apache.org for now but I'm
very much in favor of having this separated out like this:
PR and issue creation -> dev@
PR and issue comments/close -> issues@
Git commit -> commits@
Not urgent for now but if you have an opinion on this let me know.
On Mon, Feb 25, 2019 at 5:10 PM Collin Rogowski <co...@inovex.de>
wrote:
> +1 for Jira
>
> cr
>
>
> On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de> wrote:
>
> > I would also favor Jira.
> >
> > Kind regards,
> > Hans-Peter
> >
> > > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <
> soenke.liebau@opencore.com
> > .INVALID>:
> > >
> > > Heyho,
> > >
> > > in the case of jira vs github issues I am in favor of jira.
> > > Github issues just feel .. "off" to me somehow as well as simply having
> > > less functionality.
> > >
> > > Best regards,
> > > Sönke
> > >
> > >
> > > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <
> justin@classsoftware.com
> > >
> > > geschrieben:
> > >
> > >> Hi,
> > >>
> > >>> Out of curiosity: Can you point at one or two? I assume it's mostly
> the
> > >>> newer ones.
> > >>
> > >> Yes mostly newer podlings but then that’s what I mostly work with for
> > >> instance [1] (9,500+ issues), but there’s at least one TLP I also know
> > that
> > >> uses it. [2]
> > >>
> > >> This is not to say these projects are exemplar in any way or we should
> > >> copy what they do. :-)
> > >>
> > >>> Not really. There's one thread that comes to mind[1]
> > >>
> > >> Yep it would seem that GitHub issues may be a bit of a grey area here.
> > >>
> > >> BTW I'm fine with JIRA but if people want to use GitHub issues I’m
> also
> > >> fine with that. I guess it come down to what is our audience most
> > likely
> > >> to want to use, being more the technical trainer types they may be
> > familiar
> > >> with a GitHub workflow rather than a JIRA one? But I’m not really
> sure.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >> 1. https://github.com/apache/incubator-echarts/issues
> > >> 2. https://github.com/apache/royale-asjs/issues
> > >>
> > >>
> >
> >
>
Re: Jira // Bug tracker
Posted by Collin Rogowski <co...@inovex.de>.
+1 for Jira
cr
On Mon, Feb 25, 2019 at 5:02 PM Hans-Peter Zorn <hz...@inovex.de> wrote:
> I would also favor Jira.
>
> Kind regards,
> Hans-Peter
>
> > Am 23.02.2019 um 00:36 schrieb Sönke Liebau <soenke.liebau@opencore.com
> .INVALID>:
> >
> > Heyho,
> >
> > in the case of jira vs github issues I am in favor of jira.
> > Github issues just feel .. "off" to me somehow as well as simply having
> > less functionality.
> >
> > Best regards,
> > Sönke
> >
> >
> > Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <justin@classsoftware.com
> >
> > geschrieben:
> >
> >> Hi,
> >>
> >>> Out of curiosity: Can you point at one or two? I assume it's mostly the
> >>> newer ones.
> >>
> >> Yes mostly newer podlings but then that’s what I mostly work with for
> >> instance [1] (9,500+ issues), but there’s at least one TLP I also know
> that
> >> uses it. [2]
> >>
> >> This is not to say these projects are exemplar in any way or we should
> >> copy what they do. :-)
> >>
> >>> Not really. There's one thread that comes to mind[1]
> >>
> >> Yep it would seem that GitHub issues may be a bit of a grey area here.
> >>
> >> BTW I'm fine with JIRA but if people want to use GitHub issues I’m also
> >> fine with that. I guess it come down to what is our audience most
> likely
> >> to want to use, being more the technical trainer types they may be
> familiar
> >> with a GitHub workflow rather than a JIRA one? But I’m not really sure.
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1. https://github.com/apache/incubator-echarts/issues
> >> 2. https://github.com/apache/royale-asjs/issues
> >>
> >>
>
>
Re: Jira // Bug tracker
Posted by Hans-Peter Zorn <hz...@inovex.de>.
I would also favor Jira.
Kind regards,
Hans-Peter
> Am 23.02.2019 um 00:36 schrieb Sönke Liebau <so...@opencore.com.INVALID>:
>
> Heyho,
>
> in the case of jira vs github issues I am in favor of jira.
> Github issues just feel .. "off" to me somehow as well as simply having
> less functionality.
>
> Best regards,
> Sönke
>
>
> Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <ju...@classsoftware.com>
> geschrieben:
>
>> Hi,
>>
>>> Out of curiosity: Can you point at one or two? I assume it's mostly the
>>> newer ones.
>>
>> Yes mostly newer podlings but then that’s what I mostly work with for
>> instance [1] (9,500+ issues), but there’s at least one TLP I also know that
>> uses it. [2]
>>
>> This is not to say these projects are exemplar in any way or we should
>> copy what they do. :-)
>>
>>> Not really. There's one thread that comes to mind[1]
>>
>> Yep it would seem that GitHub issues may be a bit of a grey area here.
>>
>> BTW I'm fine with JIRA but if people want to use GitHub issues I’m also
>> fine with that. I guess it come down to what is our audience most likely
>> to want to use, being more the technical trainer types they may be familiar
>> with a GitHub workflow rather than a JIRA one? But I’m not really sure.
>>
>> Thanks,
>> Justin
>>
>> 1. https://github.com/apache/incubator-echarts/issues
>> 2. https://github.com/apache/royale-asjs/issues
>>
>>
Re: Jira // Bug tracker
Posted by Sönke Liebau <so...@opencore.com.INVALID>.
Heyho,
in the case of jira vs github issues I am in favor of jira.
Github issues just feel .. "off" to me somehow as well as simply having
less functionality.
Best regards,
Sönke
Am Sa., 23. Feb. 2019, 00:14 hat Justin Mclean <ju...@classsoftware.com>
geschrieben:
> Hi,
>
> > Out of curiosity: Can you point at one or two? I assume it's mostly the
> > newer ones.
>
> Yes mostly newer podlings but then that’s what I mostly work with for
> instance [1] (9,500+ issues), but there’s at least one TLP I also know that
> uses it. [2]
>
> This is not to say these projects are exemplar in any way or we should
> copy what they do. :-)
>
> > Not really. There's one thread that comes to mind[1]
>
> Yep it would seem that GitHub issues may be a bit of a grey area here.
>
> BTW I'm fine with JIRA but if people want to use GitHub issues I’m also
> fine with that. I guess it come down to what is our audience most likely
> to want to use, being more the technical trainer types they may be familiar
> with a GitHub workflow rather than a JIRA one? But I’m not really sure.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/incubator-echarts/issues
> 2. https://github.com/apache/royale-asjs/issues
>
>
Re: Jira // Bug tracker
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Out of curiosity: Can you point at one or two? I assume it's mostly the
> newer ones.
Yes mostly newer podlings but then that’s what I mostly work with for instance [1] (9,500+ issues), but there’s at least one TLP I also know that uses it. [2]
This is not to say these projects are exemplar in any way or we should copy what they do. :-)
> Not really. There's one thread that comes to mind[1]
Yep it would seem that GitHub issues may be a bit of a grey area here.
BTW I'm fine with JIRA but if people want to use GitHub issues I’m also fine with that. I guess it come down to what is our audience most likely to want to use, being more the technical trainer types they may be familiar with a GitHub workflow rather than a JIRA one? But I’m not really sure.
Thanks,
Justin
1. https://github.com/apache/incubator-echarts/issues
2. https://github.com/apache/royale-asjs/issues
Re: Jira // Bug tracker
Posted by Lars Francke <la...@gmail.com>.
>
> > As far as I know Github issues are not an option because the content is
> not
> > owned by the ASF.
>
> A lot of projects do use Github issues, some exclusively even to the point
> of hardly using the mailing list.
>
That's good to know.
You can tell that I work at different projects than you do :)
Out of curiosity: Can you point at one or two? I assume it's mostly the
newer ones.
> I don't recall anything about the content not being owned by the ASF. You
> mind pointing to where that was discussed? Do you know if this is still the
> case?
>
Not really. There's one thread that comes to mind[1] but it's more like I
thought I'd remembered this being the case when we first discussed Github
at HBase et. al but that was years ago. Your knowledge is almost certainly
more recent.
[1] <
https://lists.apache.org/thread.html/fda7637c563749c01bc7c28b9da20356568cd7b6ecdfe6ea6f623785@%3Cdev.community.apache.org%3E
>
> Thanks,
> Justin
Re: Jira // Bug tracker
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> As far as I know Github issues are not an option because the content is not
> owned by the ASF.
A lot of projects do use Github issues, some exclusively even to the point of hardly using the mailing list.
I don't recall anything about the content not being owned by the ASF. You mind pointing to where that was discussed? Do you know if this is still the case?
Thanks,
Justin