emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Org Tutorials need more structure
Date: Sat, 28 Sep 2013 16:52:31 -0500	[thread overview]
Message-ID: <CA+M2ft8=4WtpFSOt=z3sVW6M=4h4bNioYWOEqgRG+jirxctr1A@mail.gmail.com> (raw)
In-Reply-To: <20130928233159.56203f9f@aga-netbook>

On Sat, Sep 28, 2013 at 4:31 PM, Marcin Borkowski <mbork@wmi.amu.edu.pl> wrote:
> Dnia 2013-09-28, o godz. 16:50:09
> Charles Millar <millarc@verizon.net> napisał(a):
>
>> On 9/28/2013 3:52 PM, Thomas S. Dye wrote:
>> > Aloha Carsten,
>> >
>> snip
>> > First, I think that most statements about "what Org-mode is" are
>> > outdated. Many of them are quite good, but they represent the
>> > previous state of an evolving system and so fail to capture the
>> > full scope. To my mind, Org-mode is a "research programming
>> > interface" written by and for scientists who take very seriously
>> > certain core values of the scientific enterprise--reproducibility,
>> > open access, and open source (a partial list).
>> Strongly disagree with the sentiment. My undergraduate degree may
>> gave been Physics, but I work as a freelance paralegal. I use Org
>> Mode for project (file) planning, scheduling, drafting documents,
>> etc. Also, I believe that there are some very active participants on
>> this list who are not scientists and have made great contributions.
>
> +1.  Although I'm also a scientist (mathematics), I used Org-mode /once/
> for science, and it turned out that I felt very much constrained and
> quickly got back to LaTeX, where I felt much more comfortable.
> http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
> Adam Mickiewicz University
>

This is starting to remind me of bike-shedding. Org-mode is a toolbox
providing various things that can work toward whatever end one wants.
It's agnostic to field. It doesn't really matter what the end uses are
-- Org-mode "is" what functions it provides. How those are combined by
others in various fields, lines of work, or so on are simply
illustrations of it's capabilities with respect to neat ways of
combining various aspects of what Org "is."

Thus, I wouldn't try to pitch these things one way or another ("Org is
great for paralegals" or "Org is the answer for those doing
re-producible research"); I'd simply list what it does as what is "is"
and what it can be used "for" as a way to entice new users and help
get into the top results of some google searches for
tools/solutions/etc..

It seems we all get what it really "is," (TODOs/agenda, universal
markdown -> export to tons of formats, allowing mixing of
prose/code/results, and so on), but are sort of trying to lay claim to
why these tools make it best suited toward some particular field.

Whether you use one of Org's features or all of them, it is what it is
and this can be highlighted in a neat manner and made appealing to
those looking for help in these relevant areas of life.


John

  reply	other threads:[~2013-09-28 21:52 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-28  6:11 Org Tutorials need more structure Carsten Dominik
2013-09-28  7:22 ` Joseph Vidal-Rosset
2013-09-28  8:37   ` Marcin Borkowski
2013-09-28 10:30   ` Suvayu Ali
2013-09-28 11:59     ` Joseph Vidal-Rosset
2013-09-28 12:36       ` Eric Schulte
2013-09-28 13:10         ` Joseph Vidal-Rosset
2013-09-28 16:02       ` Suvayu Ali
2013-09-28 17:19         ` Joseph Vidal-Rosset
2013-10-01  7:59       ` Eric S Fraga
2013-10-01 20:34     ` David Rogers
2013-10-01 21:00       ` Marcin Borkowski
2013-09-28  8:48 ` Marcin Borkowski
2013-09-28 10:09   ` Carsten Dominik
2013-09-28 14:26 ` Charles Millar
2013-09-28 16:35   ` Carsten Dominik
2013-09-28 17:14 ` Ian Barton
2013-09-28 17:43   ` Marcin Borkowski
2013-09-28 17:48     ` Carsten Dominik
2013-09-28 19:06 ` Ramon Diaz-Uriarte
2013-09-28 19:52 ` Thomas S. Dye
2013-09-28 20:50   ` Charles Millar
2013-09-28 21:31     ` Marcin Borkowski
2013-09-28 21:52       ` John Hendy [this message]
2013-09-28 23:14         ` Charles Millar
2013-09-28 23:29         ` Thomas S. Dye
2013-09-29  0:29           ` John Hendy
2013-09-29  7:28             ` Suvayu Ali
2013-09-30  8:04               ` Alan Schmitt
2013-09-30 17:01                 ` Eric S Fraga
2013-09-30 18:36                   ` Peter Neilson
2013-09-30 21:07                     ` Eduardo Ochs
2013-10-01  8:52                       ` Michael Brand
2013-10-01  5:34                   ` Suvayu Ali
2013-10-01  8:55                     ` Marcin Borkowski
2013-10-01 12:40                       ` Joseph Vidal-Rosset
2013-09-30 17:56               ` Thomas S. Dye
2013-09-29  8:44 ` Eric Abrahamsen
2013-09-29 15:31   ` Matt Price
2013-09-30  7:25     ` Eric Abrahamsen
2013-10-01 14:08 ` William Denton
2013-10-02  1:10 ` M
2013-10-02 18:06   ` Alan E. Davis
  -- strict thread matches above, loose matches on Subject: below --
2013-09-29 16:43 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='CA+M2ft8=4WtpFSOt=z3sVW6M=4h4bNioYWOEqgRG+jirxctr1A@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    /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).