# Re: \[logstash-users\] Evaluating Moving to Discourse - Feedback Wanted
**URL:** https://discuss.elastic.co/t/re-logstash-users-evaluating-moving-to-discourse-feedback-wanted/23286
**Category:** Elasticsearch
**Created:** [April 17, 2015, 8:16am UTC](https://discuss.elastic.co/t/re-logstash-users-evaluating-moving-to-discourse-feedback-wanted/23286 "2015-04-17T08:16:19Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jmkgreen](https://discuss.elastic.co/u/jmkgreen)
#### Post date: [April 17, 2015, 8:16am UTC](https://discuss.elastic.co/t/re-logstash-users-evaluating-moving-to-discourse-feedback-wanted/23286/1 "2015-04-17T08:16:19Z")
What's the missing is a culture in which consumers put questions directly
into documentation for answering by the next person who reads it and knows
the answer.
Note that it's not good enough to implement an append-only authorship for
Q&As, the question and the answer need to feed back into a re-wording of
the original documentation.
Using plain text sources for documentation such as asciidoc within a simple
editing suite (github is just about good enough) lowers the barriers.
On 16 April 2015 at 09:28, Simon Lundström [simlu@su.se](mailto:simlu@su.se) wrote:
> On Tue, 2015-04-14 at 09:15:25 +0100, James Green wrote:
> […]
>
> > It was never intended to document software use, which is what support
> > lists
> > like this end up being used for. If I want to know how to do something or
> > what I might be doing wrong I'd prefer to place the question in precisely
> > the correct way and have it answered as part of the ongoing documentation
> > effort for others to read. This ongoing refinement of knowledge is what
> > ultimately drives forward adoption. A mailing list of far too fragmented
> > to
> > achieve this - wrong tool for the job.
>
> I don't think forums (and thus Discourse) is the solution for this
> either. StackOverflow et.al. is OK but it's not really a good medium
> IMO. The project should take ownership of their docs and discussions so
> they can be correct and not just guessing.
>
> Official documentation which can be contributed to (via PRs is OK for
> me) by the community is a better solution IMO. This demands a clear
> structure from the project where things are supposed to be (i.e.
> "reference documentation for plugin X" vs. "this is how I solved X" vs.
> "What's best practice for LS/ES/plugin X") so we don't get yet another
> messy place where noone can find anything and it's an exhausting and
> daunting experience to find (or add) anything.
>
> > However many times have we asked Google a question and come back with a
> > mailing list post four-five years old which appears to be on the money,
> > yet
> > the answer no longer appears to apply?
>
> I agree and even worse is when noone has answered it all and it's the
> only hit. Or my favourite: when your (generic and/or exact) search query
> yields no hits at all.
>
> BR,
>
> - Simon
>
> ## -- Remember: if a new user has a bad time, it's a bug in logstash.
>
> You received this message because you are subscribed to the Google Groups
> "logstash-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [logstash-users+unsubscribe@googlegroups.com](mailto:logstash-users+unsubscribe@googlegroups.com).
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Baz9e5duKcAMqCRuWy8ZhbhQW6q4QzNEdZXutrqUy22sJQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Baz9e5duKcAMqCRuWy8ZhbhQW6q4QzNEdZXutrqUy22sJQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@mingfai](https://discuss.elastic.co/u/mingfai)
#### Post date: [April 17, 2015, 9:20am UTC](https://discuss.elastic.co/t/re-logstash-users-evaluating-moving-to-discourse-feedback-wanted/23286/2 "2015-04-17T09:20:49Z")
hi,
Just want to give an example of open source project that use Discourse:
> **[Aerospike Community Forum](https://discuss.aerospike.com/)**
>
> This is a public forum for users to discuss questions around Aerospike, including installation, management, and application development.
NodeBB is probably the closely alternative to Discourse as a modern forum
software
regards,
mingfai
On Fri, Apr 17, 2015 at 4:16 PM, James Green [james.mk.green@gmail.com](mailto:james.mk.green@gmail.com)
wrote:
> What's the missing is a culture in which consumers put questions directly
> into documentation for answering by the next person who reads it and knows
> the answer.
>
> Note that it's not good enough to implement an append-only authorship for
> Q&As, the question and the answer need to feed back into a re-wording of
> the original documentation.
>
> Using plain text sources for documentation such as asciidoc within a
> simple editing suite (github is just about good enough) lowers the barriers.
>
> On 16 April 2015 at 09:28, Simon Lundström [simlu@su.se](mailto:simlu@su.se) wrote:
>
> > On Tue, 2015-04-14 at 09:15:25 +0100, James Green wrote:
> > […]
> >
> > > It was never intended to document software use, which is what support
> > > lists
> > > like this end up being used for. If I want to know how to do something
> > > or
> > > what I might be doing wrong I'd prefer to place the question in
> > > precisely
> > > the correct way and have it answered as part of the ongoing
> > > documentation
> > > effort for others to read. This ongoing refinement of knowledge is what
> > > ultimately drives forward adoption. A mailing list of far too
> > > fragmented to
> > > achieve this - wrong tool for the job.
> >
> > I don't think forums (and thus Discourse) is the solution for this
> > either. StackOverflow et.al. is OK but it's not really a good medium
> > IMO. The project should take ownership of their docs and discussions so
> > they can be correct and not just guessing.
> >
> > Official documentation which can be contributed to (via PRs is OK for
> > me) by the community is a better solution IMO. This demands a clear
> > structure from the project where things are supposed to be (i.e.
> > "reference documentation for plugin X" vs. "this is how I solved X" vs.
> > "What's best practice for LS/ES/plugin X") so we don't get yet another
> > messy place where noone can find anything and it's an exhausting and
> > daunting experience to find (or add) anything.
> >
> > > However many times have we asked Google a question and come back with a
> > > mailing list post four-five years old which appears to be on the money,
> > > yet
> > > the answer no longer appears to apply?
> >
> > I agree and even worse is when noone has answered it all and it's the
> > only hit. Or my favourite: when your (generic and/or exact) search query
> > yields no hits at all.
> >
> > BR,
> >
> > - Simon
> >
> > ## -- Remember: if a new user has a bad time, it's a bug in logstash.
> >
> > You received this message because you are subscribed to the Google Groups
> > "logstash-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to [logstash-users+unsubscribe@googlegroups.com](mailto:logstash-users+unsubscribe@googlegroups.com).
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
> To view this discussion on the web visit
> [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Baz9e5duKcAMqCRuWy8ZhbhQW6q4QzNEdZXutrqUy22sJQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Baz9e5duKcAMqCRuWy8ZhbhQW6q4QzNEdZXutrqUy22sJQ%40mail.gmail.com)
> [https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Baz9e5duKcAMqCRuWy8ZhbhQW6q4QzNEdZXutrqUy22sJQ%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAMH6%2Baz9e5duKcAMqCRuWy8ZhbhQW6q4QzNEdZXutrqUy22sJQ%40mail.gmail.com?utm_medium=email&utm_source=footer)
> .
>
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAMJPd-%3DCa9%2BKoj4ETXWepSmY6Y%3Dx%3DXh%2BNdgMXqJ0AytPN4Jv%2BQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAMJPd-%3DCa9%2BKoj4ETXWepSmY6Y%3Dx%3DXh%2BNdgMXqJ0AytPN4Jv%2BQ%40mail.gmail.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:19am UTC](https://discuss.elastic.co/t/re-logstash-users-evaluating-moving-to-discourse-feedback-wanted/23286/3 "2017-07-06T00:19:10Z")