You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Gregory Nutt <sp...@gmail.com> on 2019/12/29 20:13:48 UTC
Issue Reporting
It has been reported to me that Issues are disabled at
https://github.com/apache/incubator-nuttx-apps:
<https://github.com/apache/incubator-nuttx-apps>
https://bitbucket.org/nuttx/apps/issues/15/null-dereference-in-ftp-size-command
We need to decide how people report problems to us. GIT issues? Jira?
dev@apache.org? We need to make some decisions. I think Jira would
give us the best bug tracking options. GIT issues is well integrated on
github. I think dev@apache.org is a bad idea.
There is a backlog of Issues/bugs at
https://bitbucket.org/nuttx/nuttx/issues?status=new&status=open and
https://bitbucket.org/nuttx/apps/issues?status=new&status=open (and also
issues in the top-level NuttX TODO file). I have a personal list of
things that I thing should be done as well.
We probably need another Confluence page talking about bug-reporting.
Greg
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
> I like this. I prefer that we use Apache's Jira for several reasons,
> especially in light of the integration that Brennan describes.
I think we should give it a try. I don't know enough to have a strong
opinion.
Jira also integrates with an Agile project management process. Is that
something we want to consider? Having some project management
infrastructure would be better than trying to manage everything through
a massive number of emails.
But again, I am interested but not yet a proponent.
Greg
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
> +1 for github
There has been no formal [VOTE] started. Any formal vote must be
preceded by a [DISCUSS] so that we can all understand the issues and we
can all be qualified to vote.
It is probably too early to start a discussion or vote since we have not
eventthe vaguest plan in place for project management yet.
Re: Issue Reporting
Posted by David Sidrane <da...@nscdg.com>.
Thank You!
On Thu, Jan 9, 2020, 10:27 PM Brennan Ashton <ba...@brennanashton.com>
wrote:
> Ok we now have issues and projects on apache-nuttx.
> No projects have been configured, but I suspect a lot of the project
> management features that people were asking about can be handled via this,
> see the docs:
>
> https://help.github.com/en/github/managing-your-work-on-github/about-project-boards
>
> Also we should probably add issue templates for Bugs, Features, etc...
> This is a great place to point people to helpful things like the "how to
> debug hard-faults" article.
> If you are not familiar with this GitHub feature, Zephyr makes good use of
> it:
> https://github.com/zephyrproject-rtos/zephyr/issues/new/choose
> They come from templates placed in this directory:
>
> https://github.com/zephyrproject-rtos/zephyr/tree/master/.github/ISSUE_TEMPLATE
>
> --Brennan
>
> On Thu, Jan 9, 2020 at 7:03 PM Brennan Ashton <ba...@brennanashton.com>
> wrote:
>
>> I was going to only apply it to the os repo so we have one place to
>> triage/manage and people might not know where to file an issue or I might
>> span both. We can use labels to further filter, this is how I usually see
>> it done for projects with multiple repos.
>>
>> We can always enable the apps one later if it makes more sense.
>>
>> --brennan
>>
>> On Thu, Jan 9, 2020, 6:56 PM Xiang Xiao <xi...@gmail.com>
>> wrote:
>>
>>> Ok, I have closed it.
>>>
>>> On Fri, Jan 10, 2020 at 10:51 AM Brennan Ashton <
>>> bashton@brennanashton.com> wrote:
>>>
>>>> As I said we control this. I'll open the correct PR, let's not bother
>>>> infra when it is on us.
>>>>
>>>> --Brennan
>>>>
>>>> On Thu, Jan 9, 2020, 6:43 PM Xiang Xiao <xi...@gmail.com>
>>>> wrote:
>>>>
>>>>> I justed open a JIRA for this:
>>>>> https://issues.apache.org/jira/browse/INFRA-19692
>>>>>
>>>>> Thanks
>>>>> Xiang
>>>>>
>>>>> On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt <sp...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> My preference would be to let users submit issues on github, but then
>>>>>> track them with Jira. Is it possible to link Jira issues to github issues?
>>>>>>
>>>>>> Otherwise, the rest that you say makes good sense.
>>>>>>
>>>>>> We do need to consolidate issues in one place somehow. Currently,
>>>>>> there are issues in apps and nuttx Bitbucket, we will open up for issues on
>>>>>> apps and nuttx github. And there is the TODO list in the nuttx repository
>>>>>> (and I have my own TODO list which should be passed upward.
>>>>>>
>>>>>> That seems like a recipe for things falling through the crack (as
>>>>>> they already have).
>>>>>> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>>>>>>
>>>>>> It seems like most people are pushing towards the simplicity of
>>>>>> GitHub. My main objection was that we put such a focus on letting people
>>>>>> submit code without using GitHub that it seemed odd to then force GitHub
>>>>>> for issues. JIRA can really do a lot but I see it as tool that gives you a
>>>>>> million features and leaves you to wire it up (I have used it for work for
>>>>>> many years) Unless there is someone that wants to do the wiring work it's
>>>>>> likely not going to be better than what we get with GitHub.
>>>>>>
>>>>>> As for the project management component, we can enable the GitHub
>>>>>> features for that. It's simple but plenty powerful for what we likely need
>>>>>> to so. Even creating filtered views with tags is likely all we need for
>>>>>> some time.
>>>>>>
>>>>>> I would propose we open up GitHub issues only on the apache-nuttx
>>>>>> project and start there and let it naturally grow.
>>>>>>
>>>>>> If we need to move to JIRA for some reason as the project grows, I'll
>>>>>> volunteer to move the data.
>>>>>>
>>>>>> This can all be turned on with the .asf.yml file and I can submit the
>>>>>> pr for that if we want.
>>>>>>
>>>>>> --Brennan
>>>>>>
>>>>>>
>>>>>> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> For me I suggest we start with GitHub issues.
>>>>>>>
>>>>>>> For problem #1, the cross repo PRs, I think it is fine to have only
>>>>>>> one issue in the main repo? We can reference multiple PRs in an issue and
>>>>>>> the PRs could come from other repos.
>>>>>>>
>>>>>>> And for problem #2, once the user sends the patch to this mailing
>>>>>>> list, it is the committers duty to open an issue for this, and also open a
>>>>>>> PR with this patch to let others review and get the patch in finally.
>>>>>>>
>>>>>>> I think for most projects which use JIRA, is just because that
>>>>>>> GitHub was not available when the project was set up. And then the work
>>>>>>> flow, and release processing are already bound with JIRA, so we keep using
>>>>>>> JIRA for issue tracking. But I think for a new project, just make use of
>>>>>>> GitHub is fine.
>>>>>>>
>>>>>>> Of course I'm also fine with using JIRA, no problem. Just a
>>>>>>> suggestion.
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>>>>>>>
>>>>>>>> Hi Brenan,
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> See Below.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>>>>>>>> Sent: Monday, December 30, 2019 8:52 AM
>>>>>>>> To: dev@nuttx.apache.org
>>>>>>>> Subject: Re: Issue Reporting
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Can people who are advocating for GitHub address the two main
>>>>>>>> points that I
>>>>>>>>
>>>>>>>> had made. The second one I really don't see a workaround for. To
>>>>>>>> be clear
>>>>>>>>
>>>>>>>> if we can get around both of these I'm happy to be on the GitHub
>>>>>>>> train.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 1) Multiple repos. We might have an issue or feature the spans the
>>>>>>>> os,
>>>>>>>>
>>>>>>>> app, and website repos now we need to file tickets in each or
>>>>>>>> something
>>>>>>>>
>>>>>>>> equally ugly
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [DBS] I already suggested how this is a solved problem on Github.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> We do it all the time in PX4.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> See last post in Firmware repos
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> [image: @julianoes] <https://github.com/julianoes> julianoes
>>>>>>>> <https://github.com/julianoes> closed this in #13311
>>>>>>>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>>>>>>>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>>>>>>>
>>>>>>>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Follow it https://github.com/PX4/Firmware/pull/13311
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> And Look here
>>>>>>>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> See this post in Firmware repos it references NuttX repo.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> It just works. See https://github.com/PX4/NuttX/pull/70
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The problem is solved one in github!
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> But the real and proper answer is use a Knot repo. - But I will not
>>>>>>>> waste my typing any more on this.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2) Sounds like we have people who cannot use Github, now they
>>>>>>>> cannot use
>>>>>>>>
>>>>>>>> the issue tracker so we have people using the mailing list which is
>>>>>>>> less
>>>>>>>>
>>>>>>>> ideal.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list
>>>>>>>> bot. They (the github denied) can email one of these nifty lists.*
>>>>>>>>
>>>>>>>> *ihavenogithubaccess@nuttx.apache.org
>>>>>>>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> As for templating and the like you can do this all JIRA as well.
>>>>>>>> The
>>>>>>>>
>>>>>>>> linking between the two is also done so those are not really
>>>>>>>> blockers.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --Brennan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> > +1 for github
>>>>>>>>
>>>>>>>> >
>>>>>>>>
>>>>>>>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> >
>>>>>>>>
>>>>>>>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>>>>>>>
>>>>>>>> > > Are they mutually exclusive?
>>>>>>>>
>>>>>>>> > >
>>>>>>>>
>>>>>>>> >
>>>>>>>>
>>>>>>>
Re: Issue Reporting
Posted by Brennan Ashton <ba...@brennanashton.com>.
Ok we now have issues and projects on apache-nuttx.
No projects have been configured, but I suspect a lot of the project
management features that people were asking about can be handled via this,
see the docs:
https://help.github.com/en/github/managing-your-work-on-github/about-project-boards
Also we should probably add issue templates for Bugs, Features, etc...
This is a great place to point people to helpful things like the "how to
debug hard-faults" article.
If you are not familiar with this GitHub feature, Zephyr makes good use of
it:
https://github.com/zephyrproject-rtos/zephyr/issues/new/choose
They come from templates placed in this directory:
https://github.com/zephyrproject-rtos/zephyr/tree/master/.github/ISSUE_TEMPLATE
--Brennan
On Thu, Jan 9, 2020 at 7:03 PM Brennan Ashton <ba...@brennanashton.com>
wrote:
> I was going to only apply it to the os repo so we have one place to
> triage/manage and people might not know where to file an issue or I might
> span both. We can use labels to further filter, this is how I usually see
> it done for projects with multiple repos.
>
> We can always enable the apps one later if it makes more sense.
>
> --brennan
>
> On Thu, Jan 9, 2020, 6:56 PM Xiang Xiao <xi...@gmail.com> wrote:
>
>> Ok, I have closed it.
>>
>> On Fri, Jan 10, 2020 at 10:51 AM Brennan Ashton <
>> bashton@brennanashton.com> wrote:
>>
>>> As I said we control this. I'll open the correct PR, let's not bother
>>> infra when it is on us.
>>>
>>> --Brennan
>>>
>>> On Thu, Jan 9, 2020, 6:43 PM Xiang Xiao <xi...@gmail.com>
>>> wrote:
>>>
>>>> I justed open a JIRA for this:
>>>> https://issues.apache.org/jira/browse/INFRA-19692
>>>>
>>>> Thanks
>>>> Xiang
>>>>
>>>> On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt <sp...@gmail.com>
>>>> wrote:
>>>>
>>>>> My preference would be to let users submit issues on github, but then
>>>>> track them with Jira. Is it possible to link Jira issues to github issues?
>>>>>
>>>>> Otherwise, the rest that you say makes good sense.
>>>>>
>>>>> We do need to consolidate issues in one place somehow. Currently,
>>>>> there are issues in apps and nuttx Bitbucket, we will open up for issues on
>>>>> apps and nuttx github. And there is the TODO list in the nuttx repository
>>>>> (and I have my own TODO list which should be passed upward.
>>>>>
>>>>> That seems like a recipe for things falling through the crack (as they
>>>>> already have).
>>>>> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>>>>>
>>>>> It seems like most people are pushing towards the simplicity of
>>>>> GitHub. My main objection was that we put such a focus on letting people
>>>>> submit code without using GitHub that it seemed odd to then force GitHub
>>>>> for issues. JIRA can really do a lot but I see it as tool that gives you a
>>>>> million features and leaves you to wire it up (I have used it for work for
>>>>> many years) Unless there is someone that wants to do the wiring work it's
>>>>> likely not going to be better than what we get with GitHub.
>>>>>
>>>>> As for the project management component, we can enable the GitHub
>>>>> features for that. It's simple but plenty powerful for what we likely need
>>>>> to so. Even creating filtered views with tags is likely all we need for
>>>>> some time.
>>>>>
>>>>> I would propose we open up GitHub issues only on the apache-nuttx
>>>>> project and start there and let it naturally grow.
>>>>>
>>>>> If we need to move to JIRA for some reason as the project grows, I'll
>>>>> volunteer to move the data.
>>>>>
>>>>> This can all be turned on with the .asf.yml file and I can submit the
>>>>> pr for that if we want.
>>>>>
>>>>> --Brennan
>>>>>
>>>>>
>>>>> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> For me I suggest we start with GitHub issues.
>>>>>>
>>>>>> For problem #1, the cross repo PRs, I think it is fine to have only
>>>>>> one issue in the main repo? We can reference multiple PRs in an issue and
>>>>>> the PRs could come from other repos.
>>>>>>
>>>>>> And for problem #2, once the user sends the patch to this mailing
>>>>>> list, it is the committers duty to open an issue for this, and also open a
>>>>>> PR with this patch to let others review and get the patch in finally.
>>>>>>
>>>>>> I think for most projects which use JIRA, is just because that GitHub
>>>>>> was not available when the project was set up. And then the work flow, and
>>>>>> release processing are already bound with JIRA, so we keep using JIRA for
>>>>>> issue tracking. But I think for a new project, just make use of GitHub is
>>>>>> fine.
>>>>>>
>>>>>> Of course I'm also fine with using JIRA, no problem. Just a
>>>>>> suggestion.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>>>>>>
>>>>>>> Hi Brenan,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> See Below.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>>>>>>> Sent: Monday, December 30, 2019 8:52 AM
>>>>>>> To: dev@nuttx.apache.org
>>>>>>> Subject: Re: Issue Reporting
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Can people who are advocating for GitHub address the two main points
>>>>>>> that I
>>>>>>>
>>>>>>> had made. The second one I really don't see a workaround for. To be
>>>>>>> clear
>>>>>>>
>>>>>>> if we can get around both of these I'm happy to be on the GitHub
>>>>>>> train.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 1) Multiple repos. We might have an issue or feature the spans the
>>>>>>> os,
>>>>>>>
>>>>>>> app, and website repos now we need to file tickets in each or
>>>>>>> something
>>>>>>>
>>>>>>> equally ugly
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [DBS] I already suggested how this is a solved problem on Github.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> We do it all the time in PX4.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> See last post in Firmware repos
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [image: @julianoes] <https://github.com/julianoes> julianoes
>>>>>>> <https://github.com/julianoes> closed this in #13311
>>>>>>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>>>>>>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>>>>>>
>>>>>>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Follow it https://github.com/PX4/Firmware/pull/13311
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> And Look here
>>>>>>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> See this post in Firmware repos it references NuttX repo.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> It just works. See https://github.com/PX4/NuttX/pull/70
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The problem is solved one in github!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> But the real and proper answer is use a Knot repo. - But I will not
>>>>>>> waste my typing any more on this.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2) Sounds like we have people who cannot use Github, now they cannot
>>>>>>> use
>>>>>>>
>>>>>>> the issue tracker so we have people using the mailing list which is
>>>>>>> less
>>>>>>>
>>>>>>> ideal.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list
>>>>>>> bot. They (the github denied) can email one of these nifty lists.*
>>>>>>>
>>>>>>> *ihavenogithubaccess@nuttx.apache.org
>>>>>>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> As for templating and the like you can do this all JIRA as well. The
>>>>>>>
>>>>>>> linking between the two is also done so those are not really
>>>>>>> blockers.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --Brennan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> > +1 for github
>>>>>>>
>>>>>>> >
>>>>>>>
>>>>>>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> >
>>>>>>>
>>>>>>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>>>>>>
>>>>>>> > > Are they mutually exclusive?
>>>>>>>
>>>>>>> > >
>>>>>>>
>>>>>>> >
>>>>>>>
>>>>>>
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
> I was going to only apply it to the os repo so we have one place to
> triage/manage and people might not know where to file an issue or I
> might span both. We can use labels to further filter, this is how I
> usually see it done for projects with multiple repos.
>
> We can always enable the apps one later if it makes more sense.
Historically, people have use both depending on the repository that
contains the issue. This will certainly come up again when we try to
explain people why we do not accept issues in the apps/ repository.
Re: Issue Reporting
Posted by Brennan Ashton <ba...@brennanashton.com>.
I was going to only apply it to the os repo so we have one place to
triage/manage and people might not know where to file an issue or I might
span both. We can use labels to further filter, this is how I usually see
it done for projects with multiple repos.
We can always enable the apps one later if it makes more sense.
--brennan
On Thu, Jan 9, 2020, 6:56 PM Xiang Xiao <xi...@gmail.com> wrote:
> Ok, I have closed it.
>
> On Fri, Jan 10, 2020 at 10:51 AM Brennan Ashton <ba...@brennanashton.com>
> wrote:
>
>> As I said we control this. I'll open the correct PR, let's not bother
>> infra when it is on us.
>>
>> --Brennan
>>
>> On Thu, Jan 9, 2020, 6:43 PM Xiang Xiao <xi...@gmail.com>
>> wrote:
>>
>>> I justed open a JIRA for this:
>>> https://issues.apache.org/jira/browse/INFRA-19692
>>>
>>> Thanks
>>> Xiang
>>>
>>> On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt <sp...@gmail.com>
>>> wrote:
>>>
>>>> My preference would be to let users submit issues on github, but then
>>>> track them with Jira. Is it possible to link Jira issues to github issues?
>>>>
>>>> Otherwise, the rest that you say makes good sense.
>>>>
>>>> We do need to consolidate issues in one place somehow. Currently,
>>>> there are issues in apps and nuttx Bitbucket, we will open up for issues on
>>>> apps and nuttx github. And there is the TODO list in the nuttx repository
>>>> (and I have my own TODO list which should be passed upward.
>>>>
>>>> That seems like a recipe for things falling through the crack (as they
>>>> already have).
>>>> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>>>>
>>>> It seems like most people are pushing towards the simplicity of GitHub.
>>>> My main objection was that we put such a focus on letting people submit
>>>> code without using GitHub that it seemed odd to then force GitHub for
>>>> issues. JIRA can really do a lot but I see it as tool that gives you a
>>>> million features and leaves you to wire it up (I have used it for work for
>>>> many years) Unless there is someone that wants to do the wiring work it's
>>>> likely not going to be better than what we get with GitHub.
>>>>
>>>> As for the project management component, we can enable the GitHub
>>>> features for that. It's simple but plenty powerful for what we likely need
>>>> to so. Even creating filtered views with tags is likely all we need for
>>>> some time.
>>>>
>>>> I would propose we open up GitHub issues only on the apache-nuttx
>>>> project and start there and let it naturally grow.
>>>>
>>>> If we need to move to JIRA for some reason as the project grows, I'll
>>>> volunteer to move the data.
>>>>
>>>> This can all be turned on with the .asf.yml file and I can submit the
>>>> pr for that if we want.
>>>>
>>>> --Brennan
>>>>
>>>>
>>>> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com>
>>>> wrote:
>>>>
>>>>> For me I suggest we start with GitHub issues.
>>>>>
>>>>> For problem #1, the cross repo PRs, I think it is fine to have only
>>>>> one issue in the main repo? We can reference multiple PRs in an issue and
>>>>> the PRs could come from other repos.
>>>>>
>>>>> And for problem #2, once the user sends the patch to this mailing
>>>>> list, it is the committers duty to open an issue for this, and also open a
>>>>> PR with this patch to let others review and get the patch in finally.
>>>>>
>>>>> I think for most projects which use JIRA, is just because that GitHub
>>>>> was not available when the project was set up. And then the work flow, and
>>>>> release processing are already bound with JIRA, so we keep using JIRA for
>>>>> issue tracking. But I think for a new project, just make use of GitHub is
>>>>> fine.
>>>>>
>>>>> Of course I'm also fine with using JIRA, no problem. Just a suggestion.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>>>>>
>>>>>> Hi Brenan,
>>>>>>
>>>>>>
>>>>>>
>>>>>> See Below.
>>>>>>
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>>>>>> Sent: Monday, December 30, 2019 8:52 AM
>>>>>> To: dev@nuttx.apache.org
>>>>>> Subject: Re: Issue Reporting
>>>>>>
>>>>>>
>>>>>>
>>>>>> Can people who are advocating for GitHub address the two main points
>>>>>> that I
>>>>>>
>>>>>> had made. The second one I really don't see a workaround for. To be
>>>>>> clear
>>>>>>
>>>>>> if we can get around both of these I'm happy to be on the GitHub
>>>>>> train.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 1) Multiple repos. We might have an issue or feature the spans the
>>>>>> os,
>>>>>>
>>>>>> app, and website repos now we need to file tickets in each or
>>>>>> something
>>>>>>
>>>>>> equally ugly
>>>>>>
>>>>>>
>>>>>>
>>>>>> [DBS] I already suggested how this is a solved problem on Github.
>>>>>>
>>>>>>
>>>>>>
>>>>>> We do it all the time in PX4.
>>>>>>
>>>>>>
>>>>>>
>>>>>> See last post in Firmware repos
>>>>>>
>>>>>>
>>>>>>
>>>>>> [image: @julianoes] <https://github.com/julianoes> julianoes
>>>>>> <https://github.com/julianoes> closed this in #13311
>>>>>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>>>>>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>>>>>
>>>>>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>>>>>
>>>>>>
>>>>>>
>>>>>> Follow it https://github.com/PX4/Firmware/pull/13311
>>>>>>
>>>>>>
>>>>>>
>>>>>> And Look here
>>>>>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> See this post in Firmware repos it references NuttX repo.
>>>>>>
>>>>>>
>>>>>>
>>>>>> It just works. See https://github.com/PX4/NuttX/pull/70
>>>>>>
>>>>>>
>>>>>>
>>>>>> The problem is solved one in github!
>>>>>>
>>>>>>
>>>>>>
>>>>>> But the real and proper answer is use a Knot repo. - But I will not
>>>>>> waste my typing any more on this.
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2) Sounds like we have people who cannot use Github, now they cannot
>>>>>> use
>>>>>>
>>>>>> the issue tracker so we have people using the mailing list which is
>>>>>> less
>>>>>>
>>>>>> ideal.
>>>>>>
>>>>>>
>>>>>>
>>>>>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list
>>>>>> bot. They (the github denied) can email one of these nifty lists.*
>>>>>>
>>>>>> *ihavenogithubaccess@nuttx.apache.org
>>>>>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>>>>>
>>>>>>
>>>>>>
>>>>>> As for templating and the like you can do this all JIRA as well. The
>>>>>>
>>>>>> linking between the two is also done so those are not really blockers.
>>>>>>
>>>>>>
>>>>>>
>>>>>> --Brennan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> > +1 for github
>>>>>>
>>>>>> >
>>>>>>
>>>>>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> >
>>>>>>
>>>>>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>>>>>
>>>>>> > > Are they mutually exclusive?
>>>>>>
>>>>>> > >
>>>>>>
>>>>>> >
>>>>>>
>>>>>
Re: Issue Reporting
Posted by Xiang Xiao <xi...@gmail.com>.
Ok, I have closed it.
On Fri, Jan 10, 2020 at 10:51 AM Brennan Ashton <ba...@brennanashton.com>
wrote:
> As I said we control this. I'll open the correct PR, let's not bother
> infra when it is on us.
>
> --Brennan
>
> On Thu, Jan 9, 2020, 6:43 PM Xiang Xiao <xi...@gmail.com> wrote:
>
>> I justed open a JIRA for this:
>> https://issues.apache.org/jira/browse/INFRA-19692
>>
>> Thanks
>> Xiang
>>
>> On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt <sp...@gmail.com> wrote:
>>
>>> My preference would be to let users submit issues on github, but then
>>> track them with Jira. Is it possible to link Jira issues to github issues?
>>>
>>> Otherwise, the rest that you say makes good sense.
>>>
>>> We do need to consolidate issues in one place somehow. Currently, there
>>> are issues in apps and nuttx Bitbucket, we will open up for issues on apps
>>> and nuttx github. And there is the TODO list in the nuttx repository (and
>>> I have my own TODO list which should be passed upward.
>>>
>>> That seems like a recipe for things falling through the crack (as they
>>> already have).
>>> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>>>
>>> It seems like most people are pushing towards the simplicity of GitHub.
>>> My main objection was that we put such a focus on letting people submit
>>> code without using GitHub that it seemed odd to then force GitHub for
>>> issues. JIRA can really do a lot but I see it as tool that gives you a
>>> million features and leaves you to wire it up (I have used it for work for
>>> many years) Unless there is someone that wants to do the wiring work it's
>>> likely not going to be better than what we get with GitHub.
>>>
>>> As for the project management component, we can enable the GitHub
>>> features for that. It's simple but plenty powerful for what we likely need
>>> to so. Even creating filtered views with tags is likely all we need for
>>> some time.
>>>
>>> I would propose we open up GitHub issues only on the apache-nuttx
>>> project and start there and let it naturally grow.
>>>
>>> If we need to move to JIRA for some reason as the project grows, I'll
>>> volunteer to move the data.
>>>
>>> This can all be turned on with the .asf.yml file and I can submit the pr
>>> for that if we want.
>>>
>>> --Brennan
>>>
>>>
>>> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com>
>>> wrote:
>>>
>>>> For me I suggest we start with GitHub issues.
>>>>
>>>> For problem #1, the cross repo PRs, I think it is fine to have only one
>>>> issue in the main repo? We can reference multiple PRs in an issue and the
>>>> PRs could come from other repos.
>>>>
>>>> And for problem #2, once the user sends the patch to this mailing list,
>>>> it is the committers duty to open an issue for this, and also open a PR
>>>> with this patch to let others review and get the patch in finally.
>>>>
>>>> I think for most projects which use JIRA, is just because that GitHub
>>>> was not available when the project was set up. And then the work flow, and
>>>> release processing are already bound with JIRA, so we keep using JIRA for
>>>> issue tracking. But I think for a new project, just make use of GitHub is
>>>> fine.
>>>>
>>>> Of course I'm also fine with using JIRA, no problem. Just a suggestion.
>>>>
>>>> Thanks.
>>>>
>>>> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>>>>
>>>>> Hi Brenan,
>>>>>
>>>>>
>>>>>
>>>>> See Below.
>>>>>
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>>>>> Sent: Monday, December 30, 2019 8:52 AM
>>>>> To: dev@nuttx.apache.org
>>>>> Subject: Re: Issue Reporting
>>>>>
>>>>>
>>>>>
>>>>> Can people who are advocating for GitHub address the two main points
>>>>> that I
>>>>>
>>>>> had made. The second one I really don't see a workaround for. To be
>>>>> clear
>>>>>
>>>>> if we can get around both of these I'm happy to be on the GitHub train.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 1) Multiple repos. We might have an issue or feature the spans the os,
>>>>>
>>>>> app, and website repos now we need to file tickets in each or something
>>>>>
>>>>> equally ugly
>>>>>
>>>>>
>>>>>
>>>>> [DBS] I already suggested how this is a solved problem on Github.
>>>>>
>>>>>
>>>>>
>>>>> We do it all the time in PX4.
>>>>>
>>>>>
>>>>>
>>>>> See last post in Firmware repos
>>>>>
>>>>>
>>>>>
>>>>> [image: @julianoes] <https://github.com/julianoes> julianoes
>>>>> <https://github.com/julianoes> closed this in #13311
>>>>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>>>>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>>>>
>>>>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>>>>
>>>>>
>>>>>
>>>>> Follow it https://github.com/PX4/Firmware/pull/13311
>>>>>
>>>>>
>>>>>
>>>>> And Look here
>>>>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> See this post in Firmware repos it references NuttX repo.
>>>>>
>>>>>
>>>>>
>>>>> It just works. See https://github.com/PX4/NuttX/pull/70
>>>>>
>>>>>
>>>>>
>>>>> The problem is solved one in github!
>>>>>
>>>>>
>>>>>
>>>>> But the real and proper answer is use a Knot repo. - But I will not
>>>>> waste my typing any more on this.
>>>>>
>>>>>
>>>>>
>>>>> 2) Sounds like we have people who cannot use Github, now they cannot
>>>>> use
>>>>>
>>>>> the issue tracker so we have people using the mailing list which is
>>>>> less
>>>>>
>>>>> ideal.
>>>>>
>>>>>
>>>>>
>>>>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list
>>>>> bot. They (the github denied) can email one of these nifty lists.*
>>>>>
>>>>> *ihavenogithubaccess@nuttx.apache.org
>>>>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>>>>
>>>>>
>>>>>
>>>>> As for templating and the like you can do this all JIRA as well. The
>>>>>
>>>>> linking between the two is also done so those are not really blockers.
>>>>>
>>>>>
>>>>>
>>>>> --Brennan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> > +1 for github
>>>>>
>>>>> >
>>>>>
>>>>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> >
>>>>>
>>>>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>>>>
>>>>> > > Are they mutually exclusive?
>>>>>
>>>>> > >
>>>>>
>>>>> >
>>>>>
>>>>
Re: Issue Reporting
Posted by Brennan Ashton <ba...@brennanashton.com>.
As I said we control this. I'll open the correct PR, let's not bother infra
when it is on us.
--Brennan
On Thu, Jan 9, 2020, 6:43 PM Xiang Xiao <xi...@gmail.com> wrote:
> I justed open a JIRA for this:
> https://issues.apache.org/jira/browse/INFRA-19692
>
> Thanks
> Xiang
>
> On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt <sp...@gmail.com> wrote:
>
>> My preference would be to let users submit issues on github, but then
>> track them with Jira. Is it possible to link Jira issues to github issues?
>>
>> Otherwise, the rest that you say makes good sense.
>>
>> We do need to consolidate issues in one place somehow. Currently, there
>> are issues in apps and nuttx Bitbucket, we will open up for issues on apps
>> and nuttx github. And there is the TODO list in the nuttx repository (and
>> I have my own TODO list which should be passed upward.
>>
>> That seems like a recipe for things falling through the crack (as they
>> already have).
>> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>>
>> It seems like most people are pushing towards the simplicity of GitHub.
>> My main objection was that we put such a focus on letting people submit
>> code without using GitHub that it seemed odd to then force GitHub for
>> issues. JIRA can really do a lot but I see it as tool that gives you a
>> million features and leaves you to wire it up (I have used it for work for
>> many years) Unless there is someone that wants to do the wiring work it's
>> likely not going to be better than what we get with GitHub.
>>
>> As for the project management component, we can enable the GitHub
>> features for that. It's simple but plenty powerful for what we likely need
>> to so. Even creating filtered views with tags is likely all we need for
>> some time.
>>
>> I would propose we open up GitHub issues only on the apache-nuttx project
>> and start there and let it naturally grow.
>>
>> If we need to move to JIRA for some reason as the project grows, I'll
>> volunteer to move the data.
>>
>> This can all be turned on with the .asf.yml file and I can submit the pr
>> for that if we want.
>>
>> --Brennan
>>
>>
>> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com>
>> wrote:
>>
>>> For me I suggest we start with GitHub issues.
>>>
>>> For problem #1, the cross repo PRs, I think it is fine to have only one
>>> issue in the main repo? We can reference multiple PRs in an issue and the
>>> PRs could come from other repos.
>>>
>>> And for problem #2, once the user sends the patch to this mailing list,
>>> it is the committers duty to open an issue for this, and also open a PR
>>> with this patch to let others review and get the patch in finally.
>>>
>>> I think for most projects which use JIRA, is just because that GitHub
>>> was not available when the project was set up. And then the work flow, and
>>> release processing are already bound with JIRA, so we keep using JIRA for
>>> issue tracking. But I think for a new project, just make use of GitHub is
>>> fine.
>>>
>>> Of course I'm also fine with using JIRA, no problem. Just a suggestion.
>>>
>>> Thanks.
>>>
>>> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>>>
>>>> Hi Brenan,
>>>>
>>>>
>>>>
>>>> See Below.
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>>>> Sent: Monday, December 30, 2019 8:52 AM
>>>> To: dev@nuttx.apache.org
>>>> Subject: Re: Issue Reporting
>>>>
>>>>
>>>>
>>>> Can people who are advocating for GitHub address the two main points
>>>> that I
>>>>
>>>> had made. The second one I really don't see a workaround for. To be
>>>> clear
>>>>
>>>> if we can get around both of these I'm happy to be on the GitHub train.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 1) Multiple repos. We might have an issue or feature the spans the os,
>>>>
>>>> app, and website repos now we need to file tickets in each or something
>>>>
>>>> equally ugly
>>>>
>>>>
>>>>
>>>> [DBS] I already suggested how this is a solved problem on Github.
>>>>
>>>>
>>>>
>>>> We do it all the time in PX4.
>>>>
>>>>
>>>>
>>>> See last post in Firmware repos
>>>>
>>>>
>>>>
>>>> [image: @julianoes] <https://github.com/julianoes> julianoes
>>>> <https://github.com/julianoes> closed this in #13311
>>>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>>>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>>>
>>>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>>>
>>>>
>>>>
>>>> Follow it https://github.com/PX4/Firmware/pull/13311
>>>>
>>>>
>>>>
>>>> And Look here
>>>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> See this post in Firmware repos it references NuttX repo.
>>>>
>>>>
>>>>
>>>> It just works. See https://github.com/PX4/NuttX/pull/70
>>>>
>>>>
>>>>
>>>> The problem is solved one in github!
>>>>
>>>>
>>>>
>>>> But the real and proper answer is use a Knot repo. - But I will not
>>>> waste my typing any more on this.
>>>>
>>>>
>>>>
>>>> 2) Sounds like we have people who cannot use Github, now they cannot use
>>>>
>>>> the issue tracker so we have people using the mailing list which is less
>>>>
>>>> ideal.
>>>>
>>>>
>>>>
>>>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list
>>>> bot. They (the github denied) can email one of these nifty lists.*
>>>>
>>>> *ihavenogithubaccess@nuttx.apache.org
>>>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>>>
>>>>
>>>>
>>>> As for templating and the like you can do this all JIRA as well. The
>>>>
>>>> linking between the two is also done so those are not really blockers.
>>>>
>>>>
>>>>
>>>> --Brennan
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com> wrote:
>>>>
>>>>
>>>>
>>>> > +1 for github
>>>>
>>>> >
>>>>
>>>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
>>>>
>>>> >
>>>>
>>>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>>>
>>>> > > Are they mutually exclusive?
>>>>
>>>> > >
>>>>
>>>> >
>>>>
>>>
Re: Issue Reporting
Posted by Xiang Xiao <xi...@gmail.com>.
I justed open a JIRA for this:
https://issues.apache.org/jira/browse/INFRA-19692
Thanks
Xiang
On Fri, Jan 10, 2020 at 4:55 AM Gregory Nutt <sp...@gmail.com> wrote:
> My preference would be to let users submit issues on github, but then
> track them with Jira. Is it possible to link Jira issues to github issues?
>
> Otherwise, the rest that you say makes good sense.
>
> We do need to consolidate issues in one place somehow. Currently, there
> are issues in apps and nuttx Bitbucket, we will open up for issues on apps
> and nuttx github. And there is the TODO list in the nuttx repository (and
> I have my own TODO list which should be passed upward.
>
> That seems like a recipe for things falling through the crack (as they
> already have).
> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>
> It seems like most people are pushing towards the simplicity of GitHub. My
> main objection was that we put such a focus on letting people submit code
> without using GitHub that it seemed odd to then force GitHub for issues.
> JIRA can really do a lot but I see it as tool that gives you a million
> features and leaves you to wire it up (I have used it for work for many
> years) Unless there is someone that wants to do the wiring work it's likely
> not going to be better than what we get with GitHub.
>
> As for the project management component, we can enable the GitHub features
> for that. It's simple but plenty powerful for what we likely need to so.
> Even creating filtered views with tags is likely all we need for some time.
>
> I would propose we open up GitHub issues only on the apache-nuttx project
> and start there and let it naturally grow.
>
> If we need to move to JIRA for some reason as the project grows, I'll
> volunteer to move the data.
>
> This can all be turned on with the .asf.yml file and I can submit the pr
> for that if we want.
>
> --Brennan
>
>
> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com>
> wrote:
>
>> For me I suggest we start with GitHub issues.
>>
>> For problem #1, the cross repo PRs, I think it is fine to have only one
>> issue in the main repo? We can reference multiple PRs in an issue and the
>> PRs could come from other repos.
>>
>> And for problem #2, once the user sends the patch to this mailing list,
>> it is the committers duty to open an issue for this, and also open a PR
>> with this patch to let others review and get the patch in finally.
>>
>> I think for most projects which use JIRA, is just because that GitHub was
>> not available when the project was set up. And then the work flow, and
>> release processing are already bound with JIRA, so we keep using JIRA for
>> issue tracking. But I think for a new project, just make use of GitHub is
>> fine.
>>
>> Of course I'm also fine with using JIRA, no problem. Just a suggestion.
>>
>> Thanks.
>>
>> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>>
>>> Hi Brenan,
>>>
>>>
>>>
>>> See Below.
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>>> Sent: Monday, December 30, 2019 8:52 AM
>>> To: dev@nuttx.apache.org
>>> Subject: Re: Issue Reporting
>>>
>>>
>>>
>>> Can people who are advocating for GitHub address the two main points
>>> that I
>>>
>>> had made. The second one I really don't see a workaround for. To be
>>> clear
>>>
>>> if we can get around both of these I'm happy to be on the GitHub train.
>>>
>>>
>>>
>>>
>>>
>>> 1) Multiple repos. We might have an issue or feature the spans the os,
>>>
>>> app, and website repos now we need to file tickets in each or something
>>>
>>> equally ugly
>>>
>>>
>>>
>>> [DBS] I already suggested how this is a solved problem on Github.
>>>
>>>
>>>
>>> We do it all the time in PX4.
>>>
>>>
>>>
>>> See last post in Firmware repos
>>>
>>>
>>>
>>> [image: @julianoes] <https://github.com/julianoes> julianoes
>>> <https://github.com/julianoes> closed this in #13311
>>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>>
>>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>>
>>>
>>>
>>> Follow it https://github.com/PX4/Firmware/pull/13311
>>>
>>>
>>>
>>> And Look here
>>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>>
>>>
>>>
>>>
>>>
>>> See this post in Firmware repos it references NuttX repo.
>>>
>>>
>>>
>>> It just works. See https://github.com/PX4/NuttX/pull/70
>>>
>>>
>>>
>>> The problem is solved one in github!
>>>
>>>
>>>
>>> But the real and proper answer is use a Knot repo. - But I will not
>>> waste my typing any more on this.
>>>
>>>
>>>
>>> 2) Sounds like we have people who cannot use Github, now they cannot use
>>>
>>> the issue tracker so we have people using the mailing list which is less
>>>
>>> ideal.
>>>
>>>
>>>
>>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list bot.
>>> They (the github denied) can email one of these nifty lists.*
>>>
>>> *ihavenogithubaccess@nuttx.apache.org
>>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>>
>>>
>>>
>>> As for templating and the like you can do this all JIRA as well. The
>>>
>>> linking between the two is also done so those are not really blockers.
>>>
>>>
>>>
>>> --Brennan
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com> wrote:
>>>
>>>
>>>
>>> > +1 for github
>>>
>>> >
>>>
>>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
>>>
>>> >
>>>
>>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>>
>>> > > Are they mutually exclusive?
>>>
>>> > >
>>>
>>> >
>>>
>>
Re: Issue Reporting
Posted by Nathan Hartman <ha...@gmail.com>.
On Thu, Jan 9, 2020 at 6:55 PM Gregory Nutt <sp...@gmail.com> wrote:
> Another thing, most issues are reported by email. How would that fit in?
>
One of two ways.
Either we'd ask the reporter to file an issue.
Or we would file the issue ourselves.
Either way, triaging of issues would need to be an ongoing effort to remove
invalid issues, merge duplicate issues, verify that unique issues are
actually valid, etc. Since this project is a volunteer effort, that would
depend on someone (or multiple people) being motivated to do it, or issues
will accumulate indefinitely.
Nathan
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
Another thing, most issues are reported by email. How would that fit in?
On 1/9/2020 2:55 PM, Gregory Nutt wrote:
>
> My preference would be to let users submit issues on github, but then
> track them with Jira. Is it possible to link Jira issues to github
> issues?
>
> Otherwise, the rest that you say makes good sense.
>
> We do need to consolidate issues in one place somehow. Currently,
> there are issues in apps and nuttx Bitbucket, we will open up for
> issues on apps and nuttx github. And there is the TODO list in the
> nuttx repository (and I have my own TODO list which should be passed
> upward.
>
> That seems like a recipe for things falling through the crack (as they
> already have).
>
> On 1/9/2020 2:21 PM, Brennan Ashton wrote:
>> It seems like most people are pushing towards the simplicity of
>> GitHub. My main objection was that we put such a focus on letting
>> people submit code without using GitHub that it seemed odd to then
>> force GitHub for issues. JIRA can really do a lot but I see it as
>> tool that gives you a million features and leaves you to wire it up
>> (I have used it for work for many years) Unless there is someone that
>> wants to do the wiring work it's likely not going to be better than
>> what we get with GitHub.
>>
>> As for the project management component, we can enable the GitHub
>> features for that. It's simple but plenty powerful for what we likely
>> need to so. Even creating filtered views with tags is likely all we
>> need for some time.
>>
>> I would propose we open up GitHub issues only on the apache-nuttx
>> project and start there and let it naturally grow.
>>
>> If we need to move to JIRA for some reason as the project grows, I'll
>> volunteer to move the data.
>>
>> This can all be turned on with the .asf.yml file and I can submit the
>> pr for that if we want.
>>
>> --Brennan
>>
>>
>> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <palomino219@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> For me I suggest we start with GitHub issues.
>>
>> For problem #1, the cross repo PRs, I think it is fine to have
>> only one issue in the main repo? We can reference multiple PRs in
>> an issue and the PRs could come from other repos.
>>
>> And for problem #2, once the user sends the patch to this mailing
>> list, it is the committers duty to open an issue for this, and
>> also open a PR with this patch to let others review and get the
>> patch in finally.
>>
>> I think for most projects which use JIRA, is just because that
>> GitHub was not available when the project was set up. And then
>> the work flow, and release processing are already bound with
>> JIRA, so we keep using JIRA for issue tracking. But I think for a
>> new project, just make use of GitHub is fine.
>>
>> Of course I'm also fine with using JIRA, no problem. Just a
>> suggestion.
>>
>> Thanks.
>>
>> David Sidrane <David.Sidrane@nscdg.com
>> <ma...@nscdg.com>> 于2019年12月31日周二 上午1:47写道：
>>
>> Hi Brenan,
>>
>> See Below.
>>
>> -----Original Message-----
>> From: Brennan Ashton [mailto:bashton@brennanashton.com
>> <ma...@brennanashton.com>]
>> Sent: Monday, December 30, 2019 8:52 AM
>> To: dev@nuttx.apache.org <ma...@nuttx.apache.org>
>> Subject: Re: Issue Reporting
>>
>> Can people who are advocating for GitHub address the two main
>> points that I
>>
>> had made. The second one I really don't see a workaround
>> for. To be clear
>>
>> if we can get around both of these I'm happy to be on the
>> GitHub train.
>>
>> 1) Multiple repos. We might have an issue or feature the
>> spans the os,
>>
>> app, and website repos now we need to file tickets in each or
>> something
>>
>> equally ugly
>>
>> [DBS] I already suggested how this is a solved problem on
>> Github.
>>
>> We do it all the time in PX4.
>>
>> See last post in Firmware repos
>>
>> @julianoes <https://github.com/julianoes>julianoes
>> <https://github.com/julianoes> closed this in #13311
>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>
>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>
>> Follow it https://github.com/PX4/Firmware/pull/13311
>>
>> And Look here
>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>
>> See this post in Firmware repos it references NuttX repo.
>>
>> It just works. See https://github.com/PX4/NuttX/pull/70
>>
>> The problem is solved one in github!
>>
>> But the real and proper answer is use a Knot repo. - But I
>> will not waste my typing any more on this.
>>
>> 2) Sounds like we have people who cannot use Github, now they
>> cannot use
>>
>> the issue tracker so we have people using the mailing list
>> which is less
>>
>> ideal.
>>
>> *//*
>>
>> */[DBS] Give them a tool (Train Jira to do it) OR add a
>> mailing list bot. They (the github denied) can email one of
>> these nifty lists./*
>>
>> */ihavenogithubaccess@nuttx.apache.org
>> <ma...@nuttx.apache.org> and it can file
>> an issue for them. /*
>>
>> As for templating and the like you can do this all JIRA as
>> well. The
>>
>> linking between the two is also done so those are not really
>> blockers.
>>
>> --Brennan
>>
>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea
>> <jerpelea@gmail.com <ma...@gmail.com>> wrote:
>>
>> > +1 for github
>>
>> >
>>
>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt
>> <spudaneco@gmail.com <ma...@gmail.com>> wrote:
>>
>> >
>>
>> > > > I'm a little torn on this one, but I'd say Github wins
>> for me.
>>
>> > > Are they mutually exclusive?
>>
>> > >
>>
>> >
>>
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
My preference would be to let users submit issues on github, but then
track them with Jira. Is it possible to link Jira issues to github issues?
Otherwise, the rest that you say makes good sense.
We do need to consolidate issues in one place somehow. Currently, there
are issues in apps and nuttx Bitbucket, we will open up for issues on
apps and nuttx github. And there is the TODO list in the nuttx
repository (and I have my own TODO list which should be passed upward.
That seems like a recipe for things falling through the crack (as they
already have).
On 1/9/2020 2:21 PM, Brennan Ashton wrote:
> It seems like most people are pushing towards the simplicity of
> GitHub. My main objection was that we put such a focus on letting
> people submit code without using GitHub that it seemed odd to then
> force GitHub for issues. JIRA can really do a lot but I see it as tool
> that gives you a million features and leaves you to wire it up (I have
> used it for work for many years) Unless there is someone that wants to
> do the wiring work it's likely not going to be better than what we get
> with GitHub.
>
> As for the project management component, we can enable the GitHub
> features for that. It's simple but plenty powerful for what we likely
> need to so. Even creating filtered views with tags is likely all we
> need for some time.
>
> I would propose we open up GitHub issues only on the apache-nuttx
> project and start there and let it naturally grow.
>
> If we need to move to JIRA for some reason as the project grows, I'll
> volunteer to move the data.
>
> This can all be turned on with the .asf.yml file and I can submit the
> pr for that if we want.
>
> --Brennan
>
>
> On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <palomino219@gmail.com
> <ma...@gmail.com>> wrote:
>
> For me I suggest we start with GitHub issues.
>
> For problem #1, the cross repo PRs, I think it is fine to have
> only one issue in the main repo? We can reference multiple PRs in
> an issue and the PRs could come from other repos.
>
> And for problem #2, once the user sends the patch to this mailing
> list, it is the committers duty to open an issue for this, and
> also open a PR with this patch to let others review and get the
> patch in finally.
>
> I think for most projects which use JIRA, is just because that
> GitHub was not available when the project was set up. And then the
> work flow, and release processing are already bound with JIRA, so
> we keep using JIRA for issue tracking. But I think for a new
> project, just make use of GitHub is fine.
>
> Of course I'm also fine with using JIRA, no problem. Just a
> suggestion.
>
> Thanks.
>
> David Sidrane <David.Sidrane@nscdg.com
> <ma...@nscdg.com>> 于2019年12月31日周二 上午1:47写道：
>
> Hi Brenan,
>
> See Below.
>
> -----Original Message-----
> From: Brennan Ashton [mailto:bashton@brennanashton.com
> <ma...@brennanashton.com>]
> Sent: Monday, December 30, 2019 8:52 AM
> To: dev@nuttx.apache.org <ma...@nuttx.apache.org>
> Subject: Re: Issue Reporting
>
> Can people who are advocating for GitHub address the two main
> points that I
>
> had made. The second one I really don't see a workaround for.
> To be clear
>
> if we can get around both of these I'm happy to be on the
> GitHub train.
>
> 1) Multiple repos. We might have an issue or feature the
> spans the os,
>
> app, and website repos now we need to file tickets in each or
> something
>
> equally ugly
>
> [DBS] I already suggested how this is a solved problem on Github.
>
> We do it all the time in PX4.
>
> See last post in Firmware repos
>
> @julianoes <https://github.com/julianoes>julianoes
> <https://github.com/julianoes> closed this in #13311
> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>
> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>
> Follow it https://github.com/PX4/Firmware/pull/13311
>
> And Look here
> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>
> See this post in Firmware repos it references NuttX repo.
>
> It just works. See https://github.com/PX4/NuttX/pull/70
>
> The problem is solved one in github!
>
> But the real and proper answer is use a Knot repo. - But I
> will not waste my typing any more on this.
>
> 2) Sounds like we have people who cannot use Github, now they
> cannot use
>
> the issue tracker so we have people using the mailing list
> which is less
>
> ideal.
>
> *//*
>
> */[DBS] Give them a tool (Train Jira to do it) OR add a
> mailing list bot. They (the github denied) can email one of
> these nifty lists./*
>
> */ihavenogithubaccess@nuttx.apache.org
> <ma...@nuttx.apache.org> and it can file
> an issue for them. /*
>
> As for templating and the like you can do this all JIRA as
> well. The
>
> linking between the two is also done so those are not really
> blockers.
>
> --Brennan
>
> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea
> <jerpelea@gmail.com <ma...@gmail.com>> wrote:
>
> > +1 for github
>
> >
>
> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt
> <spudaneco@gmail.com <ma...@gmail.com>> wrote:
>
> >
>
> > > > I'm a little torn on this one, but I'd say Github wins
> for me.
>
> > > Are they mutually exclusive?
>
> > >
>
> >
>
Re: Issue Reporting
Posted by Brennan Ashton <ba...@brennanashton.com>.
It seems like most people are pushing towards the simplicity of GitHub. My
main objection was that we put such a focus on letting people submit code
without using GitHub that it seemed odd to then force GitHub for issues.
JIRA can really do a lot but I see it as tool that gives you a million
features and leaves you to wire it up (I have used it for work for many
years) Unless there is someone that wants to do the wiring work it's likely
not going to be better than what we get with GitHub.
As for the project management component, we can enable the GitHub features
for that. It's simple but plenty powerful for what we likely need to so.
Even creating filtered views with tags is likely all we need for some time.
I would propose we open up GitHub issues only on the apache-nuttx project
and start there and let it naturally grow.
If we need to move to JIRA for some reason as the project grows, I'll
volunteer to move the data.
This can all be turned on with the .asf.yml file and I can submit the pr
for that if we want.
--Brennan
On Mon, Dec 30, 2019, 11:02 PM 张铎(Duo Zhang) <pa...@gmail.com> wrote:
> For me I suggest we start with GitHub issues.
>
> For problem #1, the cross repo PRs, I think it is fine to have only one
> issue in the main repo? We can reference multiple PRs in an issue and the
> PRs could come from other repos.
>
> And for problem #2, once the user sends the patch to this mailing list, it
> is the committers duty to open an issue for this, and also open a PR with
> this patch to let others review and get the patch in finally.
>
> I think for most projects which use JIRA, is just because that GitHub was
> not available when the project was set up. And then the work flow, and
> release processing are already bound with JIRA, so we keep using JIRA for
> issue tracking. But I think for a new project, just make use of GitHub is
> fine.
>
> Of course I'm also fine with using JIRA, no problem. Just a suggestion.
>
> Thanks.
>
> David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
>
>> Hi Brenan,
>>
>>
>>
>> See Below.
>>
>>
>>
>> -----Original Message-----
>> From: Brennan Ashton [mailto:bashton@brennanashton.com]
>> Sent: Monday, December 30, 2019 8:52 AM
>> To: dev@nuttx.apache.org
>> Subject: Re: Issue Reporting
>>
>>
>>
>> Can people who are advocating for GitHub address the two main points that
>> I
>>
>> had made. The second one I really don't see a workaround for. To be clear
>>
>> if we can get around both of these I'm happy to be on the GitHub train.
>>
>>
>>
>>
>>
>> 1) Multiple repos. We might have an issue or feature the spans the os,
>>
>> app, and website repos now we need to file tickets in each or something
>>
>> equally ugly
>>
>>
>>
>> [DBS] I already suggested how this is a solved problem on Github.
>>
>>
>>
>> We do it all the time in PX4.
>>
>>
>>
>> See last post in Firmware repos
>>
>>
>>
>> [image: @julianoes] <https://github.com/julianoes> julianoes
>> <https://github.com/julianoes> closed this in #13311
>> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
>> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>>
>> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>>
>>
>>
>> Follow it https://github.com/PX4/Firmware/pull/13311
>>
>>
>>
>> And Look here
>> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>>
>>
>>
>>
>>
>> See this post in Firmware repos it references NuttX repo.
>>
>>
>>
>> It just works. See https://github.com/PX4/NuttX/pull/70
>>
>>
>>
>> The problem is solved one in github!
>>
>>
>>
>> But the real and proper answer is use a Knot repo. - But I will not waste
>> my typing any more on this.
>>
>>
>>
>> 2) Sounds like we have people who cannot use Github, now they cannot use
>>
>> the issue tracker so we have people using the mailing list which is less
>>
>> ideal.
>>
>>
>>
>> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list bot.
>> They (the github denied) can email one of these nifty lists.*
>>
>> *ihavenogithubaccess@nuttx.apache.org
>> <ih...@nuttx.apache.org> and it can file an issue for them. *
>>
>>
>>
>> As for templating and the like you can do this all JIRA as well. The
>>
>> linking between the two is also done so those are not really blockers.
>>
>>
>>
>> --Brennan
>>
>>
>>
>>
>>
>> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com> wrote:
>>
>>
>>
>> > +1 for github
>>
>> >
>>
>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
>>
>> >
>>
>> > > > I'm a little torn on this one, but I'd say Github wins for me.
>>
>> > > Are they mutually exclusive?
>>
>> > >
>>
>> >
>>
>
Re: Issue Reporting
Posted by "张铎 (Duo Zhang)" <pa...@gmail.com>.
For me I suggest we start with GitHub issues.
For problem #1, the cross repo PRs, I think it is fine to have only one
issue in the main repo? We can reference multiple PRs in an issue and the
PRs could come from other repos.
And for problem #2, once the user sends the patch to this mailing list, it
is the committers duty to open an issue for this, and also open a PR with
this patch to let others review and get the patch in finally.
I think for most projects which use JIRA, is just because that GitHub was
not available when the project was set up. And then the work flow, and
release processing are already bound with JIRA, so we keep using JIRA for
issue tracking. But I think for a new project, just make use of GitHub is
fine.
Of course I'm also fine with using JIRA, no problem. Just a suggestion.
Thanks.
David Sidrane <Da...@nscdg.com> 于2019年12月31日周二 上午1:47写道：
> Hi Brenan,
>
>
>
> See Below.
>
>
>
> -----Original Message-----
> From: Brennan Ashton [mailto:bashton@brennanashton.com]
> Sent: Monday, December 30, 2019 8:52 AM
> To: dev@nuttx.apache.org
> Subject: Re: Issue Reporting
>
>
>
> Can people who are advocating for GitHub address the two main points that I
>
> had made. The second one I really don't see a workaround for. To be clear
>
> if we can get around both of these I'm happy to be on the GitHub train.
>
>
>
>
>
> 1) Multiple repos. We might have an issue or feature the spans the os,
>
> app, and website repos now we need to file tickets in each or something
>
> equally ugly
>
>
>
> [DBS] I already suggested how this is a solved problem on Github.
>
>
>
> We do it all the time in PX4.
>
>
>
> See last post in Firmware repos
>
>
>
> [image: @julianoes] <https://github.com/julianoes> julianoes
> <https://github.com/julianoes> closed this in #13311
> <https://github.com/PX4/Firmware/pull/13311>on Oct 31
> <https://github.com/PX4/Firmware/issues/13087#event-2760401888>
>
> https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
>
>
>
> Follow it https://github.com/PX4/Firmware/pull/13311
>
>
>
> And Look here
> https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
>
>
>
>
>
> See this post in Firmware repos it references NuttX repo.
>
>
>
> It just works. See https://github.com/PX4/NuttX/pull/70
>
>
>
> The problem is solved one in github!
>
>
>
> But the real and proper answer is use a Knot repo. - But I will not waste
> my typing any more on this.
>
>
>
> 2) Sounds like we have people who cannot use Github, now they cannot use
>
> the issue tracker so we have people using the mailing list which is less
>
> ideal.
>
>
>
> *[DBS] Give them a tool (Train Jira to do it) OR add a mailing list bot.
> They (the github denied) can email one of these nifty lists.*
>
> *ihavenogithubaccess@nuttx.apache.org
> <ih...@nuttx.apache.org> and it can file an issue for them. *
>
>
>
> As for templating and the like you can do this all JIRA as well. The
>
> linking between the two is also done so those are not really blockers.
>
>
>
> --Brennan
>
>
>
>
>
> On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com> wrote:
>
>
>
> > +1 for github
>
> >
>
> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
>
> >
>
> > > > I'm a little torn on this one, but I'd say Github wins for me.
>
> > > Are they mutually exclusive?
>
> > >
>
> >
>
RE: Issue Reporting
Posted by David Sidrane <Da...@nscdg.com>.
Hi Brenan,
See Below.
-----Original Message-----
From: Brennan Ashton [mailto:bashton@brennanashton.com]
Sent: Monday, December 30, 2019 8:52 AM
To: dev@nuttx.apache.org
Subject: Re: Issue Reporting
Can people who are advocating for GitHub address the two main points that I
had made. The second one I really don't see a workaround for. To be clear
if we can get around both of these I'm happy to be on the GitHub train.
1) Multiple repos. We might have an issue or feature the spans the os,
app, and website repos now we need to file tickets in each or something
equally ugly
[DBS] I already suggested how this is a solved problem on Github.
We do it all the time in PX4.
See last post in Firmware repos
[image: @julianoes] <https://github.com/julianoes> julianoes
<https://github.com/julianoes> closed this in #13311
<https://github.com/PX4/Firmware/pull/13311>on Oct 31
<https://github.com/PX4/Firmware/issues/13087#event-2760401888>
https://github.com/PX4/Firmware/issues/13087#issuecomment-542366711
Follow it https://github.com/PX4/Firmware/pull/13311
And Look here
https://github.com/PX4/Firmware/pull/13311#issuecomment-548466442
See this post in Firmware repos it references NuttX repo.
It just works. See https://github.com/PX4/NuttX/pull/70
The problem is solved one in github!
But the real and proper answer is use a Knot repo. - But I will not waste
my typing any more on this.
2) Sounds like we have people who cannot use Github, now they cannot use
the issue tracker so we have people using the mailing list which is less
ideal.
*[DBS] Give them a tool (Train Jira to do it) OR add a mailing list bot.
They (the github denied) can email one of these nifty lists.*
*ihavenogithubaccess@nuttx.apache.org
<ih...@nuttx.apache.org> and it can file an issue for them. *
As for templating and the like you can do this all JIRA as well. The
linking between the two is also done so those are not really blockers.
--Brennan
On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com> wrote:
> +1 for github
>
> On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
>
> > > I'm a little torn on this one, but I'd say Github wins for me.
> > Are they mutually exclusive?
> >
>
Re: Issue Reporting
Posted by Brennan Ashton <ba...@brennanashton.com>.
Can people who are advocating for GitHub address the two main points that I
had made. The second one I really don't see a workaround for. To be clear
if we can get around both of these I'm happy to be on the GitHub train.
1) Multiple repos. We might have an issue or feature the spans the os,
app, and website repos now we need to file tickets in each or something
equally ugly
2) Sounds like we have people who cannot use Github, now they cannot use
the issue tracker so we have people using the mailing list which is less
ideal.
As for templating and the like you can do this all JIRA as well. The
linking between the two is also done so those are not really blockers.
--Brennan
On Mon, Dec 30, 2019, 8:38 AM Alin Jerpelea <je...@gmail.com> wrote:
> +1 for github
>
> On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
>
> > > I'm a little torn on this one, but I'd say Github wins for me.
> > Are they mutually exclusive?
> >
>
Re: Issue Reporting
Posted by Alin Jerpelea <je...@gmail.com>.
+1 for github
On Mon, Dec 30, 2019, 18:32 Gregory Nutt <sp...@gmail.com> wrote:
> > I'm a little torn on this one, but I'd say Github wins for me.
> Are they mutually exclusive?
>
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
> I'm a little torn on this one, but I'd say Github wins for me.
Are they mutually exclusive?
Re: Issue Reporting
Posted by Anthony Merlino <an...@vergeaero.com>.
My experience with Jira is that it is powerful if you know how to use it,
but that it can be really clumsy and difficult to learn. There's also a lot
of pain with certain actions, like switching issue types in bulk and things
like that.
Github on the other hand is much more straightforward and simple to use.
I'd also think Github will be better for engaging new community members to
solve existing issues, and to have higher chances of users reporting
issues. This is because Github Issues have become very popular and people
are much more familiar with it than Jira. Not to mention when they go to
the Github page to look at the codebase, they immediately find the issues
in the same place. I think this will help our image when users are
evaluating NuttX.
I'm a little torn on this one, but I'd say Github wins for me.
+1Github Issues
On Mon, Dec 30, 2019, 8:52 AM Gregory Nutt <sp...@gmail.com> wrote:
> Lots of Jira tutorials. Not knowing how to use it does not not sound
> like a strong argument against it:
>
> Quick Google:
>
> https://www.guru99.com/jira-tutorial-a-complete-guide-for-beginners.html
>
> https://www.atlassian.com/agile/tutorials
>
>
> https://www.atlassian.com/software/jira/guides/getting-started/basics#step-1-create-a-project
>
> https://www.tutorialspoint.com/jira/index.htm
>
> https://www.softwaretestinghelp.com/atlassian-jira-tutorial-1/
>
> https://www.javatpoint.com/jira-tutorial
>
>
> https://www.udemy.com/course/best-manual-software-testing-live-project-agile-jira/
>
>
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
Lots of Jira tutorials. Not knowing how to use it does not not sound
like a strong argument against it:
Quick Google:
https://www.guru99.com/jira-tutorial-a-complete-guide-for-beginners.html
https://www.atlassian.com/agile/tutorials
https://www.atlassian.com/software/jira/guides/getting-started/basics#step-1-create-a-project
https://www.tutorialspoint.com/jira/index.htm
https://www.softwaretestinghelp.com/atlassian-jira-tutorial-1/
https://www.javatpoint.com/jira-tutorial
https://www.udemy.com/course/best-manual-software-testing-live-project-agile-jira/
RE: Issue Reporting
Posted by David Sidrane <Da...@nscdg.com>.
+1 for using github
I have used both - I am more failure with github then Jira capabilities.
Jira for me was very slooooow.
So if there is a Jira PRO on the team and they can automate Github PR/Issue
tracking and syncing/closing into Jira that would be the way to go.
The benefit is that disjoint tools are not in the way of project success.
The Key features of Github that make it the right *integrated* choice are:
1) It automatically crosslink issue and pr and can close issues on PR
coming in.
2) Cross repo PR/ISSUES are already supported with inline mark up [SEE
SISTER {PR|ISSUE}] (url)
3) Git hub ass project board and supports kanban boards[1]
4) As Alin mentioned Template driven USER first encounter triage
4) A single login/location for complete lifecycle.
David
[1]https://www.atlassian.com/agile/kanban/boards
-----Original Message-----
From: Alin Jerpelea [mailto:jerpelea@gmail.com]
Sent: Monday, December 30, 2019 1:23 AM
To: dev@nuttx.apache.org
Subject: Re: Issue Reporting
for another bug tracker we use github and all issued are created on a
template.
This template can start with the following title "git name - board /
component - version - issue".
Such layout eases the sorting and people can easy spot if there is
something similar to theyr issue.
On Mon, Dec 30, 2019, 04:17 Gregory Nutt <sp...@gmail.com> wrote:
>
> > I like this. I prefer that we use Apache's Jira for several reasons,
> > especially in light of the integration that Brennan describes.
> If we do go with Jira, we should transfer all of the Bitbucket nuttx/
> and apps/ issues to Jira along with the content of the NuttX TODO list.
>
Re: Issue Reporting
Posted by Alin Jerpelea <je...@gmail.com>.
for another bug tracker we use github and all issued are created on a
template.
This template can start with the following title "git name - board /
component - version - issue".
Such layout eases the sorting and people can easy spot if there is
something similar to theyr issue.
On Mon, Dec 30, 2019, 04:17 Gregory Nutt <sp...@gmail.com> wrote:
>
> > I like this. I prefer that we use Apache's Jira for several reasons,
> > especially in light of the integration that Brennan describes.
> If we do go with Jira, we should transfer all of the Bitbucket nuttx/
> and apps/ issues to Jira along with the content of the NuttX TODO list.
>
Re: Issue Reporting
Posted by Gregory Nutt <sp...@gmail.com>.
> I like this. I prefer that we use Apache's Jira for several reasons,
> especially in light of the integration that Brennan describes.
If we do go with Jira, we should transfer all of the Bitbucket nuttx/
and apps/ issues to Jira along with the content of the NuttX TODO list.
Re: Issue Reporting
Posted by Nathan Hartman <ha...@gmail.com>.
On Sun, Dec 29, 2019 at 7:46 PM Brennan Ashton <ba...@brennanashton.com>
wrote:
> Normally I am a fan of keeping things simple and using the simple github
> issue tracker, but we have a few issues that I think make that less
> practical.
>
> 1) Multiple repos. We might have an issue or feature the spans the os,
> app, and website repos now we need to file tickets in each or something
> equally ugly
> 2) Sounds like we have people who cannot use Github, now they cannot use
> the issue tracker so we have people using the mailing list which is less
> ideal.
> 3) We already have JIRA linked with the projects.
>
> To see how this is already setup I tested it by doing this:
> 1) Created a dummy issue in JIRA
> https://issues.apache.org/jira/browse/NUTTX-1
> 2) Create a PR that mentioned this issue NUTTX-1
> https://github.com/apache/incubator-nuttx/pull/15
> 3) The issue was automatically linked with the PR as you can see in the
> issue. There is even more context if you click All under Activity.
>
> Looks like the bot did not write back to the github PR which is
> unfortunate, but not that bad.
I like this. I prefer that we use Apache's Jira for several reasons,
especially in light of the integration that Brennan describes.
Nathan
Re: Issue Reporting
Posted by Brennan Ashton <ba...@brennanashton.com>.
Normally I am a fan of keeping things simple and using the simple github
issue tracker, but we have a few issues that I think make that less
practical.
1) Multiple repos. We might have an issue or feature the spans the os,
app, and website repos now we need to file tickets in each or something
equally ugly
2) Sounds like we have people who cannot use Github, now they cannot use
the issue tracker so we have people using the mailing list which is less
ideal.
3) We already have JIRA linked with the projects.
To see how this is already setup I tested it by doing this:
1) Created a dummy issue in JIRA
https://issues.apache.org/jira/browse/NUTTX-1
2) Create a PR that mentioned this issue NUTTX-1
https://github.com/apache/incubator-nuttx/pull/15
3) The issue was automatically linked with the PR as you can see in the
issue. There is even more context if you click All under Activity.
Looks like the bot did not write back to the github PR which is
unfortunate, but not that bad.
--Brennan
On Sun, Dec 29, 2019 at 12:13 PM Gregory Nutt <sp...@gmail.com> wrote:
> It has been reported to me that Issues are disabled at
> https://github.com/apache/incubator-nuttx-apps:
> <https://github.com/apache/incubator-nuttx-apps>
>
> https://bitbucket.org/nuttx/apps/issues/15/null-dereference-in-ftp-size-command
>
> We need to decide how people report problems to us. GIT issues? Jira?
> dev@apache.org? We need to make some decisions. I think Jira would
> give us the best bug tracking options. GIT issues is well integrated on
> github. I think dev@apache.org is a bad idea.
>
> There is a backlog of Issues/bugs at
> https://bitbucket.org/nuttx/nuttx/issues?status=new&status=open and
> https://bitbucket.org/nuttx/apps/issues?status=new&status=open (and also
> issues in the top-level NuttX TODO file). I have a personal list of
> things that I thing should be done as well.
>
> We probably need another Confluence page talking about bug-reporting.
>
> Greg
>
>
>