From e0cc257356c4558dbd9942e20f65e58963f2f07b Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Thu, 7 Aug 2025 17:00:22 -0700 Subject: [PATCH 01/10] start with an example --- proposals/1_BASE64_ENCODING.md | 24 +++++++++++++++++ proposals/README.md | 47 +++++++++++++++++++++++++++++++++ proposals/_PROPOSAL_TEMPLATE.md | 22 +++++++++++++++ 3 files changed, 93 insertions(+) create mode 100644 proposals/1_BASE64_ENCODING.md create mode 100644 proposals/README.md create mode 100644 proposals/_PROPOSAL_TEMPLATE.md diff --git a/proposals/1_BASE64_ENCODING.md b/proposals/1_BASE64_ENCODING.md new file mode 100644 index 000000000..cb91ec0a4 --- /dev/null +++ b/proposals/1_BASE64_ENCODING.md @@ -0,0 +1,24 @@ +# Proposal + +--- +Author: Julien Le Dem +Created: 2025-Aug-7 +Name: add BASE64 compression +Issue: https://github.com/apache/parquet-format/issues/NNN +Status: ARCHIVED +Reason: Did not compress +--- + +## Description +Add Base64 to compression algorithms. +This is not backwards compatible as a new compression alg. + +## Spec + +See [BASE64 spec]. + +## Evaluation + +After trying out in the java implementation, file size doubled on average. +See prototype [here](github.com/julienledem/mypoc) + diff --git a/proposals/README.md b/proposals/README.md new file mode 100644 index 000000000..24445f524 --- /dev/null +++ b/proposals/README.md @@ -0,0 +1,47 @@ +# Proposals + +## Requirements + +See the [requirements document](https://docs.google.com/document/d/1qGDnOyoNyPvcN4FCRhbZGAvp0SfewlWo-WVsai5IKUo/edit?tab=t.0#heading=h.v4emiipkghrx) (Note: this doc would become a markdown page in the repo) + +## Proposal lifecycle + +Discuss -> Draft -> POC -> Approved -> Implementation -> Release + +### Discuss +Start a [DISCUSS] thread on the mailing list (dev@parquet.apache.org) with your idea. +Once you have a better idea of the direction, open a github issue using the proposal template. +You can attach a google doc to collaborate on the general idea with the community. + +### Draft +Once the discussion has stabilized and you are ready to start a POC, open a PR to add a new Markdown file in the proposals folder and give more visibility to the work in progress. + +### POC +The proposal document can evolve along the course of the POC. In particular to add more links to findings and performance evaluations. Collaboration is encouraged. More validation on the POC increases the chances of success. + +Make sure you consider the [#Requirements] to ensure the success of the POC. + +### Approved for Implementation +Once the POC has concluded, we should have a clear idea of whether we want to pursue the implementation accross the ecosystem. A PMC vote will formalize that stage + +### Implementation +At this stage we need to meet the contribution guidelines to confsider the implementation finished (ex: two independent implementations with cross compatibility tests, spec updated, ...) + +### Release +Once the implementation phase is finished, we can include the contribution in the next release. + +## Active Proposals + +| ID | Description | Status | +| [github issue] | adding this new encoding | POC | +| [github issue] | add Variant typea | Implementation | + +## Implemented + | ID | Description | Status | release it was added | +| [gihub issue] | encryption | Completed | x.y.z | + +## Archived + +| ID | Description | Status | reason for archiving | +| [github issue] | [adding base64 compression](1_BASE64_ENCODING.md) | Archived | POC showed that compression ratio was not practical | + diff --git a/proposals/_PROPOSAL_TEMPLATE.md b/proposals/_PROPOSAL_TEMPLATE.md new file mode 100644 index 000000000..f33b3ee2d --- /dev/null +++ b/proposals/_PROPOSAL_TEMPLATE.md @@ -0,0 +1,22 @@ +# Proposal + +--- +Author: ~your name~ +Created: ~date~ +Name: *short sentence describing the proposal* +Issue: https://github.com/apache/parquet-format/issues/NNN +Status: DRAFT|POC|ACCEPTED|COMPLETED +--- + +## Description +*Short description of the proposal. Is it a new encoding? Is it backwards compatible (old readers will just ignore it)? Is it additional metadata?* + +## Spec + +At the proposal stage you don't need a fully fleshed out spec yet. +Please add any link to relevant documentation, papers, etc. +at the implementation stage, the details will need to be all clarified. + +## Evaluation +What datasets is it tested on and what is a success criteria +Please add any link to the relevant codebase. From faf6b23eacff1ea72558af6066773bc4d3537d75 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Thu, 7 Aug 2025 17:04:31 -0700 Subject: [PATCH 02/10] Update 1_BASE64_ENCODING.md --- proposals/1_BASE64_ENCODING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/1_BASE64_ENCODING.md b/proposals/1_BASE64_ENCODING.md index cb91ec0a4..1c60f6b92 100644 --- a/proposals/1_BASE64_ENCODING.md +++ b/proposals/1_BASE64_ENCODING.md @@ -1,5 +1,3 @@ -# Proposal - --- Author: Julien Le Dem Created: 2025-Aug-7 @@ -9,6 +7,8 @@ Status: ARCHIVED Reason: Did not compress --- +# Proposal + ## Description Add Base64 to compression algorithms. This is not backwards compatible as a new compression alg. From ae98d5df7f51311086e8d0e926c84775140680e4 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Thu, 7 Aug 2025 17:08:34 -0700 Subject: [PATCH 03/10] Update README.md --- proposals/README.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/proposals/README.md b/proposals/README.md index 24445f524..0f8c882de 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -32,16 +32,19 @@ Once the implementation phase is finished, we can include the contribution in th ## Active Proposals -| ID | Description | Status | +| ID | Description | Status | +|-----|--------------|---------| | [github issue] | adding this new encoding | POC | -| [github issue] | add Variant typea | Implementation | +| [github issue] | add Variant type | Implementation | ## Implemented - | ID | Description | Status | release it was added | +| ID | Description | Status | release it was added | +|-----|--------------|---------|-----------------------| | [gihub issue] | encryption | Completed | x.y.z | ## Archived -| ID | Description | Status | reason for archiving | +| ID | Description | Status | reason for archiving | +|-----|--------------|---------|-----------------------| | [github issue] | [adding base64 compression](1_BASE64_ENCODING.md) | Archived | POC showed that compression ratio was not practical | From 3d0eb6f425bccb57cdc0199476c3465e31a6637c Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Fri, 29 Aug 2025 15:40:28 -0700 Subject: [PATCH 04/10] Update README.md integrated review feedback --- proposals/README.md | 34 +++++++++++++++++++--------------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/proposals/README.md b/proposals/README.md index 0f8c882de..6ae792072 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -1,34 +1,38 @@ # Proposals -## Requirements - -See the [requirements document](https://docs.google.com/document/d/1qGDnOyoNyPvcN4FCRhbZGAvp0SfewlWo-WVsai5IKUo/edit?tab=t.0#heading=h.v4emiipkghrx) (Note: this doc would become a markdown page in the repo) +This proposal process is intended for significantly impactfull additions to the Parquet spec. The goal is to facilitate those projects and help them being contributed to Parquet. +For example, changes that are not backward compatible like adding a new encoding or a new compression algorithm (older implementations can not read new files). +This gives better visibility to those projects which require coordination in several implementations. +Bug fixes, code only features or minor changes to the spec that can be ignored by older implementations can simply be filed as a github issue. ## Proposal lifecycle -Discuss -> Draft -> POC -> Approved -> Implementation -> Release +Discuss -> Draft/POC -> Implementation -> Release ### Discuss -Start a [DISCUSS] thread on the mailing list (dev@parquet.apache.org) with your idea. -Once you have a better idea of the direction, open a github issue using the proposal template. -You can attach a google doc to collaborate on the general idea with the community. +Start a [DISCUSS] thread on the mailing list (dev@parquet.apache.org) with your idea. At this point, the community can discuss whether the impact of the proposal requires a document here or just be a github issue. +Once you have a better idea of the general consensus on the proposal, open a github issue using the proposal template. +Attaching a google doc to collect feedback and collaborate with the community works usually well early on. -### Draft -Once the discussion has stabilized and you are ready to start a POC, open a PR to add a new Markdown file in the proposals folder and give more visibility to the work in progress. +*Transition:* Once you feel you received enough feedback or need to start the POC to have better answers to questions you get, you can move to the next step. Anybody is free to start POCs anytime. We just recommend getting feedback before you spend a significant amount of your time. -### POC +### Draft/POC +Once you feel the discussion has stabilized and you are ready to start a POC, open a PR to add a new Markdown file in the proposals folder and give more visibility to the work in progress. The proposal document can evolve along the course of the POC. In particular to add more links to findings and performance evaluations. Collaboration is encouraged. More validation on the POC increases the chances of success. -Make sure you consider the [#Requirements] to ensure the success of the POC. +Make sure you consider the [requirements document](https://docs.google.com/document/d/1qGDnOyoNyPvcN4FCRhbZGAvp0SfewlWo-WVsai5IKUo/edit?tab=t.0#heading=h.v4emiipkghrx) to ensure the success of the POC. (Note: this doc would become a markdown page in the repo) -### Approved for Implementation -Once the POC has concluded, we should have a clear idea of whether we want to pursue the implementation accross the ecosystem. A PMC vote will formalize that stage +*Transition:* There is enough clarity on the spec for the new feature and we have identified the reference implementations to be implemented to be able to release. ### Implementation -At this stage we need to meet the contribution guidelines to confsider the implementation finished (ex: two independent implementations with cross compatibility tests, spec updated, ...) +Once we have reached enough consensus on the formalized spec change and validated it through the POC, we should have a clear idea of whether we want to pursue the implementation accross the ecosystem. +At this stage we should finalize a formal spec contribution to parquet-format and we need to meet the contribution guidelines to consider the implementation finished. +See [CONTRIBUTING guidelines](https://github.com/apache/parquet-format/blob/master/CONTRIBUTING.md#additionschanges-to-the-format). + +*Transition:* A PMC vote will formalize that we have concluded the implementation and are ready to release. ### Release -Once the implementation phase is finished, we can include the contribution in the next release. +Once the implementation phase is finished, we can include the contribution in the next release. Congrats! ## Active Proposals From edb8e82041eb0133180db9532f6d4d22bfd802d5 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Fri, 29 Aug 2025 15:42:30 -0700 Subject: [PATCH 05/10] Update _PROPOSAL_TEMPLATE.md integrated review feedback --- proposals/_PROPOSAL_TEMPLATE.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/proposals/_PROPOSAL_TEMPLATE.md b/proposals/_PROPOSAL_TEMPLATE.md index f33b3ee2d..6329d050d 100644 --- a/proposals/_PROPOSAL_TEMPLATE.md +++ b/proposals/_PROPOSAL_TEMPLATE.md @@ -5,12 +5,15 @@ Author: ~your name~ Created: ~date~ Name: *short sentence describing the proposal* Issue: https://github.com/apache/parquet-format/issues/NNN -Status: DRAFT|POC|ACCEPTED|COMPLETED +Status: DRAFT|IMPLEMENTATION|COMPLETED --- ## Description *Short description of the proposal. Is it a new encoding? Is it backwards compatible (old readers will just ignore it)? Is it additional metadata?* +## Rationale +Describe why this is a feature that will improve the parquet format and what alternatives currently exist for the usecase (e.g. must use a different format, or "must build additional infrastructure to avoid re-parsing footer on each query", or "must use a general purpose compression algorithm to achieve the same space, thus slowing down query performance) + ## Spec At the proposal stage you don't need a fully fleshed out spec yet. From 51a4a3ff417433085577a7dd3c2535eb1498c0b2 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Fri, 29 Aug 2025 15:47:24 -0700 Subject: [PATCH 06/10] Update README.md add review feedback --- proposals/README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/proposals/README.md b/proposals/README.md index 6ae792072..b24431f88 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -7,7 +7,7 @@ Bug fixes, code only features or minor changes to the spec that can be ignored b ## Proposal lifecycle -Discuss -> Draft/POC -> Implementation -> Release +Discuss -> Draft/POC -> Implementation -> Approval ### Discuss Start a [DISCUSS] thread on the mailing list (dev@parquet.apache.org) with your idea. At this point, the community can discuss whether the impact of the proposal requires a document here or just be a github issue. @@ -20,6 +20,8 @@ Attaching a google doc to collect feedback and collaborate with the community wo Once you feel the discussion has stabilized and you are ready to start a POC, open a PR to add a new Markdown file in the proposals folder and give more visibility to the work in progress. The proposal document can evolve along the course of the POC. In particular to add more links to findings and performance evaluations. Collaboration is encouraged. More validation on the POC increases the chances of success. +Example: [https://github.com/apache/parquet-format/pull/221] + Make sure you consider the [requirements document](https://docs.google.com/document/d/1qGDnOyoNyPvcN4FCRhbZGAvp0SfewlWo-WVsai5IKUo/edit?tab=t.0#heading=h.v4emiipkghrx) to ensure the success of the POC. (Note: this doc would become a markdown page in the repo) *Transition:* There is enough clarity on the spec for the new feature and we have identified the reference implementations to be implemented to be able to release. @@ -31,7 +33,7 @@ See [CONTRIBUTING guidelines](https://github.com/apache/parquet-format/blob/mast *Transition:* A PMC vote will formalize that we have concluded the implementation and are ready to release. -### Release +### Approval Once the implementation phase is finished, we can include the contribution in the next release. Congrats! ## Active Proposals From 9cdce64d29038403b817f917bdfcea7f9f999782 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Tue, 23 Sep 2025 10:44:41 -0700 Subject: [PATCH 07/10] fix spelling and address feedback. Co-authored-by: Marc Cenac <547446+mrcnc@users.noreply.github.com> --- proposals/README.md | 10 +++++----- proposals/_PROPOSAL_TEMPLATE.md | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/proposals/README.md b/proposals/README.md index b24431f88..b1b9a36c0 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -1,7 +1,7 @@ # Proposals -This proposal process is intended for significantly impactfull additions to the Parquet spec. The goal is to facilitate those projects and help them being contributed to Parquet. -For example, changes that are not backward compatible like adding a new encoding or a new compression algorithm (older implementations can not read new files). +This proposal process is intended for significantly impactful additions to the Parquet spec. The goal is to facilitate those projects and help them being contributed to Parquet. +For example, changes that are not forward compatible like adding a new encoding or a new compression algorithm (older implementations can not read new files). [see guidelines for more details](https://github.com/apache/parquet-format/blob/master/CONTRIBUTING.md#general-guidelinespreferences-on-additions) This gives better visibility to those projects which require coordination in several implementations. Bug fixes, code only features or minor changes to the spec that can be ignored by older implementations can simply be filed as a github issue. @@ -17,7 +17,7 @@ Attaching a google doc to collect feedback and collaborate with the community wo *Transition:* Once you feel you received enough feedback or need to start the POC to have better answers to questions you get, you can move to the next step. Anybody is free to start POCs anytime. We just recommend getting feedback before you spend a significant amount of your time. ### Draft/POC -Once you feel the discussion has stabilized and you are ready to start a POC, open a PR to add a new Markdown file in the proposals folder and give more visibility to the work in progress. +Once you feel the discussion has stabilized and you are ready to start a POC, open a PR to add the proposal to the table in the [Active Proposals](#active-proposals) section bellow. Link all relevant discussion documents in the body of the corresponding github issue. If using google docs, make sure docs are owned by an account that will maintain them publicly (preffer personal account over a work account). Alternativaly you can create a new Markdown file in the proposals folder and give more visibility to the work in progress (see [the example](1_BASE64_ENCODING.md) ). The proposal document can evolve along the course of the POC. In particular to add more links to findings and performance evaluations. Collaboration is encouraged. More validation on the POC increases the chances of success. Example: [https://github.com/apache/parquet-format/pull/221] @@ -27,7 +27,7 @@ Make sure you consider the [requirements document](https://docs.google.com/docum *Transition:* There is enough clarity on the spec for the new feature and we have identified the reference implementations to be implemented to be able to release. ### Implementation -Once we have reached enough consensus on the formalized spec change and validated it through the POC, we should have a clear idea of whether we want to pursue the implementation accross the ecosystem. +Once we have reached enough consensus on the formalized spec change and validated it through the POC, we should have a clear idea of whether we want to pursue the implementation across the ecosystem. At this stage we should finalize a formal spec contribution to parquet-format and we need to meet the contribution guidelines to consider the implementation finished. See [CONTRIBUTING guidelines](https://github.com/apache/parquet-format/blob/master/CONTRIBUTING.md#additionschanges-to-the-format). @@ -46,7 +46,7 @@ Once the implementation phase is finished, we can include the contribution in th ## Implemented | ID | Description | Status | release it was added | |-----|--------------|---------|-----------------------| -| [gihub issue] | encryption | Completed | x.y.z | +| [github issue] | encryption | Completed | x.y.z | ## Archived diff --git a/proposals/_PROPOSAL_TEMPLATE.md b/proposals/_PROPOSAL_TEMPLATE.md index 6329d050d..229fe8eac 100644 --- a/proposals/_PROPOSAL_TEMPLATE.md +++ b/proposals/_PROPOSAL_TEMPLATE.md @@ -12,7 +12,7 @@ Status: DRAFT|IMPLEMENTATION|COMPLETED *Short description of the proposal. Is it a new encoding? Is it backwards compatible (old readers will just ignore it)? Is it additional metadata?* ## Rationale -Describe why this is a feature that will improve the parquet format and what alternatives currently exist for the usecase (e.g. must use a different format, or "must build additional infrastructure to avoid re-parsing footer on each query", or "must use a general purpose compression algorithm to achieve the same space, thus slowing down query performance) +Describe why this is a feature that will improve the parquet format and what alternatives currently exist for the use case (e.g. must use a different format, or "must build additional infrastructure to avoid re-parsing footer on each query", or "must use a general purpose compression algorithm to achieve the same space, thus slowing down query performance") ## Spec From ef310c3223744bb82bdb6d661a64e5b405bb22a9 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Tue, 23 Sep 2025 11:06:10 -0700 Subject: [PATCH 08/10] add license header Signed-off-by: Julien Le Dem --- proposals/1_BASE64_ENCODING.md | 18 ++++++++++++++++++ proposals/README.md | 18 ++++++++++++++++++ proposals/_PROPOSAL_TEMPLATE.md | 18 ++++++++++++++++++ 3 files changed, 54 insertions(+) diff --git a/proposals/1_BASE64_ENCODING.md b/proposals/1_BASE64_ENCODING.md index 1c60f6b92..bd0a58ff0 100644 --- a/proposals/1_BASE64_ENCODING.md +++ b/proposals/1_BASE64_ENCODING.md @@ -1,3 +1,21 @@ + --- Author: Julien Le Dem Created: 2025-Aug-7 diff --git a/proposals/README.md b/proposals/README.md index b1b9a36c0..e729e5d9d 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -1,3 +1,21 @@ + # Proposals This proposal process is intended for significantly impactful additions to the Parquet spec. The goal is to facilitate those projects and help them being contributed to Parquet. diff --git a/proposals/_PROPOSAL_TEMPLATE.md b/proposals/_PROPOSAL_TEMPLATE.md index 229fe8eac..b55fa1011 100644 --- a/proposals/_PROPOSAL_TEMPLATE.md +++ b/proposals/_PROPOSAL_TEMPLATE.md @@ -1,3 +1,21 @@ + # Proposal --- From 39c6fd9f23a2c67bdb726011b4299b6760fd633b Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Thu, 25 Sep 2025 11:29:16 -0700 Subject: [PATCH 09/10] Update proposals/1_BASE64_ENCODING.md Update proposals/README.md Co-authored-by: Andrew Lamb --- proposals/1_BASE64_ENCODING.md | 2 ++ proposals/README.md | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/proposals/1_BASE64_ENCODING.md b/proposals/1_BASE64_ENCODING.md index bd0a58ff0..be88f8639 100644 --- a/proposals/1_BASE64_ENCODING.md +++ b/proposals/1_BASE64_ENCODING.md @@ -27,6 +27,8 @@ Reason: Did not compress # Proposal +**NOTE**: This is an example proposal for use as a template + ## Description Add Base64 to compression algorithms. This is not backwards compatible as a new compression alg. diff --git a/proposals/README.md b/proposals/README.md index e729e5d9d..d07253b8b 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -29,7 +29,7 @@ Discuss -> Draft/POC -> Implementation -> Approval ### Discuss Start a [DISCUSS] thread on the mailing list (dev@parquet.apache.org) with your idea. At this point, the community can discuss whether the impact of the proposal requires a document here or just be a github issue. -Once you have a better idea of the general consensus on the proposal, open a github issue using the proposal template. +Once you have a better idea of the general consensus on the proposal, open a github issue using the [proposal template](proposals/1_BASE64_ENCODING.md) Attaching a google doc to collect feedback and collaborate with the community works usually well early on. *Transition:* Once you feel you received enough feedback or need to start the POC to have better answers to questions you get, you can move to the next step. Anybody is free to start POCs anytime. We just recommend getting feedback before you spend a significant amount of your time. @@ -42,7 +42,7 @@ Example: [https://github.com/apache/parquet-format/pull/221] Make sure you consider the [requirements document](https://docs.google.com/document/d/1qGDnOyoNyPvcN4FCRhbZGAvp0SfewlWo-WVsai5IKUo/edit?tab=t.0#heading=h.v4emiipkghrx) to ensure the success of the POC. (Note: this doc would become a markdown page in the repo) -*Transition:* There is enough clarity on the spec for the new feature and we have identified the reference implementations to be implemented to be able to release. +*Transition:* There is enough clarity on the spec for the new feature and we have identified the 2 initial reference implementations for verification. ### Implementation Once we have reached enough consensus on the formalized spec change and validated it through the POC, we should have a clear idea of whether we want to pursue the implementation across the ecosystem. From 7e3cb6af24e0b1f5e54497a14725fc7d4ae117b1 Mon Sep 17 00:00:00 2001 From: Julien Le Dem Date: Thu, 25 Sep 2025 11:45:35 -0700 Subject: [PATCH 10/10] fix readme Signed-off-by: Julien Le Dem --- proposals/README.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/proposals/README.md b/proposals/README.md index d07253b8b..fa7aa2f31 100644 --- a/proposals/README.md +++ b/proposals/README.md @@ -29,7 +29,7 @@ Discuss -> Draft/POC -> Implementation -> Approval ### Discuss Start a [DISCUSS] thread on the mailing list (dev@parquet.apache.org) with your idea. At this point, the community can discuss whether the impact of the proposal requires a document here or just be a github issue. -Once you have a better idea of the general consensus on the proposal, open a github issue using the [proposal template](proposals/1_BASE64_ENCODING.md) +Once you have a better idea of the general consensus on the proposal, open a github issue using the [proposal template](proposals/_PROPOSAL_TEMPLATE.md) Attaching a google doc to collect feedback and collaborate with the community works usually well early on. *Transition:* Once you feel you received enough feedback or need to start the POC to have better answers to questions you get, you can move to the next step. Anybody is free to start POCs anytime. We just recommend getting feedback before you spend a significant amount of your time. @@ -61,14 +61,19 @@ Once the implementation phase is finished, we can include the contribution in th | [github issue] | adding this new encoding | POC | | [github issue] | add Variant type | Implementation | +(Those are examples to be removed as we start using this) + ## Implemented | ID | Description | Status | release it was added | |-----|--------------|---------|-----------------------| | [github issue] | encryption | Completed | x.y.z | +(Those are examples to be removed as we start using this) + ## Archived | ID | Description | Status | reason for archiving | |-----|--------------|---------|-----------------------| | [github issue] | [adding base64 compression](1_BASE64_ENCODING.md) | Archived | POC showed that compression ratio was not practical | +(Those are examples to be removed as we start using this)