On 6/13/18, Warren Young <war...@etr-usa.com> wrote: >> Indeed, there are many advantages to just tacking a forum capability >> onto Fossil. > > Let’s list them: > > 2. Everyone who clones a Fossil project repository would henceforth also get > a clone of the project’s message traffic.
This is not necessarily an advantage. We I have found is that forum and ticket traffic far exceeds the amount of source code. Furthermore this kind of traffic does not lend itself well to delta compression. And so what you would likely encounter is that clones would swell uncontrollably with most of the extra space going to extraneous and noisy forum traffic. This is especially true if attachments are allowed on forum posts, because what I have found is that you will quickly accumulate many multi-megabyte incompressible screenshot attachments. It doesn't take too many people attaching screenshots off of their hi-res "retinue" screen to give you 1GB clone bandwidth even for a smaller project. > > 3. Forum posts can show up in the timeline. Yikes. I think I would certainly want that to be turned off by default. > > 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. > These last three are nice ideas. But they depend on (2) which comes with associated bandwidth and storage overhead. My current design does not automatically sync forum content. I might add the ability to sync forum traffic separately, using a separate command, just as one can now optionally sync unversioned content using the "fossil uv sync" command. But that will come later, if at all. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
