emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Sebastien Vauban
	<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: Collaborating on a shared project
Date: Wed, 15 Aug 2012 14:23:17 +0200	[thread overview]
Message-ID: <87txw41gzu.fsf@gnu.org> (raw)
In-Reply-To: <80obmctmxb.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 15 Aug 2012 13:27:44 +0200")



Hi Sébastien,

"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:

> I think we should have a way to upgrade Org to more than a *personal*
> organizer -- of course, it already is much more, but I'm emphasizing
> here over "personal".

There is work under the way to make Org more collaboration-ready.

See the org-merge-driver by Andrew:

  http://orgmode.org/w/org-merge-driver.git

It helps merging possible conflicts when people use the same repo to
store org files.  Andrew asked for feedback -- if you have time to test
this, that would be great.

See also org-sync by Aurélien:
 
  http://orgmode.org/w/org-sync.git

It helps synchronize local org files with a remote backend such as
redmine, github, RememberTheMilk, etc.  Here again, feedback is very
welcome.

Now, what I would do in your situation is to have one .org file per
collaborator, then various views to get the information you want.  
This reduces possible merge conflicts, makes it easy to publish it
as a web page -- even publishing agendas should be okay.  I've never
used Org in this way though, so this is not grounded on experience.

Best,

-- 
 Bastien

      reply	other threads:[~2012-08-15 12:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 11:27 Sebastien Vauban
2012-08-15 12:23 ` Bastien [this message]

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=87txw41gzu.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
    --cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org \
    --subject='Re: Collaborating on a shared project' \
    /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

Code repositories for project(s) associated with this 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).