Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Sterling Hughes]

I think we’ve left enough time, and everybody has agreed.  Let’s get 
on GitHub issues ASAP!




On 23 Feb 2018, at 5:31, Fabio Utzig wrote:


So, when is a decision going to be made?

On Thu, Feb 8, 2018, at 11:15 AM, Miguel Azevedo wrote:

+1

I strongly agree to track issues on github, the integration with
github issues and PRs is very good and there's a lot of people 
already

using it on other projects.
Thanks,

Miguel

On Thu, Feb 8, 2018 at 5:34 AM, Fabio Utzig  wrote:

+1

I prefer as much information in a single place as possible, and GH 
as been adding more and more "project management" features making it 
better suited as a Jira alternative (and btw, we already made this 
move with MCUBoot!).


Cheers,
Fabio Utzig

On Tue, Feb 6, 2018, at 2:27 PM, Christopher Collins wrote:

On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:

Hi,

Multiple people have suggested that issues be tracked on Github 
close
to the code. The benefit is that contributors don’t have to 
switch

between two systems to raise and clear issues.  Please let your
thoughts known either way.


I agree with switching to github issues.

Jira seems more powerful and I do like it, but I find the extra
flexibility is outweighed by the difficulty of using two different
systems (github for PRs, Jira for issues).

Chris




--
--
Miguel Azevedo

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Fabio Utzig]

So, when is a decision going to be made?

On Thu, Feb 8, 2018, at 11:15 AM, Miguel Azevedo wrote:
> +1
> 
> I strongly agree to track issues on github, the integration with
> github issues and PRs is very good and there's a lot of people already
> using it on other projects.
> Thanks,
> 
> Miguel
> 
> On Thu, Feb 8, 2018 at 5:34 AM, Fabio Utzig  wrote:
> > +1
> >
> > I prefer as much information in a single place as possible, and GH as been 
> > adding more and more "project management" features making it better suited 
> > as a Jira alternative (and btw, we already made this move with MCUBoot!).
> >
> > Cheers,
> > Fabio Utzig
> >
> > On Tue, Feb 6, 2018, at 2:27 PM, Christopher Collins wrote:
> >> On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:
> >> > Hi,
> >> >
> >> > Multiple people have suggested that issues be tracked on Github close
> >> > to the code. The benefit is that contributors don’t have to switch
> >> > between two systems to raise and clear issues.  Please let your
> >> > thoughts known either way.
> >>
> >> I agree with switching to github issues.
> >>
> >> Jira seems more powerful and I do like it, but I find the extra
> >> flexibility is outweighed by the difficulty of using two different
> >> systems (github for PRs, Jira for issues).
> >>
> >> Chris
> 
> 
> 
> -- 
> --
> Miguel Azevedo

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Miguel Azevedo]

+1

I strongly agree to track issues on github, the integration with
github issues and PRs is very good and there's a lot of people already
using it on other projects.
Thanks,

Miguel

On Thu, Feb 8, 2018 at 5:34 AM, Fabio Utzig  wrote:
> +1
>
> I prefer as much information in a single place as possible, and GH as been 
> adding more and more "project management" features making it better suited as 
> a Jira alternative (and btw, we already made this move with MCUBoot!).
>
> Cheers,
> Fabio Utzig
>
> On Tue, Feb 6, 2018, at 2:27 PM, Christopher Collins wrote:
>> On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:
>> > Hi,
>> >
>> > Multiple people have suggested that issues be tracked on Github close
>> > to the code. The benefit is that contributors don’t have to switch
>> > between two systems to raise and clear issues.  Please let your
>> > thoughts known either way.
>>
>> I agree with switching to github issues.
>>
>> Jira seems more powerful and I do like it, but I find the extra
>> flexibility is outweighed by the difficulty of using two different
>> systems (github for PRs, Jira for issues).
>>
>> Chris



-- 
--
Miguel Azevedo

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Fabio Utzig]

+1

I prefer as much information in a single place as possible, and GH as been 
adding more and more "project management" features making it better suited as a 
Jira alternative (and btw, we already made this move with MCUBoot!).

Cheers,
Fabio Utzig

On Tue, Feb 6, 2018, at 2:27 PM, Christopher Collins wrote:
> On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:
> > Hi,
> > 
> > Multiple people have suggested that issues be tracked on Github close
> > to the code. The benefit is that contributors don’t have to switch
> > between two systems to raise and clear issues.  Please let your
> > thoughts known either way.
> 
> I agree with switching to github issues.
> 
> Jira seems more powerful and I do like it, but I find the extra
> flexibility is outweighed by the difficulty of using two different
> systems (github for PRs, Jira for issues).
> 
> Chris

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Christopher Collins]

On Tue, Feb 06, 2018 at 12:26:17AM -0800, aditi hilbert wrote:
> Hi,
> 
> Multiple people have suggested that issues be tracked on Github close
> to the code. The benefit is that contributors don’t have to switch
> between two systems to raise and clear issues.  Please let your
> thoughts known either way.

I agree with switching to github issues.

Jira seems more powerful and I do like it, but I find the extra
flexibility is outweighed by the difficulty of using two different
systems (github for PRs, Jira for issues).

Chris

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Andrzej Kaczmarek]

Hi Aditi,

On Tue, Feb 6, 2018 at 9:26 AM, aditi hilbert  wrote:

> Hi,
>
> Multiple people have suggested that issues be tracked on Github close to
> the code. The benefit is that contributors don’t have to switch between two
> systems to raise and clear issues.  Please let your thoughts known either
> way.
>

​+1​
GitHub issues are just enough for Mynewt purposes and I guess more people
will be willing to file issues - Jira is just overly complicated.


> In preparation for such a move (if the majority agrees to), “Issues” has
> been enabled on our GitHub repos.
> https://github.com/apache/mynewt-core  mynewt-core>
> https://github.com/apache/mynewt-newt  mynewt-newt>
> https://github.com/apache/mynewt-newtmgr  mynewt-newtmgr>
> https://github.com/apache/mynewt-nimble  mynewt-nimble>
> https://github.com/apache/mynewt-documentation  mynewt-documentation>
> https://github.com/apache/mynewt-mcumgr  mynewt-mcumgr>
>
> Issues are yet to be turned on for a couple of repos.
>
> thanks,
> Aditi


​Best,
Andrzej
​

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Jacob Rosenthal]

I find github issues vastly easier to subscribe track and submit +1

On Tue, Feb 6, 2018 at 4:21 AM, Łukasz Rymanowski <
lukasz.rymanow...@codecoup.pl> wrote:

> Hi,
>
> On 6 February 2018 at 09:26, aditi hilbert  wrote:
> > Hi,
> >
> > Multiple people have suggested that issues be tracked on Github close to
> the code. The benefit is that contributors don’t have to switch between two
> systems to raise and clear issues.  Please let your thoughts known either
> way.
> >
> > In preparation for such a move (if the majority agrees to), “Issues” has
> been enabled on our GitHub repos.
> > https://github.com/apache/mynewt-core  mynewt-core>
> > https://github.com/apache/mynewt-newt  mynewt-newt>
> > https://github.com/apache/mynewt-newtmgr  mynewt-newtmgr>
> > https://github.com/apache/mynewt-nimble  mynewt-nimble>
> > https://github.com/apache/mynewt-documentation <
> https://github.com/apache/mynewt-documentation>
> > https://github.com/apache/mynewt-mcumgr  mynewt-mcumgr>
> >
> > Issues are yet to be turned on for a couple of repos.
>
> I like the idea.
> +1
>
> >
> > thanks,
> > Aditi
>
> Best
> Łukasz
>

Re: [DISCUSS] To track issues on Github for Apache Mynewt projects or not?

[Łukasz Rymanowski]

Hi,

On 6 February 2018 at 09:26, aditi hilbert  wrote:
> Hi,
>
> Multiple people have suggested that issues be tracked on Github close to the 
> code. The benefit is that contributors don’t have to switch between two 
> systems to raise and clear issues.  Please let your thoughts known either way.
>
> In preparation for such a move (if the majority agrees to), “Issues” has been 
> enabled on our GitHub repos.
> https://github.com/apache/mynewt-core 
> https://github.com/apache/mynewt-newt 
> https://github.com/apache/mynewt-newtmgr 
> 
> https://github.com/apache/mynewt-nimble 
> 
> https://github.com/apache/mynewt-documentation 
> 
> https://github.com/apache/mynewt-mcumgr 
> 
>
> Issues are yet to be turned on for a couple of repos.

I like the idea.
+1

>
> thanks,
> Aditi

Best
Łukasz