Callback systems for projects

As mentioned in a previous post I would like an interface for each project.

Here is an idea for one standards based git hooks based approach.

Using git you have the following hooks server side :
https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks

• pre-receive on the server before the push is taken
• update for each branch in the push
• post-receive after the commit is received

So let's think about a posting of an artifact to a project as some type of committing of meta data to a repository.

There are git based wikis already like https://github.com/gollum/gollum and many others.

First lets think about each bug report or artifact or post as a git commit of markdown with metadata like mentioned here and detailed here as some kind of wiki and the wiki is based on git based on the blockchain

There is already some integration between git and bugzilla like this and many other projects
see also the [emacs org mode sync] (https://github.com/arbox/org-sync)
We were to create a git user account for utopian that would push a commit in third party project owned for each change to the post or update. This would be pushed into an special utopian.io branch on the other server. If that branch exists it will be pushed to.

That repo would contain standard git hooks that would be managed by the admins of the project to deal with the interactions, calling shell scripts etc. If it was a github project there are other ways to implement hooks but it is all hidden by the git interface.

The interface would be :

• Branch : Utopian
• Directory Structure :

1. suggestions/
2. bug_hunting/
3. etc

• File names
  Each report is given a new name like the url of the utopian post
  For example https://utopian.io/utopian-io/@h4ck3rm1k3st33m/wanted-elm-package-uninstall
  would be in : Suggestion/wanted-elm-package-uninstall

Any feedback from the other system would be sent as commits to a meta section of the post,
so feedback/comments will be appended in a #comments section of the post and the utopian will get callbacks/webhooks to feed back from the project.

Existing Implementations

Debian has a simple text based bug reporting system based on email that should be reviewed for format and implementation https://www.debian.org/Bugs/

Now fossil is a distributed version control system but rejects using files for bug reports instead using a table. I dont see this as an issue because we already have the posts on the blockchain.

The closest implementations that I could find of this idea so far is http://veracity-scm.com/ that also puts the project metadata on the version control system.

Here is one for git :
https://github.com/neithernut/git-dit

There is a detailed implementation based on git internals https://github.com/neithernut/git-dit/blob/master/doc/datamodel.md
and https://github.com/neithernut/git-dit/blob/master/git-dit.1.md

Another project mentioned here on ycombinator
http://www.digitalgemstones.com/projects/b/

it is based on the task manager t http://stevelosh.com/projects/t/ that is similar to the emacs org mode.

See also

• https://en.wikipedia.org/wiki/Bug_tracking_system
• https://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems
• https://en.wikipedia.org/wiki/Issue_tracking_system
• https://news.ycombinator.com/item?id=13732598

---

Posted on Utopian.io - Rewarding Open Source Contributors

---