From bb97d75aaa26bc7d8e796af47e59521600fb2e95 Mon Sep 17 00:00:00 2001 From: Josh Cincinnati Date: Sun, 20 Aug 2017 16:23:29 -0700 Subject: [PATCH] fixes translation working group, adds zApps working group, modifies README --- WorkingGroups/README.md | 2 +- .../{ZcashTranslation => ZcashTranslation.md} | 0 WorkingGroups/zApps.md | 24 +++++++++++++++++++ 3 files changed, 25 insertions(+), 1 deletion(-) rename WorkingGroups/{ZcashTranslation => ZcashTranslation.md} (100%) create mode 100644 WorkingGroups/zApps.md diff --git a/WorkingGroups/README.md b/WorkingGroups/README.md index 16c7a7d..c6f4587 100644 --- a/WorkingGroups/README.md +++ b/WorkingGroups/README.md @@ -14,6 +14,6 @@ Recognition Process Working groups are intended to be community-driven, indepdendent, and led by volunteers, rather than organized top-down. As such, the idea is that although the Foundation will officially "recognize" Working Groups, the Working Groups should be able to exist independently of the Foundation too. For example, a working group can exist before being recognized by the Foundation, a working group could be simultaneously recognized by some other organization as well (e.g., a WC3 working group), and a working group could continue to exist even if the Zcash Foundation withdraws recognition. -To propose a working group for recognition by Zcash Foundation, create a draft file explaining the above, and either create an issue or a pull request to this repo, or contact the. +To propose a working group for recognition by Zcash Foundation, create a draft file explaining the above, and either create an issue or a pull request to this repo. The authority to recognize working groups rests with the Zcash Foundation board, who have also authorized the President to approve a working group directly. diff --git a/WorkingGroups/ZcashTranslation b/WorkingGroups/ZcashTranslation.md similarity index 100% rename from WorkingGroups/ZcashTranslation rename to WorkingGroups/ZcashTranslation.md diff --git a/WorkingGroups/zApps.md b/WorkingGroups/zApps.md new file mode 100644 index 0000000..89b3fc9 --- /dev/null +++ b/WorkingGroups/zApps.md @@ -0,0 +1,24 @@ +zApps Working Group +========================== + +- *Coordinator:* Josh Cincinnati (interim coordinator) + +- *Forums:* This working group will initially begin as a scheduled Hangout among participants, but will eventually include a chat room on chat.zcashcommunity.com and IRL meetings/presentations as well. + +- *Statement of Purpose:* Pursuant to [issue 28](https://github.com/ZcashFoundation/ZcashFoundation/issues/28) and [issue 35](https://github.com/ZcashFoundation/ZcashFoundation/issues/35), there are many projects—blockchain related and beyond—that are potentially integrating zeroknowledge proofs and processes. To paraphrase [@nathan-at-least](https://github.com/nathan-at-least), this is a newly emerging technical field without well-established techniques, and it stands to reason that a working group could help standardize efforts, hasten development, and improve security across implementations. + +Next Steps: + - Assemble list of potential participants and directly reach out. The current outreach list includes: + - Filecoin + - Ethereum + - Chronicled + - Qedit + - Tezos + - Quorum + - Zcash Company + - Libsnark + - Schedule Hangout, including a small presentation by the Zcash Company to describe their latest work and to collect feedback from other participants + - Initiate other channels for discussion (chat.zcashcommunity.com) and highlight opportunities for mutual development. + - IRL presentation by working group at a large venue (Devcon/meetup?) + +Long Term Goal: In addition to fostering cooperation between many supporters and researchers behind zeroknowledge systems, the group would publish reports on their findings...and eventually offer services to other developers/researchers who want to build their own zeroknowledge applications (hence the *zApp* moniker).