I think you gave a perfect description of the status quo - and that's what i'd like to see improved:
answers are kind of buried in this 'back and forth'. That leads to the situation that some questions have to be answered over and over again.

I consider it a quality that stackoverflow enforces a certain discipline when asking questions and enforces separating them from wishes, opinions or discussions. That makes the answers much more useful and reduces the probability of having to deal with the same stuff again and again.

Many people are simply not aware that they are creating work for those who answer and simply throw their stuff onto the list without properly qualifying which versiont they are using, on which OS and so forth. stackoverflow is 'punishing' such behavior with the voting feature. I wish i could get back all the time i've answered silly requests on mailinglists (no offense to anyone specific).

Please consider:  those who answer are often also those that implement features or fix issues - wouldn't it be better that their time is effectively used?

There's nothing against using this list for the discussions and moving the questions to stackoverflow - i agree that exist-developer is rather hardly used.




On Tue, Jul 22, 2014 at 5:23 PM, Chris Tomlinson <chris.j.tomlinson@gmail.com> wrote:
I don't see much activity on exist-development. 

Discussions about new features - often related to performance - seem to often evolve by initial questions on exist-open that then morph into considerations of how to address an issue. 

A recent example is the discussion surrounding how to use the kwic feature w.r.t. some performance concerns. This evolved into a project to provide a native java implementation. 

I don't see such back-and-forth on stackoverflow and exist-development isn't used and doesn't provide an effective entry-point for many of these situations which arise from users simply asking how-to questions that expose some underlying issue. Wolfgang often identifies an opportunity for improvements and implements them in a timely manner. 

This sort of flow seems to be somewhat counter to stackoverflow policy I think.


On Jul 22, 2014, at 10:04 AM, Joern Turner <joern.turner@gmail.com> wrote:

we still have exist-development for discussions on features etc. Yes, i agree that stackoverflow is not the right place for that.

Actually we already have a co-existance of list and stackoverflow. A search revealed already about 36k of hits on stackoverflow. What i like about it is the presence of a search and the presentation of the results plus the fact that answers are easier to find, qualify and not deeply buried within threads. The tagging feature makes searches more effective as in google.

What i also like - and here we're probably coming to the point - is that in stackoverflow you're much closer to other technologies and existdb potentially gets exposed to developers not knowing it already. We have to think about ways and use every opportunity to grow the visibility of existdb if we want it to live and grow.

If we continue to run exist-open - which was actually meant mainly for questions - i fear we'll still get the majority of questions there and not in stackoverflow - doesn't make it easier for the people that actually answer questions.


On Tue, Jul 22, 2014 at 4:01 PM, Chris Tomlinson <chris.j.tomlinson@gmail.com> wrote:
Is stackoverflow a proper venue for discussing development issues, new features and so forth? 

I see it primarily as a place to get answers to how to use a tool or feature. 

A great place for how to use XQuery in eXist-db or how to configure triggers or security and so on.

It seems to me also that there's a place for the mailing lists as well as perhaps an increased use of stackoverflow.


On Jul 22, 2014, at 8:17 AM, W.S. Hager <wshager@gmail.com> wrote:

Either/or? I can see those co-eXist...


2014-07-22 15:03 GMT+02:00 Joern Turner <joern.turner@gmail.com>:
Hi *,

this might have been suggested earlier by others but i'd like to revive this debate:

wouldn't it be better to make stackoverflow our main forum and replace exist-open

stackoverflow is the de-facto google for developers. Everybody looking for an answer in technical questions will visit this site or quickly ending up there (coming via google).

The voting feature gives you some indication about the quality of answers (and questions) which a maling cannot offer.

Furthermore you always have to register to a mailinglist - a hurdle that is a bit counterproductive  and esp. if you are new to a product you'll hesitate to register for another inbox stuffing list that you probably don't want. IMO the hurdles to get an answer should be as low as possible.

Opinions?

Joern



------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Exist-open mailing list
Exist-open@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/exist-open




--

W.S. Hager
Lagua Web Solutions
http://lagua.nl

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds_______________________________________________
Exist-open mailing list
Exist-open@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/exist-open