emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: would take more than an org-mode strip-down.
Date: Wed, 28 Sep 2011 10:33:07 -0500	[thread overview]
Message-ID: <20110928153306.GS5718@x201> (raw)
In-Reply-To: <FC65329B-ADCA-4A93-98A0-29A5ED47CB0E@me.com>

On Wed, Sep 28, 2011 at 10:47:31AM -0400, James Levine wrote:
> I?ll go on leap of faith that the email I?ve been provided actually contributes to the same thread I emailed to earlier. Please everyone: thank you for looking out. This is clearly a thoughtful and supportive community. You can not deny, however, that even the design of this forum is but one example of how the Emacs community maintains its exclusivity. Own up to it. If there?s no problem, then don?t fix it. But for those who are following the statements on comparing org-mode to commercial substitutes like Taskpaper and see this as an outcome of people making less-informed choices, I hope I can keep your attention. Once I know which way to point my eyes, I promise I will fall in line. Please take a step back folks, there?s an implied objective that I?m making which I?ll state more explici
 tly:
>
> In order for org-mode to be attractive as an alternative to popular self-help like GTD, Covey and the market of task managers both digital and paper that exist, this community would need to take all this extensive documentation and package it. Do not confuse content with transparency. People don?t even read this much before electing their President. Should open-source software not concern itself with good bullet points? Does this imply that I?m not appreciative of the work?  There?s an opportunity cost with finding the time for even this thread, which I?m hoping we can agree should not be a barrier of entry for those who are simply interested in trying org-mode. As it stands, however, just trying org-mode takes lots of reading if just to install correctly. That?s all I?m saying.

Or you can watch a single 30 minute video:

http://vimeo.com/16533939

May be tooting my own horn, but I understand what you're saying. Org
isn't "prepackaged" nor does it come with documentation saying "here's
how you use me to accomplish X". Everyone tends to find their own
style of using the tools Org provides to manage information.

Good luck!

>
> Text is but one way that people learn. If you?re documenting sofware, it leans towards rational, logical, and linear thinking. Some people require a full-picture model first seeing things from many angles. Other?s prefer trial and error, and others, still, enjoy hypotheticals. People can adopt different strategies along the way. But to insist on only one method of learning and sharing, while being concerned that you?re not meeting a larger audience is tantamount to calling the rest of the class stupid, or simply a manner of dishonesty with one?s own motivations.
>
> Maybe what would be helpful is some bridge instruction: ?Graduating from Taskpaper: so you?re ready to try org-mode. What to expect:? I do find that if I have an orientation point, even if it wasn?t the best decision in the first place, I have a better reference as to the changes I would envision and what the value of future options would be.
>
> cheers
>
> James
> On Sep 28, 2011, at 10:18 AM, Jambunathan K wrote:
>
> James
>
> > Greetings,
> >
> > As an expert end-user but outside the computer science field, I?ve
> > felt there to be a high cost of entry for working in org-mode.
>
> This is another perfectly practical way to address the problem that you
> are contending to with.
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2011-04/msg00173.html
>
> Jambunathan K.
>
>
>


------------------------------------------------------------------
Russell Adams                            RLAdams@AdamsInfoServ.com

PGP Key ID:     0x1160DCB3           http://www.adamsinfoserv.com/

Fingerprint:    1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

  parent reply	other threads:[~2011-09-28 15:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27 17:04 would take more than an org-mode strip-down James Levine
2011-09-28  9:28 ` Jude DaShiell
2011-09-28  9:39 ` Eric S Fraga
2011-09-28 13:27 ` Jambunathan K
2011-09-28 14:18 ` Jambunathan K
2011-09-28 14:47   ` James Levine
2011-09-28 14:58     ` Jude DaShiell
2011-09-28 15:33     ` Russell Adams [this message]
2011-09-28 18:34     ` Rasmus
2011-09-28 14:54   ` James Levine
2011-09-30  6:00 ` Carsten Dominik
2011-09-30  9:38   ` Jambunathan K
2011-09-30 16:59   ` Thomas S. Dye
2011-10-04  0:13   ` suvayu ali
2011-10-03 20:44 ` Allen S. Rout
2011-10-04 13:28   ` Carson Chittom
  -- strict thread matches above, loose matches on Subject: below --
2011-09-29  7:46 Rustom Mody
2011-09-29  7:57 ` Rustom Mody
2011-09-29  8:01 ` Rainer M Krug
2011-10-04  6:33   ` Rustom Mody

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=20110928153306.GS5718@x201 \
    --to=rladams@adamsinfoserv.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).