Author: hboutemy
Date: Sat Feb 17 16:15:20 2024
New Revision: 1915832

URL: http://svn.apache.org/viewvc?rev=1915832&view=rev
Log:
inform board on board@

Modified:
    attic/site/xdocs/process.xml

Modified: attic/site/xdocs/process.xml
URL: 
http://svn.apache.org/viewvc/attic/site/xdocs/process.xml?rev=1915832&r1=1915831&r2=1915832&view=diff
==============================================================================
--- attic/site/xdocs/process.xml (original)
+++ attic/site/xdocs/process.xml Sat Feb 17 16:15:20 2024
@@ -27,7 +27,7 @@
 <section id="moving">
   <title>Moving a PMC to the Attic</title>
 
-  <p>At some point a PMC may vote to join the Attic. The following defines a 
process 
+  <p>At some point a PMC may want to join the Attic. The following defines a 
process
      to move that PMC into the Attic and gently close it down. </p>
 
   <ol>
@@ -36,7 +36,7 @@
         <li>Conduct a discussion on the public developer list whether to 
dissolve the PMC. Do not conduct it on the private PMC list.</li>
         <li>Consider an appeal to the user list for interested users to 
provide their interest in helping out more.</li>
         <li>Conduct a PMC vote on the public dev list. </li>
-        <li>If the PMC votes to dissolve the PMC and move to the Attic, inform 
the board of the successful vote (linking or forwarding the 'successful' vote) 
and add a <a href="resolution.html">resolution</a> to dissolve the PMC to the 
next board meeting agenda. </li>
+        <li>If the PMC votes to dissolve the PMC and move to the Attic, inform 
the board of the successful vote on board@ mailing list (linking or forwarding 
the 'successful' vote) and add a <a href="resolution.html">resolution</a> to 
dissolve the PMC to the next board meeting agenda. </li>
         <li>If the PMC can't get enough people to vote to dissolve the PMC 
(and there are not three -1 votes), then that is grounds for moving to the 
Attic. They should inform the board as above, noting that the vote failed to 
get enough votes. </li>
       </ul>
     </li>


Reply via email to