Merge pull request astropy#416 from taldcroft/contribute-role

taldcroft · web-flow · commit a9d530b5d657 · 2020-12-02T04:58:09.000-05:00
Add section to Contribute page for taking on an Astropy role
diff --git a/contribute.html b/contribute.html
@@ -154,6 +154,31 @@ <h2 id="contribute-code-or-docs">Contribute code or documentation<a class="paral
 		<p> If you want to propose a larger change to Astropy, there's a procedure for that:  <a href="https://github.com/astropy/astropy-APEs">Astropy Proposals for Enhancement (APEs)</a> (modeled after Python's <a href="http://legacy.python.org/dev/peps/">PEPs</a>).  The sort of changes that APEs are intended for include plans for new sub-packages, wide-ranging code re-organizations, a new procedure needing review by a lot of the Astropy community, or an informational document on some decision for Astropy that you want remembered.  For more background on APEs, check out <a href="https://github.com/astropy/astropy-APEs/blob/master/APE1.rst">APE #1</a> and the <a href="https://github.com/astropy/astropy-APEs/blob/master/README.rst">APE repository's README</a>.  There is also a <a href="https://github.com/astropy/astropy/wiki/APE-Overview">wiki page on Astropy's github repository</a> that has an overview of the existing APEs.</p>
 
 
+	</section>
+
+	<section id="role">
+		<h2 id="formal-project-role">Taking on a formal project role<a class="paralink"
+		href="#formal-project-role" title="Permalink to this headline">¶</a></h2>
+
+		<p>
+            AIf you are interested in a higher level of contribution to the project, you can consider taking on one of the formal
+            project roles as listed in the <a href="team.html">Astropy Team</a> page.
+            </p>
+        <p>
+            In order to be nominated for a named Astropy role, it is typical that a person will have
+            been actively involved in the project for a considerable amount of time (at least a year
+            and often longer) and have made substantial contributions. They will have shown a
+            sustained commitment to Astropy by participating actively already in activities related
+            to the role. This could involve submitting pull requests and participating in
+            reviews, or discussions in other channels such as mailing lists or Slack, or other
+            contributions as defined by a particular role. Finally, they need to express a desire to
+            maintain this involvement going forward and accept the responsibility of having a role.
+            For example, being a core sub-package maintainer involves interacting with users and
+            responding to bug reports in a timely manner. If you are interested in taking on such a role, you can volunteer
+            either on `astropy-dev` or by talking to a holder of the role you are interested in, or a coordination commitee 
+            member.
+        </p>
+
 	</section>
 
 	<section id="affiliated">
