From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Google Summer of Code -- 3 Org projects for our first participation! Date: Sun, 29 Apr 2012 10:22:36 +0200 Message-ID: <87ipgij2k5.fsf@altern.org> References: <8762cpad2q.fsf@gnu.org> <4F9653BD.7030201@wilkesley.net> <87obqh8s6m.fsf@googlemail.com> <4F98A7F0.6080405@neilsmithline.com> <87mx5zrklf.fsf@altern.org> <4F9C8937.2030709@neilsmithline.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:42543) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SOQeQ-0001HF-Tk for emacs-orgmode@gnu.org; Sun, 29 Apr 2012 05:42:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SOQeO-0005aE-VA for emacs-orgmode@gnu.org; Sun, 29 Apr 2012 05:42:42 -0400 Received: from mail-wg0-f49.google.com ([74.125.82.49]:35745) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SOQeO-0005a4-Mm for emacs-orgmode@gnu.org; Sun, 29 Apr 2012 05:42:40 -0400 Received: by wgbds1 with SMTP id ds1so1494548wgb.30 for ; Sun, 29 Apr 2012 02:42:38 -0700 (PDT) In-Reply-To: <4F9C8937.2030709@neilsmithline.com> (Neil Smithline's message of "Sat, 28 Apr 2012 20:20:07 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Neil Smithline Cc: emacs-orgmode@gnu.org Hi Neil, Neil Smithline writes: > In the end, I think the way that the best way the list could help improve > Github's support of Org files would be to provide two things: > > 1) Come up with a prioritized list of features that would be nice to be > supported by Github. This may just be the most used features of Org Mode or > it may be something special to how Org Mode is used in Github. I'm not > sure. This is a good idea. We could start a page on Worg for this -- if you want to edit Worg, please send me your public key in private and I'll give you access. When you're done with a preliminary list of yours, perhaps inviting the github developers could boost both the brainstorming and the development of org-ruby. > 2) Have a few people look at the org-ruby gem and then brainstorm about the > best way to proceed. This would either require people who know Ruby or more > experienced software engineers. I modified the gem and learned Ruby by > reading the source for this gem and occasionally looking something up in a > reference manual. But I'd bet I've been coding longer than list members > such as Thorsten have been alive. If there are Ruby hackers around, that might work. But since org-ruby is widely used by a (big?) company like github, perhaps this company could lead such effort. > I really don't know enough about the culture of the Org Mode developers to > know if this is possible or not. The alternative is that I can just keep > adding features as I need them and think I can implement them. That would be nice. One thing to be aware of: there is an ongoing work by Nicolas to write a parser (see org-element.el in contrib/lisp/ from the git repo). It is already quite useful -- and used in the new exporters (e.g. org-e-latex.el) One nice side-effect of having this parser is that we will be able to document the syntax of Org files more clearly. Actually, org-element.el *is* such a description, but we need to make it widely available as a documentation page (on Worg). Thanks, -- Bastien