-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add StorageHub Proposal #1970
Add StorageHub Proposal #1970
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the application. Based on my previous discussions with you and your team, I will approve the application, mark it as ready for review, and share it with the rest of the team. That said, both milestones currently contain very few concrete details, and the rest of the committee might complain about it. Potentially, for example, it might make sense to initially only apply for the initial research and follow up later with a more concrete PoC proposal. But let's see what the rest of the team thinks.
I agree with @Noc2. Please add more concrete details in the milestones specifically the deliverables. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the application @Cwilli30 I have a couple comments as well:
- For the "Research and Design" milestone 1, you can probably go ahead and remove the "infrastructure" deliverable since there isn't anything to evaluate there.
- M1 seems rather expensive to me for a single article. Could you perhaps integrate more technical details about what problems/issues you are looking to solve, the methodologies used, any analysis procedures used in producing the material, and how the knowledge will be useful for others?
- Regarding M2 "Testing & Guide", I understand that it's just a prototype and not production-ready, but would there still be some basic unit tests to evaluate?
- I agree that M2 could be expanded as well; for example what kind of limited features do you plan to implement? What functionalities will we be able to test when it comes time to evaluate the delivery?
I have read and hereby sign the Contributor License Agreement. |
Grant team - The Moonsong Labs team spent the last week or so revising our Milestone deliverables for our grant application. Please review at your convenience. Thank you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update. I'm still happy to go ahead with it and share it again with the rest of the team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Cwilli30 and team,
I am happy to see a proposal being made on this topic. And I am happy with a prototype being included in this proposal already. Given that this is largely a research grant, I'm fine with the lack of technical specifications. Instead, I would like to see all the key questions and challenges you laid out to be directly addressed in your reports. Currently, it sounds like you are just focusing on delivering a solution ("The research & design document will include the gathered requirements and the list of researched solutions & features"), but the documentation of how you came up with the requirements (calculations, interviews, comparisons) I think would be equally interesting and potentially useful down the road. If you could make this a bit more explicit in your deliverable specs, I would be happy to approve.
One last thing: I don't understand the spec for deliverable 2.0g
. Are you saying you are going to write about the deliverables? Can you clarify what the difference between 2.0b
and 2.0g
is? I'm guessing one is the spec document and one is the project documentation, but it's not clear from the specification.
Hi @semuelle - Thank you for the feedback. I can add content in Milestone #1 (0b.) that reads, "The research & design document will include the gathered requirements and the list of researched solutions & features that could meet those requirements, as well as all supporting evidence and documentation that led to those proposed requirements and features. The document will also expand its research on the “Key Questions and Anticipated Challenges” section". Does that provide some additional clarity on what you were asking to see? With regards to your other comment "I don't understand the spec for deliverable 2.0g & Can you clarify what the difference between 2.0b and 2.0g". Deliverable (g) is simply calling out specifically what the deliverable is for Milestone #2. Milestone #2 is focused on providing follow on research applied to the v0.5 doc to get it to a v1.0 state, build some prototype code to begin to support the v1.0 doc, and provide a code tutorial so the code can be easily used by a user. |
I have read and hereby sign the Contributor License Agreement. |
Yep, that'd be great, thanks. |
@semuelle - Thank you for the feedback! I made the adjustment and submitted a PR. @keeganquigley & @nikw3f - I welcome your feedback or approval on the adjustments made from the last 2 PRs. Thank you in advance for your support we look forward to working on this project! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the update, @Cwilli30. Happy to approve.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Good from my side.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the changes @Cwilli30 LGTM.
Thank you all for the approvals. The Moonsong Labs team is super excited about this project. We are currently hiring to build the team to work on this. We have some high quality engineering candidates in the works. We look forward to rocking and rolling once they are in place! |
Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions. |
Hi W3F Team - Just wanted to provide an update. We just finalized the hiring process for the Principal Blockchain Engineer for this StorageHub project. We are really excited to have this individual (Facundo Farall) join our team. The candidate is extremely strong and was top of his class from Polkadot blockchain academy, with a perfect score! Facundo starts Monday, we plan to pair Facundo with one of our strong team members. Looking forward to really kicking this off! |
Project Abstract
Grant level
Application Checklist
project_name.md
).@_______:matrix.org
(change the homeserver if you use a different one)