Sectors / Software companies
Years of tickets, code reviews and design choices
How real software gets built and kept running shows up in commit history, pull requests, bug reports and architecture docs. That is the record labs want. Client code and customer details can be left out.
Check my estimateWhat qualifies
Records that are usually useful
Which of these go in is your choice. You can always leave any of them out.
PRs and review threads
What reviewers spot, challenge and why.
Commit history and repositories
How a codebase grows, is refactored and changes across the years.
Design docs and release notes
The reasons behind how systems are built, and how they evolved.
Issue and bug history
How issues are reported, reproduced, prioritized and closed.
What software firms ask first: code that belongs to clients
If you build software for clients, much of that code may belong to them. Who owns what is part of scoping, and client projects can be left out. Whether you need a client's permission is a question for you and your counsel.
Your tickets and logs also name your customers. The de-identified copy replaces customer and developer names with placeholders, and any repo, tool or time period can be left out.
How the process works
Everything starts under an NDA. No one asks for tokens or passwords. Nothing goes out until you approve a sample, and your repos never move.
Two short questions
Do we need to share our core product?
No. You can hold back any repo or product you consider core.
Is our ticket history enough?
It may be. A well-kept issue tracker is a good place to start the conversation.