-
Notifications
You must be signed in to change notification settings - Fork 526
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
Delivery report for milestone one of the third grant of OpenBrush(6 milestone) #515
Delivery report for milestone one of the third grant of OpenBrush(6 milestone) #515
Conversation
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.
@TtomaS7 is there a specific reason for submitting M6 before M5?
Also, feel free to accept my edit suggestion since this should be a numeric value (and in this case, I think it should be 6
).
Co-authored-by: S E R A Y A <takahser@users.noreply.github.com>
In previous reports, we used "X milestone of the grant Y and Z milestone of the OpenBrush"=) But if it is okay to use just 6, we prefer that way=) I don't remember why we decided to go the previous way. We added a small description in the delivery report, but I can provide more description. Milestone five contains two points, which are changes in the ink!.
All that already took a lot of time. We've started work on milestone six before the creation of the grant because of milestone five. Most of the points in milestone seven are also ready(because we work on it in parallel). Soon we will start working on milestone eight(and we need to create a new grant for that, but we can't because milestone six is not delivered cause of milestone five). Milestone five depends on ink! team and related to ink!. It is partially related to OpenBrush, but we will refactor OpenBrush when the change is merged. We only want to unblock our work and avoid cases where all milestones in the grant are already done before the creation of that grant. So it is why delivering milestone six without milestone five can make things simpler for us. |
@xgreenx thanks for elaborating on why you deliver M6 before M5 and updating the Milestone value in the doc. |
hello! we faced up with it on Typechain grant, so now it’s updated everywhere :D |
Hi @TtomaS7, thank you for your delivery & I wanted to update you that I began work on this evaluation today. |
I've completed my evaluation of your M6 and forwarded your invoice internally. Thank you very much! By the way, @TtomaS7, I vaguely remember from your pitch call--I mentioned I could send you some resources but I cannot remember what these are. Now I am much more familiar with your project having completed an evaluation for you. I believe I'm much more able to help. I remember Green perhaps mentioning that there's no native inheritance in Rust but that you've done a workaround? Are you in need of any resources? By the way, excellent job with the Wasm Conference and great job managing the versioning of ink!! |
Thank you for the review! I don't remember too :D |
@TtomaS7 You're welcome! Btw, I remembered over the weekend! And so I just sent you a ping on Element. :) |
Preview
Milestone Delivery Checklist
Link to the application pull request: w3f/Grants-Program#921