While the close queue is certainly one thing that can and will take care of the following question in either direction I wanted to make a meta post about the on-topic-ness of questions like this one.

Edison Ubilinux Flash Error "Cannot allocate memory of size 1610612736"

This is not an IoT question. Questions about basic usage of random development boards are not on topic here. IoT specific tasks on them might in some cases be, but the question being asked here is not IoT related at all, but rather a basic "how to use this board" question which should be pursued using board-specific resources. – Chris Stratton 10 hours ago

This is first time I have posted a question, first on one board who then told me to post here and it seems you guys are more concerned on removing the question then the real purpose of it which is to help people who come across the problem. I'm sorry but the Intel Edison is an IOT device and this is a real world issue people will come across and appreciate. The Internet of Things (IoT) refers to the ever-growing network of physical objects that feature an IP address for internet connectivity, and the communication that occurs between these objects and other Internet-enabled devices and system – theweekendcoder 4 hours ago

While the edison might be usable for IoT (do keep in mind it is an orphaned product), your specific question does not belong here, because your actual question is not about IoT. Each site in the stack exchange system is required to justify its existence by having and maintaining a unique theme. Indistinct scope like allowing general development board questions would imperil the continued existence of this beta site and make it unlikely to graduate to a full site in the system. – Chris Stratton 1 hour ago

We have tangled a bit with some other topics but in my view there's not a very strong meta consensus in either direction. References:

  • This seems to have become irrecoverably sidetracked into a debate about the Intel Edison board specifically. As a result, no sound general policy conclusion seems likely to be reached here. It would probably be best to delete this and re-post with a better example question - either a less IoT specific problem with an inarguably IoT device or program, or an inarguably IoT problem with a general purpose device. – Chris Stratton Jul 7 '17 at 15:06
  • @ChrisStratton the discussion has been moved to chat. – Helmar Jul 7 '17 at 17:20

This question is absolutely on-topic. I'm not sure if there are enough details for it to be answerable, so it might be unclear. But it is on-topic.

A question on this site doesn't have to be about “IoT specific tasks”. Whatever that means.

Rejecting a question about an Intel Edison just because the question doesn't involve the Internet (or whatever “IoT specific” means) would be like rejecting a question about romance in Star Wars on Science Fiction and Fantasy on the basis that romance is a distinct genre from SF, or rejecting a question about Bash on Unix & Linux on the basis that Bash runs natively on Windows 10. The Intel Edison is marketed as an IoT device, therefore any question about building it, setting it up, writing software for it, connecting to it, etc. is on-topic.

Generic questions that could be applied to any environment, in particular generic programming questions, may be off-topic. The point is, is this question relevant to IoT experts? For example, a generic C programming question is best answered by a C programmer, who may not be an IoT expert. A question about setting up a board is not generic. Every board is different. An expert on setting up an Edison board is, by definition, an expert on an aspect of IoT, so the question is firmly on-topic here.

The existence of other Stack Exchange sites is irrelevant to determining what is on-topic here. Please respect the community. Our site's topic isn't “IoT except for the parts that are covered elsewhere”.

This site tries to unite end-users and developers. This is proving to be difficult cohabitation. The preponderance of end-user questions, combined with rejecting development questions for insufficient IoTness, makes this site off-putting for developers. Maybe it would be best to redefine the scope of this site as being for end-users. (I would be personally uninterested in this new scope. I'm making this proposal because I'm finding so little of interest on this site as it is, even though my job description says “IoT”.)

  • Comments are not for extended discussion; this conversation has been moved to chat. – Helmar Jul 7 '17 at 17:19

Questions actually about IoT Use Cases are fine.

The problem is that the question linked is not an IoT use case. It's merely a generic problem with the Edison board, a very generic (not to mention discontinued) Embedded Computer that may be used for IoT purposes among many others. The only thing possibly IoT related about this question is that the poster might hypothetically be hoping to use the board for something IoT-ish after they figure out how to make it work at all - but that IoT aspect doesn't figure in the question actually asked at all.

If the question had actually been about an IoT use case, for example trying to get mosquitto-client to run on it or something like that, it would be on topic. Further, an actual IoT question like that is likely to have some degree of commonality to problems and solutions on other platforms which might be used for IoT - so unlike with the cited question, "IoT" actually would be the appropriate subject area.

But a generic question about making a general purpose embedded board "go" is not an IoT question - it's an embedded question or an Intel Edison question and needs to be moved to a site appropriate to those topics within the stack exchange system, or deleted and posted on an appropriate forum or vendor site outside of it.

Defining our purpose is not only essential to the development of IoT Stack Exchange as a legitimate site in the SE network, rejecting questions that do not belong here is a service to their askers because asking them in the appropriate places for their actual topic matter will yield better answers from the wider community of those with relevant expertise, not only the IoT afficanados found in this small community. And in looking to more appopriate sites, askers are also more likely to discover existing questions and resources which can resolve their issue without a need to post at all.

  • 3
    Even if I did agree about “IoT use cases” as a definition — which I don't, both because it's poorly defined and because I don't think use cases are relevant — that doesn't help. I think this question is about an IoT use case: it's about setting up an IoT board, not about setting up a generic board. This site cannot survive if we drive away all the experts about Edison, Arduino, etc. because their expertise is about a specific topic rather than about “IoT”. – Gilles 'SO- stop being evil' Jul 7 '17 at 10:47
  • 1
    @Gilles The Edison is not "an IoT" board. It's a general purpose embedded computer. That may be your fundamental error (and no, finding some piece of marketing material selling it for that purpose won't change the fact that it is not an IoT device until someone puts IoT software on it and uses it in an IoT application). The linked question was purely about the "general purpose-ness" of the Edison. – Chris Stratton Jul 7 '17 at 14:02

You must log in to answer this question.

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