An Empirical Study on README contents for JavaScript Packages

February 23, 2018 Β· Declared Dead Β· πŸ› IEICE Trans. Inf. Syst.

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Shohei Ikeda, Akinori Ihara, Raula Gaikovina Kula, Kenichi Matsumoto arXiv ID 1802.08391 Category cs.SE: Software Engineering Citations 12 Venue IEICE Trans. Inf. Syst. Last Checked 4 months ago
Abstract
Contemporary software projects often utilize a README.md to share crucial information such as installation and usage examples related to their software. Furthermore, these files serve as an important source of updated and useful documentation for developers and prospective users of the software. Nonetheless, both novice and seasoned developers are sometimes unsure of what is required for a good README file. To understand the contents of a README, we investigate the contents of 43,900 JavaScript packages. Results show that these packages contain common content themes (i.e., usage, install and license). Furthermore, we find that application-specific packages more frequently included content themes such as options, while library-based packages more frequently included other specific content themes (i.e., install and license).
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted