11

This site has a longstanding policy to close pre-release software questions as off topic.

Is there clear consensus to expand this to include:

  • "pre-release software and hardware"
  • "pre-release products and services"

We can edit the existing default close reason to be either of the above, but I would like to see if there are any downsides to either of these suggestions.

The current default close reason just refers to software

Questions about pre-release software are off-topic. For more information, see Are iOS 8 and OS X Yosemite questions OK? and Can I ask about not-yet-publicly released OS?.

  • Is there an example of what you want to close? – Mark Sep 12 '14 at 21:13
  • 1
  • 2
    @mark ... and people asking about ApplePay before it's baked. Same for Apple Watch, Family Sharing on iCloud, handoff for iOS 8 and Yosemite, etc... – bmike Sep 12 '14 at 22:11
  • Consider my up-vote of the question and @Mark's answer my support to broaden the pre-release ban notice. – Ian C. Sep 13 '14 at 3:12
  • Do you consider Golden Master to be released? – Rob Sep 13 '14 at 9:22
  • 1
    @Rob No - things can still change (in previous OSX the install differed) and if you have to agree to NDA then there will be a lack of people answering. Note the Xcode later beta releases are fully public so you do get answers see stack overflow - but many answers are now wrong as they changed – Mark Sep 13 '14 at 12:38
  • @bmike Why do you want to close them anyway? – arya Sep 14 '14 at 19:12
  • @arya see meta.apple.stackexchange.com/questions/1712/…. Basically a lot of these questions can't be answered without breaking the NDA (technically even mentioning simple things like including a screenshot or mentioning non-announced features breaks the NDA) – nohillside Sep 16 '14 at 9:01
  • @arya - I'll include an answer as to what / why we might extend the prohibition formally by editing the help center for the main site. – bmike Sep 30 '14 at 2:37
10

Yes it makes sense to increase the scope from just software to include hardware, products and services.

The important thing is that the answer should be able to quote some actual measurement or definitive statement that can be verified

  • Amen to focusing on the ability for people to provide actual / definitive answers. I used a lot more words in my answer, but this is my pick after hearing the comments and answers so far. – bmike Sep 30 '14 at 2:49
5

This is tricky because of the new open Betas that Apple are expanding into a wider audience. I am running Beta Yosemite, maybe next year they will do the same for iOS?

But, as a whole I think that if it's not released, it's not up for discussion. Anyone using these products for anything other than idle interest will know about the associated dev forums and know to use them properly. We do not want this place to be a discussion ground for the curious, so expanding (or perhaps more accurately just making it clearer by expanding the wording) the scope of our out of scope topics makes sense.

Make it as obvious as possible, and also include the old "including but not limited to" clause, to stop someone finding something we didn't explicitly list then complaining when we shut discussion down about it :)

1

Here are some reasons to prohibit pre-release questions for hardware and services.

Apple has currently announced the following services and hardware in Fall 2014 that is not available.

  • Apple Watch
  • Apple Pay
  • Home Kit

Even with iOS 8, Apple committed to shipping Health Kit apps on release day and that was changed at the last moment and the first 3 weeks of iOS 8 had no support for Health Kit. The Watch is committed to be released in Early 2015 (assuming that regulatory approval is granted). Apple Pay was committed in October 2014 and I don't have a good date for when Home Kit will arrive.

The reasons for prohibiting questions in general about pre-release software is to maintain the possibility to have high quality answers that don't enter into rumor, reading tea leaves, or over-parsing limited details that are released before the work to finish the product is done. Had we allowed Health Kit answers, we would have had incorrect information at launch as well as demonstrably poor answers to health kit questions until 8.0.2 and releases today September 29 allowed consumers to actually use the product.

The Stack Exchange sites are optimized to provide great answers by attracting knowledgable, expert people to address clearly worded questions. We even tolerate miserable questions when there is a demonstrated good answer or the possibility of a good answer to be provided.

With pre-release products that may or may not be covered with NDA - the pool of professional, capable, and knowledgable answers is severely limited. Furthermore, anyone that comes up with a good answer can probably be assumed to be breaking NDA. That environment fosters a "those who know aren't talking, those who are talking don't know" effect.

By widening the prohibition, it helps site moderators of all reputation levels to know that they should probably close most or all questions on pre-release software so that the site doesn't waste attention and discussion on un-answerable questions.

Once the product is released, all of the on-hold questions are easily reviewed and edited and reopened for all of the well worded questions.

I have seen these patterns as a user of the site as well as one of the elected moderators since day one. By following the same spirit of discouraging all but the most answerable and helpful questions on pre-release software - we would have consistency by prohibiting all but the most answerable questions about pre-release hardware and services.

My vote is to edit the [help] to broaden the prohibition on pre-release to cover hardware and services.

You must log in to answer this question.

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