Skip to main content
replaced http://blog.stackoverflow.com with https://blog.stackoverflow.com
Source Link

I really applaud your recent announcement to have per-site Metasper-site Metas from now on for Super User and Server Fault too, as well as migrating lots of questions from here over there accordingly already.

I really applaud your recent announcement to have per-site Metas from now on for Super User and Server Fault too, as well as migrating lots of questions from here over there accordingly already.

I really applaud your recent announcement to have per-site Metas from now on for Super User and Server Fault too, as well as migrating lots of questions from here over there accordingly already.

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

Well, I'm going to bed now and hope my morning coffee will be strong enough for the outcome of this instant questioning into the most recent decision of the Stack Exchange PantheonStack Exchange Pantheon ;)

Well, I'm going to bed now and hope my morning coffee will be strong enough for the outcome of this instant questioning into the most recent decision of the Stack Exchange Pantheon ;)

Well, I'm going to bed now and hope my morning coffee will be strong enough for the outcome of this instant questioning into the most recent decision of the Stack Exchange Pantheon ;)

replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
Source Link

It looks like this is finally getting addressed (see The future of meta.stackoverflow and meta.stackexchangeThe future of meta.stackoverflow and meta.stackexchange) - I'm quite happy that Jeff has reconsidered this indeed as envisioned in his answerhis answer back in July 2010, and will accept it accordingly, once the decision is final, i.e. the discussion has settled a bit :)

While analyzing the count of remaining questions tagged superuser (67 vs. ~295 migrated), serverfault (69 vs. ~110 migrated) or stackoverflow (1517 vs. 12873 total) I just found the question Will the StackExchange meta site behaviour be backported to the trilogy?Will the StackExchange meta site behaviour be backported to the trilogy?, and Robert Cartainos answerRobert Cartainos answer at least touches part of the topic regarding naming implications when referring to Stack Overflow Inc. vs. Stack Exchange Network/sites.

While this backs my assumption of the subject matter being decided finally for somewhat personal reasons already (though the phrase For now implies here's hoping ;) I'll still keep the question and arguments below as they are addressing the topic in particular and from a different angle after Jeffs considerationsJeffs considerations have fortunately materialized for Server Fault and Super User at least.

  • As outlined already you will gain a consistent Meta experience within the Stack Exchange Network from now on for all future users.
  • You will gain consistency with your section Proper Use of the Stack Overflow and Stack Exchange Name as outlined on the legal pages:
  • You'll have Stack Exchange [network|sites|API] and, a perfect match, a dedicated standalone community with a standalone reputation system for all things meta regarding these entities.
  • The poor homeless posts living on meta.stackexchange.com right now would finally find a new home, where they will be most welcome and just feel, well, at home ;)
    [I realize there might be some issues for sites staying on Stack Exchange 1.0 eventually though]
  • The diamond moderator shoot-outdiamond moderator shoot-out regarding Proper location of Meta questionsProper location of Meta questions might be easier to resolve as well in the long run ;)

It looks like this is finally getting addressed (see The future of meta.stackoverflow and meta.stackexchange) - I'm quite happy that Jeff has reconsidered this indeed as envisioned in his answer back in July 2010, and will accept it accordingly, once the decision is final, i.e. the discussion has settled a bit :)

While analyzing the count of remaining questions tagged superuser (67 vs. ~295 migrated), serverfault (69 vs. ~110 migrated) or stackoverflow (1517 vs. 12873 total) I just found the question Will the StackExchange meta site behaviour be backported to the trilogy?, and Robert Cartainos answer at least touches part of the topic regarding naming implications when referring to Stack Overflow Inc. vs. Stack Exchange Network/sites.

While this backs my assumption of the subject matter being decided finally for somewhat personal reasons already (though the phrase For now implies here's hoping ;) I'll still keep the question and arguments below as they are addressing the topic in particular and from a different angle after Jeffs considerations have fortunately materialized for Server Fault and Super User at least.

  • As outlined already you will gain a consistent Meta experience within the Stack Exchange Network from now on for all future users.
  • You will gain consistency with your section Proper Use of the Stack Overflow and Stack Exchange Name as outlined on the legal pages:
  • You'll have Stack Exchange [network|sites|API] and, a perfect match, a dedicated standalone community with a standalone reputation system for all things meta regarding these entities.
  • The poor homeless posts living on meta.stackexchange.com right now would finally find a new home, where they will be most welcome and just feel, well, at home ;)
    [I realize there might be some issues for sites staying on Stack Exchange 1.0 eventually though]
  • The diamond moderator shoot-out regarding Proper location of Meta questions might be easier to resolve as well in the long run ;)

It looks like this is finally getting addressed (see The future of meta.stackoverflow and meta.stackexchange) - I'm quite happy that Jeff has reconsidered this indeed as envisioned in his answer back in July 2010, and will accept it accordingly, once the decision is final, i.e. the discussion has settled a bit :)

While analyzing the count of remaining questions tagged superuser (67 vs. ~295 migrated), serverfault (69 vs. ~110 migrated) or stackoverflow (1517 vs. 12873 total) I just found the question Will the StackExchange meta site behaviour be backported to the trilogy?, and Robert Cartainos answer at least touches part of the topic regarding naming implications when referring to Stack Overflow Inc. vs. Stack Exchange Network/sites.

While this backs my assumption of the subject matter being decided finally for somewhat personal reasons already (though the phrase For now implies here's hoping ;) I'll still keep the question and arguments below as they are addressing the topic in particular and from a different angle after Jeffs considerations have fortunately materialized for Server Fault and Super User at least.

  • As outlined already you will gain a consistent Meta experience within the Stack Exchange Network from now on for all future users.
  • You will gain consistency with your section Proper Use of the Stack Overflow and Stack Exchange Name as outlined on the legal pages:
  • You'll have Stack Exchange [network|sites|API] and, a perfect match, a dedicated standalone community with a standalone reputation system for all things meta regarding these entities.
  • The poor homeless posts living on meta.stackexchange.com right now would finally find a new home, where they will be most welcome and just feel, well, at home ;)
    [I realize there might be some issues for sites staying on Stack Exchange 1.0 eventually though]
  • The diamond moderator shoot-out regarding Proper location of Meta questions might be easier to resolve as well in the long run ;)
replaced http://meta.stackoverflow.com/ with https://meta.stackoverflow.com/
Source Link
Loading
Post Closed as "Duplicate" by Shadow Wizard discussion
edited tags
Link
Adam Lear StaffMod
  • 160.1k
  • 45
  • 501
  • 690
Loading
Fixup of bad MSO links to MSE links migration
Source Link
Loading
Migration of MSO links to MSE links
Source Link
Loading
Updated regarding state of affairs with meanwhile proposed split.
Source Link
Steffen Opel
  • 2.2k
  • 17
  • 23
Loading
Given the distinct functionality of per-site-meta vs. meta-meta this has definitely meant to be a feature-request, albeit one suspected to be discussed extensively first; admittedly tag discussion is redundant in this regard though ;)
Link
Steffen Opel
  • 2.2k
  • 17
  • 23
Loading
This does not sound like a feaure request. Why should it be tagged "discussion" otherwise?
Link
Ladybug Killer
  • 17.1k
  • 4
  • 43
  • 65
Loading
edited tags
Link
Steffen Opel
  • 2.2k
  • 17
  • 23
Loading
Fixed typos.; edited body
Source Link
Steffen Opel
  • 2.2k
  • 17
  • 23
Loading
Updated with question statistics and a discovered related question.
Source Link
Steffen Opel
  • 2.2k
  • 17
  • 23
Loading
Source Link
Steffen Opel
  • 2.2k
  • 17
  • 23
Loading