Question: Now that we have this network, I'm sure there'll be newbies coming in asking questions like,

> 
> How do I get started with Mozilla/KDE/etc?
> 
> 
> 

or

> 
> How do I start contributing to project xyz?
> 
> 
> 

I guess these questions would be very organisation specific, and would spam the network. Would these questions be relevant?

Answer: 
Over at [Programmers.SE](https://softwareengineering.stackexchange.com/), we have already discussed this and covered it in great depth:

* [Where to start?](https://softwareengineering.meta.stackexchange.com/q/6366/22815)
* [Green fields, blue skys, and the white board - what is too broad?](https://softwareengineering.meta.stackexchange.com/q/6961/22815)

The essence of the answers in the linked questions are that:

* Too broad. Good answers would be so long they lose focus and end up being worthless (the opposite of good).
* Unclear. Without enough details to narrow the problem down into something answerable in a reasonable amount of space, the problem statement is a bit fuzzy.

In the context of open source I think asking "which license is right for me given these goals?" would be fine, but the examples you posted are a bit broad and perhaps off-topic (if that is even well-defined in private beta).
These "where do I start" sort of questions will attract opinions and most likely spam (ex. You should start with this). They will be closed for a multitude of reasons. If people want to start and get support for a project, then they should go to the project's existing contributors, or owners.

If we get a bunch of "newbies" asking these sorts of questions, the site could adapt to create a specific reason for closure to send a message to provide well thought out questions if they still apply, or to go directly to the project itself.