Deft is a simple distributed feature tracker (aka issue tracker, task tracker, bug tracker) designed to work with a distributed version control system such as Git.
Principles
All features have a status (e.g. new, in-development, ready-for-testing, ready-for-deployment)
Absolute prioritisation of features that have the same status
Store feature database alongside the code in VCS, not in another tool
Store the feature database in plain-text files that play well with VCS and diff/merge tools
Don’t re-implement functionality that is already in the VCS
Getting Started
Install from PyPI using easy_install or pip. For example:
% pip install deft
After that you can use the deft command to create, manipulate and query Deft feature trackers. Use deft --help and/or read the Quickstart Guide to get started.
Support
You can join the Deft discussion group.
Issues are tracked with Deft itself. If you want to raise issues or feature requests:
Fork the repo & check it out locally
Follow the ‘Developing Deft’ steps
use the ./dev-deft command to create a new issue
commit the new issue
send a pull request
Yes… there should be a tool to make this process simpler and easy for a project’s users to do.
Developing Deft
To work on the Deft code itself:
You need Python 2.7 and virtualenv installed
Check out from GitHub
Run make env to create a python environment for development
Run make to run all the tests.
The dev-deft script will run deft from the development environment. Run dev-deft --help for help.
1 maintainer
Metadata
1 maintainer
Release files for Deft 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| Deft-0.2.0.tar.gz | 43.8 kB | Without provenance | Details |
Release files / Deft-0.2.0.tar.gz
| Download URL | Deft-0.2.0.tar.gz |
|---|---|
| Size | 43.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b30d41cab3615fec96e6c86b4fba9a30b03cae047a721272eb951c9c6fca3b82
|
|
BLAKE2b-256 checksum How to use checksums |
7d14960989a6e668a2b49283664f040539d18394d57f7baa5c8aa70e723c060c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Deft 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
