Re: [O] editing The compact Org-Mode Guide
Evan Misshula evanmissh...@gmail.com writes: Thanks for the instructions on how to play nice in the sandbox. We noobs are always afraid we are going to cause more work than we fix. We are all n00bs! Somehow. -- Bastien
[O] editing The compact Org-Mode Guide
I started reading orgguide.pdf, Release 7.9.3e and came across a couple of grammatical errors right away. I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. Please provide me with instructions on downloading the source, and after I finish editing, uploading the diffs or updated version. Thank you. Best, Greg Benjamin
Re: [O] editing The compact Org-Mode Guide
Aloha Greg, Gregory Benjamin gr...@laserlab.com writes: I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. The source is /path/to/org-mode/doc/orgguide.texi There is a file in that directory called Documentation_Standards.org, which contains what the file name advertises. Please provide me with instructions on downloading the source, and after I finish editing, uploading the diffs or updated version. Assuming you are using the git version of Org mode, you should create a new branch, check it out, and edit orgguide.texi there. When you are happy with your edits, stage and commit them in the git repository. Once the edits have been committed, you can make a patch like this: git format-patch -o ~/temp/ HEAD~1 where ~/temp/ is what I use and might not be appropriate for your setup, so should be changed accordingly. You should read the instructions on formatting patches here: http://orgmode.org/worg/org-contribute.html#sec-4 It saves the developers a lot of time if you follow these instructions. Finally, if you're likely to go over the limits of a TINY CHANGE, then you will want to assign your work to FSF so that it can be included in Emacs. See the instructions here: http://orgmode.org/worg/org-contribute.html#sec-2 Hopefully, I've remembered all the steps. If this doesn't work for you, come back to the list with queries. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] editing The compact Org-Mode Guide
Hi Gregory, Gregory Benjamin gr...@laserlab.com writes: I started reading orgguide.pdf, Release 7.9.3e and came across a couple of grammatical errors right away. I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. thanks in advance for this work! Thomas gave all information you need to start -- one correction: orgguide.texi is not part of Emacs, so you don't need to assign your copyright to the FSF for them. Another caveat: most of orgguide.texi comes from org.texi, so it is very like that, if you find a typo in orgguide.texi, the typo will be in org.texi too. If you want to provide a patch for org.texi too, then you'll have to assign your copyright to the FSF -- or to let Thomas or/and I backport your changes into org.texi. All best, -- Bastien
Re: [O] editing The compact Org-Mode Guide
Thanks for the instructions on how to play nice in the sandbox. We noobs are always afraid we are going to cause more work than we fix. :-) On Tue, Feb 5, 2013 at 2:11 PM, Thomas S. Dye t...@tsdye.com wrote: Aloha Greg, Gregory Benjamin gr...@laserlab.com writes: I'd like to take a stab at making some corrections and would like to have access to the source for this document. With some guidance, I should be able to produce a patch that can be incorporated into the next realease. The source is /path/to/org-mode/doc/orgguide.texi There is a file in that directory called Documentation_Standards.org, which contains what the file name advertises. Please provide me with instructions on downloading the source, and after I finish editing, uploading the diffs or updated version. Assuming you are using the git version of Org mode, you should create a new branch, check it out, and edit orgguide.texi there. When you are happy with your edits, stage and commit them in the git repository. Once the edits have been committed, you can make a patch like this: git format-patch -o ~/temp/ HEAD~1 where ~/temp/ is what I use and might not be appropriate for your setup, so should be changed accordingly. You should read the instructions on formatting patches here: http://orgmode.org/worg/org-contribute.html#sec-4 It saves the developers a lot of time if you follow these instructions. Finally, if you're likely to go over the limits of a TINY CHANGE, then you will want to assign your work to FSF so that it can be included in Emacs. See the instructions here: http://orgmode.org/worg/org-contribute.html#sec-2 Hopefully, I've remembered all the steps. If this doesn't work for you, come back to the list with queries. All the best, Tom -- Thomas S. Dye http://www.tsdye.com -- Evan Misshula Doctoral Student (Criminal Justice) CUNY John Jay Let us reform our schools, and we shall find little reform needed in our prisons. John Ruskin, Unto This Last, essay 2 (1862) English critic, essayist, reformer (1819 - 1900) Instruction does much, but encouragement does everything. Johann Wolfgang Von Goethe www.snrg-nyc.org
