To expand on this... We don't allow projects to host their code at places like sourceforge or github or anything. We don't allow projects to host their web sites off site at some other location. Basically, all "official" resources of a project should exist at Apache. If the blog is an "official resource", then it belongs at Apache.
Dan On Wed October 14 2009 1:13:56 am Niclas Hedhman wrote: > On Wed, Oct 14, 2009 at 4:42 AM, Alasdair Nottingham > > <[email protected]> wrote: > > In this inter connected world where community is commonly spread > > between services like blogger, facebook, twitter and so on I do not > > understand an argument that says that the community must be on one > > domain to succeed. > > What Bertrand is trying to say; BlogSpot may disappear overnight, > which leads to loss of data. We have no guarantees whatsoever that the > content will survive such event. If it is hosted on Apache > infrastructure we are sure that the content will survive as long as > Apache (hence the content) exist and is relevant. > > The question would really be; Does it matter if BlogSpot and our blog > disappears? If the answer is "Yes", then Apache infrastructure is the > answer, otherwise "Anywhere" is Ok. > > And I don't have a good the answer to that, hence not voting... > > > Another aspect is the "Eat your own dog food", and that we can very > easily work with both infrastructure and Apache Roller project to get > missing features in. > > > Cheers > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
