From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: org mode vs basecamp
Date: Tue, 23 Oct 2007 18:09:35 +0100 [thread overview]
Message-ID: <877ild4v1s.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87myuaxk9y.fsf@myhost.localdomain> (cezar@mixandgo.ro's message of "Tue, 23 Oct 2007 12:17:13 +0300")
Hi Cesar,
cezar@mixandgo.ro writes:
> I was curios if there is a way to use org mode as a project
> management and collaboration tool.
As for the "project management" part, it's quite obvious to me that Org
qualifies, at least for 90% of the core functions that are needed to be
a "project management tool" (see the recent discussion on dependencies.)
But I guess the important side of your question is: can I use Org as a
*collaboration* tool?
Well -- please do :)
1. One idea is to put an Org file on a CVS server, letting people check
it in and out, so that everybody knows what he has to-do and what is
the state of the project.
2. Another idea is to give someone the responsability to maintain an Org
file dispatching to-do list items through the team, displaying clear
deadlines, tasks status, etc.
3. The third idea is to let a web interface directly operate changes on
underlying Org files. I think this is achievable: Org files are text,
but with a reasonable set of conventions to format them we could edit
them through another tool.
I don't think such a tool exist right now, but that would actually be
fun.
> Here is a cool web app that does this:
> www.basecamphq.com
What PM/collaborative features do you have in this that you would like
to see in Org?
--
Bastien
next prev parent reply other threads:[~2007-10-23 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 9:17 org mode vs basecamp cezar
2007-10-23 17:09 ` Bastien [this message]
2007-10-23 18:43 ` cezar
2007-10-23 20:21 ` Bastien
2007-10-24 9:06 ` cezar
2007-10-24 10:26 ` Bastien
2007-10-24 10:52 ` cezar
2007-10-24 12:05 ` Bastien
2007-10-24 7:27 ` Stefan Kamphausen
2007-10-24 9:43 ` Bastien
2007-10-24 8:58 ` Stefan Kamphausen
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=877ild4v1s.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
/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).