3 ms·
Then if SF goes down we'll go back to emails & patches. Issues will be tracked with post-its & todo lists and communicated by voice.
by antoineMoPa 10y ago
Then if SF goes down we'll go back to emails & patches. Issues will be tracked with post-its & todo lists and communicated by voice.
- ben_jones 10y agoYoung blood here. Can we go further?
- wckronholm 10y agoThere's only so far tin can and string will go.
- hueving 10y agoI really wish we could get the community effects of github without github and have everyone self-hosting repos or even a fully distributed solution on top of something like IPFS.
- AndyNemmity 10y agoI gave up and started posting to usenet.
- naibafo 10y agoLet's just get rid of the darn computers already.
- cm3 10y agoIt's not fossil-scm, but git-appraise restores some of the lost distributed'ness: https://github.com/google/git-appraise https://github.com/google/git-appraise https://github.com/google/git-appraise-web https://github.com/google/git-appraise-web https://github.com/Nemo157/git-appraise-rs https://github.com/Nemo157/git-appraise-rs And there's also http://jk.ozlabs.org/projects/patchwork/ http://jk.ozlabs.org/projects/patchwork/ (http://patchwork.ozlabs.org/project/qemu-devel/list/ http://patchwork.ozlabs.org/project/qemu-devel/list/).
- happyslobro 10y agoI am sorely tempted to just start tracking issues as YML or CSV + markdown files in an issues directory. That gets me all kinds of features that GH doesn't provide: - offline issue management (bugs on a plane) - issues associated with branches - grep, awk, ack, sed - all of the above, available to git hook scripts The only thing he holding me back, is that I really want to get this right. This needs to become a standard, not "Dan's weird repo that no one understands".