<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="" bgcolor=""> It took a couple years, but the PTA's webhosting account is now actually the PTA's. In 2011, <a href="http://www.9.0ne.org/w/Vera_Kornylak">Vera Kornylak</a> setup a webhosting with <a href="http://www.9.0ne.org/w/Sagamore_Hills_PTA_Dreamhost_account">Dreamhost for the PTA</a>, becoming the sole agent and contact. I recently established the <a href="http://www.9.0ne.org/w/Sagamore_email">collaborative email inbox, <code>communications@sagamorehillspta.org</code></a> , made a new Dreamhost contact with it, and had Dreamhost move our webhosting from Vera to <code><a class="moz-txt-link-abbreviated" href="mailto:communications@sagamorehillspta.org">communications@sagamorehillspta.org</a></code> . No more downtime from missed communications! For tiresome details, see the <a href="https://groups.google.com/a/sagamorehillspta.org/forum/#%21searchin/communications/dreamhost%7Csort:date">communications collaborative inbox</a> (sign in with <code><a class="moz-txt-link-abbreviated" href="mailto:sagamorehillspta@sagamorehillspta.org">sagamorehillspta@sagamorehillspta.org</a></code> ) I think taking individuals out of such PTA relationships and using @sagamorehillspta.org accounts instead is a smart direction to take. I'm working to document how our collaborative email inboxes might work. </body> </html>