Fossil is (and Codeville was) a BSD-licensed distributed revision control system.
Note that unless you're actually modifying the version control software itself, the license doesn't affect you; you're free to develop non-GPL'ed software using a GPL'ed tool to manage revisions.
Since 2 years passed since started professionally working with git (after 20 years of not-git...) I can say this:
GIT has it's advantages when it comes to merging code bases between branches and multiple users. Once you master it, and learn to ignore its - sometimes utterly confusing command line UI - can be easy to work with.
On the downside, GIT IS complex to understand and LEARN. There is a long steep learning phase, especially if you work from the command line in multiply branched repository (the common and the recommended approach). Working with UI tools like InteliJ IDE's can hide some of the details, but these require their learning attention and time too + some not so basic GIT knowledge. And this knowledge is required by ALL members of your team.
OLD AND (not so) BELOVED ANSWER:
Forget the license... You want to NOT use GIT for so many other reasons...
If you want things to work faster for your team - stay away from GIT. Why not use SVN? It is supported by any service that supports GIT, and is the most popular alternative to GIT (as far as I know).
To commit/merge/manage a team in GIT it'll take you exponentially more time than other SVN/Fossil/... All in the name of advance "distributed" design, and a rich set of methods to kill your code, merge it wrongly, give you so many options to do horrible mistakes (that happen to pro's and newbies alike), and do simple things the HARD HARD way. Were in reality it only serves the ritual hungry souls of geeky programmers, who would otherwise have to go home late and face the empty walls of their houses... (poetic answer too).
REALLY - It would actually be funny if it wasn't the number one pain-in-the-arse time killer in the office. And once you go GIT you can never go back, so my advice, don't let the geeks have it. Keep it out or pay the price.
And, yeah, I know the crowd here, and I am more than willing to loose a few points. It's not like it means anything real.
发布评论
评论（3）
化石是（
和Codeville 是）一个 BSD 许可的分布式版本控制系统。请注意，除非您实际修改版本控制软件本身，否则许可证不会影响您；您可以使用 GPL 版工具自由开发非 GPL 版软件来管理修订。
Fossil is (
and Codeville was) a BSD-licensed distributed revision control system.Note that unless you're actually modifying the version control software itself, the license doesn't affect you; you're free to develop non-GPL'ed software using a GPL'ed tool to manage revisions.
其他选项是：
The other options are:
更新：
自从开始专业使用 git 以来已经过去了 2 年（经过 20 年的非 git ......）我可以这样说：
GIT 在合并分支和多个用户之间的代码库方面具有优势。一旦掌握了它，并学会忽略它（有时完全令人困惑的命令行 UI），使用起来就会很容易。
缺点是，GIT 理解和学习起来很复杂。有一个漫长而陡峭的学习阶段，特别是如果您在多分支存储库中使用命令行工作（常见且推荐的方法）。使用像 InteliJ IDE 这样的 UI 工具可以隐藏一些细节，但是这些也需要他们学习注意力和时间 + 一些不那么基本的 GIT 知识。您团队的所有成员都需要这些知识。
旧的且（不那么）可爱的答案：
忘记许可证...您出于许多其他原因不想使用 GIT...
如果您希望您的团队工作得更快 - 远离 GIT。为什么不使用SVN？它受到任何支持 GIT 的服务的支持，并且是 GIT 的最流行的替代品（据我所知）。
要在 GIT 中提交/合并/管理一个团队，它会比其他 SVN/Fossil/ 花费更多的时间......所有这一切都是以先进的“分布式”设计的名义，以及一组丰富的方法来杀死你的代码，合并错误地，给你这么多的选择来犯可怕的错误（这发生在专业人士和新手身上），并以困难的方式做简单的事情。如果实际上它只服务于极客程序员的仪式性饥饿灵魂，否则他们就不得不很晚回家并面对房屋空荡荡的墙壁......（也是诗意的答案）。
真的——如果它不是办公室里头号令人讨厌的时间杀手，那真的会很有趣。一旦你进入 GIT，你就永远无法回去，所以我的建议是，不要让极客拥有它。要么阻止它，要么付出代价。
是的，我了解这里的人群，我非常愿意失去一些分数。这并不意味着任何真实的东西。
UPDATE:
Since 2 years passed since started professionally working with git (after 20 years of not-git...) I can say this:
GIT has it's advantages when it comes to merging code bases between branches and multiple users. Once you master it, and learn to ignore its - sometimes utterly confusing command line UI - can be easy to work with.
On the downside, GIT IS complex to understand and LEARN. There is a long steep learning phase, especially if you work from the command line in multiply branched repository (the common and the recommended approach). Working with UI tools like InteliJ IDE's can hide some of the details, but these require their learning attention and time too + some not so basic GIT knowledge. And this knowledge is required by ALL members of your team.
OLD AND (not so) BELOVED ANSWER:
Forget the license... You want to NOT use GIT for so many other reasons...
If you want things to work faster for your team - stay away from GIT. Why not use SVN? It is supported by any service that supports GIT, and is the most popular alternative to GIT (as far as I know).
To commit/merge/manage a team in GIT it'll take you exponentially more time than other SVN/Fossil/... All in the name of advance "distributed" design, and a rich set of methods to kill your code, merge it wrongly, give you so many options to do horrible mistakes (that happen to pro's and newbies alike), and do simple things the HARD HARD way. Were in reality it only serves the ritual hungry souls of geeky programmers, who would otherwise have to go home late and face the empty walls of their houses... (poetic answer too).
REALLY - It would actually be funny if it wasn't the number one pain-in-the-arse time killer in the office. And once you go GIT you can never go back, so my advice, don't let the geeks have it. Keep it out or pay the price.
And, yeah, I know the crowd here, and I am more than willing to loose a few points. It's not like it means anything real.