Fossil

Status:

• Fossil 2.0 is currently just an idea. No code has been written.

Core Principles:

• 100% repository compatible. Reuse existing repos (perhaps with "rebuild")

• 100% sync compatible. Push, pull, and clone with version 1.x repos.

Web Interface Enhancements:

• Refactor to a small, sensible, well-defined and well-document set of CSS classes that are easy to configure.

• OK to break existing skins.

• Push toward being closer to RESTful

• Strive for basic operation w/o javascript, though clearly javascript is allowed when necessary. (Javascript draws the timeline graph for example.) This principle does not change from 1.x.

Command-line Interface:

• "fossil mv" and "fossil rm" actually rename and delete the underlying files.

Implementation Strategy:

• Make changes in a long-running branch (named "fossil-2.0"?) until ready to cut-over, then merge into trunk.

• Keep two versions of Fossil (1.x and 2.0-alpha) both running on https://www.fossil-scm.org/ so that people can compare the changes to the web-interface easily.

• Provide a place to download pre-compiled binaries of 2.0-alpha.

On 2015-02-06 02:10:35 UTC nobody (claiming to be sean) added:

• Possibility of using a different hash, such as sha384 or sha512. Just because sha1 is fine doesn't mean it will always be fine. -- drh replies: Unable. This would be an incompatible file format change.
• online file editing
• alphabetization of lists
• some style of pastebin with syntax highlighting, similar to tech notes or wiki
• libressl support

On 2015-02-06 02:31:59 UTC nobody (claiming to be isxek) added:

• Allow markdown use when writing tickets & ticket comments -- drh replies: Doesn't this already work in Fossil 1.30?