1

Is it okay to recommend using meta.stackoverflow.com as a support channel for stackapp I've written. For example, say I had been the person who wrote StackPrinter, on the bottom of the home page could I have something like:

If you have any questions about StackPrinter, please post them on meta.stackoverflow.com with the tag "stackprinter" for the quickest response. Otherwise you can email me

Would this be considered acceptable, or an abuse? Perhaps we need a support.stackapps.com stack-exchange site?

Improve this question
2
  • 1
    +1 You are the person who wrote StackPrinter? Really? Good job man :)! Your awesome app really deserve a big prizee.
    – systempuntoout
    Commented Jul 23, 2010 at 9:51
  • Nope, wasn't me. I was just using it as an example. That's why I phrased it above as "say I had been the person who wrote..."
    – Evan
    Commented Jul 23, 2010 at 12:07

5 Answers 5

Reset to default
4

No.

[app]s are not owned, or operated by Stack Overflow Internet Services, Inc.

meta.stackoverflow is for support, discussion, etc. focused on stackoverflow.com and the StackExchange family of sites.

Not for support of third-party products, like [app]s

Providing a means of reporting problems using an [app] is the responsibility of the [app] developer.

Improve this answer
1
  • Thanks Kevin. Good to have an official answer to the question on record.
    – Evan
    Commented Jul 23, 2010 at 6:52
2

Uh... I hate to plug my own stuff, but it directly applies.

Why not use StackList for this?

It has an integrated comment / bug management system... and you've already listed your app there.

Improve this answer
2
  • 4
    Since when do you hate to plug your own stuff? ;)
    – lfoust
    Commented Jul 23, 2010 at 6:12
  • Excellent idea. Plug away, George.
    – Evan
    Commented Jul 23, 2010 at 6:53
2

that was before stackapps.com existed. This is the place do discuss all things related to the API.

I guess I misread the question.

This is my take on it:

Users should not be coming to stackapps and posting [app] support questions, but the [app]/[library] announcement post is meant for those sorts of things. e.g. examples, docs, questions (in the form of an answer) comments, feedback etc etc. as we have all been doing with demonstrable benefit.

How many bugs/suggestions do we see simply mentioned in a comment only to have it fixed in short measure and for all to see.

Of course, an app should have an official home, but while we are all learning the in's and outs and announcing new work, this centralized location is a perfect place to communicate within our small cadre of devs for qualified and agile discourse.

On the announcement post of the code in question of course.

That's just my .2 pesos.

Improve this answer
1
  • stackapps is not for reporting problems with [app]s, its for announcing [app]s (and keeping those announcements up to date, etc.) and discussion about the API (including usage and future developments).
    – Kevin Montrose
    Commented Jul 23, 2010 at 3:11
1

I would just email the developer or post a question in their topic.

Improve this answer
1

Short answer: No. See here for the official response from SO staff, which is fair enough.

However George made the good suggestion that we use StackList that he developed for this. It is an integrated comments/reviews/bug reporting system for StackExchange related applications, so looks perfect for the task. Thanks George!

Improve this answer

You must log in to answer this question.

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