-
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
Proposal changes #583
Proposal changes #583
Conversation
Thanks @MilGard91. Could you please also adjust the price to account for the missing functionality and sign the CLA? |
Hi @alxs, price is adjusted and I signed the CLA. |
@@ -87,8 +84,7 @@ We have experience in several private and open source projects aswell as project | |||
| 2. | Design an individual identity page | Create design mockups in Figma. | | |||
| 3. | Implement list page | Build UI components in VueJS used in the identity list page. | | |||
| 4. | Implement individual identity page | Build UI components in VueJS used in the individual identity page. | |||
| 5. | Implement query logic for identity data | Implement query logic which will be used to retrieve identity data. | | |||
| 6. | Query identity activities | Implement query logic which will be used to retrieve activities indicative of a member’s reputation. | |
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.
Could you move this to a different milestone instead, together with the treasury and governance modules? Feel free to distribute the price across the two milestones as you think fit.
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.
I have created Milestone 3 out of that deliverable. @alxs
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.
To clarify, I meant you may split the price of this milestone (which previously contained all deliverables) between this and the new milestone.
@@ -87,8 +84,7 @@ We have experience in several private and open source projects aswell as project | |||
| 2. | Design an individual identity page | Create design mockups in Figma. | | |||
| 3. | Implement list page | Build UI components in VueJS used in the identity list page. | | |||
| 4. | Implement individual identity page | Build UI components in VueJS used in the individual identity page. | |||
| 5. | Implement query logic for identity data | Implement query logic which will be used to retrieve identity data. | | |||
| 6. | Query identity activities | Implement query logic which will be used to retrieve activities indicative of a member’s reputation. | |
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.
To clarify, I meant you may split the price of this milestone (which previously contained all deliverables) between this and the new milestone.
|
||
| Number | Deliverable | Specification | | ||
| ------------- | ------------- | ------------- | | ||
| 1. | Index data from nodes | Setup [substrate-archive](https://github.com/paritytech/substrate-archive) with postgres for Polkadot and Kusama chains to store required data | |
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.
We also only fund deliverables that may be useful to others in the ecosystem, i.e. we can't support you in integrating existing software.
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.
I am not sure if I understand. This backend infrastructure is a requirement for governance & treasury data to be retrieved.
## Future Plans | ||
|
||
After finishing milestones 1 and 2 users can utilize the basic application which supports querying by address, index or identity fields. Application has a list page and a single page view with a basic info column fully functional. Users will be able to set their own node endpoint. | ||
After finishing milestones 1 and 2 users can utilize the basic application which supports querying by address. Application has a list page and a single page view with a basic info column fully functional. Users will be able to set their own node endpoint. |
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.
Why did you remove this? Seems like a very useful feature to me.
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.
Accidentally. I have reverted that now.
@alxs I have just contacted Kuba to schedule another meeting, so we can solve this faster. |
* https://github.com/paritytech/substrate-archive/issues/97 | ||
* https://github.com/paritytech/substrate-archive/issues/111 | ||
* https://github.com/paritytech/substrate-archive/issues/132 |
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.
These are different PRs from the one you mentioned in your previous email, could you please explain? And do you care to elaborate on how this is blocking you exactly? Polkascan for example have implemented pretty much this exact functionality https://polkascan.io/kusama/account/EGVQCe73TpFyAZx5uKfE1222XfkT3BSKozjgcqzLBnc5eYo
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.
I have added the missing PR to the list. To be able to retrieve and decode extrinsics from older blocks, this PR and issues must be merged and solved. Those three issues on substrate-archive are related to type-decoding.
Also, this is the response we got from the official discord server:
"At what blocks are you not getting any traces? State tracing is only supported on runtime versions v8.27 and above, so if you are on a block height below that runtime version then you will not get any traces. For runtime v0.9.XX a release is being cut to include support for those runtime versions today or tomorrow."
That is still not live in the latest version.
As agreed on the call, let's proceed with the payment for the first two milestones as they are delivered and not connected to the current issue. Thank you for your input about polkascan, we will research milestone 3 on their method for retrieving the missing data.
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.
I would rather suggest you look into this now as it was (and still is as long as the amendment hasn't been accepted) part of the deliverables for milestone 1. As far as I'm aware, Polkascan are open source and just using their harvester might do.
Nevertheless, I will share with the rest of the committee.
Payment for the first two milestones will be made when the review has been completed.
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.
Btw: Subscan also provides this functionality https://polkadot.subscan.io/account/EGVQCe73TpFyAZx5uKfE1222XfkT3BSKozjgcqzLBnc5eYo?tab=extrinsic
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.
I think the identity activities are the most important and useful part of the project, so I would suggest to split the price between M1 and M3 60:40, rather than the 92:8 split you are proposing. As far as I can see, the archive issues currently holding you back are already being worked on?
I agree. I have updated the cost ratio between M1 and M3 |
You did not update the cost ratio, you just raised the total price. What makes you think we would support raising the price by more than a third without any extra deliverables? |
You propose that we reduce the price of the first and second milestone vs third in 60:40 so that first 2 milestones are worth 20700$ and the 3rd milestone is worth 13800$? |
Since M2 is unchanged, I would leave its price as is, but shift more of the payment from M1 to M3. |
Updated. |
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.
I'm happy to approve this, however I don't know how likely it is the functionality discussed above will be added to subtrate-archive any time soon, so I encourage you to consider alternative solutions.
* Proposal changes * milestone 3 added * Updating proposal with required changes * updated costs Co-authored-by: Jakov Buratovic <kraljipo007@gmail.com> Co-authored-by: Edi Sinovcic <edi.sinovcic@gmail.com>
Project Abstract
This is a update for previous grant PR.
Application Checklist
project_name.md
) and updated.