org-agenda-property version number incorrect?

Ah, thanks. I haven't felt the need to update, but it doesn't mean I shouldn't.

re: delegation, tags, etc.

I think I need to start making a design document.

First, from a purely practical standpoint, you don't want to delegate something to more than one person. By which I mean, it has to be very clear who you're going to talk to, and they likely need to be very clear about the fact that you're going to talk to them. Even if you have "contractors" working on the house, and even if that's what you write, you're very likely going to be talking to the lead, the representative, whoever. If you have to call the tire shop because they ordered tires for you, then you call the tire shop, and that's "who" you delegated to. Basically, you need a single point of contact. This is the fundamental justification for using a property vs a tag. in this instance.

Second, and this is one of the most critical, most difficult things I've come across while doing this work... Org-mode allows you to implement bits and pieces of GTD in so many different ways that at some point you have to choose one way to do it, for consistency's sake, and for the sake of creating meaningful agenda views.

For instance, and I am 95% certain now that I actually forgot to document this, I provide a function which dynamically goes through the tags and creates an agenda view of next actions grouped by contexts -- tags starting with a @ ( https://github.com/Trevoke/org-gtd.el/blob/master/org-gtd-agenda.el#L67, org-gtd-engage-grouped-by-context ). When you look at all the tags in the view, you ideally shouldn't be saying "okay let me look at all these words to understand this action on my agenda view". AND of course org-mode has implemented features around tags so that you don't have to do that, either!

You could absolutely argue that a person is a context, and you wouldn't be completely wrong, but I would rather create a specific agenda view for specific people, and the main reason why is because I think it's crucially important to have as clear a separation of meaning as possible when looking at an agenda view. So it's super-easy to start talking to each other in circles because "you can do it this way in org-mode"

So, maybe, how would you use the knowledge that an item is delegated to someone? What are the ideal agenda views and agenda tools and filters for you? This might allow us to not talk in circles about "how to do it in org mode".

On Tue, May 16, 2023 at 6:15 AM doolio @.***> wrote:

https://github.com/Trevoke/org-gtd.el/blob/578e83b0f67cb57dd1b10e9eea4f40d2e925b9b9/org-gtd.el#L7

The latest version is v1.3.2 https://github.com/Malabarba/org-agenda-property/blob/3b469f3e93de0036547f3631cd0366d53f7584c8/org-agenda-property.el#L7 and the repository has not been updated since 2015.

Aside, are you still only using org-agenda-property to display to whom a task has been delegated? I believe we discussed this in the past and I argued to reduce your number of dependencies you could encourage users to use a tag rather than a property. I believe this is the approach recommended by Karl Voit as well. See here https://karl-voit.at/2019/09/25/categories-versus-tags/.

— Reply to this email directly, view it on GitHub https://github.com/Trevoke/org-gtd.el/issues/146, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQSSO3WZJ7QP76PHJKUPDXGNHT7ANCNFSM6AAAAAAYDNLDJU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Trevoke / org-gtd.el

org-agenda-property version number incorrect? #146