Grant #7: Clear step-by-step instructional guide for users #7
Comments
|
-----BEGIN VOTE----- |
|
Y:7:r18fiaRwkHZNy2n37wRLrH4SuFTfJJCS2HV:1594695743:IBYYg1V+xoZJ3sj+qIAo1RyglO9GDH0xzLym7zUIYWshQmsqjIyLHIrcwOKgUFD8Rsf7ZrSJEJJDWcnM/5ItRdo= |
|
-----BEGIN VOTE----- |
|
This will involve testing, documenting and possibly FIXING the API in the DEX (given that the API has zero documentation it can only be discerned from sources - and changes will likely be required) - the scope of the task is too large for the simple spec/reward above. There is no way to test the DEX safely without disposable/test assets configured into the DEX which requires new assets and DEX configuration as well as setup of relevant Electrum servers. It is far from trivial. Also needs a clear definition of what entails successful completion - if the underlying DEX does not work but the REST API does work - will the reward be made ? The scope of the work needs defining with far more detail |
|
Ian, this is not something that a community dev does alone nor the previous tasks. There is a common group with all resistance devs and there numerous conversations as things progress . I have asked Luke to clarify your points but for me it is clear the task. If resdex does not work this task will point out the issues and that will become next task. However, I reiterate my point that we work with the devs as we progress , it is not a tachaaaan this is the work! Give me the money. You can ask them the whole time (if they are available) |
|
A better description would be series of Grants that MIGHT go as follows: (IN ORDER)
Specifying a series of grants for this would entail specifying a dependence on sources of RESDEX for which there is no timescale, or even stated intention - in fact i would say that the FIRST step would be access as there is no way to work out what the API is without access to the sources as it is a MODIFIED Komodo MM2 API - the differences are crucial enough to impede successful testing and documentation. A later step would likely require access to the DEX GUI sources to ensure that operations in the API are reflected in the GUI correctly Granting proposals which cannot be serviced because of inadequate access to code would be entirely pointless and meaningless. This is my opinion of the prerequisites |
|
-----BEGIN VOTE----- |
|
The votes have been tallied and the results are in favor of accepting this proposal. cat list_of_votes7.txt tr -d '\r' < list_of_votes7.txt | grep -v "BEGIN VOTE" | grep -v "END VOTE" | ./verify.sh 7 | Final Tally for GitHub Issue: 7
This grant is approved. |
ghost
added
approved
|
i can try this. but as i have already committed on grant 2 and 8. i will finish those and try this. if any devs takes this grant before that.., no issues on my part. |
|
Hi, |
Hi You have just been assigned. All yours!!! Good luck!!! |
|
As with grant #8 - do we get to review, comment on and test the work before the "terms of the proposal are met" ? |
|
The resistance team is in charge in reviewing and approval the work done and decide whether the developer gets the grant |
|
But there should be some concrete result - a deliverable - or will it just be a tick on a box |
|
Again, please let them tick the boxes . |
|
And do not hesitate that if @whiteknightrader does the job he will do his best . In fact, we are ticking the boxes for them so this project becomes what it truly was aimed for: a decentralised project for the community. We are more than capable to turn this project around . I am 100% sure but when we can manage it and make decisions towards that goal. So, Anthony should make clear WHEN this will be fully decentralised. |
Grant #7
This is a proposal for a Resistance Support task:
An API developer is required to test the Resistance RestAPI and create a clear step-by-step instructional guide for users.
With a functioning RestAPI, users will be able to tap into, and potentially provide more liquidity to ResDEX and could earn a small arbitrage by doing so.
If this proposal is approved by the Masternode voters, then the community member who performs this task will be issued a grant from the developer's fund (from the 10% reward splitting).
The amount of RES granted will be: 175,877
A simple majority will be used to approve or reject this proposal. At least one Masternode must vote on an issue for it to be approved. To apply with a proposal email admin [at] resistance.io and include your GitHub username in your email so our admins can verify your development record. For information on how to cast your vote, please refer to the README in this repository.
Voting opens immediately and will close on: 22nd July 2020, developers have until 1st August to send in proposals if the grant is approved.
The text was updated successfully, but these errors were encountered: