This is an unsolicited recommendation for Danny Brooke. When Danny and I worked in the Institute for Quantitative Social Science (IQSS) at Harvard we were friendly but ran separate projects that did not overlap. After he left however, I got a chance to live in his shoes as acting project manager and truly came to understand just how capable he is. For about 6 years, Danny was at the heart of the dataverse.org team. He did much more than act as a project manager. He balanced work coming in from over a dozen competing external stakeholders in the community and within Harvard. Internally he negotiated the product future with multiple sponsors. He gave structure to the team and guided technical discussions. He managed the Dataverse User Community and was involved in the organizing of yearly user conferences. He negotiated the tradeoffs involved with ongoing operations support for the Harvard Dataverse instance. He was also manager of the team. Dataverse is the largest ongoing software project in the Institute for Quantitative Social Science at Harvard University. If you're not involved in academia you will be forgiven for not understanding the impact of the dataverse.org project in the research community. It and other data repositories like it, are an important part of the push for open sharing of data and support reproducibility in research. It's large. It's complex. It's opensource. The internal development team is supplemented by an active user community. There are around 100 deployments of this server software around the world at academic institutions. The project is more than just software. There is an additional data curation service team that works closely with the development team and there ongoing collaborations with other organizations on integrations and features. It has continued to grow in popularity because the team has managed to maintain the tightrope balancing act of remaining responsive to the community while delivering on strategic features. Danny was a key player in making Dataverse the successful mature product that it is today. I firmly believe that he will make any firm he works at more successful for his being there.

This is an unsolicited recommendation for Danny Brooke. When Danny and I worked in the Institute for Quantitative Social Science (IQSS) at Harvard we were friendly but ran separate projects that did not overlap. After he left however, I got a chance to live in his shoes as acting project manager and truly came to understand just how capable he is. For about 6 years, Danny was at the heart of the dataverse.org team. He did much more than act as a project manager. He balanced work coming in from over a dozen competing external stakeholders in the community and within Harvard. Internally he negotiated the product future with multiple sponsors. He gave structure to the team and guided technical discussions. He managed the Dataverse User Community and was involved in the organizing of yearly user conferences. He negotiated the tradeoffs involved with ongoing operations support for the Harvard Dataverse instance. He was also manager of the team. Dataverse is the largest ongoing software project in the Institute for Quantitative Social Science at Harvard University. If you're not involved in academia you will be forgiven for not understanding the impact of the dataverse.org project in the research community. It and other data repositories like it, are an important part of the push for open sharing of data and support reproducibility in research. It's large. It's complex. It's opensource. The internal development team is supplemented by an active user community. There are around 100 deployments of this server software around the world at academic institutions. The project is more than just software. There is an additional data curation service team that works closely with the development team and there ongoing collaborations with other organizations on integrations and features. It has continued to grow in popularity because the team has managed to maintain the tightrope balancing act of remaining responsive to the community while delivering on strategic features. Danny was a key player in making Dataverse the successful mature product that it is today. I firmly believe that he will make any firm he works at more successful for his being there.

This is an unsolicited recommendation for Danny Brooke. When Danny and I worked in the Institute for Quantitative Social Science (IQSS) at Harvard we were friendly but ran separate projects that did not overlap. After he left however, I got a chance to live in his shoes as acting project manager and truly came to understand just how capable he is. For about 6 years, Danny was at the heart of the dataverse.org team. He did much more than act as a project manager. He balanced work coming in from over a dozen competing external stakeholders in the community and within Harvard. Internally he negotiated the product future with multiple sponsors. He gave structure to the team and guided technical discussions. He managed the Dataverse User Community and was involved in the organizing of yearly user conferences. He negotiated the tradeoffs involved with ongoing operations support for the Harvard Dataverse instance. He was also manager of the team. Dataverse is the largest ongoing software project in the Institute for Quantitative Social Science at Harvard University. If you're not involved in academia you will be forgiven for not understanding the impact of the dataverse.org project in the research community. It and other data repositories like it, are an important part of the push for open sharing of data and support reproducibility in research. It's large. It's complex. It's opensource. The internal development team is supplemented by an active user community. There are around 100 deployments of this server software around the world at academic institutions. The project is more than just software. There is an additional data curation service team that works closely with the development team and there ongoing collaborations with other organizations on integrations and features. It has continued to grow in popularity because the team has managed to maintain the tightrope balancing act of remaining responsive to the community while delivering on strategic features. Danny was a key player in making Dataverse the successful mature product that it is today. I firmly believe that he will make any firm he works at more successful for his being there.