On Mon, Feb 11, 2013 at 08:49:49AM -0500, Jack Hill wrote:
Even if upstream accepts your fix, I'm not sure if requiring a
development version of ditz would be too high of a barrier of entry to
contributing to copyleft-next. It may not be considering that
submitting an issue via a distributed issue tracker already seems to
require more work than a centralized solution (there is the additional
step of submitting patches or a pull request after creating the
ticket), and people who do not wish or are not able to use ditz can
post their comments to the mailing list and a bug wrangler could be
appointed to create and update ditz issues.
Yes. Assuming ditz is adopted (which presupposes I can figure out how
to use it, something I'm assuming at the moment), I'm willing to be
that bug wrangler (unless someone else really wants to be).
If non-ditz uses wish to
read the bugs, the yaml files are mostly human readable and we could
post the ditz html view on
copyleft-next.org.
Basically, anything I can figure out how to use is probably not too
high a barrier to entry. :)
- RF