Sectors / Software companies
Years of tickets, code reviews and design choices
Commit history, pull requests, bug reports and architecture docs show how real software is built and maintained. That record is what labs want. Client code and customer details can stay out.
Check my estimateWhat counts
Records that are usually useful
Which of these go in is your choice. Any of them can be left out at any time.
Pull requests and reviews
What reviewers catch, push back on and why.
Commit history and repositories
How a codebase grows, is refactored and changes across the years.
Issue and bug history
How issues are reported, reproduced, prioritized and closed.
Design docs and release notes
The reasons behind how systems are built, and how they evolved.
The concern we hear most: code that is not ours
When you build software for clients, much of the code may be theirs. Scoping covers who owns what, and any client project can be left out. You and your counsel decide whether a client's permission is needed.
Your tickets and logs also name your customers. Customer and developer names become placeholders in the de-identified copy, and you can exclude any repo, tool or period.
How the process works
From the very first step, an NDA covers everything. Nobody asks for tokens or passwords. You approve a sample before anything goes out, and your repositories stay exactly where they are.
Two quick questions
Must our core product be part of it?
No. You are free to hold back any repo or product you consider core.
Could our ticket history be enough?
It may be. A well-kept issue tracker is a good starting point for the conversation.