emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Marvin Doyley <m.doyley@rochester.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: org in the wild update
Date: Sat, 8 Feb 2014 16:28:10 -0500	[thread overview]
Message-ID: <CAJ51ETrgMFO_+txN-CFNrqz-j4CPwTqi=5CykEY7U0JB8-RJzw@mail.gmail.com> (raw)
In-Reply-To: <159FF32B-4136-4B1C-80B5-C6B0916D7355@rochester.edu>

[-- Attachment #1: Type: text/plain, Size: 2911 bytes --]

This has been an ongoing process for the past 3 years that started with me
learning org-mode to manage my todo list.  Most of my students have taken
a  class with me, where they already had some familiarity with emacs, and
in which I use org-mode for the assignments. Some of them took to it like
fish in water. A few have not drunk the water, and are thirsty as a result
;) For track changes, I use git, and look at diffs when needed.

I have had to train my students to prepare simple documents, e.g. org
documents, that grow in sophistication over time.  I generally provide a
lot of support for this, through my blog (http://kitchingroup.cheme.cmu.edu),
and in meetings. I am certain my students are tired of hearing answers to
their questions that start with "I wrote a blog post that explains..." But
they probably realize they get faster and better feedback when they send me
org docs. I am working towards a set of emacs packages for my group that
will streamline manuscript preparation, and communication.

For file sharing there are two main approaches we use. 1) Part of my group
is computational and we all have accounts on a shared cluster. We share
some documents there. 2) PArt of my group does experimental research. We
use Dropbox too. I have a folder for each student that is shared with them.
Each student has an org-file that outlines their current research projects
and priorities. We use this document to guide our meetings. These documents
are on my agenda list so I know what should be done and by when. And the
students know it too. This is also how we coordinate manuscripts.

Manuscripts are a primary learning experience. Our supporting information
files are routinely 20-100 pages long now because I make my students put
comprehensive detail about what they did in them. Partly so I can be sure
of what they did, and partly for others to learn from.

So, it is still ongoing. The only alternative I am offering my group to
org-mode is LaTeX. They usually make a wise choice ;)




John

-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu



On Sat, Feb 8, 2014 at 7:12 AM, Marvin Doyley <m.doyley@rochester.edu>wrote:

> Hi John,
>
> Org have also revolutionized the way I work. I  use it for teaching
> (making slides, creating homework and exams),  presentation, and in a
> couple of weeks we will be submitting our first org generated manuscript.
> In general,  works great for me, but for the students and my assistant
>  that have been another story. I would be interested to learn how you (a)
> cultivated an org centered culture in your lab, and (b) established an org
> based research environment (i.e., file sharing, org equivalent of track
> changes, etc. ).
>
> Best Wishes,
>  M
>
>
> Sent from my iPad

[-- Attachment #2: Type: text/html, Size: 3549 bytes --]

  reply	other threads:[~2014-02-08 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 12:12 org in the wild update Marvin Doyley
2014-02-08 21:28 ` John Kitchin [this message]
2014-02-08 23:03   ` Marvin Doyley
  -- strict thread matches above, loose matches on Subject: below --
2014-02-06 21:45 John Kitchin

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='CAJ51ETrgMFO_+txN-CFNrqz-j4CPwTqi=5CykEY7U0JB8-RJzw@mail.gmail.com' \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=m.doyley@rochester.edu \
    /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).