Merge pull request #19 from cheeky-gorilla/patch-8

Grammar + consistency changes - 5-initial-pilot.md

Author: tvanepps

docs/5-initial-pilot.md

@@ -4,25 +4,25 @@
 
 To prepare for launch, there are a few tasks we wanted to properly complete:
 
-- perform an informal audit of the 0xSplits contracts by members
-- verify the 0xSplits contracts and frontend on testnet
-- deploy the 6/10 multisig, the Split contract itself, and the Vesting Module
-- onboard as many eligible Members through the process we have bootstrapped
-- broadcast the intent of the Protocol Guild to the broader community and potential sponsors, getting a precommitment of funds where possible
-- refine and document the operating process, which includes curating and deliberating on potential members, onboarding them
+- Perform an informal audit of the 0xSplits contracts by members.
+- Verify the 0xSplits contracts and frontend on testnet.
+- Deploy the 6/10 multisig, the Split contract itself, and the Vesting Module.
+- Onboard as many eligible members as possible.
+- Broadcast the intent of the Protocol Guild to the broader community and potential sponsors, including getting a precommitment of funds where possible.
+- Refine and document the operating process, which includes curating and deliberating on potential members, as well as onboarding them.
 
 ## 5.2 Pilot Characteristics
 
-As of May 8th 2022, all of the above have been completed. Here's an overview of how the Pilot is structured.
+As of May 8th 2022, all of the above tasks have been completed. What follows is an overview of how the pilot is structured.
 
 - Sponsoring assets will vest for one year (365 days) from stream initialization. Sponsoring streams may overlap with the next iteration of the vesting contract by a few months.
-- We are targeting between ~$10-20mm in sponsorships. If you're interested in being part of this initial cohort of sponsors, you can send permissionlessly to the [vesting contract 0xF29...1a9 here](https://app.0xsplits.xyz/accounts/0xF29Ff96aaEa6C9A1fBa851f74737f3c069d4f1a9/). If you or your project have questions, please reach out on [Twitter](https://twitter.com/protocolguild) or to any of the existing members.
-- We will plan to update [membership](https://protocol-guild.readthedocs.io/en/latest/9-membership.html#member-list) and [weights](https://protocol-guild.readthedocs.io/en/latest/9-membership.html#addresses-and-weights) ideally once per quarter, barring any special cases.
-- The beneficiary split has been launched with 111 beneficiary addresses - see the contract through the [0xsplits interface](https://app.0xsplits.xyz/accounts/0x84af3D5824F0390b9510440B6ABB5CC02BB68ea1/). The initial set of Pilot beneficiaries include:
-  - Diviners (Researchers / Spec Writers / Client Tinkerers): responsible for divining the future needs of the protocol
-  - Framers (Client Maintainers): In dialogue with the previous set, responsible for manifesting the best fit frameworks to hold these needs in balance with each other
-  - Guides (Ecosystem relations, client tinkerers): in dialogue with both previous sets and responsible for guiding both of their paths of divination and manifestation 
-  - the donations.0xSplits.eth address, which represents the 0xSplits team and some of their Public Goods dependencies
+- We are targeting between $10-20mm in sponsorships. If you’re interested in being part of this initial cohort of sponsors, you can permissionlessly send funds to the [vesting contract 0xF29...1a9](https://app.0xsplits.xyz/accounts/0xF29Ff96aaEa6C9A1fBa851f74737f3c069d4f1a9/). If you or your project have questions, please reach out on [Twitter](https://twitter.com/protocolguild) or to any of the existing members.
+- We will plan to update the [membership list](https://protocol-guild.readthedocs.io/en/latest/9-membership.html#member-list) and [weights](https://protocol-guild.readthedocs.io/en/latest/9-membership.html#addresses-and-weights) ideally once per quarter, barring any special cases.
+- The beneficiary split has been launched with 111 beneficiary addresses - see the contract through the [0xsplits interface](https://app.0xsplits.xyz/accounts/0x84af3D5824F0390b9510440B6ABB5CC02BB68ea1/). The initial set of pilot beneficiaries include:
+  - Diviners (Researchers / Spec Writers / Client Tinkerers): Responsible for divining the future needs of the protocol.
+  - Framers (Client Maintainers): In dialogue with the previous set, responsible for manifesting the best fit frameworks to hold these needs in balance with each other.
+  - Guides (Ecosystem relations, client tinkerers): In dialogue with both previous sets and responsible for guiding both of their paths of divination and manifestation.
+  - The donations.0xSplits.eth address, which represents the 0xSplits team and some of their public goods dependencies.
 
 ## 5.4 Documenting Process
 
@@ -37,33 +37,40 @@ As of May 8th 2022, all of the above have been completed. Here's an overview of
 
 ### Dune Dashboard
 
-An overview of Pilot finances can be explored via this Dune Analytics dashboard: [Protocol Guild Finances](https://dune.com/datamonkey_eth/protocol-guild). Thanks to [@datamonkey_eth](https://twitter.com/datamonkey_eth) for working with us to make it happen - we can strongly recommend them if your project needs data viz done!
+An overview of pilot finances can be explored via this Dune Analytics dashboard: [Protocol Guild Finances](https://dune.com/datamonkey_eth/protocol-guild). Thanks to [@datamonkey_eth](https://twitter.com/datamonkey_eth) for working with us to make it happen - we can strongly recommend them if your project needs data viz done!
 
 ## 5.3 Documenting Outcomes
 
-Throughout the pilot, special attention should be given to evaluating outcomes related to the above characteristics. The information gathered should be archived in the docs as a cohesive report for the edification of future members and operational adjustments. The  report should include the following topics:
+Throughout the pilot, special attention should be given to evaluating outcomes related to the aforementioned **Pilot Characteristics**. The information gathered should be archived in the docs as a cohesive report for the edification of future members and operational adjustments. The report should include the following topics:
 
 ### Timing
-  - Was one year the right length for a Pilot? 
-  - what should the typical vesting period be in regular operation? 
-  - What's the earliest the next iteration would launch ahead of the Pilot vest concluding?
+  - Was one year the right length for the pilot?
+  - What should the standard vesting period be post-pilot?
+  - What’s the earliest the next iteration should launch ahead of the pilot concluding?
 
 ### Funding
-  - Were funding targets hit ahead of launch? 
-  - Was the initial raise too low / high?
+  - Were funding targets hit ahead of launch?
+  - How were the funds impacted by asset price fluctuations during the pilot? 
+  - Was the initial raise too low/high?
   - Was there a healthy number and variety of sponsors?
 
-### Operating
+### Operations
   - What sort of operating procedures worked? Which ones didn't? 
   - What role did voting play in decision-making, if any? 
   - What were the best practices that emerged with regard to voting, onboarding, curation?
-  - Should the weighting be modified eg. more granular, more subjective measures?
+  - Should the weighting be modified e.g. more granular, more subjective measures?
+  - Were there any issues with compromised wallets, contracts or multisigs during the pilot?
+
+### Communications
+  - What sort of communication activities were carried out by the Guild during the pilot?
+  - What was the engagement level of said communications with Guild members, sponsors and the community more broadly?
+  - What sort of questions, feedback or concerns (if any), did Guild members, sponsors, or the community have during the pilot?
 
 ### Membership
   - Did the Guild start with an accurate representation of protocol contributors? 
-  - What areas in the ecosystem should eligibility be expanded to over the pilot?
-  - What were the notable membership changes/ disputes, if any?
+  - What areas in the ecosystem should eligibility be expanded to after the pilot? Are there areas where eligibility should be restricted?
+  - What were the notable membership changes/disputes, if any?
   - What is the general state of the membership?
-  - Has the presence of the Protocol Guild lead to negative or positive affects to relationships, the progress of regular projects?
+  - Has the presence of the Guild lead to negative or positive affects to relationships, the progress of regular projects?
   - What frequency has someone's decision to join or remain in core protocol work cited the Guild as a compelling benefit?
   - Have any Guild members participated in mentorship programs to support diverse array of future contributors?