How and Why you can and should Participate in Open Source Projects (AMIS, Software Engineering SIG, February 2022)

Editor's Notes

• #2: URLs to share: The Dapr.io open source project https://dapr.io/ The Dapr.io Components GitHub Repo https://github.com/dapr/components-contrib Dapr.io Docs on State Store Components: https://docs.dapr.io/reference/components-reference/supported-state-stores/#oracle-cloud-infrastructure-oci And Dapr.io Docs Preview 1.7 (with OCI Autonomous Database and Oracle Database): https://v1-7.docs.dapr.io/reference/components-reference/supported-state-stores/#oracle-cloud-infrastructure-oci Dapr Discord https://discord.com/invite/ptHhX6jc34 The Medium article on my open source contribution: https://medium.com/@lucasjellema/submitting-my-custom-dapr-state-component-as-a-formal-open-source-contribution-work-in-progress-a8bd3fc1ece4
• #3: https://en.wikipedia.org/wiki/Ubuntu Ubuntu is named after the Nguni philosophy of ubuntu, which Canonical indicates means "humanity to others" with a connotation of "I am what I am because of who we all are".[7]
• #31: https://github.com/dapr/components-contrib/issues/1400
• #60: https://docs.dapr.io/reference/components-reference/supported-state-stores/#oracle-cloud-infrastructure-oci
• #67: https://opensource.guide/starting-a-project/
• #81: Allow retrieval of past generations of historical state from Oracle Database State Store <!-- If you need to report a security issue please visit https://docs.dapr.io/operations/support/support-security-issues --> ## Describe the feature <!-- Please also discuss possible business value --> Through the use of a few metadata parameters in requests to get data from the state store, users of the Oracle Database State Store are able to indicate they want to retrieve state from the past, instead of the current state. They can for example ask for a specific generation (similar to HEAD~2 or HEAD~5 instruction in Git) such as the previous state or the state from five generations ago. Users can also ask for the state at a specific timestamp or the state as it existed the indicated number of seconds ago. Proposed metadata parameters: * _flashback-generation_ – values 0 (for current value), -1 (for previous value), -2 (for the one but previous value), -3...-X – to ask for a specific generation of the state under the specified key * _flashback-atTime_ – a UTC timestamp in the past - to ask for the value of the state under the specified key at a specific moment in the past * _flashback-age_– a positive integer - to ask for the value of the state under the specified key at the specified number seconds ago * _flashback-allow-deleted_ – true or false – to indicate whether a value should be returned if the key currently is deleted or expired from the state store When the state did not exist at the specified point in time (or generation) or is no longer available from the state store's flashback mechanism, the response is empty (no error) just in the case of a request for state under a key that does not occur. The response will include the following meta data parameter when the returned historical state corresponds to a state record that is in the present expired or deleted: * _flashback-deleted_ – true or false – to indicate whether the key is deleted or expired from the state store at the present moment The proposed feature leverages the Oracle Database mechanisms of Flashback Query and Flashback Versions Query. No additional setup of the database is required. This feature allows applications to track changes to a specific state element in time - and to construct a consistent picture of the world by getting all state for a specific moment in time. The retrieval of past generations can be used to resolve issues around state changes from different sources - especially when a LAST WRITE policy was used. And the feature makes it possible to rollback changes and even recover from delete and expire operations. ## Release Note <!-- How should this new feature be announced in our release notes? It can be populated later. --> <!-- Keep it as a single line. Examples: --> <!-- RELEASE NOTE: **ADD** New feature in Dapr. --> <!-- RELEASE NOTE: **FIX** Bug in runtime. --> <!-- RELEASE NOTE: **UPDATE** Runtime dependency. --> RELEASE NOTE: **ADD** Retrieval of historic state from Oracle Database state store (using metadata parameters in get state requests) 
• #82: Describe new feature in Oracle Database State Store for retrieval of historical state **What content needs to be created or modified?** <!--A clear and concise description of what the problem is. Ex. There should be docs on how pub/sub works...--> The docs for state store component based on Oracle Database should describe the functionality that allows retrieval of historic and deleted/expired state. **Describe the solution you'd like** <!--A clear and concise description of what you want to happen--> The page describing the state store component for Oracle Database must be complemented with the description of retrieving historic state in get requests. **Where should the new material be placed?** <!--Please suggest where in the docs structure the new content should be created--> Changes are needed (only) in this page daprdocs/content/en/reference/components-reference/supported-state-stores/setup-oracledatabase.md **The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos** <!-- Specify the URL to the associated pull request, if applicable For example: https://github.com/dapr/dapr/pull/3277 --> **Additional context** <!--Add any other context or screenshots about the feature request here--> 
• #89: Allow retrieval of past generations of historical state from Oracle Database State Store # Description Changes in Get request flow against the Oracle Database state store component: * four new metadata parameters are supported - to control the potential retrieval of historic and even deleted or expired state * extended unit test to validate the behavior that checks these parameters for acceptable values * extended integration test to validate the intended behavior based on the flashback metadata parameters * modified state store implementation for Oracle Database to provide the flashback behavior specified through the parameters when executing get requests Note: no impact on any of the functionality outside get-ting state from this state store. Through the use of a few metadata parameters in requests to get data from the state store, users of the Oracle Database State Store are able to indicate they want to retrieve state from the past, instead of the current state. They can for example ask for a specific generation (similar to HEAD~2 or HEAD~5 instruction in Git) such as the previous state or the state from five generations ago. Users can also ask for the state at a specific timestamp or the state as it existed the indicated number of seconds ago. Supported metadata parameters: * _flashback-generation_ – values 0 (for current value), -1 (for previous value), -2 (for the one but previous value), -3...-X – to ask for a specific generation of the state under the specified key * _flashback-atTime_ – a UTC timestamp in the past - to ask for the value of the state under the specified key at a specific moment in the past * _flashback-age_– a positive integer - to ask for the value of the state under the specified key at the specified number seconds ago * _flashback-allow-deleted_ – true or false – to indicate whether a value should be returned if the key currently is deleted or expired from the state store When the state did not exist at the specified point in time (or generation) or is no longer available from the state store's flashback mechanism, the response is empty (no error) just in the case of a request for state under a key that does not occur. The response to a get request includes the following meta data parameter when the returned historical state corresponds to a state record that is in the present expired or deleted: * _flashback-deleted_ – true or false – to indicate whether the key is deleted or expired from the state store at the present moment The implementation leverages the Oracle Database mechanisms of Flashback Query and Flashback Versions Query. No additional setup of the database is required. ## Issue reference We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation. Please reference the issue this PR will close: #_[issue number]_ ## Checklist Please make sure you've completed the relevant tasks for this PR, out of the following list: * [X] Code compiles correctly * [X] Created/updated tests * [ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#_[issue number]_ 
• #91: https://stackoverflow.com/questions/9153598/how-do-i-fetch-a-branch-on-someone-elses-fork-on-github
• #92: https://stackoverflow.com/questions/9153598/how-do-i-fetch-a-branch-on-someone-elses-fork-on-github
• #95: https://web.yammer.com/main/threads/eyJfdHlwZSI6IlRocmVhZCIsImlkIjoiMTYwMTE5MjgyNTQyMTgyNCJ9