human: Given a node-centered hypergraph: <hypergraph>, where nodes represent papers and hyperedges represent sets of papers co-cited by a source paper.

Details of the hypergraph:
Center node: "why modern open source projects fail"
  Abstract: Open source is experiencing a renaissance period, due to the appearance of modern platforms and workflows for developing and maintaining public code. As a result, developers are creating open source software at speeds never seen before. Consequently, these projects are also facing unprecedented mortality rates. To better understand the reasons for the failure of modern open source projects, this paper describes the results of a survey with the maintainers of 104 popular GitHub systems that have been deprecated. We provide a set of nine reasons for the failure of these open source projects. We also show that some maintenance practices -- specifically the adoption of contributing guidelines and continuous integration -- have an important association with a project failure or success. Finally, we discuss and reveal the principal strategies developers have tried to overcome the failure of the studied projects.

Connected through hyperedge HE-1 (induced by source paper "is this github project maintained measuring the level of maintenance activity of open source projects"):
  with members:
    - "what s in a github star understanding repository starring practices in a social coding platform"
    - "identifying unmaintained projects in github"
    - "why we engage in floss answers from core developers"
    - "predicting the popularity of github repositories"
    - "understanding the factors that impact the popularity of github repositories"
    - "robust classification for imprecise environments"

Connected through hyperedge HE-2 (induced by source paper "a topological analysis of communication channels for knowledge sharing in contemporary github projects"):
  with members:
    - "communication channels in safety analysis an industrial exploratory case study"
    - "human capital in software engineering a systematic mapping of reconceptualized human aspect studies"
    - "extracting insights from the topology of the javascript package ecosystem"
    - "understanding the factors that impact the popularity of github repositories"

Connected through hyperedge HE-3 (induced by source paper "on the abandonment and survival of open source projects an empirical investigation"):
  with members:
    - "why do developers take breaks from contributing to oss projects a preliminary analysis"
    - "why we engage in floss answers from core developers"
    - "an empirical comparison of developer retention in the rubygems and npm software ecosystems"
    - "a novel approach for estimating truck factors"

Connected through hyperedge HE-4 (induced by source paper "why do developers take breaks from contributing to oss projects a preliminary analysis"):
  with members:
    - "an empirical comparison of developer retention in the rubygems and npm software ecosystems"
    - "a novel approach for estimating truck factors"

Connected through hyperedge HE-5 (induced by source paper "what s in a github star understanding repository starring practices in a social coding platform"):
  with members:
    - "how do developers promote open source projects"
    - "a novel approach for estimating truck factors"
    - "predicting the popularity of github repositories"
    - "understanding the factors that impact the popularity of github repositories"
    - "why we refactor confessions of github contributors"
    - "dynamical classes of collective attention in twitter"
    - "robust classification for imprecise environments"

Connected through hyperedge HE-6 (induced by source paper "why we engage in floss answers from core developers"):
  with members:
    - "why and how java developers break apis"
    - "towards an interdisciplinary socio technical analysis of software ecosystem health"
    - "a novel approach for estimating truck factors"
    - "classifying developers into core and peripheral an empirical study on count and network metrics"
    - "understanding the factors that impact the popularity of github repositories"
    - "why we refactor confessions of github contributors"

Connected through hyperedge HE-7 (induced by source paper "identifying unmaintained projects in github"):
  with members:
    - "why we engage in floss answers from core developers"
    - "understanding the factors that impact the popularity of github repositories"
    - "robust classification for imprecise environments"

Question: Please tell me which class the center node 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)