-
Notifications
You must be signed in to change notification settings - Fork 75
Notes for Meeting 29 #109
Comments
Sachin Mittal (@thesachinmittal) has been allocated by the Ethereum Cat Herders to take the notes. |
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 100.0 SAI (100.0 USD @ $1.0/SAI) attached to it.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done Workers have applied to start work. These users each claimed they can complete the work by 2 weeks, 4 days from now. 1) calvinoea has applied to start work (Funders only: approve worker | reject worker). I have taken meeting notes at board level for organizations (listed companies as well as non-listed companies) before. I would be grateful and honoured to take meeting notes for Ethereum. To complete the task, I will carry out the following steps:
Thank you for your consideration. My experience in note taking is rather ordinary. I have transcribing experience of hour long interviews (if that counts). My proposal is simple. I will watch the entire stream in the date proposed and generate a markdown document (using hackmd.io) summarizing every point in the agenda (Testing and Release Updates, Client Updates, Research Updates, Networking, Spec discussion, Testnets discussion, Open Discussion/Closing Remarks). This would be posted in the Github thread and linked to at the end of the livestream in the form of a comment. I hope to use this experience as a starting point to getting further involved in the ethereum community. I have completed the assign task. Learn more on the Gitcoin Issue Details page. |
Completed and approved! thank you :) |
⚡️ A tip worth 100.00000 SAI (100.0 USD @ $1.0/SAI) has been granted to @thesachinmittal for this issue from @ceresstation. ⚡️ Nice work @thesachinmittal! Your tip has automatically been deposited in the ETH address we have on file.
|
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This Bounty has been completed. Additional Tips for this Bounty:
|
Take notes for Ethereum 2.0 call meeting 29.
The text was updated successfully, but these errors were encountered: