You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To implement support for some sort of "embargo" period for requests.
Context
One feature that was added on top of the original fork was an embargo period. As noted in the website's FAQ:
Yes, we recognize that reporters and others may have an interest in not immediately disclosing a request and any documents received in response to that request. You control whether a request and any government response is released publicly for up to 1 year after the request. When making the request, uncheck the box stating “This request is public.” If you do not uncheck the box when making the request, your request will be publicly disclosed on the Internet as soon as it is made.
We should investigate whether or not this feature is something we want to reimplement (basically does the above reasoning still apply), and whether or not we want to take a more granular approach (embargo requests for 1 week, 1 month, ...etc).
Tasks
Figure out the granularity of embargo periods we should support
Basically, one path forward for this task would be to find a way to define tasks to show up in the periodic task list, define a crontab schedule for tasks to run, and tie that schedule to the defined task.
Other interesting things to look at might be a make_public_num_days_after_due_date variable supported by Froide. I couldn't find any documentation on what this means/does (we actually use it in CodeWithAloha/uipamaster here as well, but I'm wondering if we are overloading it's intended use and it's meant to be used for something else.
Objective
To implement support for some sort of "embargo" period for requests.
Context
One feature that was added on top of the original fork was an embargo period. As noted in the website's FAQ:
We should investigate whether or not this feature is something we want to reimplement (basically does the above reasoning still apply), and whether or not we want to take a more granular approach (embargo requests for 1 week, 1 month, ...etc).
Tasks
Success Criteria
Requests can be successfully embargoed.
Related Items
Parent Epic: #50
The text was updated successfully, but these errors were encountered: