Why is the website still missing content? As someone who does IT project management and has done web application development and project management this type of "cutover" is absurd. Why wasn't the new website fully developed in a QA type environment and then just cutover on one night? Why is the PDGA website being hacked an issue? Are they hosting their own website? If so, that is bad form ... they aren't in the business of hosting and should outsource to a company that hosts and can manage security type of issues. I'm not trying bash here ... just providing some constructive feedback on how to handle future issues.

I think the new website is going to be much better for the members and the PDGA in general. On the other hand, I do have to agree with some of what Stagger is saying here. The old site was hacked and that is a bummer, but the new site should have been developed in full and hosted externally before any new uploads in order to provide the PDGA community with semi-uninterrupted service and content.

That being said, since the hacking issue most likely was a major reason the site had to be transitioned quickly, a big thank you is in order for those of you who are volunteering to get the new site up while you try your hardest not to pull your hair out.

Looking forward to the completed version!

Why is the website still missing content? As someone who does IT project management and has done web application development and project management this type of "cutover" is absurd. Why wasn't the new website fully developed in a QA type environment and then just cutover on one night? Why is the PDGA website being hacked an issue? Are they hosting their own website? If so, that is bad form ... they aren't in the business of hosting and should outsource to a company that hosts and can manage security type of issues. I'm not trying bash here ... just providing some constructive feedback on how to handle future issues.



Our plan was to complete the new site before launching. During development, our existing site was hacked three times in a row. Each time, we spent hours getting the old site back online. The third time, we decided not to spend more time on restoring the old site, and to launch the incomplete new site. I take full responsibility for that decision, since I'm the one that pushed it. Feel free to let me know why you think I should have spent more of my volunteer time propping up a compromised server so that the web community wouldn't be exposed to an incomplete alternative.

-Theo

Feel free to let me know why you think I should be exposed.

-Theo



Ummm...