Not signed in (Sign In)

Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.

  1.  
    I hardly ever use math.stackexchange, but I've used it a couple of times recently, and both times now I've thought "hey, this interface really _is_ better than MO isn't it". In particular the easy editing of comments. People here _still_ ask "can't we implement this great new idea I've had?" and the answer is usually "we can't implement anything at all" or sometimes even "it's been implemented in 2.0 but we don't have 2.0". And people also moan "my question was closed for a reason that I find incomprehensible" to which our answer is "we're stuck with a small finite list of reasons to close and the community now has an understanding of what these reasons mean, which is now a long way from what the phrase actually means". This looks amateurish (to me).

    When this was first talked about a year or so ago my initial reaction was "MO works fine, why change?" but now my feelings are "MO works fine except for just some slightly rough bits around the edges which are now beginning to annoy me a bit, so why don't we change?"

    Because a year or so ago I could see no reason for upgrading, I never bothered to listen to the other arguments that people had against upgrading. I wonder whether now is a good time for people to remind me what they were, because I have lost sight of them.
    • CommentAuthorNoah Snyder
    • CommentTimeApr 30th 2011 edited
     
    The main argument against upgrading is that so far we have not been given the option of upgrading in a way that doesn't cede ownership and long-term control of the site to SE Inc. Given the recent behavior of Jeff Atwood over at math.SE, I am not very excited about the possibility of them controlling the site.

    Also, keep in mind that SE wants their network to be uniform, so we wouldn't actually be able to change things like the list of reasons to close. We would get all the awesome new goodies that SE2.0 has, but we would not gain any abilities to fix problems in the way that we want them to be fixed. (For example, we wouldn't be allowed to change the closing system to allow votes to stay open.)
    • CommentAuthorgrp
    • CommentTimeApr 30th 2011
     

    I think Kevin should also be reminded of efforts to become independent by "rolling our own" version of the software. The names Scott Morrison and alpha.mathoverflow.net come to mind, but I may have them wrong. A simple search on meta.mathoverflow might turn the right names/discussions up.

    Gerhard "Ask Me About System Design" Paseman, 2011.04.30

  2.  
    Yeah, I think becoming independent is the way to go. However, I also think this should be done by us hiring someone, rather than by Scott working on it. (Because instead he should be writing papers with me!)
  3.  

    What happened to the idea of using OSQA?

    (As it's written in python, we could even get decent mathematics support. I've lost count of the number of times that MO and Maths-SX have stalled on me due to MathJaX.)

  4.  

    Probably I should let Anton handle this, since he knows the details, but my understanding is that we haven't been offered the opportunity to upgrade. Period. The ball is in SE's court, and I don't think they've served it.

  5.  
    Noah: thanks for the multitude of reasons. "rolling your own" is _always_ the best way to go, if you can be bothered and have the time/energy to write and maintain the software. I have little scripts which do silly things like "monitor a web page to see if it's changed, and if it does then send me an email" which are basically 6 line unix shell scripts, but I have friends who use custom software to do the same thing! I far prefer my way of doing things. On the other hand it would take a huge amount of effort to roll your own mathoverflow, and maintaining it would be much harder than the maintenance I have to do on my 6-line shell scripts...
  6.  

    I'd second Andrew Stacey's idea to revisit OSQA (although I'm very fond of MathJax). OSQA seems to have matured significantly over the last year.

    A colleague suggested http://kodingen.com, a very interesting young web development platform. I tried to get OSQA to run there, but my time and skills were not sufficient. Maybe somebody else has more luck.

  7.  

    @Ben: We were effectively offered the opportunity to migrate a while ago (in response to me bringing up the issue), but only by giving up access to the full database dumps. They're not very receptive to that condition, so in the long term we will probably migrate to another platform.

    In the short/medium term, it seems like the best/easiest option is to keep running on SE 1.0, but the longer term is definitely something we're thinking about. In the near future, Scott and I were planning to try to get a copy of OSQA running to get a better feel for how it's evolved since we last looked at it. There are still lots of things that need to be sorted out before there are any big changes, so don't hold your breath yet.

  8.  
    It might be interesting to talk to the folks at moms4mom http://meta.moms4mom.com/questions/206/what-changed-when-moms4mom-moved-hosting-providers-on-february-5th-2011 , another SE 1.0 site who has recently moved to OSQA. I imagine they know a lot about how to move between the systems.
  9.  
    Nice find, David. It looks like they've done a great job migrating.