Haha I was confused by your tweet, but I realize the title of the blog was confusing you. I now edited it to say
Drizzle.org *was* unavailable Perhaps you should delete that tweet and send a new one. henrik On Wed, Nov 9, 2011 at 12:38 AM, Kent Bozlinski <[email protected]> wrote: > The twitter sphere is taking notice as well, I am going to use henriks > suggestion and go ahead and do a fire control tweet. > > -----Original Message----- > From: > drizzle-advocacy-bounces+kent.bozlinski=datadifferential.com@lists.launchpad > .net > [mailto:drizzle-advocacy-bounces+kent.bozlinski=datadifferential.com@lists.l > aunchpad.net] On Behalf Of Henrik Ingo > Sent: Tuesday, November 08, 2011 2:16 PM > To: Drizzle Discuss; [email protected] > Subject: [Drizzle-advocacy] drizzle.org was unavailable today > > Hi all > > Patrick, someone, I think the following could also be posted to the Drizzle > blog. > > ***** > The entire drizzle.org domain was unavailable for about 10 hours today. This > made our website, documentation, jenkins master and mail server > inaccessible. On the other hand as we use public services such as Launchpad > and Freenode for code repository, bug tracking, mailing list and IRC, this > meant that development work continued as active as ever - in fact I think it > was the most active day on IRC #drizzle channel in a while! > > The DNS outage was related to our transferring of the drizzle.org domain > from an individual Drizzle developer to Software in the Public Interest, > Inc, our umbrella non-profit corporation. We don't know exactly why, but > something went wrong between the registrars, so that the Whois record listed > Tucows, the sponsoring registrar used by SPI, as the new registrar, but all > other information was still pointing to the old registrar, including some > Godaddy nameservers. As Godaddy eventually stopped answering DNS queries for > drizzle.org - as they should - the drizzle.org domain became unavailable. 10 > hours later the issue was fixed, and the correct SPI nameservers started to > propagate through the DNS system. At the time of this writing, everything > should have been working normally for some hours already. > > And yes, in related news, drizzle.org is now transfered to the ownership of > Software in the Public Interest. This is yet another step in our process of > becoming a solid non-profit community project, with fiscal services provided > by the SPI. So far the experience has been enjoyable and we've really felt a > warm welcome into the family of SPI hosted free and open source software > projects. > > On that note I'd like to thank Ganneff, Solver and Hydroxide from the #spi > channel for actively helping in troubleshooting and fixing the problem > today. > > > ***** > > -- > [email protected] > +358-40-8211286 skype: henrik.ingo irc: hingo > www.openlife.cc > > My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-advocacy > Post to : [email protected] > Unsubscribe : https://launchpad.net/~drizzle-advocacy > More help : https://help.launchpad.net/ListHelp > > -- [email protected] +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
