From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Subject: Collaborating on a shared project Date: Wed, 15 Aug 2012 13:27:44 +0200 [thread overview] Message-ID: <email@example.com> (raw) Hello, After months, if not years, of insistence, I've convinced (even VI) colleagues to use Org as the format for keeping tracks of tasks to do, and of time spent on them. Now, as projects involve more people than me only, I'm a bit stuck because I'd like to get all tasks (of everybody) in _one unique_ file (currently, with tags for the assignee), and I require them to track time with Org. Doing so, that file being part of my `org-agenda-files', I have the following problems: - By default, I see *their* tasks in my basic agenda view. OK, that can be solved by filtering on tags, eventually making up a customized agenda view for me. Not a real problem, then. - I see *their* clock lines when checking the clocks (for gaps or overlaps). The workaround I had until now was to put all project information in one unique file, but the clock times (and the corresponding tasks) in personal (but public among us) files. That solved the problem of (much more) conflicts when committing updates to the Org project file as well. However, there is now good view of the tasks, even INCLUDE'ing those Org files in the project file, as everybody has made up its own structure for the tasks, and tasks about a same subject may be spread over multiple personal files. If I want a nice HTML project page, with tasks logically ordered, I must return to the "one big file" view. But what happens with the tasks done by others? If one task is begun by someone, then finished by another, do I need to create two tasks, as I use tags for setting the assignee? It does not make real sense, semantically, as we speak of the same task. Then, the clock lines should be owned by some user (identified by kind of a tag): they could be set under the same task, and the "clock check" functions should be improved to take into account some sort of identifier. That's, here, the current results of my thoughts about how to resolve the above problem. I'd be interested to hear other solutions or workaround, and 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". Best regards, Seb -- Sebastien Vauban
next reply other threads:[~2012-08-15 11:27 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-15 11:27 Sebastien Vauban [this message] 2012-08-15 12:23 ` Bastien
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 \ --firstname.lastname@example.org \ --email@example.com \ --cc=emacs-orgmode-mXXj517/zsQ@public.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).