These tools are placed under shared maintenance and development in the <code>scverse</code> GitHub organization.</p><p><code>scverse</code> <em>core</em> tools are expected to interface with and be supplemented by other tools in the ecosystem. <code>scverse</code> strives for synergy and interoperability with the ecosystem of packages built around these <em>core</em> tools, to ultimately provide users to cutting-edge and varied selection of analysis methods.</p><h2 id=user-engagement>User engagement</h2><p>We are community-driven and committed to keeping the <code>scverse</code> community open. We strive to actively foster a community where everyone is and feels welcomed, and where there are no barriers to contributions in any form. We welcome newcomers and pledge to build an environment where they can grow as contributors, developers, and community members. Together with technical and development support, we also support our users through:</p><ul><li>Clear documentation of code and usage via docs and tutorials.</li><li>Participation in development through issues and pull requests.</li><li>Community forums, such as our Discourse, Zulip, and Twitter.</li><li>Workshops at which we teach analysis workflows based on the <code>scverse</code> ecosystem.</li></ul><h2 id=developer-engagement>Developer engagement</h2><p>Tools within <code>scverse</code> are deliberately not unified under a single package, and instead form a consortium of <em>core</em> analytic tools with shared maintenance responsibilities.
0 commit comments