Xeel

I started working on Xeel after seeing the many internal developer productivity tools and metrics tracked in larger organizations and how they help development teams write better software. As an engineer on the Trello team at Atlassian I helped build some of these internal tools and have seen the benefits integrating them into team workflows has had. Routine maintenance becomes more achievable, and easier to plan for, when there's quantifiable data available to represent that work. In the initial launch of Xeel, the focus is on version debt and tailored changelogs, allowing software teams to get a better understanding of the state of their projects' dependencies, and the changes involved in bringing them up to date, no matter the ecosystems they are working in. Longer term, Xeel will provide additional metrics impacting the software development lifecycle, with a focus on the teams and projects (vs. the individual contributors). Too often, internal tools used to measure and improve metrics affecting productivity end up becoming proxies for "measuring" individual performance; Xeel's design decisions will continue to be made to ensure this does not happen. Some ideas currently being explored are: - more first-party ecosystem plugins (go, java, kotlin, swift) - more VCS host integrations (GitLab, Bitbucket) - build/CI duration analysis - assigning owning teams/squads to dependencies (think: CODEOWNERS, but for dependencies) - pull request duration analysis (time to green builds, time to review, time to merge, etc) - digests for daily/weekly updates to metrics (via email, slack, discord, webhooks) - integration with existing data/metrics platforms like Splunk, Datadog, Newrelic Let me know in the comments what you think, and which of these ideas would be valuable to you and your team!