Comments (3)
I would imagine, using the same storage model, or at least have a bridge (importer & exporter) from one format to the other would be cool.
It has been a while that I had a look at that project. IIRC and things didn't change dramatically, the data model itself is indeed completely incompatible. While git-dit is modelled after mailing lists, git-bug is essentially based on a file-based data storage of issues which are designed to be easily diffable and mergable (using a custom tool). In git-dit you alter a single knob of an issue while in git-bug you commit a full representation of an issue's metadata (incorporating a change). Both models have their pros and cons. But it is a rather hard choice what model to choose.
An import/export functionality could be drafted. But a seamless interaction between both systems is probably not possible.
That being said, there are opportunities for collaboration. For example, handling of an issue's state (e.g. "open"/"closed") and other metadata may benefit from a common ground. And be it for the user-experience alone. One of my neglected and dormant projects called issue-state was intended as possible base. Authentication and/or exchange of issue data between different forks is also a problem which (probably) all distributed issue trackers based on git face. A solution for one issue-tracker would probably also work for other issue-trackers.
this issue might be a good point for initiating contact, if it does not exist yet.
Well, I don't think that git-bug will completely redesign their storage model. That would not make much sense. I do have to say, however, that git-dit's data model was chosen partly to avoid the entire collision-avoidance mess the issue talks about. So... git-dit simply doesn't have that particular issue
from git-dit.
sorry for the late answer, I wanted to have a free head to answer...
In git-dit you alter a single knob of an issue while in git-bug you commit a full representation of an issue's metadata (incorporating a change).
I am not sure I understood this correctly, but if I did, I think.. the git-bug model works differently now. There are commits altering a bug, which consists of packs of "Operation"s, each modifying a part of the bug, for example the title, the message, the due-date, ... and there is a different type of Operation for each modification, for example CREATE, MODIFY_DATE, ADD_COMMENT, MODIFY_COMMENT,...
so .. I would guess it is more similar then, no?
from git-dit.
I am not sure I understood this correctly, but if I did, I think.. the git-bug model works differently now.
Well, I may also just have mixed up git-bug's data-model with the data model of another distributed issue tracker in the end (there are quite a few, some also called "git-bug").
The data-model you described is indeed more similar to that of git-dit. However, I do have to have a closer look at git-bug again in order to assess whether direct interaction is feasible or not.
from git-dit.
Related Issues (20)
- Get the next release out HOT 2
- Workflow examples HOT 2
- Please add your project to https://dist-bugs.branchable.com/ HOT 6
- git-dit list/show panics HOT 14
- No crates actually released HOT 3
- We have no way to show all issue trees HOT 2
- [UI] "git dit show -g" should have colors
- Neither --verbose nor --trace print any output HOT 1
- `git dit list` shows committer date, should show author date
- Flag to _not_ use pager HOT 2
- Helppage: new --metadata missing prefix description HOT 1
- new --metadata keys HOT 1
- libgitdit is too hard to use HOT 6
- git-dit gc is slow HOT 11
- Trailers not beeing recognized (when having underscore in key?) HOT 4
- Workflow: Sending issues with git-format-patch / applying with git-am
- README clarifications HOT 3
- Does not build manpages with pandoc 2.2.1 HOT 3
- malformed URL error for git+ssh://user@host:/path/foo.git HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from git-dit.