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 <spudan...@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) <palomino...@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.sidr...@nscdg.com> 于2019年12月31日周二 上午1:47写道： >> >>> Hi Brenan, >>> >>> >>> >>> See Below. >>> >>> >>> >>> -----Original Message----- >>> From: Brennan Ashton [mailto:bash...@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.* >>> >>> *ihavenogithubacc...@nuttx.apache.org >>> <ihavenogithubacc...@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 <jerpe...@gmail.com> wrote: >>> >>> >>> >>> > +1 for github >>> >>> > >>> >>> > On Mon, Dec 30, 2019, 18:32 Gregory Nutt <spudan...@gmail.com> wrote: >>> >>> > >>> >>> > > > I'm a little torn on this one, but I'd say Github wins for me. >>> >>> > > Are they mutually exclusive? >>> >>> > > >>> >>> > >>> >>
