5 ms·

We do, it's called Fossil! http://fossil-scm.org/ http://fossil-scm.org/ Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it

by cytzol 11y ago

We do, it's called Fossil! http://fossil-scm.org/ http://fossil-scm.org/ Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. You can then respond to tickets and perform repo maintenance offline, syncing everything to the server when you're back up. Edit: A few weeks ago I got a job a one-hour train ride away. I can commit, close tickets, and write docs on my way in, sync everything to the internet when I get to work, then do the same on my way back - even though I don't have a net connection during my commute. It works great. (Ok, not as good as not having to travel at all, but great nonetheless!)

thecatspaw 11y ago
the parent commentator was joking that git _is_ decentralised, but that we made it centralised again by relying on a small number of hosters (github, bitbucket and others)
- cytzol 11y ago
  Heh, don't worry, I got the joke. But I also got the joke the last time this was posted, and the time before that, and the time before that... This just keeps happening. It's not GitHub's fault that they keep getting DDoSed or have a network outage every now and again. But it's not a problem with no solution.
  - popey456963 11y ago
    To be honest, I can cope with Github's downtime, it is probably less than if I was hosting a Git solution myself and the service is much more reliable than all the other solutions I've tried (which are either lacking features or have bugs or have massive downtimes). Github is trying their best as far as I can see, they manage to fix the majority of issues within three hours and even during those three hours its not the end of the world because you can still code.
simula67 11y ago
Most developers will not be able to write code without being able to look up stuff on the Internet.
asdfadr1344kk 11y ago
<3 Fossil. I wish it were more popular so I could use it on non-personal projects and still have a hope of attracting collaborators...
- CMay 11y ago
  Yeah, fossil is all I use. It's so clean, tiny and self contained with no install or bloat. I've always been in love with software written that way. It makes me look at things like git as just a product of engineers that can get the job done, but don't know what it means to write good software or use imagination. Being fair, fossil performance on giant scale projects might not compare quite as well against git or proprietary solutions like Perforce, but for the large majority of projects I expect it is more than adequate.
  - popmystack 11y ago
    > but don't know what it means to write good software or use imagination. You can't do patches. You can't rebase. You can't rename files. Tell me all about this good software and imagination you speak of?
    - richieadler 11y ago
      > You can't do patches. You can create bundles and submit them for approval. Very similar. > You can't rebase. You have alternatives. The work philosophy is different, though. > You can't rename files. False.
      - popmystack 11y ago
        >You can create bundles and submit them for approval. Very similar. Bundles do not have anywhere near the same flexibility and nuanced capacity that patches do. >The work philosophy is different, though. That's an apology if I've ever seen one. Again, not the same. >False. Rename a file. Then try to merge. Tell me what happens.
gkya 11y ago
> Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. Issue tracking and wikis are not a version control problem. Sure, their data can be version controlled. And documentation has been version controlled since Sccs, why would it require special care?
- cytzol 11y ago
  > why would it require special care? It doesn't, really, but it's in the same place as the code and everything else (this is what I meant as being "on the same level"). You don't need to clone the code and then clone the tickets, for instance. When you run "fossil timeline" on your local machine, you'll see entries for tickets being closed and wiki pages being updated interspersed among the actual code commits. This is useful to me as they're as much a part of the project as the code itself. Does this answer your question?
  - gkya 11y ago
    No, unfortunately. How is this different to and / or better than having a "wiki/" subfolder, and, e.g. an Org-mode file (need not be org-mode, even a plain text file is o.k., and there are wiki systems and todo managers that use plain text) for issues on the project root? I can easily "git/hg/cvs log project.org" to see the history. And the format is not tied to the VCS software, so, if I switch to sth. else, it's still perfectly usable. An basic example of an org file for tracking issues: #+title: Project issue tracker #+description: descr... #+todo: OPEN(o!) | CLOSED (c@) This is the issue tracker for Project. In order to add a new issue, add it to the top of the entries as a plain org entry, then hit =C-c C-t o= to mark it as open. In order to close an issue, on it's headline, hit =C-c C-t C=, this will prompt for a closing comment, see the buffer that pops up for instructions. Common tags: docs, features, bugs, security, ideas * CLOSED Write README. :docs:bookkeeping: - State "CLOSED" from "OPEN" [2016-03-22 Tue 02:16] \\ Written. - State "OPEN" from [2016-03-18 Fri 22:33] * OPEN Implement new features :features: - State "OPEN" from [2016-01-27 Çrş 23:35]
joshschreuder 11y ago
Is it easy to fix merge conflicts on something like an issue?
- cytzol 11y ago
  Argh, I don’t actually know, and I probably should. I’ll ask on the mailing list and reply with what I find out.
not_kurt_godel 11y ago
> http://fossil-scm.org/ http://fossil-scm.org/ Off-topic, but I'd reccomend that you install HTTPS Everywhere: https://www.eff.org/https-everywhere https://www.eff.org/https-everywhere - the fact that you are linking the HTTP version means you don't have this very basic extension that really improves your security.
- deleted 11y ago
  [deleted]
kevinmgranger 11y ago
For those wanting to stick with Git, the concept extends to Fedora's Pagure: https://fedoramagazine.org/pagure-diy-git-project-hosting/ https://fedoramagazine.org/pagure-diy-git-project-hosting/ Granted, the documentation needs work. But all issues and docs are exposed as git repos.

by cytzol 11y ago

thecatspaw 11y ago

the parent commentator was joking that git _is_ decentralised, but that we made it centralised again by relying on a small number of hosters (github, bitbucket and others)

cytzol 11y ago
Heh, don't worry, I got the joke. But I also got the joke the last time this was posted, and the time before that, and the time before that... This just keeps happening. It's not GitHub's fault that they keep getting DDoSed or have a network outage every now and again. But it's not a problem with no solution.
- popey456963 11y ago
  To be honest, I can cope with Github's downtime, it is probably less than if I was hosting a Git solution myself and the service is much more reliable than all the other solutions I've tried (which are either lacking features or have bugs or have massive downtimes). Github is trying their best as far as I can see, they manage to fix the majority of issues within three hours and even during those three hours its not the end of the world because you can still code.

simula67 11y ago

Most developers will not be able to write code without being able to look up stuff on the Internet.

asdfadr1344kk 11y ago

<3 Fossil. I wish it were more popular so I could use it on non-personal projects and still have a hope of attracting collaborators...

CMay 11y ago
Yeah, fossil is all I use. It's so clean, tiny and self contained with no install or bloat. I've always been in love with software written that way. It makes me look at things like git as just a product of engineers that can get the job done, but don't know what it means to write good software or use imagination. Being fair, fossil performance on giant scale projects might not compare quite as well against git or proprietary solutions like Perforce, but for the large majority of projects I expect it is more than adequate.
- popmystack 11y ago
  > but don't know what it means to write good software or use imagination. You can't do patches. You can't rebase. You can't rename files. Tell me all about this good software and imagination you speak of?
  - richieadler 11y ago
    > You can't do patches. You can create bundles and submit them for approval. Very similar. > You can't rebase. You have alternatives. The work philosophy is different, though. > You can't rename files. False.
    - popmystack 11y ago
      >You can create bundles and submit them for approval. Very similar. Bundles do not have anywhere near the same flexibility and nuanced capacity that patches do. >The work philosophy is different, though. That's an apology if I've ever seen one. Again, not the same. >False. Rename a file. Then try to merge. Tell me what happens.

gkya 11y ago

> Fossil tracks issues (tickets), documentation, and wiki pages at the same level as it tracks code, so when you clone a Fossil repo, everything gets downloaded to your local computer. Issue tracking and wikis are not a version control problem. Sure, their data can be version controlled. And documentation has been version controlled since Sccs, why would it require special care?

cytzol 11y ago
> why would it require special care? It doesn't, really, but it's in the same place as the code and everything else (this is what I meant as being "on the same level"). You don't need to clone the code and then clone the tickets, for instance. When you run "fossil timeline" on your local machine, you'll see entries for tickets being closed and wiki pages being updated interspersed among the actual code commits. This is useful to me as they're as much a part of the project as the code itself. Does this answer your question?
- gkya 11y ago
  No, unfortunately. How is this different to and / or better than having a "wiki/" subfolder, and, e.g. an Org-mode file (need not be org-mode, even a plain text file is o.k., and there are wiki systems and todo managers that use plain text) for issues on the project root? I can easily "git/hg/cvs log project.org" to see the history. And the format is not tied to the VCS software, so, if I switch to sth. else, it's still perfectly usable. An basic example of an org file for tracking issues: #+title: Project issue tracker #+description: descr... #+todo: OPEN(o!) | CLOSED (c@) This is the issue tracker for Project. In order to add a new issue, add it to the top of the entries as a plain org entry, then hit =C-c C-t o= to mark it as open. In order to close an issue, on it's headline, hit =C-c C-t C=, this will prompt for a closing comment, see the buffer that pops up for instructions. Common tags: docs, features, bugs, security, ideas * CLOSED Write README. :docs:bookkeeping: - State "CLOSED" from "OPEN" [2016-03-22 Tue 02:16] \\ Written. - State "OPEN" from [2016-03-18 Fri 22:33] * OPEN Implement new features :features: - State "OPEN" from [2016-01-27 Çrş 23:35]

joshschreuder 11y ago

Is it easy to fix merge conflicts on something like an issue?

cytzol 11y ago
Argh, I don’t actually know, and I probably should. I’ll ask on the mailing list and reply with what I find out.

not_kurt_godel 11y ago

> http://fossil-scm.org/ http://fossil-scm.org/ Off-topic, but I'd reccomend that you install HTTPS Everywhere: https://www.eff.org/https-everywhere https://www.eff.org/https-everywhere - the fact that you are linking the HTTP version means you don't have this very basic extension that really improves your security.

deleted 11y ago
[deleted]

kevinmgranger 11y ago

For those wanting to stick with Git, the concept extends to Fedora's Pagure: https://fedoramagazine.org/pagure-diy-git-project-hosting/ https://fedoramagazine.org/pagure-diy-git-project-hosting/ Granted, the documentation needs work. But all issues and docs are exposed as git repos.