emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Bastien <bzg@gnu.org>
Cc: Nicolas Goaziou <n.goaziou@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-review-schedule
Date: Wed, 21 May 2014 14:58:00 +0200	[thread overview]
Message-ID: <m2k39fgug7.fsf@top-wifi.irisa.fr> (raw)
In-Reply-To: <871tvnxrjg.fsf@bzg.ath.cx> (Bastien's message of "Wed, 21 May 2014 14:08:51 +0200")

Hi Bastien,

On 2014-05-21 14:08, Bastien <bzg@gnu.org> writes:

>> Thank you for the opportunity. I've been getting spoiled by the use of
>> github (to track issues, and to have documentation at the same place
>> than the code). I'm wondering if there is a way to have the code both on
>> github and in the contrib directory. Is there any current package doing
>> it?
> No.  And that's why I'm considering the migration of contributed
> packages into a new Org ELPA, where sync'ing the Org ELPA package
> from another repository would be possible.  A win-win situation
> for everyone.

I've thought about this and I will try to go the ELPA route. Even if it
means less exposure, it seems to be conceptually closer to my vision of
this package (an add-on that does not need to add to the already huge
git repository).

>> Regarding the documentation, by the way, where should one put it for
>> contrb packages? On worg?
> Yes.  You can even add documentation for stuff that is not in contrib
> but available on github or on some other repository service.

It makes sense. I'll add "writing a tutorial on worg" on my todo list.



  reply	other threads:[~2014-05-21 13:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 20:27 org-review-schedule Alan Schmitt
2014-04-19  8:14 ` org-review-schedule Bastien
2014-04-19 11:16   ` org-review-schedule Alan Schmitt
2014-04-19 11:51     ` org-review-schedule Bastien
2014-04-24 11:51   ` org-review-schedule Alan Schmitt
2014-04-25  6:51     ` org-review-schedule Nicolas Goaziou
2014-04-25  7:43       ` org-review-schedule Alan Schmitt
2014-04-25  8:02         ` org-review-schedule Nicolas Goaziou
2014-04-27  8:09           ` org-review-schedule Alan Schmitt
2014-04-28  7:20             ` org-review-schedule AW
2014-04-28 11:29               ` org-review-schedule Alan Schmitt
2014-05-06  9:27             ` org-review-schedule Bastien
2014-05-15 10:07             ` org-review-schedule Bastien
2014-05-20 12:48               ` org-review-schedule Alan Schmitt
2014-05-21 12:08                 ` org-review-schedule Bastien
2014-05-21 12:58                   ` Alan Schmitt [this message]
2014-04-26  8:57       ` org-review-schedule Alan Schmitt
2014-04-26 10:38         ` org-review-schedule Thorsten Jolitz
2014-04-26 12:25           ` org-review-schedule Nicolas Goaziou
2014-04-27  8:08             ` org-review-schedule Alan Schmitt

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:

  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=m2k39fgug7.fsf@top-wifi.irisa.fr \
    --to=alan.schmitt@polytechnique.org \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \


* 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


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).