Can people also respond on the Projects feature of GitHub? I imagined it would be used for thinks like new ports, releases, and large features. Most of these would have tasks spanning two repos.
Take crypto. There is an OS interface component, at least a demo app, and likely a configuration to be configured in testing. Do we open tickets in the three and link them to one project in a single repo's Projects? Or do we have three projects all called crypto each under each repos Projects? Here is my vote: JIRA or GitHub I don't care. But I would prefer a single issue tracker not spanning multiple repos, although I would not vote against it if it came down to it. I would vote against multiple Projects, checking 5 boards to cut a release, no thank you. I would also vote against using both GitHub and JIRA mixing issue tracking and project management. --Brennan On Tue, Jan 14, 2020, 4:09 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > On Tue, Jan 14, 2020 at 6:32 PM Justin Mclean <jus...@classsoftware.com> > wrote: > > > Hi, > > > > Part of the issues to consider is that If you use GitHub issues, having > > multiple repos you may need to enable issues in multiple places. This > means > > more to manage and track. Having all issues for multiple repos on a > single > > github repo also has issues. > > > > I don’t think there’s an ideal solution here, I’ve used both JIRA and > > GitHub issues in the past and they both have their advantages and > > disadvantages. The PPMC needs to come up with a solution that everyone is > > willing to work with, even if it is not everyone first choice. It might > be > > a good idea if each of the 13 PPMC members express their opinion or > someone > > listed the possible options and people indicated their choice. A valid > > opinion would be "I’m fine with any solution”. > > > I am fine with either of the following two options (not in any order of > preference): > > (1) GitHub issues with separate issues for each repository, i.e., issues > with "apps" are reported against "apps," *not* against NuttX. > Pros: Convenience and widespread familiarity across the FOSS world. > Cons: Excludes those who can not access GitHub. Does not support an > issue that affects both repositories. Not running on ASF infrastructure. > > (2) Jira, with issues correctly tagged as affecting the OS, or affecting > apps, or affecting both. > Pros: Running on ASF infrastructure. Inclusiveness for those who cannot > use GitHub. > Cons: Loss of the conveniences provided by the GitHub option. > > Of course, I am open to consider other suggestions that might be offered. > :-) > > Cheers, > Nathan >
