[copyleft-next] Distributed issue tracking with ditz

Jack Hill jackhill at jackhill.us
Mon Feb 11 04:10:24 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Ahoy hoy,

I took a stab at setting up a distributed issue tracker for us. I
decided to go with ditz [0] because I liked its feature set and it
seemed to be a reasonable state of maintenance. It meets Richard
Fontana's requirements of not being written in PHP (it's written in
Ruby) and not using a database (state is stored in yaml files). I have
published a version of the repository with some ditz issues here [1],
look at the ditz-experiment branch.

I have created two issue so far. The first is to track to migration to
ditz and second is the start of importing a github issue. Between the
readme on the ditz website and the built-in help "ditz help" I felt
comfortable working with ditz in about 10 minutes.

Important things to note about ditz:

It has the ability to assign issues to releases. I have created two
releases (0.1.2. and 0.2.0), but did not assign the issues I created to
a release.

It has a concept of whether an issue is being worked on, governed by
ditz start and ditz stop. I started working on the migration ticket,
but not on the one imported from github.

After working with ditz changes need to be committed. ditz reminds you
of this.

ditz is packaged in Debian and a Gentoo ebuild is available from the
betagarden overlay.

I look forward to hearing what you think about ditz.

Best,
Jack

[0] http://ditz.rubyforge.org/
[1]
https://user.physics.unc.edu/~jackhill/revision-control/copyleft-next.git
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iQIcBAEBCgAGBQJRGG80AAoJECuXUNTWhOopNeEP/iX300wnHocOEtwupkgdj1Cr
2uT+A+mbWVrXIY3bTHz4bLJ9F5fgkYauaM9sFGxEuH2iymnQUx8CZcYacqxwF1Jx
IRt/MQtOVK1TQaF474I3Js6SONCDYEV8lRcL84f+ssatPc8xw0VXYfri9b012pY8
eIcK7lqQA5gObmwt20YkUrPjBxpeT+Zv418raGGHJiGJyf0hhMW5ucwceBWawi/U
IZpd8NLXvp2fmFjnIWIdikWk28Zz/MV2o+5f7yxObaj6ocg1k8dCwM19LGqwfitT
Hw7TOPvsYhsqFCYHo/9HH0iu01+2Bhi/ne63UIGyANrw7yOi8ZrU2ZKzUvJzspr1
7ZUezxPATeng37mGRjpZV3vYMzM+sAwCht2svQBL54Xi1AToNMn1d6MqxOp6pv0J
pyntmKqw3rKhHDfOdGf1AUs1VEHa+mtGgSM9KQ9U9PNbINv+ZTyK0365Hk3wHsye
TPDbX1Xt7xk3JbGHdgZYKACpuWW5F+cbNKzWlHzhJbxYbNjxltcGQ4korME3FG+N
FTmLEblF7nC7kEbpfCMgvPzeHc/Jvb19rQ1/ZyBoywVFlw4UT42t60A3yMjHfqwU
3er3et5fCk/l7i2k32TX6/9Wcoyo2q36qSUdxRu48KMLZxUeYSviFEHQ534ipEzb
Pp/kDC+Z1BqovbVb9hRY
=A1pf
-----END PGP SIGNATURE-----


More information about the copyleft-next mailing list