{"action":"created","issue":{"url":"https://api.github.com/repos/FreedomCoop/valuenetwork/issues/130","repository_url":"https://api.github.com/repos/FreedomCoop/valuenetwork","labels_url":"https://api.github.com/repos/FreedomCoop/valuenetwork/issues/130/labels{/name}","comments_url":"https://api.github.com/repos/FreedomCoop/valuenetwork/issues/130/comments","events_url":"https://api.github.com/repos/FreedomCoop/valuenetwork/issues/130/events","html_url":"https://github.com/FreedomCoop/valuenetwork/issues/130","id":173638458,"number":130,"title":"Should resource types, exchange types, patterns be tied to contexts like projects?","user":{"login":"bhaugen","id":117439,"avatar_url":"https://avatars.githubusercontent.com/u/117439?v=3","gravatar_id":"","url":"https://api.github.com/users/bhaugen","html_url":"https://github.com/bhaugen","followers_url":"https://api.github.com/users/bhaugen/followers","following_url":"https://api.github.com/users/bhaugen/following{/other_user}","gists_url":"https://api.github.com/users/bhaugen/gists{/gist_id}","starred_url":"https://api.github.com/users/bhaugen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bhaugen/subscriptions","organizations_url":"https://api.github.com/users/bhaugen/orgs","repos_url":"https://api.github.com/users/bhaugen/repos","events_url":"https://api.github.com/users/bhaugen/events{/privacy}","received_events_url":"https://api.github.com/users/bhaugen/received_events","type":"User","site_admin":false},"labels":[{"id":484515841,"url":"https://api.github.com/repos/FreedomCoop/valuenetwork/labels/This%20sprint","name":"This sprint","color":"d93f0b","default":false}],"state":"open","locked":false,"assignee":{"login":"bum2","id":7437454,"avatar_url":"https://avatars.githubusercontent.com/u/7437454?v=3","gravatar_id":"","url":"https://api.github.com/users/bum2","html_url":"https://github.com/bum2","followers_url":"https://api.github.com/users/bum2/followers","following_url":"https://api.github.com/users/bum2/following{/other_user}","gists_url":"https://api.github.com/users/bum2/gists{/gist_id}","starred_url":"https://api.github.com/users/bum2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bum2/subscriptions","organizations_url":"https://api.github.com/users/bum2/orgs","repos_url":"https://api.github.com/users/bum2/repos","events_url":"https://api.github.com/users/bum2/events{/privacy}","received_events_url":"https://api.github.com/users/bum2/received_events","type":"User","site_admin":false},"assignees":[{"login":"bum2","id":7437454,"avatar_url":"https://avatars.githubusercontent.com/u/7437454?v=3","gravatar_id":"","url":"https://api.github.com/users/bum2","html_url":"https://github.com/bum2","followers_url":"https://api.github.com/users/bum2/followers","following_url":"https://api.github.com/users/bum2/following{/other_user}","gists_url":"https://api.github.com/users/bum2/gists{/gist_id}","starred_url":"https://api.github.com/users/bum2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bum2/subscriptions","organizations_url":"https://api.github.com/users/bum2/orgs","repos_url":"https://api.github.com/users/bum2/repos","events_url":"https://api.github.com/users/bum2/events{/privacy}","received_events_url":"https://api.github.com/users/bum2/received_events","type":"User","site_admin":false}],"milestone":null,"comments":31,"created_at":"2016-08-28T09:47:18Z","updated_at":"2016-11-21T20:06:46Z","closed_at":null,"body":"By \"context\", I mean \"context agent\", like project, cooperative, group, etc.\n\nAs of now, they are not. Resource types apply to all contexts. That is necessary if different contexts want to trade with each other.\n\nIt may also be useful to have a set of common resource types that each context does not need to re-invent.\n\nBut it can also be confusing, and if a commonly-used resource type gets changed by one project, that can affect other projects.\n\nPossible changes could be:\n- tie all resource types to a context, and limit their use to that context, or\n- optionally tie resource types to contexts, and allow others to be usable by all contexts, but changes to the common resource types could only be made by Freedom Coop admins.\n"},"comment":{"url":"https://api.github.com/repos/FreedomCoop/valuenetwork/issues/comments/262051801","html_url":"https://github.com/FreedomCoop/valuenetwork/issues/130#issuecomment-262051801","issue_url":"https://api.github.com/repos/FreedomCoop/valuenetwork/issues/130","id":262051801,"user":{"login":"bum2","id":7437454,"avatar_url":"https://avatars.githubusercontent.com/u/7437454?v=3","gravatar_id":"","url":"https://api.github.com/users/bum2","html_url":"https://github.com/bum2","followers_url":"https://api.github.com/users/bum2/followers","following_url":"https://api.github.com/users/bum2/following{/other_user}","gists_url":"https://api.github.com/users/bum2/gists{/gist_id}","starred_url":"https://api.github.com/users/bum2/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bum2/subscriptions","organizations_url":"https://api.github.com/users/bum2/orgs","repos_url":"https://api.github.com/users/bum2/repos","events_url":"https://api.github.com/users/bum2/events{/privacy}","received_events_url":"https://api.github.com/users/bum2/received_events","type":"User","site_admin":false},"created_at":"2016-11-21T20:06:46Z","updated_at":"2016-11-21T20:06:46Z","body":"> Unfortunately I don't see any way to try to do this with any global piece, because the model is too interconnected. Either everything is global, or everything is context agent related. \r\n\r\nThen is going to be everything 'context agent related', but not isolated one from the other because most of the things will be related general contexts, so inherited by all childs.\r\n\r\n> I think I am missing something on the trees of agent relationships. It is a cool UI concept, but I am missing the use case for it. Is it about traveling the relationships for notifying other agents about new resource types, etc?\r\n\r\nYes, one use case is for notifying other agents or the parent project coordinators about new types, but is just to make clear the different behaviors or kinds of relations. Sometimes we have to reach the parent of a project, so as they can be many parents, we can choose the kind of relation to narrow a subset. These ui trees i propose are indended at admin level just to see the relation-kinds clear and navigate with any of the trees. Of course is nothing urgent, just another todo. The point about this is that i was puzzleing my mind around these relation types and their grouping (behaviors), and the role of the 'child' behavior (or 'node'), different from the 'member' behavior (or 'participant'). What is supposed to be the difference?\r\nI'm assuming the 'member' relation is somewhat more 'official', like membership or being part of a commission or project, and the 'child' relation is a more general relation, like being into a sector or another of activity or being a node in a network. If we do this diferentiation, maybe we need to edit actual ocp data or duplicate relations (one with child, one with participant, with the same parent) to achieve what we want. \r\nI think is good to have this 4 behavior groups i propose (and the agent trees they generate), so\r\n"}}
{"actor":{"display_login":"bum2"}}