On Jun 13, 2018, at 12:55 PM, Steve Schow <st...@bstage.com> wrote: > > There are other deep solutions such as redmine and others which provide deep > collaboration capabilities…which is where that kind of feature would lead to.
That makes me like the idea even more. :) It would be nice, for instance, to be able to reply to a checkin. A coworker/collaborator often checks something in that you want to discuss, so you reply to the checkin, creating a discussion thread from it. That would also be a step on the path towards a code review feature. In the initial version, simply being able to attach an “Approved” or “Merge it” reply to the latest checkin on an experimental feature branch would be useful. You can sorta do this today with tech notes, but the message target may miss seeing it, just monitoring the timeline. Adding in email notification solves that, since the email comes from a trusted source, and is thus easy to filter, tag, sort, and escort past the anti-spam filters. This also allows a platform for CI/CD tools: the tool can “reply” to the checkin with the status of the build, tests, etc. That in turn allows Fossil to display build and test status badges in the default Home wiki article. > Collaboration such as what we see on GitHub, etc..would be cool, don’t get me > wrong, but in my opinion would greatly add to complexity in fossil. I would > be using one of those solutions already if I wanted a big complicated > collaborative platform like that. Any software project with more than one remote member needs such a thing. For such projects, a discussion forum is probably more important than a wiki or ticket tracker. I think it’s fair to consider some kind of discussion forum an essential tool for software development collaboration, which puts it right in Fossil’s space. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
