===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/Attic/porting.html,v
retrieving revision 1.56
retrieving revision 1.57
diff -c -r1.56 -r1.57
*** www/Attic/porting.html	2006/11/04 10:53:37	1.56
--- www/Attic/porting.html	2007/06/18 15:27:16	1.57
***************
*** 52,57 ****
--- 52,69 ----
     its address to <a href="mailto:ports@openbsd.org">ports@openbsd.org</a>
     or send the port mime encoded to the same address.  Pick whichever
     method works best for you.
+   <p>
+    Porting some new software takes time. Maintaining it over time is harder.
+    It is quite okay to port software, and let other people handle it 
+    afterwards. It is also okay to help other people update and maintain
+    other ports, as long as you communicate to avoid doing the same things
+    twice.
+   <p>
+    In the OpenBSD culture, <code>MAINTAINER</code>ship is not a status item,
+    but a responsibility.  We have CVS and comments to give credit to the
+    person who did the work.  A port <code>MAINTAINER</code> is something else:
+    a person who assumes responsibility for the working of the port, and is
+    willing to spend some time ensuring it works as best as can be.
  
  <h3><font color="#0000e0">Index of Porting Documentation</font></h3>
  <ul>
***************
*** 394,399 ****
    <hr>
    <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a> 
    <a href="mailto:www@openbsd.org">www@openbsd.org</a>
! <br><small>$OpenBSD: porting.html,v 1.56 2006/11/04 10:53:37 espie Exp $</small>
   </body>
  </html>
--- 406,411 ----
    <hr>
    <a href="index.html"><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a> 
    <a href="mailto:www@openbsd.org">www@openbsd.org</a>
! <br><small>$OpenBSD: porting.html,v 1.57 2007/06/18 15:27:16 espie Exp $</small>
   </body>
  </html>