On Feb 14, 2016, at 5:10 AM, Scott Robison <sc...@casaderobison.com> wrote: > > there can be a lot of noise in forums and mailing lists and such that you > wouldn't necessarily want to keep in the fossil record, much more so than > changes to code or documentation.
I wonder... If you knew that every post you made to the project forum would be sent to everyone who cloned that repository, would you be less likely to write off-topic posts, start flamewars, etc. than the purely social mechanisms we have today? Email is seen as somewhat ephemeral, despite mail archives, Google, etc. There’s something more…official about committing changes to the project repo. There are further upsides particular to a natural Fossil-ish implementation of this than just mimicking a classic web forum: 1. A moderator / project admin could shun spam, unwanted posts, etc. Because shunning is handled cooperatively between repos, the bogus inevitable cries of “censorship!” would be easier to dismiss. 2. If forum posts worked like wiki articles, you could edit posts after sending them. The ability to walk back in history would keep people from misusing this feature, evidenced by Stack Exchange, where edits are almost always improvements. 3. Markdown / wiki formatting. 4. You could sync your local clone of the project repo, get on a plane, and answer posts offline. When you get to your destination, you could sync back up, thereby posting your replies. Thus, you get a key benefit of email while still working on a web UI. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
