Skip to main content
Tweeted twitter.com/#!/ServerFault/status/106205699201171457
pendant
Source Link
Zypher Mod
  • 37.7k
  • 18
  • 18

A lot of other sites are using blog.site.stackexchange.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so. This was the original intention of the blog when it was created:

You can expect to find blog posts there related to us documenting our own efforts of running and scaling our network of websites — the same sort of stuff you’ve come to expect from the server category on this blog. We want to actively give back to the community by documenting everything we’re doing on the sysadmin front — both by discussing it on the blog, and asking (and answering!) relevant questions about it on Server Fault whenever possible.

However, since other sites are taking a different direction, I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebecca's post.

A lot of other sites are using blog.site.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so. This was the original intention of the blog when it was created:

You can expect to find blog posts there related to us documenting our own efforts of running and scaling our network of websites — the same sort of stuff you’ve come to expect from the server category on this blog. We want to actively give back to the community by documenting everything we’re doing on the sysadmin front — both by discussing it on the blog, and asking (and answering!) relevant questions about it on Server Fault whenever possible.

However, since other sites are taking a different direction, I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebecca's post.

A lot of other sites are using blog.site.stackexchange.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so. This was the original intention of the blog when it was created:

You can expect to find blog posts there related to us documenting our own efforts of running and scaling our network of websites — the same sort of stuff you’ve come to expect from the server category on this blog. We want to actively give back to the community by documenting everything we’re doing on the sysadmin front — both by discussing it on the blog, and asking (and answering!) relevant questions about it on Server Fault whenever possible.

However, since other sites are taking a different direction, I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebecca's post.

added 676 characters in body
Source Link
Kyle Brandt
  • 85.1k
  • 19
  • 27

A lot of other sites are using blog.site.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so. This was the original intention of the blog when it was created:

You can expect to find blog posts there related to us documenting our own efforts of running and scaling our network of websites — the same sort of stuff you’ve come to expect from the server category on this blog. We want to actively give back to the community by documenting everything we’re doing on the sysadmin front — both by discussing it on the blog, and asking (and answering!) relevant questions about it on Server Fault whenever possible.

However, since other sites are taking a different direction, I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebbecca'sRebecca's post.

A lot of other sites are using blog.site.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so.

I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebbecca's post.

A lot of other sites are using blog.site.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so. This was the original intention of the blog when it was created:

You can expect to find blog posts there related to us documenting our own efforts of running and scaling our network of websites — the same sort of stuff you’ve come to expect from the server category on this blog. We want to actively give back to the community by documenting everything we’re doing on the sysadmin front — both by discussing it on the blog, and asking (and answering!) relevant questions about it on Server Fault whenever possible.

However, since other sites are taking a different direction, I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebecca's post.

Source Link
Kyle Brandt
  • 85.1k
  • 19
  • 27

Community Posts for Blog.SF?

A lot of other sites are using blog.site.com to create a blog on their topic with contributions from the community.

The Server Fault blog has mostly been posts from George and I about running these sites and our experiences and thoughts in doing so.

I'd be interested if the SF community would like to:

  1. keep the blog the way it is so it sort of tells the story our site
  2. keep it pretty much the way it is with the occasional guest post
  3. see blog.sf become primarily a community blog

Now, if people would really like to see #3, that would come with the requirement that several top users are interested in writing posts, taking the time review each others posts etc. For more on what would be involved see Rebbecca's post.