Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[emf-dev] [Academic study] how do OSS developers annotate Technical Debt?
  • From: "Cassee, Nathan" <n.w.cassee@xxxxxx>
  • Date: Fri, 17 Sep 2021 13:15:45 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9IPuKH+5sB69TDvZ3xh+q0e7Tko9w3Toemy+xjUU1uc=; b=TPJtwjVYj0Hc+RIgKt64+U0aVUHCw5YFYGrUpa6SBkJ2XWu6R8b3vns/eLV4gUzN1FK81GydrmCNJ7y8+VKIkavq1jZ6cnORwCErGD8eVPFWRBut+75y+UfqKNw9U1iwzYQZrIUFGfCqvMQvki1KAyN7YoJmM9ZgbQAOClO4EbOTWADJpcRYfG75Hkt7/Acqk/jxqVdT3xrEhqjMvD3jF3sPGP5uCGn0UyhDvNZaNJ05Gi8f880UDcnv+XaJJInCWyxZCB7qWZAdlPrprw9FKbe2sWO3tYzO6q2Q25xQ151348hFNseSE/K/WCm7Rbr0n8cqc5by/OZtJNuK2KBZhw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=R2roBn2OpS9ELIPmxm6qduhGoBTQWN2p7mL83+wCtEAlZdcUs0I0WKUtkmKyK7wfGZcCVHblfT56QeVBFu6XjTQrnIan2gkxEVt64A/Delg9aR6vu5t24KVJg42mh71CbCc8lEBX+VuGMNsqcnNkdJgW/kW5h1gfz4mkLgsB9Vbx1dC6I4Dl8lNIYATNwzZXKq+Ww37WFRJcYnJ5HWK1+jjN6njVGjtwQGFu6hsNmcx3aiXXa3VqZa6mFd/gEOlisvcghGEUsB9oWNB7LedrVMRXG/5HR5xGf54Rs5LgNWXqCUFce5Z6Lm07PHa/mN0ps86ch7sgFVt7Ww1I0uau3A==
  • Delivered-to: emf-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: Aderxh8Jt1yayTtLTyOpr35IZDkrZQ==
  • Thread-topic: [Academic study] how do OSS developers annotate Technical Debt?



We're a team of Software Engineering researchers investigating technical debt. Technical debt refers to "not quite right code which we postpone making it right” (Cunningham) and this may often introduce a cost. More specifically, the aim of this study is to gather information on how open source developers respond to specific source code phenomena such as partially or wrongly implemented functionality. With the results of this study we aim to create a better understanding of how developers annotate issues in source code. These results will be used to support prioritisation of maintenance activities in software systems. The survey data will be collected, analyzed and stored so that research questions can be answered and the results can be published. Since the survey is anonymous, no personal information is collected. For the same reason we cannot modify or remove answers upon request.


If you contribute code to this project you can help us out by filling out the following survey: The survey should take you at most 15 minutes.


Thanks in advance,



Back to the top