- Production Website
- Changelog
- Contributing
- Getting Started
- Database & Assets
- Old Datatracker Branches
This project is following the standard Git Feature Workflow development model. Learn about all the various steps of the development workflow, from creating a fork to submitting a pull request, in the Contributing guide.
Make sure to read the Styleguides section to ensure a cohesive code format across the project.
You can submit bug reports, enhancement and new feature requests in the discussions area. Accepted tickets will be converted to issues.
As outlined in the Contributing guide, you will first want to create a fork of the datatracker project in your personal GitHub account before cloning it.
Because of the extensive history of this project, cloning the datatracker project locally can take a long time / disk space. You can speed up the cloning process by limiting the history depth, for example (replace USERNAME with your GitHub username):
- To fetch only up to the 10 latest commits:
git clone --depth=10 https://github.com/USERNAME/datatracker.git
- To fetch only up to a specific date:
git clone --shallow-since=DATE https://github.com/USERNAME/datatracker.git
A beginning of a walkthrough of the datatracker models was prepared for the IAB AID workshop.
In order to simplify and reduce the time required for setup, a preconfigured docker environment is available.
Read the Docker Dev Environment guide to get started.
Nightly database dumps of the datatracker are available at
https://www.ietf.org/lib/dt/sprint/ietf_utf8.sql.gz
Note that this link is provided as reference only. To update the database in your dev environment to the latest version, you should instead run the
docker/cleandbscript!