Create governance.html

governance.html

@@ -0,0 +1,86 @@
+---
+layout: default
+title: Governance
+---
+
+<style> 
+.support-logos{
+text-align: center;
+}
+</style>
+<div class="container support" style="margin-top: 10px;">
+
+  <div class="row" style="padding-top: 20px;">
+    <div class="col-lg-12">
+      <h1 style="color: #285893;">Governance</h1>
+      <h2>Committees</h2>
+      <p>Parsl is reliant on the collaborative efforts of community contributors who undertake various crucial roles. These responsibilities encompass a wide range of activities, including core development, communication and outreach, and management tasks. Below we outline core project roles and committees and their respective responsibilities. We denote leads of each committee in bold. </p>
+      <p>We encourage members of the community to join these committees and contribute to the project. If you would like to join a committee, please use this form to indicate your interest: <a href="https://bit.ly/parsl-committee-form" target="_blank">https://bit.ly/parsl-committee-form</a>.</p>
+      <p>Membership decisions for each committee are made by a simple majority vote of current members of that committee.</p>
+
+      <h3 style="font-color: #285893;">Coordination</h3>
+      <p>Overall coordination and management of the project, including:</p>
+      <ul>
+        <li>Keeping a large-scale view of the Parsl ecosystem</li>
+        <li>Evaluating new affiliated package submissions and review of existing affiliated packages</li>
+        <li>Approving or rejecting Parsl EPs (ParEPS)</li>
+        <li>Arbitrating disagreements in the core package, including final decisions when otherwise deadlocked</li>
+        <li>Maintaining the list of roles and related GitHub permissions</li>
+        <li>Managing finances for the project</li>
+        <li>Coordinating with funding organizations</li>
+        <li>Securing funding for the project via discussions and proposals to funding agencies</li>
+        <li>Monitoring the [email protected] email account</li>
+        <li>Manage violations of the code of conduct or other ethical concerns</li>
+        <li>Determine and manage the process for paying people from project funding</li>
+        <li>Oversee payment for services, licenses, and travel and other miscellaneous expenses the project pays for</li>
+        <li>Maintain and continuously develop a transparent process for reporting to the wider Parsl community</li>
+      </ul>
+      <p>Coordination Committee Members: Yadu Babuji, Sophie Bui, Kyle Chard, Ben Cliford, Daniel S. Katz, Logan Ward</p>
+
+      <h3>Code Maintenance</h3>
+      <p>Overall management and maintenance of core code, including:</p>
+      <ul>
+        <li>Curating issues, reviewing and merging code contributions, managing releases, etc.</li>
+        <li>Automated testing and release infrastructure</li>
+        <li>Keeping documentation for the release process of the Parsl package up to date</li>
+        <li>Evaluating new pull requests for quality, API consistency, and Parsl coding standards</li>
+        <li>Perform initial triaging of issues and pull requests</li>
+        <li>Keeping track of frequent contributors and their relevant areas of expertise</li>
+        <li>Maintaining the Parsl GitHub repository</li>
+        <li>Maintaining the coordinated package's infrastructure (usually via the helpers and package template</li>
+        <li>Managing the Sphinx infrastructure</li>
+        <li>Implementing changes and improvements to the documentation website</li>
+        <li>Overseeing content (although primary responsibility for content lies with subpackage maintainers)</li>
+      </ul>
+      <p>Code Maintainance Committee Members: Yadu Babuji, Ben Cliford, Logan Ward</p>
+
+      <h3>Training and Outreach</h3>
+      <ul>
+        <li>Managing tutorial content, organizing tutorials and outreach events, organizing community meetings</li>
+        <li>Ensuring that documentation and tutorials are internally consistent and cover key areas of the ecosystem</li>
+        <li>Development and testing of notebooks, reviewing issues and contributions to tutorial content, soliciting new content</li>
+        <li>Identify opportunities for workshops and training activities in different locations, working with team members to organize and deliver workshops</li>                                                                                                                                                     
+      </ul>
+      <p>Training and Outreach Committee Members: Kyle Chard, Daniel S. Katz</p>
+
+      <h3>Communication</h3>
+      <p>Overall management of communications and promotions across website, Slack, and social media, including:</p>
+      <ul>
+        <li>Managing website content and updates through GitHub pull requests to the website repository, which is automatically synced to parsl-project.org</li>
+        <li>Maintain Parsl’s social media accounts and content development</li>
+        <li>Monitor/moderate non-technical Slack discussions and email inquiries</li>
+        <li>Keep track of/help organize conferences and workshops</li>                                                                                                                                                     
+      </ul>
+      <p>Communications Committee Members: Sophie Bui, Daniel S. Katz</p>
+
+      <h3>Under Development</h3>
+      <h4>Community Champions</h4>
+      <ul>
+        <li>Advocating for and support the use of Parsl within their specific communities</li>
+        <li>Facilitate connections and collaborations between members</li>
+        <li>Answer Parsl-related inquiries specific to their domain in Slack and GitHub</li>                                                                                                                                               
+      </ul>
+      <p>Community Champions Committee Members: Sophie Bui (community manager), Logan Ward (Materials Science, Machine Learning)</p>
+    </div>
+    </div>
+</div>