emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Suggestion: Stackoverflow for Orgmode
Date: Wed, 20 Jul 2011 13:45:03 +0000 (UTC)	[thread overview]
Message-ID: <87sjq1f5ou.fsf@mean.albasani.net> (raw)
In-Reply-To: loom.20110720T093138-957@post.gmane.org

Thomas Renkert <tunnelblick@quantentunnel.de> writes:

> I noticed that - as more people with a diverse range of background knowledge
> start to use orgmode - the mailing list is getting more and more difficult to
> navigate: 

I do agree that the volume of mails did considerably increase.

> a lot of threads are long and winding and many of the posts are basic
> questions from beginners and questions about special use cases or scenarios from
> more experienced users. 

At this point, however, I have a different impression.
Yes, there are some long threads, but those seem to be rarley those
interesting for new users while setting up their orgworld.
Those threads are *imho* usually about new features that need
discussion, clarification etc.: a ping pong of ideas.
When subareas emerge, tags like [BABEL] or now [CALFW] make it easy to
parse them out if you are not interested. 

OTOH, I am used to dealing with mailing lists and I find them very
convenient. Others may very well have a different impression.
Is this worth a poll in a new thread?

> An idea:
> Many of you may be familiar with the Q&A-Sites www.stackoverflow.com or
> www.superuser.com. 

There are already some questions about org on stackoverflow, if people
are interested in this format, they can already go there. Setting this
up seems overkill to me, especially, because we have Worg to collect
the nuggets of all threads. If newcomers find the volume on this list 
overwhelming, I think splitting it into a -dev and a -user list would 
be the next logical step, first.

However, I am not opposed to this idea when others agree it would be
usefull. I can't really see myself using it so far, but that may very
well change. 

Memnon

  parent reply	other threads:[~2011-07-20 13:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  8:10 Suggestion: Stackoverflow for Orgmode Thomas Renkert
2011-07-20  9:44 ` Jambunathan K
2011-07-20 12:13   ` Thomas Renkert
2011-07-20 13:53     ` Rainer M Krug
2011-07-20 15:32       ` A. Ryan Reynolds
2011-07-20 15:39       ` John Hendy
2011-07-20 13:45 ` Memnon Anon [this message]
2011-07-20 16:02   ` Rehan Iftikhar
2011-07-20 21:37     ` Wes Hardaker
2011-07-21  9:51 ` Bastien
2011-07-21 10:59   ` Thomas Renkert
2011-07-21 13:58   ` Jason Dunsmore
2011-07-21 14:15     ` suvayu ali
2011-07-21 14:27       ` John Hendy
2011-07-22  9:38       ` Bastien
2011-07-22 12:23         ` Bastien
2011-07-22 12:31           ` Rainer M Krug
2011-07-22 13:27             ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sjq1f5ou.fsf@mean.albasani.net \
    --to=gegendosenfleisch@googlemail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).