updated info on the provisional status

eteq · eteq · commit 362b082b33b6 · 2015-05-05T14:06:59.000-04:00
diff --git a/affiliated/index.html b/affiliated/index.html
@@ -168,9 +168,8 @@ <h2>Affiliated Packages Registry</h2>
 
 	<h2>Becoming an Affiliated Package</h2>
 
-	<p>If you are a developer of an astronomy package and would like your package to become affiliated with the Astropy project, contact the Astropy coordination commitee by leaving a message on the <a href="http://groups.google.com/group/astropy-dev">astropy-dev</a> group requesting affiliated package status. The committee and community will consider the package based on the standards below.  If your package is judged by the committe to meet these standards, it will be added to the affiliated package registry.  If the package is not quite at these standards, but working towards them, the package will be given "provisional" status.  Provisional packages will be re-evaluated yearly by the coordinating committee.  In this re-evaluation, the package will either be judged to meet the standards and no longer be provisional, or if little or no progress is being made, it may be removed from the registry. </p>
+	<p>If you are a developer of an astronomy package and would like your package to become affiliated with the Astropy project, leave a message on the <a href="http://groups.google.com/group/astropy-dev">astropy-dev</a> group requesting affiliated package status.  If you are comfortable doing so, you should also create a pull request to the <a href="https://github.com/astropy/astropy.github.com">github repository for this web site</a>, which adds your package to the registry file.  The Astropy coordination commitee and community will then consider your package based on the standards below. </p>
 
-	<p>A candidate affilated package will be judged by the coordination committee on the following standards:
 	<ul>
 		<li>It should use <a href="http://docs.astropy.org/">classes and functions from the astropy package</a> wherever possible and appropriate. This facilitates re-use of code and sharing of resources.  </li>
 
@@ -184,6 +183,9 @@ <h2>Becoming an Affiliated Package</h2>
 	</ul>
 	</p>
 
+
+	<p>If your package is judged by the coordination committe to meet these standards, it will be added to the affiliated package registry.  If the package is not quite at these standards, but working towards them, the package will be given "provisional" status.  Provisional packages will be re-evaluated yearly by the coordinating committee.  In this re-evaluation, the committee will look at progress the package has made over the previous year.  If it has been advanced sufficiently to meet the standards above, it will be considered a full affiliated package (no longer provisional).  If it has made some progress but is not yet up to the standards, provisional status will be renewed for a year.  If no progress seems to be being made, the committee will contact the authors and determine what their plans are to improve the situation.  Based on that, the committee may decide to renew the provisional status, or remove the package from the registry. </p>
+
 	<h2>Affiliated Package Template</h2>
 	<p>If you are considering creating a new astronomy package and would like it to be an Astropy affiliated package, we provide a <a href="https://github.com/astropy/package-template">package template</a> to make it much easier to meet these standards. It provides the necessary structure to generate documentation like that used in the astropy package, a ready-to-use testing framework, and a variety of tools that streamline tasks like user configuration, caching downloaded files, or linking C-compiled extensions. More details on this template are available in the <a href="https://github.com/astropy/package-template/blob/master/README.rst">usage instructions for the template</a>.
 	</p>
