From: Bastien <bzg@gnu.org>
To: Neil Smithline <emacs-orgmode@neilsmithline.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Google Summer of Code -- 3 Org projects for our first participation!
Date: Sun, 29 Apr 2012 10:22:36 +0200 [thread overview]
Message-ID: <87ipgij2k5.fsf@altern.org> (raw)
In-Reply-To: <4F9C8937.2030709@neilsmithline.com> (Neil Smithline's message of "Sat, 28 Apr 2012 20:20:07 -0400")
Hi Neil,
Neil Smithline <emacs-orgmode@neilsmithline.com> 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
next prev parent reply other threads:[~2012-04-29 9:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 5:55 Google Summer of Code -- 3 Org projects for our first participation! Bastien
2012-04-24 7:17 ` Carsten Dominik
2012-04-24 7:18 ` Ian Barton
2012-04-24 8:12 ` Thorsten
2012-04-26 1:42 ` Neil Smithline
2012-04-26 7:48 ` Thorsten Jolitz
2012-04-28 23:12 ` Neil Smithline
2012-04-26 7:57 ` Bastien
2012-04-28 23:30 ` Neil Smithline
2012-04-29 8:26 ` Bastien
2012-04-29 0:20 ` Neil Smithline
2012-04-29 8:22 ` Bastien [this message]
2012-05-05 0:19 ` Neil Smithline
2012-05-05 5:39 ` Bastien
2012-05-05 10:52 ` Bernt Hansen
2012-05-05 9:36 ` Nicolas Goaziou
2012-05-04 22:37 ` Neil Smithline
2012-05-04 21:04 ` Eric Schulte
2012-04-24 9:54 ` Rasmus
2012-04-24 19:00 ` Achim Gratz
2012-04-24 23:16 ` Rasmus
2012-04-26 8:19 ` Bastien
2012-04-24 11:29 ` Richard Riley
2012-04-24 14:19 ` Andrew Young
2012-05-08 3:42 ` Neil Smithline
2012-05-08 8:06 ` Thorsten Jolitz
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=87ipgij2k5.fsf@altern.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=emacs-orgmode@neilsmithline.com \
/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).