Re: [O] Release 8.0
I wanted to report that the problem seems to be solved in the latest release. I just compiled and ran all the tests (including the maxima ones) without a hitch on my Mac (OSX 10.8.3, Emacs 24.3.1) On Apr 18, 2013, at 8:01 PM, Achim Gratz strom...@nexgo.de wrote: Neuwirth Erich writes: I compiled from the repository after the announcement. On my Mac (OSX 10.8.3, Emacs 24.3.1) the test for maxima still fail. I reported this a few weeks ago. I can't find any post from you on this mailing list that fits that description and your last post mentioning maxima is from March last year. Ran 443 tests, 436 results as expected, 7 unexpected (2013-04-18 19:38:30+0200) 5 expected failures 7 unexpected results: FAILED ob-maxima/integer-input FAILED ob-maxima/list-input FAILED ob-maxima/matrix-output FAILED ob-maxima/simple-list-input FAILED ob-maxima/string-input FAILED ob-maxima/table-input1 FAILED ob-maxima/table-input2 make[1]: *** [test-dirty] Error 1 Well this looks like all maxima tests have failed, so you might want to check if it's correctly configured on your system and/or if there's some extra definition you'll have to give so that the test will find it (it runs from 'emacs -Q', so you'll have to add any extra setup to the config variables that make uses). Also, please trim your quotes. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] Release 8.0
On Sun, Apr 21, 2013 at 9:25 AM, Bastien b...@gnu.org wrote: Hi Memnon, Memnon Anon gegendosenflei...@googlemail.com writes: [ snip ] Quick question: is it true, now that Org 8.0 has been released, that the engine which publishes Worg is now Org 8.0, too? In other words, is it now safe to publish to Worg all of that stuff which was written compatible with the new exporter, without breaking Worg in the process? Cheers, -- Jay
Re: [O] Release 8.0
Hi Jay, Jay Kerns gjkerns...@gmail.com writes: On Sun, Apr 21, 2013 at 9:25 AM, Bastien b...@gnu.org wrote: Hi Memnon, Memnon Anon gegendosenflei...@googlemail.com writes: [ snip ] Quick question: is it true, now that Org 8.0 has been released, that the engine which publishes Worg is now Org 8.0, too? No, not yet. In other words, is it now safe to publish to Worg all of that stuff which was written compatible with the new exporter, without breaking Worg in the process? No. Someone needs to carefully check he can exports his local clone of worg.git with the new exporter, fix the wrong syntax, then commit it. This surely deserves a public branch of Worg, which people can hack together. -- Bastien
Re: [O] Release 8.0
On 22.4.2013, at 19:17, Bastien b...@gnu.org wrote: Hi Jay, Jay Kerns gjkerns...@gmail.com writes: On Sun, Apr 21, 2013 at 9:25 AM, Bastien b...@gnu.org wrote: Hi Memnon, Memnon Anon gegendosenflei...@googlemail.com writes: [ snip ] Quick question: is it true, now that Org 8.0 has been released, that the engine which publishes Worg is now Org 8.0, too? No, not yet. In other words, is it now safe to publish to Worg all of that stuff which was written compatible with the new exporter, without breaking Worg in the process? No. Someone needs to carefully check he can exports his local clone of worg.git with the new exporter, fix the wrong syntax, then commit it. This surely deserves a public branch of Worg, which people can hack together. Thanks Bastien, I was about to write about this. We need a volunteer who is willing to coordinate the conversion of Worg to the new exporter. This is an important task. Dogfooding Worg to the new exporter will be a good way to find remaining bugs in the parser/exporter setup. This task would entail: 1. Creating a public branch of Worg for this work. 2. Creating and maintaining a file that contains a site map of Worg, with all files that need publishing 3. Organizing contributors who will look at one page after the other and implementing any changes needed to make the page export (not yet publish) cleanly with the new exporter. In this way we need to walk through all Worg files, and someone needs to keep the tabs on this. 4. When all this is done, see what changes have to be made to the publishing setup to fix the automatic publishing. Any takers? Once we are done with this, we also need the orgmode.org website, but that contains fewer pages, so it should be a lot simpler. - Carsten
Re: [O] Release 8.0
On Mon, Apr 22, 2013 at 1:32 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 22.4.2013, at 19:17, Bastien b...@gnu.org wrote: Hi Jay, Jay Kerns gjkerns...@gmail.com writes: On Sun, Apr 21, 2013 at 9:25 AM, Bastien b...@gnu.org wrote: Hi Memnon, Memnon Anon gegendosenflei...@googlemail.com writes: [ snip ] Quick question: is it true, now that Org 8.0 has been released, that the engine which publishes Worg is now Org 8.0, too? No, not yet. In other words, is it now safe to publish to Worg all of that stuff which was written compatible with the new exporter, without breaking Worg in the process? No. Someone needs to carefully check he can exports his local clone of worg.git with the new exporter, fix the wrong syntax, then commit it. This surely deserves a public branch of Worg, which people can hack together. Thanks Bastien, I was about to write about this. We need a volunteer who is willing to coordinate the conversion of Worg to the new exporter. This is an important task. Dogfooding Worg to the new exporter will be a good way to find remaining bugs in the parser/exporter setup. This task would entail: 1. Creating a public branch of Worg for this work. Can I just update my clone and push to github? If so, sure. I'd just use my own github account (unpaid). If there's a better location, suggest it or someone else can volunteer to host/create the clone if they have better tools/access for this. 2. Creating and maintaining a file that contains a site map of Worg, with all files that need publishing I could take a stab at this, but it won't be instantaneous. If someone has the time and energy to do this in the short term ( 1 week), they'd be better. If a week or so is acceptable, I can take this one as well, at least the creation part. I'm assuming it will be a big todo list? From there, it would be much easier if editors updated it themselves. 3. Organizing contributors who will look at one page after the other and implementing any changes needed to make the page export (not yet publish) cleanly with the new exporter. In this way we need to walk through all Worg files, and someone needs to keep the tabs on this. Not sure we totally need to organize this. I'm wondering about something like an editor property in the file from #2. Contributors could self-assign by adding their name to that property in the tracker file and then push. Perhaps an agenda view or simply column view could quickly show who is assigned to what file? 4. When all this is done, see what changes have to be made to the publishing setup to fix the automatic publishing. I'd be really bad at this as I've never actually set up publishing. I can definitely help with some of the #+attr_backend and general syntax stuff, but I never got heavy into the site publishing features and have never even looked at Worg's setup for this. If this is the process... how does the public Worg get updated in the mean time? I'm pretty new to git and only do basic stuff. Diffs have always been intimidating (and I've found them to really stink even for really, really small changes I've had). How will we maintain the public site and then re-combine with the public one down the road? Editing on the public one needs to happen in old syntax; public repo for upgrade hacking needs to be in the new syntax. Should we freeze Worg for the time being and direct editing to happen at the other one? Best regards, John Any takers? Once we are done with this, we also need the orgmode.org website, but that contains fewer pages, so it should be a lot simpler. - Carsten
Re: [O] Release 8.0
On 22.4.2013, at 21:46, John Hendy jw.he...@gmail.com wrote: On Mon, Apr 22, 2013 at 1:32 PM, Carsten Dominik carsten.domi...@gmail.com wrote: On 22.4.2013, at 19:17, Bastien b...@gnu.org wrote: Hi Jay, Jay Kerns gjkerns...@gmail.com writes: On Sun, Apr 21, 2013 at 9:25 AM, Bastien b...@gnu.org wrote: Hi Memnon, Memnon Anon gegendosenflei...@googlemail.com writes: [ snip ] Quick question: is it true, now that Org 8.0 has been released, that the engine which publishes Worg is now Org 8.0, too? No, not yet. In other words, is it now safe to publish to Worg all of that stuff which was written compatible with the new exporter, without breaking Worg in the process? No. Someone needs to carefully check he can exports his local clone of worg.git with the new exporter, fix the wrong syntax, then commit it. This surely deserves a public branch of Worg, which people can hack together. Thanks Bastien, I was about to write about this. We need a volunteer who is willing to coordinate the conversion of Worg to the new exporter. This is an important task. Dogfooding Worg to the new exporter will be a good way to find remaining bugs in the parser/exporter setup. This task would entail: 1. Creating a public branch of Worg for this work. Can I just update my clone and push to github? If so, sure. I'd just use my own github account (unpaid). If there's a better location, suggest it or someone else can volunteer to host/create the clone if they have better tools/access for this. Do you have commit access at the worg repository at orgmode.org? Then it would be easiest to set it up there. I could do it, but maybe you want to? Basically: You create a new branch in your repository: $ git checkout -b worg-new-exporter Then you push this new branch to the remote repository: $ git push -u origin worg-new-exporter Then you can work in this new branch and just push from this branch whenever you want: $ git push Everybody else can hook onto this branch with $ git checkout --track -b worg-new-exporter origin/worg-new-exporter and then work in this branch and push it whenever they want. 2. Creating and maintaining a file that contains a site map of Worg, with all files that need publishing I could take a stab at this, but it won't be instantaneous. If someone has the time and energy to do this in the short term ( 1 week), they'd be better. If a week or so is acceptable, I can take this one as well, at least the creation part. I'm assuming it will be a big todo list? From there, it would be much easier if editors updated it themselves. I agree, this would be easiest. Organizing this would then mean to announce to precise procedure on the mailing list and hope that people hack away. 3. Organizing contributors who will look at one page after the other and implementing any changes needed to make the page export (not yet publish) cleanly with the new exporter. In this way we need to walk through all Worg files, and someone needs to keep the tabs on this. Not sure we totally need to organize this. I'm wondering about something like an editor property in the file from #2. Contributors could self-assign by adding their name to that property in the tracker file and then push. Yes this is a good way. Organizing then means to check for files that have not been done and do them yourself or encourage other directly to do it. Perhaps an agenda view or simply column view could quickly show who is assigned to what file? 4. When all this is done, see what changes have to be made to the publishing setup to fix the automatic publishing. I'd be really bad at this as I've never actually set up publishing. I can definitely help with some of the #+attr_backend and general syntax stuff, but I never got heavy into the site publishing features and have never even looked at Worg's setup for this. Well, if you get everything working with the new exporter, we will find a way to fix publishing if necessary. If this is the process... how does the public Worg get updated in the mean time? I'm pretty new to git and only do basic stuff. Diffs have always been intimidating (and I've found them to really stink even for really, really small changes I've had). How will we maintain the public site and then re-combine with the public one down the road? Editing on the public one needs to happen in old syntax; public repo for upgrade hacking needs to be in the new syntax. We definitely do NOT stop to edit Worg in the mean time. The master branch can be edited in parallel. This is git, so we can merge both branches when the time comes. It would be great if you can take a stab at this, John. - Carsten Should we freeze Worg for the time being and direct editing to happen at the other one? Best regards, John Any takers? Once we are done with this, we also need the orgmode.org website, but that contains fewer
Re: [O] Release 8.0
John Hendy jw.he...@gmail.com writes: No. Someone needs to carefully check he can exports his local clone of worg.git with the new exporter, fix the wrong syntax, then commit it. This surely deserves a public branch of Worg, which people can hack together. We need a volunteer who is willing to coordinate the conversion of Worg to the new exporter. This is an important task. Dogfooding Worg to the new exporter will be a good way to find remaining bugs in the parser/exporter setup. This task would entail: [...] 3. Organizing contributors who will look at one page after the other and implementing any changes needed to make the page export (not yet publish) cleanly with the new exporter. In this way we need to walk through all Worg files, and someone needs to keep the tabs on this. Not sure we totally need to organize this. I'm wondering about something like an editor property in the file from #2. Contributors could self-assign by adding their name to that property in the tracker file and then push. Perhaps an agenda view or simply column view could quickly show who is assigned to what file? Any takers? I don't know if this would put a huge work load on somebody who contributed *much* content to Worg, but otherwise I would propose for this step that all authors of Worg articles/pages take care of their own pages. In my case that would be e.g. half a dozen of pages, not that much of a problem. Once most Worg authors have fixed their own pages, another round of fixing the (few?) remaining pages by some volunteers could be started. Just my 2cents -- cheers, Thorsten
Re: [O] Release 8.0
Bastien b...@gnu.org writes: I'm releasing Org 8.0. Excellent. To include other entries too, you can set the limit to a negative number. For example (setq org-agenda-max-tags 3) (setq org-agenda-max-tags -3) ? will not show the fourth tagged headline (and beyond), but it will also show non-tagged headlines. Use `%s' for displaying breadcrumbs in the agenda view ^%b • New speedy key `s' pour org-narrow-to-subtree Memnon
Re: [O] Release 8.0
Hi Memnon, Memnon Anon gegendosenflei...@googlemail.com writes: To include other entries too, you can set the limit to a negative number. For example (setq org-agenda-max-tags 3) (setq org-agenda-max-tags -3) ? Indeed. will not show the fourth tagged headline (and beyond), but it will also show non-tagged headlines. Use `%s' for displaying breadcrumbs in the agenda view ^%b Ditto. Fixed, thanks! -- Bastien
Re: [O] Release 8.0
On Apr 19, 2013, at 1:53 PM, Brian van den Broek brian.van.den.br...@gmail.com wrote: On 18 Apr 2013 18:05, Carsten Dominik carsten.domi...@gmail.com wrote: On 18.4.2013, at 18:41, Bastien b...@gnu.org wrote: Dear all, I'm releasing Org 8.0. This is a beautiful release. Just reading the list of changes wets my appetite to try it all out. A looong list con contributors. Thanks to you all for your contributions! An intimidatingly long list of changes, actually. :-) For what it is worth, I think if Bastien erred in the list of contributors he thanked, it was on the side of over-inclusion, rather than under. In the last year or so, I think I've contributed a tiny change doc patch, a bug report or two, and a few Please, could someone magically make it work like this? messages, yet I find myself included. Yes, indeed! Honestly, I didn't read the long list of contributors that carefully at first. I decided to take another read after through your message, and ... Wow... I really didn't expect my name be in the list, since I have only sent a few messages to the list. Congrats and thanks to all who helped in whatever way. The efforts from the heroic and steady to minor and irregular have all helped to make my life better. Congratulations to all the orgmode users! Please allow me to take this chance to express my sincere gratitude to everyone subscribed to this orgmode mailing list and also people who contributed in other ways! It is you who have made orgmode so fantastic! Best Regards, Xiao-Yong
Re: [O] Release 8.0
Great! Thanks, everybody. Yours, Christian
Re: [O] Release 8.0
On 18.04.2013, at 18:41, Bastien wrote: I'm releasing Org 8.0. EXCELLENT - thank you for the hard work and the patience! Aaron Ecay, Abdó Roig-Maranges, Achim Gratz, Adam Spiers, Alan Schmitt, Alexander Willand, Andreas Leha, Andreas Röhler, Andrew M. Nuxoll, Arun Persaud, Bernd Haug, Bernt Hansen, Bill Day, Bill White, Brian van den Broek, Carsten Dominik, Charles C. Berry, Christian Egli, Christian Moe, Christophe Junke, Christopher Schmidt, Christopher Witte, Chuck Berry, Daniel Clemente, Daniel Dehennin, Dave Abrahams, David Kincaid, Derek Upham, Enda, Eric Abrahamsen, Eric S Fraga, Eric Schulte, Esben Stien, Fabrice Popineau, Feng Shu, Florian Beck, Francesco Pizzolante, Frank Fischer, Frank Terbeck, François Pinard, G. Jay Kerns, Gaizka Villate, Gary Oberbrunner, Greg Minshall, Gregor Kappler, Grégoire Jadi, Henry Atting, Hiroshi Saito, Hrvoje Nikšić, Ian Barton, Ingo Lohmar, Ippei FURUHASHI, Ivan Vilata i Balaguer, J. David Boyd, Jae Hee Lee, Jambunathan K, James Harkins, Jarmo Hurri, John Foerch, John Hendy, John J Foerch, John Wiegley, Jonas Bernoulli, Jonathan Leech-Pepin, Joost Helberg, Justus Piater, Kalev Takkis, Ken Williams, Kevin Buchs, Kodi Arfer, Kyle Machulis, Le Wang, Leo Liu, Luca Sabbatini, Luis Anaya, Marcel van der Boom, Mark Edgington, Matt Lundin, Max Mikhanosha, Michael Brand, Michael Crouch, Michael Gauland, Michael Heerdegen, Michael Strey, Mirko Vukovic, Myles English, Nick Dokos, Nicolas Goaziou, Nicolas Richard, Oliver Večerník, Paul Sexton, Peder Stray, Peter Münster, Philipp Kroos, Raghavendra D Prabhu, Rainer M. Krug, Rainer Stengele, Rasmus, Rene, Richard Stanton, Rick Frankel, Rick Hanson, Robert Goldman, Robert Horn, Robert Klein, Roland Winkler, Ryo TAKAISHI, Rémi Vanicat, Rüdiger Sonderfeld, Sacha Chua, Samuel Loury, Samuel Wales, Sean O'Halpin, Sébastien Vauban, Simon Thum, Stefan Monnier, Stefan Vollmar, Stephen Eglen, Steve Purcell, Suhail Shergill, Suvayu Ali, T.F. Torrey, Thomas S. Dye, Thorsten Jolitz, Toby S. Cubitt, Tokuya Kameshima, Tony Day, Viktor Rosenfeld, Vincent Beffara, Vladimir Lomov, Wanrong Lin, William Lechelle, Xiao-Yong Jin, Xue Fuqiao, Yann Hodique, Yasushi SHOJI, Zech, sabof, Дядов Васил Стоянов. Thanks to everybody who made Orgmode such a great tool! Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature
[O] Release 8.0
Dear all, I'm releasing Org 8.0. See the release notes below or at http://orgmode.org/Changes.html This release is potentially the most disruptive release since long, so please don't use it in production before you can carefully review the release notes and update your configuration -- especially with respect to export features. I would like to thank you all again for your patience, and special thanks to Nicolas who is just great to work with. I'm happy to see his code finally widely available for all Org users, not just the happy few. Enjoy! ORG 8.0 Installation Installation instructions have been updated and simplified. If you have troubles installing or updating Org, focus on these instructions: • when updating via a `.zip/.tar.gz' file, you only need to set the `load-path' in your `.emacs'. Set it before any other Org customization that would call autoloaded Org functions. • when updating by pulling Org's Git repository, make sure to create the correct autoloads. You can do this by running `~$ make autoloads' (to only create the autoloads) or by running `~$ make' (to also compile the Emacs lisp files.) `~$ make help' and `~$ make helpall' gives you detailed explanations. • when updating through ELPA (either from GNU ELPA or from Org ELPA), you have to install Org's ELPA package in a session where no Org function has been called already. When in doubt, run `M-x org-version RET' and see if you have a mixed-up installation. See [http://orgmode.org/org.html#Installation] for details. Incompatible changes Org 8.0 is the most disruptive major version of Org. If you configured export options, you will have to update some of them. If you used `#+ATTR_*' keywords, the syntax of the attributes changed and you will have to update them. Below is a list of changes for which you need to take action. See [http://orgmode.org/worg/org-8.0.html] for the most recent version of this list and for detailed instructions on how to migrate. New export engine ╌ Org 8.0 comes with a new export engine written by Nicolas Goaziou. This export engine relies on `org-element.el' (Org's syntax parser), which was already in Org's core. This new export engine triggered the rewriting of /all/ export back-ends. The most visible change is the export dispatcher, accessible through the keybinding `C-c C-e'. By default, this menu only shows some of the built-in export formats, but you can add more formats by loading them directly (e.g., `(require 'ox-texinfo)' or by configuring the option org-export-backends. More contributed back-ends are available from the `contrib/' directory, the corresponding files start with the `ox-' prefix. If you customized an export back-end (like HTML or LaTeX), you will need to rename some options so that your customization is not lost. Typically, an option starting with `org-export-html-' is now named `org-html-'. See the manual for details and check [this Worg page] for directions. [this Worg page] http://orgmode.org/worg/org-8.0.html New syntax for #+ATTR_HTML/LaTeX/… options ╌╌ ╭ │ #+ATTR_HTML width=200px ╰ should now be written ╭ │ #+ATTR_HTML :width 200px ╰ Keywords like `#+ATTR_HTML' and `#+ATTR_LaTeX' are defined in their respective back-ends, and the list of supported parameters depends on each backend. See Org's manual for details. `org-remember.el' has been removed ╌╌ You cannot use `remember.el' anymore to capture notes. Support for remember templates has been obsoleted since long, it is now fully removed. Use `M-x org-capture-import-remember-templates RET' to import your remember templates into capture templates. `org-jsinfo.el' has been merged into `ox-html.el' ╌ If you were requiring `ox-jsinfo.el' in your `.emacs.el' file, you will have to remove this requirement from your initialization file. Note for third-party developers ╌╌╌ The name of the files for export back-end have changed: we now use the prefix `ox-' for those files (like we use the `ob-' prefix for Babel files.) For example `org-html.el' is now `ox-html.el'. If your code relies on these files, please update the names in your code. Packages moved from core to contrib ╌╌╌ Since packages in Org's core are meant to be part of GNU Emacs, we try to be minimalist when it comes to adding files into core. For 8.0, we moved some contributions into the `contrib/' directory. The rationale for deciding that these files should live in `contrib/' is either because they rely on
Re: [O] Release 8.0
Bastien Could you please correct the headers to ox-html.el and ox-odt.el. I have not assigned the rights to my changes to FSF. These files - due to Emacs project policy - cannot be part of Emacs. Jambunathan K.
Re: [O] Release 8.0
Hi Jambunathan, Jambunathan K kjambunat...@gmail.com writes: Could you please correct the headers to ox-html.el and ox-odt.el. I corrected the header for ox-html.el: the header said you were the only author while it's clear half of the code was simply copied from Carsten. I added Carsten as the author. I have not assigned the rights to my changes to FSF. These files - due to Emacs project policy - cannot be part of Emacs. RMS confirmed that you changes were assigned in a private email that we both received this morning. It's your right to disagree, but first solve this dispute with the FSF before asking me to obey to you. I'm following the advice of the FSF for now. -- Bastien
Re: [O] Release 8.0
Bastien b...@gnu.org writes: I'm releasing Org 8.0. Fantastic work. Warm congratulations to all those involved! François
Re: [O] Release 8.0
On Thu, Apr 18, 2013 at 11:41 AM, Bastien b...@gnu.org wrote: Dear all, I'm releasing Org 8.0. Simply fantastic. Many thanks and great work on such a detailed list of changes. Just mind-blowing how awesome this project is. Thanks to all the contributors for this great piece of software -- I use it everyday with outstanding benefits compared to not having it. John
Re: [O] Release 8.0
Neuwirth Erich writes: I compiled from the repository after the announcement. On my Mac (OSX 10.8.3, Emacs 24.3.1) the test for maxima still fail. I reported this a few weeks ago. I can't find any post from you on this mailing list that fits that description and your last post mentioning maxima is from March last year. Ran 443 tests, 436 results as expected, 7 unexpected (2013-04-18 19:38:30+0200) 5 expected failures 7 unexpected results: FAILED ob-maxima/integer-input FAILED ob-maxima/list-input FAILED ob-maxima/matrix-output FAILED ob-maxima/simple-list-input FAILED ob-maxima/string-input FAILED ob-maxima/table-input1 FAILED ob-maxima/table-input2 make[1]: *** [test-dirty] Error 1 Well this looks like all maxima tests have failed, so you might want to check if it's correctly configured on your system and/or if there's some extra definition you'll have to give so that the test will find it (it runs from 'emacs -Q', so you'll have to add any extra setup to the config variables that make uses). Also, please trim your quotes. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] Release 8.0
I added Carsten as the author. I have no problem with that. You can even add N other authors as long as my name stays there. I'm following the advice of the FSF for now. FSF position is ambivalent. They have made a decision (to suit their convenience) and shifting the burden on me. Their response is simply not consistent with Emacs project policy or the most ethical one. Both FSF and you [1] are robbing Peter and paying Paul. For the serious observers, I have posted a response here. http://lwn.net/Articles/547737/ I also cite the specific term of my future assignment based on which I claim that I have the right to report on changes that is not covered by contract. [1] You didn't take my permission to move the files from contrib/lisp to lisp. Jambunathan K.
Re: [O] Release 8.0
François Pinard pin...@iro.umontreal.ca writes: Bastien b...@gnu.org writes: I'm releasing Org 8.0. Fantastic work. Warm congratulations to all those involved! Seconded!! The new exporter is terrific :-) atb Glyn
Re: [O] Release 8.0
Excellent news! Thanks to you Bastien and to all the other people who have helped make this possible. -- Aaron Ecay
Re: [O] Release 8.0
Aaron Ecay aarone...@gmail.com writes: Excellent news! Thanks to you Bastien and to all the other people who have helped make this possible. You speak as though other people don't exist or matter. IMO, you are doing a disservice to other contributors by *not* naming them. Is it really difficult for you to read the soruce code or changelog and educate yourself on who these other people are. Please name the people who are thanking. It's just basic courtesy. Stop saying other people and all contributors. Jambunathan K.
Re: [O] Release 8.0
Bastien b...@gnu.org writes: I would like to thank you all again for your patience, and special thanks to Nicolas who is just great to work with. I'm happy to see his code finally widely available for all Org users, not just the happy few. I would also like to thank Nicolas for this impressive archivement! Thanks a lot! It is much appreciated! ORG 8.0 Congrats Bastien! It's looks like a nice release (and indeed based on the git version it is!) –Rasmus -- When the facts change, I change my mind. What do you do, sir?
Re: [O] Release 8.0
Jambunathan K kjambunat...@gmail.com writes: You speak as though other people don't exist or matter. IMO, you are doing a disservice to other contributors by *not* naming them. All contributors, including you, have been thanked in the release notes I attached with the original announcement. We don't want everybody to copy-past this section in their reply :) -- Bastien
Re: [O] Release 8.0
François Pinard pin...@iro.umontreal.ca writes: Fantastic work. Warm congratulations to all those involved! You are a regular. Is it really difficult for you to spell out the names explicitly? All those involved is politically correct but it is a disservice to few individuals whose efforts have been nothing short of Herculean. Jambunathan K.
Re: [O] Release 8.0
Bastien b...@gnu.org writes: Jambunathan K kjambunat...@gmail.com writes: You speak as though other people don't exist or matter. IMO, you are doing a disservice to other contributors by *not* naming them. All contributors, including you, have been thanked in the release notes I attached with the original announcement. We don't want everybody to copy-past this section in their reply :) Perceptions matter. A name that is repeated gets remembered. All credits go to that name while other names fade. Politicians know that perception matter. I am just educating users on how warped their perceptions could be when they thank just a single person for what is essentially the work of many hands. Users of Free Software should be appreciative of and show respect to all hands that did the grunt work. Jambunathan K.
Re: [O] Release 8.0
Jambunathan K kjambunat...@gmail.com writes: Perceptions matter. A name that is repeated gets remembered. All credits go to that name while other names fade. See this post: http://lwn.net/Articles/501751/ People still continue to thank RMS for new Emacs releases. IIRC, it is good 5-6 years since RMS retired from daily Emacs work. There is a gap between what people hold to be true and what the reality is. Some perceptions are wrong and it is important that these be corrected. Jambunathan K.
Re: [O] Release 8.0
Jambunathan K kjambunat...@gmail.com writes: Bastien b...@gnu.org writes: Jambunathan K kjambunat...@gmail.com writes: You speak as though other people don't exist or matter. IMO, you are doing a disservice to other contributors by *not* naming them. All contributors, including you, have been thanked in the release notes I attached with the original announcement. We don't want everybody to copy-past this section in their reply :) Perceptions matter. A name that is repeated gets remembered. There is very little danger that your name will not be remembered.
Re: [O] Release 8.0
Thanks to everybody who made this release possible.
Re: [O] Release 8.0
Jambunathan K kjambunat...@gmail.com writes: Can you name the person who funds http://orgmode.org website? Indeed, I forget to add Jason Dunsmore in the list of people to thank. Sorry for that. Jason is still helping with anything regarding the server, we are lucky to have him! -- Bastien
Re: [O] Release 8.0
Jambunathan K kjambunat...@gmail.com writes: There is very little danger that your name will not be remembered. Let me be clear, it's not about me. I am a nobody who likes to troll. Confession noted. In which case it IS all about you. It is about others (as well) who deserve a explicit word of thanks. So far you have totally failed to offer any word of thanks - either to Bastien or to any one else. [1] Why cannot people thank Nicolas Goaziou for the parser and exporter framework and also for most of the exporters. Why can't you? People are under the mistaken notion that it is the maintainer who does the most or important work. It is this mistake I am endeavouring to correct. Obviously I am failing. You are failing because the 'mistaken notion' you are trying to correct does not exist. Glyn Footnotes: [1] Anyone else? Lots of attributions here - http://orgmode.org/Changes.html - you are all wonderful and I love you!
Re: [O] Release 8.0
On 18.4.2013, at 18:41, Bastien b...@gnu.org wrote: Dear all, I'm releasing Org 8.0. See the release notes below or at http://orgmode.org/Changes.html This is a beautiful release. Just reading the list of changes wets my appetite to try it all out. A looong list con contributors. Thanks to you all for your contributions! - Carsten
Re: [O] Release 8.0
Bastien b...@gnu.org writes: I'm releasing Org 8.0. Great work! Wow what a huge list of new things to try :) I'm looking forward to experimenting with it. Thanks!! Bernt
Re: [O] Release 8.0
On 18 Apr 2013 18:05, Carsten Dominik carsten.domi...@gmail.com wrote: On 18.4.2013, at 18:41, Bastien b...@gnu.org wrote: Dear all, I'm releasing Org 8.0. This is a beautiful release. Just reading the list of changes wets my appetite to try it all out. A looong list con contributors. Thanks to you all for your contributions! An intimidatingly long list of changes, actually. :-) For what it is worth, I think if Bastien erred in the list of contributors he thanked, it was on the side of over-inclusion, rather than under. In the last year or so, I think I've contributed a tiny change doc patch, a bug report or two, and a few Please, could someone magically make it work like this? messages, yet I find myself included. Congrats and thanks to all who helped in whatever way. The efforts from the heroic and steady to minor and irregular have all helped to make my life better. Best, Brian vdB
