Sectors / Software companies
Years of tickets, code reviews and design choices
Commit history, pull requests, bug reports and architecture docs show how real software gets built and kept alive. Labs are after exactly that record. Client code and customer details can be left out.
Check my estimateWhat counts
Records that are usually useful
Which of these go in is your choice. Leaving any of them out is always an option.
Commit history and repositories
The way a codebase expands, gets refactored and shifts over the years.
Design docs and release notes
The reasons behind how systems are built, and how they evolved.
Code reviews and pull requests
The things reviewers catch and push back on, and the reasons.
Issue and bug history
How problems get reported, reproduced, prioritized and closed.
The concern we hear most: code that is not ours
When you build software for clients, much of the code may be theirs. Who owns what is part of scoping, and client projects can be left out. You and your counsel decide whether a client's permission is needed.
Tickets and logs also mention your customers. In the de-identified copy, customer and developer names are replaced with placeholders, and any repo, tool or period can be excluded.
How it is handled
Everything starts under an NDA. Tokens and passwords are never requested. Nothing goes out until you approve a sample, and your repos never move.
Two common questions
Do we need to share our core product?
No. You are free to hold back any repo or product you consider core.
Is our ticket history enough?
It can be. A tidy issue tracker is a solid place to begin the conversation.