On 11/22/2017 09:27 PM, Jan Kiszka wrote: > On 2017-11-22 16:32, Philippe Gerum wrote: >> >> Hi Kendall, >> >> On 11/21/2017 08:27 PM, Auel, Kendall wrote: >>> Hi Philippe, >>> >>> Is there an online bug tracking and feature request database? This would be >>> a useful way to distribute work and to sync up contributors. I think the >>> kernel uses Bugzilla, and Ubuntu has Launchpad. No doubt there are many >>> others. >>> >>> I'd like to contribute in some way. I've been having a lot of fun as a >>> Xenomai user. >>> >> We don't have that unfortunately. As suggested by several posters, >> moving to a git-based, integrated development framework such as gitlab >> or github would bring in that feature, and others we need too (CI). >> >> I have no issue moving the project from the current git server at >> xenomai.org to any of these environments. >> > > If it helps the community to grow, I would not refuse such a move. But I > would like to raise some concerns about platforms like github or gitlab > that we must be aware of: > > - lacking integration with email-based workflows (while kernel > development tends to be based on that...) > > - risk of decoupling communities when parts of the discussions happen on > tickets or PRs and parts in mailing list threads > > Therefore, most projects I manage on github and in our internal gitlab > have clear policies like "no emails, only tickets and PRs" or "no PRs, > only patches on the mailing list". Even just using the issue tracker to > keep some to-do list requires discipline to direct discussions > consequently to a mailing list if that exists as well (and that usually > does not work very well). > > IOW: we need to be clear in what we want a platform for - and what not. >
Defining the process first may help, then we could certainly find a tool that fits the requirement. AFAICT, reports from users and maintainers mainly fall into these categories: - perceived runtime bugs (confirmed or not) - configuration, installation problems - request for change, improvements Reports about runtime bugs should be posted to mailing list first, unless they have been directly observed by a subsystem maintainer. If the issue is confirmed, it should be logged into the tracker by the concerned subsystem maintainer. Many users report bugs which have already been solved, the tracker should help making the solution visible for closed issues, or maybe we'd need another way to bring up that information to the attention of users. Request for changes should translate into RFCs to the mailing list so they can be discussed, last but not least to prevent duplicate effort with potentially ongoing work. A detailed description of what is needed/planned could then be published to a dedicated section of the web site in free form; this would contribute to the general TODO list Greg mentioned earlier. Questions about configuration and installation can be efficiently dealt with good documentation (TBD) and a mailing list. To get this process working, I don't think we'd need more than a tracker with write access to subsystem maintainers only (once we have some, that is), and the existing mailing list, which should prevent crosstalk. -- Philippe. _______________________________________________ Xenomai mailing list Xenomai@xenomai.org https://xenomai.org/mailman/listinfo/xenomai
