{
  "fetched_at": "2026-10-20T05:15:48Z",
  "source_url": "https://www.kaggle.com/competitions/declutter20v2/data",
  "pages": [
    {
      "name": "rules",
      "content": "Standard academic integrity rules apply.",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "data-description",
      "content": "<h2>File descriptions</h2>\n<ul>\n<li><strong>train.csv</strong> - the training set</li>\n<li><strong>test.csv</strong> - the test set. Use these IDs for submission.</li>\n<li><strong>sampleSubmission.csv</strong> - a sample submission file in the correct format</li>\n</ul>\n<h2>Data fields</h2>\n<ul>\n<li><strong>id</strong> - an anonymous id for each comment</li>\n<li><strong>type</strong> - either Javadoc (using /**) or line (//) </li>\n<li><strong>path_to_file</strong> - the Jabref file the comment appears in</li>\n<li><strong>begin_line</strong> - the line number the comment first appears on in `file`</li>\n<li><strong>link_to_comment</strong> - hyperlink to Github display of the comment</li>\n<li><strong>comment</strong> - the text of the comment, newlines removed</li>\n<li><strong>Expected</strong> - either \"yes\" for non-informative, or \"no\" for informative. The dataset is approximately 70% no, i.e., informative comments.</li>\n</ul> ",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Description",
      "content": "** This is the 2nd version of the challenge featuring an expanded dataset**\n\n# Decluttering Challenge (DeClutter)\n\nIn the scope of [DocGen2, the Second Software Documentation Generation Challenge](https://dysdoc.github.io/docgen2/index.html), hosted by [ICSME 2020](https://icsme2020.github.io/index.html).\n\n### Task Description\nThe goal of the DeClutter challenge is to build an automated tool that can identify unnecessary software  documentation at the class or file level. For example, a comment saying ```//loop from 1 to N``` just before code implementing \nexactly that is not helpful, and worse, could drift when the underlying code is changed to (N-1) (for example). As such, it is considered as non-informative and labeled as \"Non-information = Yes\". \n\nThe tool should take in a CSV file and output a label for each row as either \"Non-information = Yes\" for clutter, non-informative comments and \"Non-information = No\" for non-clutter ones.\n\n### Definition of Non-information\nIn this study, we label as *Non-information* the comments that contain only non-information sentences. As such, the final criterion for annotation of non-information is defined as follows:\n“non-information is a comment that is completely uninformative and hence useless/should be removed (in the perspective of documentation decluttering)”. \n\nOur definition grounds on the [CADO](https://cado.informatik.uni-hamburg.de/coding-guide/) guidelines for Content Analysis for Software Documentation, which defines as non-information \"any complete sentence or self-contained fragment of text that provides only uninformative boilerplate text\". Among examples, simply restating the name of the API element without adding any detail, or stating the obvious, or simply restating the information in the rest of the code block\" [(Maleej and Robillard, TSE 2013)](https://dl.acm.org/citation.cfm?id=2554417). \n\nOur annotation unit is the entire comment. Consistently with the CADO guidelines, if a comment contains both uninformative and informative sentences, we consider that the uninformative part of the sentence is only context for the informative part, and we rate the comment as 'Non-information = No' (i.e., the comment is informative). \n\n### How to Participate\nWe invite the potential participants to register using the [web form](https://forms.gle/jkGKF44Roc51L6ZT6). **Registration is compulsory to participate in the challenge, although it is not binding**. To qualify for inclusion [in the workshop proceedings](https://dysdoc.github.io/docgen2/index.html), participants must prepare a 4 page report describing their approach and lessons learned. Otherwise, we will merely present the leaderboard. \n\n### Important Dates\nTimeline for the DeClutter Challenge\n* **20th May 2020:** Test data available\n* 28th July 2020: Kaggle competition closes\n* 31st July 2020: Report submission deadline \n* 14th August 2020: Notification deadline\n* 28th August 2020: Camera-ready deadline (tentative)\n* September 2020: Workshop dates, subject to change given pandemic.\n\n### Challenge Chairs\n- [Nicole Novielli](http://collab.di.uniba.it/nicole/), University of Bari, Italy\n- [Neil Ernst](http://www.neilernst.net/), University of Victoria, Canada\n\n### Contacts\nIf you have any questions, please contact the challenge chairs.\n\n<a rel=\"license\" href=\"http://creativecommons.org/licenses/by/4.0/\"><img alt=\"Creative Commons License\" style=\"border-width:0\" src=\"https://i.creativecommons.org/l/by/4.0/88x31.png\" /></a><br />The challenge dataset is licensed under a <a rel=\"license\" href=\"http://creativecommons.org/licenses/by/4.0/\">Creative Commons Attribution 4.0 International License</a>.\n\n### References\nIf you have any questions, please contact the challenge chairs.\n",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    },
    {
      "name": "Evaluation",
      "content": "Evaluation is using mean F-Score.",
      "isPublished": false,
      "hasIsPublished": false,
      "postTitle": "",
      "hasPostTitle": false,
      "mimeType": "",
      "hasMimeType": false
    }
  ]
}