Vanilla 1.1.9 is a product of Lussumo. More Information: Documentation, Community Support.
What CSiegel says might work for the moment. But from the longer perspective this is not enough. Eventually there should be another site for CS. Most universities think that math and CS are different, in fact different enough to make them into different departments. So as the number of stack exchange sites grows, one day there should be a CS site also.
Afterwards, there will be a natural overlap of questions between the math site and CS sites, which is fine, and which is exactly as things stand among published papers in the two subjects.
I don't think we should treat computer science differently from any other discipline to which mathematics can be applied (physics, biology, ...). We currently don't have much applied math on the site, but I'm all for encouraging it.
Of course, there's a continuum that runs from pure mathematics to hardcore computer science, with theoretical/mathematical computer science lying in between. There's no obvious place to draw the line. If we do manage to attract more applied mathematicians, we'll have to fine-tune our instincts as to which questions to allow or encourage and which to declare to be outside the site's remit. But that's OK; there have already been several issues on which the community's had to feel its way.
I don't really see a meaningful difference between CS theory and mathematics. MO currently doesn't have much in the way of algorithms and complexity theory, but I see no reason it shouldn't. It currently has even less of a differential equations community, but that's not because "pdes aren't really math" or anything silly like that. My understanding of computer science is that it is not a discipline to which mathematics can be applied, but a branch of mathematics which can be applied to computer programming. Lots of CS people are interested in other areas of math, and lots of mathematicians are interested in theoretical CS. In case I'm way off the mark, let me explain a bit about how I think SE-like communities should work.
There are two competing forces that we have to strike a balance between:
I think (2) is strong enough that we should shoot to be as inclusive as possible so long as we don't end up with a fragmented community. The situation we want to avoid is having two or more essentially non-interacting sub-communities on a single site. They would just annoy each other since they'd have to go to the trouble of filtering out what they want to see. The communities would be much better served by separate sites. Let me add a couple of clarifying points in anticipation of misinterpretation:
In the case of computer science, I think CS people should experiment. For questions related to programming (e.g. any question that involves a specific language), ask and answer them on SO. For theoretical questions that you could classify as research/graduate level, ask and answer them on MO. If it turns out that people at SO and MO are happy to have those questions and this covers most of your field, great! It means that you only have two websites to keep an eye on, you get the advantage of a large number of eyeballs, and you make SO and MO better. If it turns out that people at SO or MO don't like it, or that you have questions that don't really belong on either one, then it may be worth the hassle of creating and running CSOverflow.
1 to 9 of 9