What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 128 Stack Exchange communities.

I yesterday asked how to achieve knowledge-transfer between developers on stackoverflow.com, but it was closed because it is "subjective". Because I am new to this platform I don't know all the secret rules to create a succesful question. And english is not my first language.

Afterwards I realized that not making it a community wiki could be the problem. Was that the problem? Or are there other flaws?

Should I repost it? Because I think it is unlikely that a closed question will be reopened.

share|improve this question
6  
No, don't repost it. –  random Jan 27 '10 at 8:23
1  
An interesting discussion would be whether it is ok to create one meta question for each closed question in SO. But I'll leave that for Meta Meta StackOverflow. –  Daniel Daranas Jan 27 '10 at 8:32
2  
It has been reopened now. –  Daniel Daranas Jan 27 '10 at 8:34
4  
@Daniel: Yes, it's a little bit like "Mama! Stevie closed my question!" -- "Stevie, give your little brother his question back!" -- "But Mama..." -- "No 'But Mama'! Go ahead and reopen it now!" -- "Yes Mama... stupid little brother " -- "What was that?" -- "Nothing, Mom. I'll be searching for dupes now." –  balpha Jan 27 '10 at 8:38
    
@balpha it is definitely a case of sour grapes, but we all do that when we're downvoted over something we consider reasonable. Though you have to love the irony of not knowing the answer to a question relating to knowledge transfer. –  Unsliced Jan 27 '10 at 8:41
    
I am sorry, I cannot delete this question. But I did not understand the reasons for closing my SO question. There was no comment about the closing reason. Also it was marked as "subjective and argumentative" what confused me. Besides that Meta SO has a special "support" tag, which looked like I am allowed to ask for closing reasons. –  Christian Jan 27 '10 at 8:48
2  
@Christian: It's absolutely okay that you asked this. We're just having a little fun here. Cheers! –  balpha Jan 27 '10 at 9:05
    
@Christian, CW is not 'intended' for subjective or 'one-answer-only' questions, but it's often used for that as a defense against those who close questions that they don't think they can get good information out of, or doesn't apply to their niche. Your question shouldn't have to be CW since it's asking for specific answers, but it should be closed because it's a duplicate of multiple other questions. –  Lance Roberts Jan 27 '10 at 16:36
    
And now it's closed as a duplicate. –  David Thornley Jan 27 '10 at 22:02
    
That's ridiculous. I could bet, you didn't even read those questions to the end which are to be duplicates. –  Christian Jan 28 '10 at 7:25
add comment

4 Answers 4

up vote 1 down vote accepted

My opinion: The question is fine. Yes, it's a candidate for "community wiki," because there's no real one-and-only answer, but now that you made it wiki, it's okay. I voted to reopen.

Closing this question as "subjective and argumentative" was wrong. The definition of this close reason is

It's impossible to objectively answer this question, and the question was asked in a confrontational, argumentative way.

The first part holds for your question, the second one definitely doesn't.

share|improve this answer
add comment

Afterwards I realized that not making it a community wiki could be the problem. Was that the problem?

I don't know. I think it's an interesting question. It is true that it is a typical community wiki question, but don't worry about that - it is already marked as community wiki.

Should I repost it? Because I think it is unlikely that a closed question will be reopened.

No, don't repost it. It has been reopened already. In any case, never post duplicates of your own closed questions.

share|improve this answer
add comment

Community wiki, yes. There's no finite answer to the question. But closure seems harsh - there are a lot of open questions regarding estimating tasks. Your question about knowledge transfer between developers seems just as appropriate.

share|improve this answer
    
+1: agreed. And not sure why this was downvoted... –  RSolberg Jan 27 '10 at 16:52
add comment

The actual title is "How to make developers learn from each other?". That sounds confrontational, at best, and may be why some people thought the question was argumentative.

I think it's a good question. I'm glad it's back open.

share|improve this answer
    
So, why was this answer downvoted? –  John Saunders Jan 27 '10 at 18:45
add comment

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .