Hi Nathan, On 1/3/20, Nathan Hartman <hartman.nat...@gmail.com> wrote: > On Fri, Jan 3, 2020 at 4:01 PM Justin Mclean <jus...@classsoftware.com> > wrote: >> >> Re which tool to use, which one are your users likely to use. From >> >> previous discussion I don’t think many would have used git issues, but >> >> I’m not sure than many would be familiar with JIRA. >> > >> > The majority problem reports .. well over 90% ... are recieved via >> > email. Sometimes several today. If some knowledgeable person is >> > online, they may respond with some help. But most go unanswered because >> > no one has an answer to offer. >> >> Some projects ask user to create an issue (JIRA or GitHub) if it an >> actually bug rather than just helping with some setup or config issue. You >> might want to consider that. > > Maybe people should not file a bug for hardware-specific issues that > affect only their specific configuration. As you point out, it is > unlikely that anyone else will be able to fix or test such an issue. > So, for those cases, maybe we should encourage people not to file an > issue but rather to fix it right away, and help in any way possible. > > In contrast, for things that affect the RTOS itself, build system, > etc., we would let people file issues. > > Thoughts? >
Well, I think an option is to suggest to people facing this issue to test on some reference board that more people could have and could duplicate the issue easily. We don't have an official reference board, but many people use the stm32f4discovery as I reference board. Also we need to have a page where people can see which features each arch/board has support. It will make their life easier and our as well, because they will know that such features is not working and will not open an issue. BR, Alan
