2 added 1322 characters in body
source | link

I'm not entirely convinced that Raspberry Pi actually fits that well within "embedded programming." It's more like a PC than it is an embedded system (though, admittedly it shares some attributes of both).

Also, I'm pretty sure sites in beta don't generally get merged into sites currently in definition phase. A site that is gaining success on its own probably should not be used to prop up a site that hasn't been started. If the embedded system site is worthwhile, it will stand up on its own--that's sort of the way this process works.

Additionally, you missed some really important parts of the text you quoted:

In general, if a site makes sense as part of a bigger site, it's better to have one big site than a bunch of little niche sites. Site X should be subsumed by site Y if:

  1. Almost all X questions are on-topic for site Y
  2. If Y already exists, it already has a tag for X, and nobody is complaining
  3. You're not creating such a big group that you don't have enough experts to answer all possible questions
  4. There's a high probability that users of site Y would enjoy seeing the occasional question about X

In this situation, the Raspberry Pi site is further along than the proposal. You treating Raspberry Pi as Site X, when it's actually Site Y.

The fact of the matter is, there exists a community of Raspberry Pi SE users who probably would not find a site centered around Embedded Systems with the "occasional" Raspberry Pi question very useful.

In fact, there's a reason we worked so hard to end up with our own site and community. We followed (and are continuing to follow) the proper process and did not build this site on cannibalizing other ones. If Embedded Systems launches and does significantly better than Raspberry Pi, then and only then is this a proper discussion.

I'm not entirely convinced that Raspberry Pi actually fits that well within "embedded programming." It's more like a PC than it is an embedded system.

Also, I'm pretty sure sites in beta don't generally get merged into sites currently in definition phase. A site that is gaining success on its own probably should not be used to prop up a site that hasn't been started. If the embedded system site is worthwhile, it will stand up on its own--that's sort of the way this process works.

I'm not entirely convinced that Raspberry Pi actually fits that well within "embedded programming." It's more like a PC than it is an embedded system (though, admittedly it shares some attributes of both).

Also, I'm pretty sure sites in beta don't generally get merged into sites currently in definition phase. A site that is gaining success on its own probably should not be used to prop up a site that hasn't been started. If the embedded system site is worthwhile, it will stand up on its own--that's sort of the way this process works.

Additionally, you missed some really important parts of the text you quoted:

In general, if a site makes sense as part of a bigger site, it's better to have one big site than a bunch of little niche sites. Site X should be subsumed by site Y if:

  1. Almost all X questions are on-topic for site Y
  2. If Y already exists, it already has a tag for X, and nobody is complaining
  3. You're not creating such a big group that you don't have enough experts to answer all possible questions
  4. There's a high probability that users of site Y would enjoy seeing the occasional question about X

In this situation, the Raspberry Pi site is further along than the proposal. You treating Raspberry Pi as Site X, when it's actually Site Y.

The fact of the matter is, there exists a community of Raspberry Pi SE users who probably would not find a site centered around Embedded Systems with the "occasional" Raspberry Pi question very useful.

In fact, there's a reason we worked so hard to end up with our own site and community. We followed (and are continuing to follow) the proper process and did not build this site on cannibalizing other ones. If Embedded Systems launches and does significantly better than Raspberry Pi, then and only then is this a proper discussion.

1
source | link

I'm not entirely convinced that Raspberry Pi actually fits that well within "embedded programming." It's more like a PC than it is an embedded system.

Also, I'm pretty sure sites in beta don't generally get merged into sites currently in definition phase. A site that is gaining success on its own probably should not be used to prop up a site that hasn't been started. If the embedded system site is worthwhile, it will stand up on its own--that's sort of the way this process works.