From bac0317417218d429cc48e435e6f5fece8a989b7 Mon Sep 17 00:00:00 2001 From: "J. George" Date: Tue, 5 Mar 2024 07:26:06 +0100 Subject: [PATCH 1/3] Revert "Revert "Next chair person"" This reverts commit a028f0c5dde49fc6298bbd278fed03af6621ac88. --- decisions/0015-code-stability-versioning | 28 ++++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 decisions/0015-code-stability-versioning diff --git a/decisions/0015-code-stability-versioning b/decisions/0015-code-stability-versioning new file mode 100644 index 0000000..43480d0 --- /dev/null +++ b/decisions/0015-code-stability-versioning @@ -0,0 +1,28 @@ +# Materials Project Software Foundation Mission Statement + +## Context and Problem Statement + +Many projects are built directly on core Materials Project codes. Changes in our core codes will directly affect many other software projects. This applies in particular to breaking changes. It is therefore very important to have a certain code stability and regularity with regard to the versions. + +## Decision drivers +- It is very difficult for individual developers to take changes in other codes into account. In some cases, changes in codes influence each other extremely strongly and require multiple adjustments. +- We would like to keep the workload minimal +- We would like to have many users of our codes and encourage developments based on our codes. +- Keeping track of compatible versions of software packages + +## Considered Options +1. Update individual code requirements + - Other codes have to be considered to avoid the issues described above +2. Build a meta package including the most relevant MP codes, including a requirement file + - requires additional work + - Potentially similar effort to make packages compatible as currently + - additional tests could be run to check compatibility of codes + - Compatible versions could be tracked +3. Build a meta package including the most relevant MP codes, including a requirement file, and link to MP data generation + - workload would be very high + - hard to communicate that database building and data generation have not happened with the same software versions + + +## Decision Outcome + +Proposal X was adopted by unanimous consent on January 9, 2023 From 9a83049a18dd301758961b60094daed3bcf3a20f Mon Sep 17 00:00:00 2001 From: "J. George" Date: Tue, 5 Mar 2024 10:46:11 +0100 Subject: [PATCH 2/3] Update 0015-code-stability-versioning --- decisions/0015-code-stability-versioning | 1 + 1 file changed, 1 insertion(+) diff --git a/decisions/0015-code-stability-versioning b/decisions/0015-code-stability-versioning index 43480d0..6ee1b79 100644 --- a/decisions/0015-code-stability-versioning +++ b/decisions/0015-code-stability-versioning @@ -9,6 +9,7 @@ Many projects are built directly on core Materials Project codes. Changes in our - We would like to keep the workload minimal - We would like to have many users of our codes and encourage developments based on our codes. - Keeping track of compatible versions of software packages +- Evaluation of a Prototype of a meta package ## Considered Options 1. Update individual code requirements From 8af7081908417e1f12f981a5fbcb3fa55e2f17b1 Mon Sep 17 00:00:00 2001 From: "J. George" Date: Sun, 12 May 2024 00:36:55 +0200 Subject: [PATCH 3/3] Rename 0015-code-stability-versioning to 0024-code-stability-versioning --- ...5-code-stability-versioning => 0024-code-stability-versioning} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename decisions/{0015-code-stability-versioning => 0024-code-stability-versioning} (100%) diff --git a/decisions/0015-code-stability-versioning b/decisions/0024-code-stability-versioning similarity index 100% rename from decisions/0015-code-stability-versioning rename to decisions/0024-code-stability-versioning