"ubuntu+1" is the developmental release of Ubuntu, so it changes every day so it can cause people to have lots of problems and ask for help. So for example people asking 11.04 (aka natty) questions months before the release, etc.

I think a bunch of us agreed in chat on how we handle these kind questions but we never actually posted here.

share
    
for the record, i noticed a bunch of new threads popping up for ubuntu+1 (Oneiric at the time of this comment), and I asked @Stefano to tag this as featured so its tacked to the main page. In reality, it probly should be FAQ, but new posters need to be able to see this thread (hence its ressurection to the top of meta at this time) –  Thomas W. Jul 7 '11 at 17:50
add comment

3 Answers

Since it would be a waste of time cleaning up most of this stuff since it's too localized here are my proposals.

Shouldn't be allowed:

Should be allowed:

share
2  
"How safe is it to upgrade at the moment?" I agree is localized, but it is possible to answer "how safe is it to upgrade to alpha1/2/beta etc". –  poolie Aug 5 '11 at 6:11
1  
This needs clarification on when questions about upcoming features are allowable. –  WarriorIng64 Nov 15 '11 at 20:35
2  
@WarriorIng64 See Oli's answer. –  Jorge Castro Nov 15 '11 at 20:43
add comment

Almost all Natty threads I've seen so far fell into one of these categories:

  1. "Will natty/unity/other-new-feature do X"

    I despise speculative threads. Not only can I not answer them but often only the person driving the project can. I don't really see a difference between this and a feature request, even if the question is levelled directly against the whole distribution.

    These should live on Brainstorm or Launchpad, filed under the specific project. If we can get people into that mentality, they'll see the current feature requests and targets before they ask, saving people triage time. That's the point of doing all this in the open, right?

    I'm all for shooting these threads down as off-topic the instant they appear but I've seen enough of bug trackers to know that just hiding the issue just means the next person will ask... Repeating this process and expecting people to figure it out is, I believe, the very definition of insanity.

    As a compromise, perhaps just keeping one master thread for each topic and being a lot more diligent getting things marked as duplicates. At the moment a sub-3k user might comment that it's a dupe but that doesn't stop five people piling in with duplicate answers.

  2. "I just upgraded and I my screen doesn't work" aka bugs

    We're not a bug tracker. To try and be one is hugely unfair on the developers. We need to push people to Launchpad (and upstream where applicable) so that proper bugs are filed.

    Similar logic applies though. If we close down a popular bug topic that affects a lot of natty users, we'll just spawn dozens of duplicates.

    Of course to help people we need to push people to the right place. Instead of just punching them off to Launchpad we send them to the exact bug (and then close as off-topic).

  3. "How do I upgrade to Natty?" and other direct process questions

    I'm warmer to these as they usually have lasting value but they're just as prone to duplicates as other hot topics.

    There's also a technical protectionism argument to make. If a user has to ask how to upgrade (and the upgrades function as documented), they've already demonstrated an inability or unwillingness to help themselves. On pre-release software the will and skill to Google your way out of an issue is as important as knowing how to file a bug.

    I know we're not doctors or lawyers but I feel we should show some professionalism and part of that is knowing when not to give advice.

share
    
We need to push people to Launchpad - I'm just going to say that just telling them "please file a bug", is likely to lead to a lot of low-quality duplicative bugs, repeating the same problem within Launchpad or elsewhere. But I suppose that's thrashed out here. –  poolie Jun 18 '13 at 7:39
add comment

In addition to the above considerations, I would suggest allowing ubutnu +1 as on topic with some concrete milestone, with the release of the RC or beta 2 ?

Sort of depends on when, in general, ubuntu +1 is both stable enough and in use enough such that closing all the threads becomes too burdensome and / or appears unwelcoming.

share
2  
We're kind of already doing that now but yeah, we should explicitly state when that is, so far we've been doing it by "feel". –  Jorge Castro Mar 7 '12 at 1:26
add comment

You must log in to answer this question.

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