human: Given a hyperedge-centered hypergraph: <hypergraph>, where the center hyperedge is induced by one source paper and its member nodes are the cited papers.

Details of the hypergraph:
Center hyperedge (induced by source paper "won t we fix this issue qualitative characterization and automated identification of wontfix issues on github"):
  Abstract: Addressing users requests in the form of bug reports and Github issues represents a crucial task of any successful software project. However, user-submitted issue reports tend to widely differ in their quality, and developers spend a considerable amount of time handling these reports. Moreover, an inefficient prioritization of requested changes could have a negative impact on the developers' workloads. By collecting a dataset of around 6,000 issues from the history of 323 GitHub projects, we observe that developers spend a long time (i.e., about five months, on average) before labeling an issue as a wontfix. For this reason, in this paper, we empirically investigate the nature of wontfix issues, by manually analyzing a sample of 800 issues of this kind, extracted from heterogeneous projects. We explore the common reasons behind a "wontfix decision", the main characteristics of wontfix issues and the potential factors that could be connected with the time to close them. Furthermore, we experiment approaches for just-in-time prediction of wontfix issues using machine learning techniques to analyze the titles and descriptions of reported issues. Our investigation shed some light on the wontfix issues' characteristics, as well as the potential factors that may affect the time required to make a "wontfix decision". Our results also demonstrate that it is possible to predict whether an issue will be closed as a wontfix with average values of precision, recall, and F-measure close to 99%, confirming the practical usefulness of the proposed approach for improving the issue management practices on GitHub.

Includes members:
  Member "on the diversity of software package popularity metrics an empirical study of npm":
    also connected through other hyperedges:
      - Hyperedge HE-1 (induced by source paper "the emergence of software diversity in maven central")
  Member "what s in a github star understanding repository starring practices in a social coding platform":
    also connected through other hyperedges:
      - Hyperedge HE-2 (induced by source paper "is this github project maintained measuring the level of maintenance activity of open source projects")

Question: Please tell me which class the source paper belongs to. The 40 classes are: cs.NA(Numerical Analysis), cs.MM(Multimedia), cs.LO(Logic in Computer Science), cs.CY(Computers and Society), cs.CR(Cryptography and Security), cs.DC(Distributed, Parallel, and Cluster Computing), cs.HC(Human-Computer Interaction), cs.CE(Computational Engineering, Finance, and Science), cs.NI(Networking and Internet Architecture), cs.CC(Computational Complexity), cs.AI(Artificial Intelligence), cs.MA(Multiagent Systems), cs.GL(General Literature), cs.NE(Neural and Evolutionary Computing), cs.SC(Symbolic Computation), cs.AR(Hardware Architecture), cs.CV(Computer Vision and Pattern Recognition), cs.GR(Graphics), cs.ET(Emerging Technologies), cs.SY(Systems and Control), cs.CG(Computational Geometry), cs.OH(Other Computer Science), cs.PL(Programming Languages), cs.SE(Software Engineering), cs.LG(Machine Learning), cs.SD(Sound), cs.SI(Social and Information Networks), cs.RO(Robotics), cs.IT(Information Theory), cs.PF(Performance), cs.CL(Computation and Language), cs.IR(Information Retrieval), cs.MS(Mathematical Software), cs.FL(Formal Languages and Automata Theory), cs.DS(Data Structures and Algorithms), cs.OS(Operating Systems), cs.GT(Computer Science and Game Theory), cs.DB(Databases), cs.DL(Digital Libraries), cs.DM(Discrete Mathematics). Directly output the class name.

gpt: cs.SE(Software Engineering)