Page Comparison

...

Overrides/Supersedes 

When applicable, provide links to all DRs that this DR overrides or supersedes 

RFC 

Provide links to all relevant RFC's

Stakeholders

@mention individual(s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decision

Contributors

List individual(s) sposnoring/advocating for the decisionThis decision was migrated from the Tech Leads Decision Log as part of a consolidation process.  The original decision record can be found here.

RFC 

N/A

Stakeholders

VBar Matt Reno Vasily Gancharov 

Contributors

Craig McNally

Approvers

This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.

Background/Context Explain the need that triggered the need for making a decision

A new process has been put in place to help determine the personal data being stored by FOLIO.  The process involves filling out a PERSONAL_DATA_DISCLOSURE.md form and placing it at the top level of each module's github repository.  Of course it must also be maintained thereafter as changes are made in the module.

Assumptions

N/A

Constraints

N/A

Rationale

N/A

Decision

...

All modules must have a completed PERSONAL_DATA_DISCLOSURE.md file at the top-level of their GitHub repository.

Implications

• Pros
  • N/A
• Cons
  • N/A

Other Related Resources

• Technical Council meeting notes:  
  • 2020-11-11 Tech Council Meeting Minutes 
  • 2020-11-18 Tech Council Meeting Minutes
• Additional Details: https://github.com/folio-org/personal-data-disclosure
• Related JIRAs:
  • Image AddedUXPROD-2831 - Fill in and place the personal data disclosure form in all module repositories CLOSED