emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode@gnu.org, Thomas Renkert <tunnelblick@quantentunnel.de>
Subject: Re: Suggestion: Stackoverflow for Orgmode
Date: Wed, 20 Jul 2011 10:39:20 -0500	[thread overview]
Message-ID: <CA+M2ft8sfe=t88bfKeayZ3Hhfu_aACvGwoajJ3KfxhvNqJJJTw@mail.gmail.com> (raw)
In-Reply-To: <CAGhLh6G3GYQSBt+mgRc29nXiY64mS8+xn_18xQK0rTfZ8arvAA@mail.gmail.com>

On Wed, Jul 20, 2011 at 8:53 AM, Rainer M Krug <r.m.krug@gmail.com> wrote:
>
>
> On Wed, Jul 20, 2011 at 2:13 PM, Thomas Renkert
> <tunnelblick@quantentunnel.de> wrote:
>>
>> Jambunathan K <kjambunathan <at> gmail.com> writes:
>>
>> >
>> > The biggest diasadvantage would be fragmentation of information.
>> >
>> > All information needs to have authoritative sources and archives. I
>> > believe the info manual, GNU mailing list and the Orgmode.org domain (of
>> > which Worg is but a part) are the right place for such archival
>> > references.
>>
>> Sure. But reading the manual from a to z or searching the mailing list for
>> the
>> right line of elisp is sometimes very slow if you need a quick solution. I
>> am by
>> no means suggesting that we should give up the established ways of
>> archiving
>> information or discussion, though.
>>
>> I simply think that something like "ask.orgmode.org" with a
>> stackexchange-like
>> interface could be very helpful for a larger portion of users.
>>
>> It may happen that redundant information is produced by this idea but I
>> think it
>> will make orgmode more usable and less intimidating for new users.
>> Something
>> similar has happened before: the orgguide was Carsten's solution for the
>> complex
>> 200+ pages of the original manual.
>>
>> Besides I find that useful information is already pretty much fragmented
>> across
>> the threads of this mailing list (there is also a lot of bugfixing,
>> regression
>> reports and feature request going on).
>>
>> Sure, the knowledge is there somewhere but it would be nice to see what
>> works
>> and what is useful without having to try everything for yourself.
>>
>>
>>
>> > I don't think anyone would object to having a secondary marketplace for
>> > trading of orgmode related tips and tricks.
>>
>>
>> My question is if anyone on this list would actively participate to get it
>> off
>> the ground. And I think that hosting it on the orgmode.org-server would
>> make a
>> lot of sense.
>>
>> Is somebody here interested in starting this?
>>
>>
>
> Not starting - but I think it is a really good idea.
> Nothing against worg (an absolutely fantastic resource) - but I consider the
> way that worg is edited as more static then a dynamic FAQ page, which this
> would result in if I understand correctly.
> I would definitely add to it. I agree that this should not replace any of
> the great resources of org, but it could supplement as a more dynamic format
> then worg, but more structured then a mailing list.


I'd definitely participate. I keep an "emacs" label in gmail with the
mailing list items where I've specifically had a question resolved. I
have to refer to them often. Sometimes my searches for the mailing
list exchange I *know* happened result in diddly because I just can't
remember the title of the email dialog. I think something like SE
would be fantastic, and in my opinion is a much more robust than
mailing lists *once the answer is determined.*

Mailing lists are great for hashing out discussions and getting
input... but I think a more concrete (but still modify-able)
repository would be better once a tangible outcome from the mailing
list has resulted.

Honestly, I don't see much difference than doing the same thing with a
wiki... but SE is infinitely more fun to contribute to. I could see
the benefit of SE's multiple answers format as well, since my
observation on the mailing list has often been that many users do
things differently.

I'd be open to starting this in Area51 if there is significant
interest. I don't think it's all that difficult and it's fairly
self-fulfilling; if users commit/participate... it launches. If not,
it won't.


John

> Cheers,
> Rainer
>
> --
> Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
> UCT), Dipl. Phys. (Germany)
>
> Centre of Excellence for Invasion Biology
> Stellenbosch University
> South Africa
>
> Tel :       +33 - (0)9 53 10 27 44
> Cell:       +33 - (0)6 85 62 59 98
> Fax (F):       +33 - (0)9 58 10 27 44
>
> Fax (D):    +49 - (0)3 21 21 25 22 44
>
> email:      Rainer@krugs.de
>
> Skype:      RMkrug
>
>

  parent reply	other threads:[~2011-07-20 15:39 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 [this message]
2011-07-20 13:45 ` Memnon Anon
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='CA+M2ft8sfe=t88bfKeayZ3Hhfu_aACvGwoajJ3KfxhvNqJJJTw@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=r.m.krug@gmail.com \
    --cc=tunnelblick@quantentunnel.de \
    /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).