Open Hodlatoor opened 1 year ago
@sergfeldman please take a look at https://www.notion.so/ubiquitydao/Github-web3-foundation-grant-275ba644b49f4bad920df4b80508c7b9?pvs=2
- In red are items which I would like you to add initial content to. I will append as needed.
@Hodlatoor I added a few extras in blue font.
- Let's talk about the scope of this grant. We need to package a deliverable and milestones therein. I am wonder if we can pick something specific that is already a work in progress or select something from: UbiquiBot Capabilities Overview bounty-bot#1
@Hodlatoor The first question to clarify - are we going to build for Polkadot/Substrate/Kusama?
@sergfeldman we are not building for polka dot at the moment. You might have seen that my approach was to call it project agnostic and to focus it on GitHub for all project that utilize GitHub
@sergfeldman we are not building for polka dot at the moment. You might have seen that my approach was to call it project agnostic and to focus it on GitHub for all project that utilize GitHub
@Hodlatoor Yep, I have read all the points in the document. Ok, I will continue to add answers according to this logic.
@Hodlatoor The status by now
The paragraph on the Development Roadmap No answers provided yet, I will add them in the coming days.
All other points I wrote answers wherever I could. Please let me know if I should expand or change the information.
I'm still thinking what to put to the Development Roadmap given we are not related to Polkadot ecosystem
Perhaps we shouldn't pursue this if it doesn't make sense to.
@sergfeldman @pavlovcik
I think it's a good association if we can get it and because the platform is project agnostic. it fits exactly into what GitHub's strives to accomplish and dovetails into its ethos. as such I think we should give them something easy to digest in terms of project roadmap and goals. something easy to bite on, easy to understand and easy to approve. now we just need to decide what the scope of that is exactly.
as for pursuing it, I would rather take a 5% chance of something happening versus 100% chance that it doesn't.
I'm still thinking what to put to the Development Roadmap
Then lets just focus the development roadmap around GitHub specifically (the bot) and I'm not sure if its strategic to mention that we're seeking to build on Ethereum or an Ethereum rollup (e.g. Optimism.)
let's pick a few interesting components of the bot that will be deliverables for this smaller scope. And I don't think we need to mention optimism because we are platform agnostic? unless you think it would help for reputation sake
And I don't think we need to mention optimism because we are platform agnostic?
I commented on this in the notion document. I think it's not relevant.
let's pick a few interesting components of the bot that will be deliverables for this smaller scope.
You could use the BETA roadmap: https://github.com/ubiquity/bounty-bot/discussions/70
I guess you could also use any of the open issues on https://github.com/ubiquity/bounty-bot/issues as those are clearly spec'd out and in the more immediate pipeline of miscellaneous tasks/features.
I guess you could also use any of the open issues on https://github.com/ubiquity/bounty-bot/issues as those are clearly spec'd out and in the more immediate pipeline of miscellaneous tasks/features.
I added the draft of the roadmap based on open GitHub issues. I also addressed all the points where I was tagged. @Hodlatoor Please let me know if there is anything else I can help with.
@Hodlatoor Please, review the video and let me know if anything should be changed
that looks good. let's add it to the notion and then submit by adding the fork
@Hodlatoor Please, review the video and let me know if anything should be changed
This is awesome. Unfortunately it looks like it was shot before we did that but fix on the claims dApp with the "loading"
I vote to submit as is, and possibly re-record and edit the post later with these small incremental improvements. Great demo @sergfeldman
We should also include the quick program overview somewhere with the video for context:
https://dao.ubq.fi/devpool-flow
@0xcodercrane can we unset his wallet using the 0 address? That way we can easily re-record the registration user flow
This is awesome. Unfortunately it looks like it was shot before we did that but fix on the claims dApp with the "loading"
I vote to submit as is, and possibly re-record and edit the post later with these small incremental improvements. Great demo @sergfeldman
We should also include the quick program overview somewhere with the video for context:
@pavlovcik @Hodlatoor Thank you for the positive feedback on the demo!
So far added a video at the bottom of the page https://dao.ubq.fi/devpool-flow
So far added a video at the bottom of the page https://dao.ubq.fi/devpool-flow
The issue with this is that all the media was intentionally made in dark mode to be cohesive. The video is going to look bad on that page.
So far added a video at the bottom of the page https://dao.ubq.fi/devpool-flow
The issue with this is that all the media was intentionally made in dark mode to be cohesive. The video is going to look bad on that page.
@pavlovcik Then maybe I record the demo with dark theme of GitHub?
So far added a video at the bottom of the page https://dao.ubq.fi/devpool-flow
The issue with this is that all the media was intentionally made in dark mode to be cohesive. The video is going to look bad on that page.
I re-recorded the video with a dark theme and added it at the bottom of the page https://dao.ubq.fi/devpool-flow
@pavlovcik @Hodlatoor I created a draft PR with the grant application https://github.com/w3f/Grants-Program/pull/1718 I will re-check and add more information soon. Please let me know if you have any recommendations.
The initial PR contains only one commit (squash and force-push if needed).
lol you added multiple commits to your pull request so you might want to fix that.
The semantic versioning you used, "v0.1" seems arbitrary and should be removed.
Lastly it might be savvy for me to be the one to open the pull request as they might judge based on the GitHub activity too. But let's only do that if we need to redo the grant application.
level three requires more people signing off on it. we can shoot for that but then we need a more substantial timeline and milestones. I don't think we're limited to one grant so another working theory is get in the door and expand.
agree with the remaining points.
As I never did this before, I created a draft PR intended to check everything before the real grant application. This draft PR is not planned as a real application.
@pavlovcik may I ask whether you checked 1) Our wallet 2) Software license (I put Apache-2.0) 3) Name of the team leader (it is kind of doxxed that you dislike)
The change requests from W3F
1) https://github.com/w3f/Grants-Program/pull/1718#pullrequestreview-1412461538
2) https://github.com/w3f/Grants-Program/pull/1718#issuecomment-1534214914
After all the changes we should create a new PR according to all the requirements, ie
Also, Alvaro should monitor the Ubiquity email address because he is determined a contact person
pretty much the same as we discussed before. I encouraged looking into patenting.
It would have to be non-obvious components and technology but my bigger concern right now is potentially being barred from patenting, depending on a jurisdiction (US /Europe/ china) - if it considered public we cannot. we can try and counter that by saying that private alpha is not public. I would like some more clarification from you on this point.
another thought is to look into patent pending and punt some of these issues down the road. especially since we don't have to disclose as much in a patent pending as opposed to a full application.
I think it could be a good idea to start some research related to this but I'm always happy to punt down the road and handle when we need to.
Steps if we want to complete and submit this grant application:
Define the software license. As I understand by the comments in this issue, this is for Jon.
Update the content: add the table with deliverables according to W3F comments in the draft PR, change Alex name according to his input. I can do this.
Create new PR with 1 commit. Alex mentioned in the comments in this issue that he wanted to do this.
Define the software license. As I understand by the comments in this issue, this is for Jon.
MIT
Create new PR with 1 commit. Alex mentioned in the comments in this issue that he wanted to do this.
I can yes. Just tag me when you want me to.
Define the software license. As I understand by the comments in this issue, this is for Jon.
MIT
Create new PR with 1 commit. Alex mentioned in the comments in this issue that he wanted to do this.
I can yes. Just tag me when you want me to.
@pavlovcik Thank you!
ok so this is good to submit correct?
@sergfeldman please post the link to the source content (on notion I guess) and the repository that I should open a pull request to when it is confirmed to be completed. Thanks!
@pavlovcik @Hodlatoor In the comments to the draft PR, W3F representative requested to fill in the tables with deliverables. The main points of these tables are related to Substrate modules, Substrate chain, libraries, etc.
I have added the tables to our application, but for many questions, I put N/A because we do not plan to provide them. Also, I put the MIT license and updated Alex's name according to his input.
The current version of the application is here https://github.com/sergfeldman/Grants-Program/blob/DevPool_by_UbiquityDAO/applications/DevPool_by_UbiquityDAO.md
Please, let me know if I should change something.
The current version of the application is here https://github.com/sergfeldman/Grants-Program/blob/DevPool_by_UbiquityDAO/applications/DevPool_by_UbiquityDAO.md
You should add all documents in this repository because
I will let you know what needs to be changed by changing the document directly.
For educational purposes I will let you post the document on this repository and then we can go from there.
According to the W3F Grant program, it is required to fork their repository and create 1 new file with our application https://github.com/w3f/Grants-Program#pencil-process
To apply for the grant, it is only needed to paste the content to this file and create the PR to the W3F repository according to all the requirements, ie
As requested by @pavlovcik I tried to add all documents to this repository. I have not figured out how to fork the W3F repository here.
However, I saved the content of the grant application file in various ways in this repository:
Uploaded file to the comment W3F grant application.md
Created discussion https://github.com/ubiquity/partnerships/discussions/17
I`m ready to continue the activity for educational purposes.
I submitted the W3F Application https://github.com/w3f/Grants-Program/pull/1800
@sergfeldman please take a look at https://www.notion.so/ubiquitydao/Github-web3-foundation-grant-275ba644b49f4bad920df4b80508c7b9?pvs=2