{"action":"created","issue":{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1726","repository_url":"https://api.github.com/repos/globaleaks/GlobaLeaks","labels_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1726/labels{/name}","comments_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1726/comments","events_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1726/events","html_url":"https://github.com/globaleaks/GlobaLeaks/issues/1726","id":165947567,"number":1726,"title":"Implement specific data retention policy for unread submissions.","user":{"login":"evilaliv3","id":217034,"avatar_url":"https://avatars.githubusercontent.com/u/217034?v=3","gravatar_id":"","url":"https://api.github.com/users/evilaliv3","html_url":"https://github.com/evilaliv3","followers_url":"https://api.github.com/users/evilaliv3/followers","following_url":"https://api.github.com/users/evilaliv3/following{/other_user}","gists_url":"https://api.github.com/users/evilaliv3/gists{/gist_id}","starred_url":"https://api.github.com/users/evilaliv3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/evilaliv3/subscriptions","organizations_url":"https://api.github.com/users/evilaliv3/orgs","repos_url":"https://api.github.com/users/evilaliv3/repos","events_url":"https://api.github.com/users/evilaliv3/events{/privacy}","received_events_url":"https://api.github.com/users/evilaliv3/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/A:%20OpenWhistleblowing","name":"A: OpenWhistleblowing","color":"fbca04"},{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/C:%20Backend","name":"C: Backend","color":"eb6420"},{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/labels/F:%20Security","name":"F: Security","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-07-16T21:05:32Z","updated_at":"2016-07-17T05:31:15Z","closed_at":null,"body":"Most of the real use cases have data retention policies too broad; typical settings enable the submission to survive one year.\r\n\r\nWith this ticket I propose to add an additional specific configuration for managing automatic deletion of unread contents.\r\n\r\ni think in fact that if from one side is ok that an organization set the data retention policy to one year, t would be important to enforce in the workflow that in case of unresponsible receivers that do not read submissions the content is deleted with a more short timeout (e.g. if the data retention policy is set to 1year, the deletion of unread submissions could be set to 3months)"},"comment":{"url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/comments/233166126","html_url":"https://github.com/globaleaks/GlobaLeaks/issues/1726#issuecomment-233166126","issue_url":"https://api.github.com/repos/globaleaks/GlobaLeaks/issues/1726","id":233166126,"user":{"login":"fpietrosanti","id":770363,"avatar_url":"https://avatars.githubusercontent.com/u/770363?v=3","gravatar_id":"","url":"https://api.github.com/users/fpietrosanti","html_url":"https://github.com/fpietrosanti","followers_url":"https://api.github.com/users/fpietrosanti/followers","following_url":"https://api.github.com/users/fpietrosanti/following{/other_user}","gists_url":"https://api.github.com/users/fpietrosanti/gists{/gist_id}","starred_url":"https://api.github.com/users/fpietrosanti/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fpietrosanti/subscriptions","organizations_url":"https://api.github.com/users/fpietrosanti/orgs","repos_url":"https://api.github.com/users/fpietrosanti/repos","events_url":"https://api.github.com/users/fpietrosanti/events{/privacy}","received_events_url":"https://api.github.com/users/fpietrosanti/received_events","type":"User","site_admin":false},"created_at":"2016-07-17T05:31:15Z","updated_at":"2016-07-17T05:31:15Z","body":"Given the fact that with case management functionalities we Will have other \"states\" for the submission (from open to assigned to closed and other states), it maybe valuable to do a generic data cleaner based on tip status, with different data retention policy periods per status per context. \nThat general framework based on tip status should eventually consider that following the recommendation from The privacy authority The cleanup of data will have to be done also based on the specific sensibility of an information piece on a tip (cleanup wb identity and persons involved but not generic submission data).\n\nSent from mobile\n\n> On 17 lug 2016, at 06:05, Giovanni Pellerano <notifications@github.com> wrote:\n> \n> Most of the real use cases have data retention policies too broad; typical settings enable the submission to survive one year.\n> \n> With this ticket I propose to add an additional specific configuration for managing automatic deletion of unread contents.\n> \n> i think in fact that if from one side is ok that an organization set the data retention policy to one year, t would be important to enforce in the workflow that in case of unresponsible receivers that do not read submissions the content is deleted with a more short timeout (e.g. if the data retention policy is set to 1year, the deletion of unread submissions could be set to 3months)\n> \n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub, or mute the thread.\n> \n"}}
{"actor":{"display_login":"fpietrosanti"}}