On Jun 13, 2018, at 9:18 AM, Richard Hipp <d...@sqlite.org> wrote: > > On 6/13/18, Warren Young <war...@etr-usa.com> wrote: >> If you do this atop Fossil, then you end up inches away from being able to >> provide an oft-wanted feature: email notifications on checkins, wiki article >> changes, and other Fossil events. > > Indeed, there are many advantages to just tacking a forum capability > onto Fossil.
Let’s list them: 1. Lots of “free” infrastructure: user management, role-based access control, web framework, wiki and Markdown to HTML formatters, durable and efficient message storage with deltas, pre-designed shunning mechanism. 2. Everyone who clones a Fossil project repository would henceforth also get a clone of the project’s message traffic. 3. Forum posts can show up in the timeline. 4. Forum posts will be able to ink to Fossil artifacts in the same way that checkin comments, wiki articles, and such can today. 5. Vice versa: a checkin comment can say “Closes issue raised in forum post [abcd1234]” and get an automatic *and durable* link to the post. (How many web mail archives have gone away or broken their link structure since the SQLite ML was started?) 6. Trivially-implemented delayed offline replies: sync the project repo before you go off-network, write your forum message replies on the airplane, in the tent, etc. then sync when you get back into the warm wifi bath to push all your replies out. > But there are also disadvantages. The biggest problem I > see is that one does not necessarily want the standard Fossil page > header and footer to appear on the forum pages. That’s a small cost, and arguably not a cost at all. If you’re at the SQLite project web site and are posting a message, you might well want to make use of other Fossil services while you’re there. The forum feature may well have a sub-header, but that doesn’t argue against having a top-level header linking to other site services. Hacker News, Stack Exchange, Slashdot and other forum sites offer services other than messaging in their top-level site headers. > People looking for > help with an SQLite question do not need to see "Timeline", "Files", > "Branches", "Tags", and "Tickets" menu items across the top of the > page. (ex: https://www.sqlite.org/src/doc/trunk/README.md) Some may, and those that don’t need it can ignore it. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
