There was recently a question on renaming files from bioacoustic recorders on the Beta. IMO this is a programming question and all such future questions too are better suited on another SE (e.g. on Stack Overflow). What are your thoughts on this matter?
The Sound Design site also overlaps sometimes with our "audio-signal-oriented" questions: https://sound.stackexchange.com/questions.
Maybe before asking a question that may overlaps with one of these other sites (Physics, Sound Design, Signal Processing, etc, depending on the question), we should check if it has not been already asked on one of these sites. If it is really bioacoustics-oriented, I think it should stays on our site even if has already been asked because we may answer it differently, however, if it is borderline, we should not include it (or downvote the question) or we should add at least a comment below the question "Related: https://blabalbla" with the link of the question that was asked in an other group.
I agree with a lot of what has been said so far. Some additional things to consider.
On-topic elsewhere vs off-topic here
Simply being on-topic on another site alone does not make a question off-topic on this one. I think that's true even if it has been asked elsewhere. It's a hard enough task to keep track of which questions have already been asked on this site. It'd be almost impossible to keep track of which questions have already been asked network-wide. So, while I agree that general programming questions that are not (clearly) related to bioacoustics should not be on-topic here, I don't believe that questions answered elsewhere or borderline should be excluded on this basis. (There are other closure reasons like "Needs Details or Clarity" and comments to explain that the question is not clearly about bioacoustics)
What kind of expertise is needed?
In general, when asking a questions, what is most important is:
- the type of expert are you looking for,
- the knowledge that expert needs to be able to answer the question, and
- if that expert will be able to find your question where you've asked it.
For example, if a programming question does not require domain specific knowledge, you are more likely to be able to receive an answer on Stack Overflow just due to the higher number of both programmers and users in general.
However, implementation questions specific to some bioacoustics problem may require an expert in this area, and that's where asking on Bioacoustics.SE makes more sense.
Beyond this, domain specific applications of known solutions can also have significant value for this community. Outlining how to use a known/generic programming solution (which may be a duplicate on another site) to solve a specific bioacoustics problem provides value to those searching for "how to solve X bioacoustics problem" instead of "how to write a program that does X".
Community Specific Closure Reason
After the beta phase, and after moderators are elected, two moderators can create (and activate) a new community specific reason. If general programming questions become an issue you may consider creating a reason that explains this.
Some similar existing closure reasons across the network are:
Your question should be specific to WordPress. Generic PHP/JS/SQL/HTML/CSS questions might be better asked at [so] or another appropriate Stack Exchange network site. Third party plugins and themes are off topic, they are better asked about at their developers' support routes.
Programming questions not specific to SharePoint are off-topic here, but can be asked on Stack Overflow.
Questions on programming, PHP, SQL, etc. that do not relate directly to Drupal are off-topic here, but can be asked on Stack Overflow.
Exact wording for this community and the other fields of the closure dialogue would need to be worked out, but this may be a good way to formalise the community standard once a consensus is reached.
How wide to cast the net? One could argue that bioacoustics is anyway very interdisciplinary, and in some sense the physics, psychoacoustics etc could all somehow go on other platforms.
However, it also seems like there is very little to be gained from language/package -specific answers with no bioac. content. Also another thing that speaks against having programming questions is the duplicated effort of Stack Overflow's focus area. I don't see a problem with code/answers having language/package specific content, but it should have something that the bioac community can gain from as a whole conceptually and scientifically too.