DR - FAQs

What kind of decisions are documented as Decision Records (DR)?

Decisions at any level can be captured/logged here From high level/architectural to low level/design.

What are significant architectural decisions ?

An architecturally significant decision is something that has a measurable effect on the application architecture's llities such as

- Usability
- Reliability
- Availability
- Portability
- Testability
- Scalability
- Flexibility
- Reusability
- Maintainability
- Supportability
- Interoperability
- Performance
- Security

Who can create/edit the DR ?

Any who is a part of FOLIO community can create a DR for review

Who approves the DR ?

Technical Council

What is the minimum required information for getting a Decision reviewed ?

How do I need to do to get my DR reviewed and approved ?

Where can I store supporting documents?

Supporting documents of a DR can live anywhere. Wiki , Google Docs, external blog posts, articles etc. While we support having documents anywhere, it is highly recommended that most immediate/relevant information for the DR is documented in the wiki. This helps us avoid losing the content in the future for a variety of reasons. For E.g, the site is no longer available, issues related to ownership etc..

How are the decisions communicated to the larger community ?

FOLIO Community has a system demo that happens every month. The plan is have some dedicated slot for the TC to highlight some their work. This can include information about ACCEPTED decisions