Hi all, How is Leo currently used collaboratively?
In my mind I imagine something like this: - I have a node labeled Matt that I use as a personal view, that I add cloned nodes to. - Each node has a stream that returns 1) updates to any node in its transitive children, and 2) any nodes being added or removed from its transitive children. - I interpret the stream of updates on node Matt as my inbox. It tells me when something in my responsibility has changed, or when the scope of my responsibility has changed. This is useful for code changes, sure, but it's also useful for higher-level nodes used as collaborative design documents. And if nodes are tasks, I can easily delegate them by moving the clone from my view to somebody else's view. If I want I can also look for orphaned nodes that aren't on anybody's radar. Is this conception sane? How does it relate to the current state of Leo? Is it a plan for Leo issues to eventually be tracked on Leo itself, rather than through GitHub issues? Thank you! -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/366f1f3a-939b-4566-9307-0b08c2b2e0fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
