Skip to main content
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

While its come up on metameta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

replaced http://superuser.com/ with https://superuser.com/
Source Link

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like thisthis, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

Fixup of bad MSO links to MSE links migration
Source Link

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

While its come up on meta before, I'm wondering if allowing companies to have 'Official' support accounts would be a good idea. Unlike SO, most of SU's scope is hardware (which is often a black box) and compiled software, which even if its open source, we're unlikely to tear apart and fix.

While I love that someone from the company is watching SU, and is attempting to help solve the situation, with situations like this, can we actually work out some way where these folks are recognised, and hopefully we'll have some way where solutions are fed back into the site from them?

Migration of MSO links to MSE links
Source Link
Loading
Tweeted twitter.com/#!/StackSuper_User/status/233928172691931136
restructured the sentence to read a little better.
Source Link
James Mertz
  • 26.5k
  • 3
  • 37
  • 76
Loading
Source Link
Journeyman Geek Mod
  • 132k
  • 2
  • 76
  • 165
Loading