I've been using the new auto keyword available in the C++0x standard for complicated templated types which is what I believe it was designed for. But I'm also using it for things like:
auto foo = std::make_shared<Foo>();
And more skeptically for:
auto foo = bla(); // where bla() return ...
There is a way to "undo" a migration. I'd have to ping an SO mod and see what's what. That said, I'm not sure that it was a bad migration. Seems like one of those grey area questions to me.
Oh, and you can always flag a post for moderator attention in these cases and we'll take a look. :)
@AnnaLear the thing is that it's certainly a "gray area". And I was trying to find a way to signal that I think this "gray" should be resolved as "migrate back to SO". However, I'd like to ensure that there are 4 more people who think like that (so that the cannonical 5 people voting for a question to be moved is adhered)
@whatsisname This "news feed" is a cool reminder that we actually gathered here not to jabber, but to answer questions ;-)
@PavelShved One way to do that would be to post on meta and/or comment on the question. Either way, this is something that will eventually should be resolved by a moderator. I believe the question can still gather "migrate to SO" votes, but I don't know what the implications of migrating back would be.
@PavelShved I know we're discouraged from migrating the same question twice in general, but I don't know the technical details behind that or what would happen if a question was migrated back to its source site that way.
A new blog post was made on the Stack Overflow blog. Unfortunately, I'm moving next week and starting a new job about a week after that, so I'm just trying to poke around the idea until I get settled into my new place and get Internet accesss.
It's the fact of how it works. See, I mostly use Stack Overflow and Programmers. I know what questions belong on those sites, but I don't know what belongs on other sites.
Migration shouldn't be handled by users who don't know how the other sites work.
But instead be a process of saying "this is a good question, but it doesn't belong in this community" and then another community accepting it.
@ThomasOwens Migrations to other sites are pretty rare, far as I know. Every site gets at most 5 default migration paths and on many sites they don't even have any set up beyond a path to their own meta.
@ThomasOwens All other migrations are done by flagging for a moderator and moderators are expected to either know or ask mods on the target site if the question is suitable.
Yeah. I don't like the migration paths thing, other than between the site and meta, honestly. Mods that aren't part of the other community are better, since they are mods and have some authority to make the call.
But I think it should be something like a flag on X -> a mod on X saying "I think it belongs on Y" -> a mod on Y saying "yes, this belongs here" or "no, this belongs on Z" or "there is no place for this"
It would be slower, but I think it would improve the quality of questions. I'm seeing a lot more questions on programmers that, IMO, don't belong. And questions on Stack Overflow that I think belong somewhere else but I can't say for sure because I'm not a member of that community.
@ThomasOwens That's been brought up on meta.SO many times from various angles. The argument against it is along the lines of "we don't want to put questions in limbo until a moderator gets around to reviewing the pending migrations"
Although my favourite idea was for moderators to be able to view questions with votes to migrate to their site before the migration happened and have the opportunity to reject it at that point. So, no question HAS to be approved, but a question can be rejected.
Is it possible to add a tool that shows mods all posts on the network that have at least one vote to migrate to their site? For example, a page SO moderators can see that shows all posts on the network where at least one person has cast a "belongs on Stack Overflow" vote. In this mockup, there ar...
There's only one problem. On a high-traffic site (like Stack Overflow), the can get the 5 votes to migrate before a moderator on a low-traffic site can say yes/no.
I almost think that there's no good solution to this problem, simply because of the human/community factor. No human is infallible and no individual can understand another community.
I think in general it's not too bad. Sometimes we get bad questions migrated to us, but it's pretty easy to close them. Sometimes they just need a bit of editing help. Sometimes they're good as they are. It was worse when SO first got the migration path set up, but I think it evened out since then.
There's a page available to moderators that shows questions recently migrated to the site. I don't get to it a lot, but we can at least theoretically review questions coming in.
Correction: that's available in the mod tools for 10k+ users as well.
I've been using the new auto keyword available in the C++0x standard for complicated templated types which is what I believe it was designed for. But I'm also using it for things like:
auto foo = std::make_shared<Foo>();
And more skeptically for:
auto foo = bla(); // where bla() return ...
The Whiteboard
The Whiteboard