add queryweb3 #2458
Open
add queryweb3 #2458
+304
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
admin-review
|
CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment: I have read and hereby sign the Contributor License Agreement. 1 out of 2 committers have signed the CLA. |
|
I have read and hereby sign the Contributor License Agreement. |
semuelle
added
the
discussion private
|
The applicant has requested the discussion of the application to happen in a private chat room. |
|
Thanks for the application, @lechangxu. I will review it as soon as possible (we are rather busy at the moment) and leave questions and/or notes in the chat room linked above. |
|
recheck |
|
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
@font-face
***@***.***";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
***@***.***";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
-->It‘s a great honor to hear from you. Waiting for your information.Thank you very much. Best wishes. Roger Le From: Sebastian Müller ***@***.***>Date: Tuesday, November 26, 2024 at 20:52To: w3f/Grants-Program ***@***.***>Cc: lechangxu ***@***.***>, Mention ***@***.***>Subject: Re: [w3f/Grants-Program] add queryweb3 (PR #2458)recheck—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
semuelle
requested changes
Nov 29, 2024
Comment on lines
+177
to
+181
| This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe *the functionality we should expect in as much detail as possible*, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. | ||
|
|
||
| Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We *recommend* that teams structure their roadmap as 1 milestone ≈ 1 month. | ||
|
|
||
| > :exclamation: If any of your deliverables are based on somebody else's work, make sure you work and publish *under the terms of the license* of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Projects that submit other people's work without proper attribution will be immediately terminated.** |
There was a problem hiding this comment.
Suggested change
| This section should break the development roadmap down into milestones and deliverables. To assist you in defining it, we have created a document with examples for some grant categories [here](../docs/Support%20Docs/grant_guidelines_per_category.md). Since these will be part of the agreement, it helps to describe *the functionality we should expect in as much detail as possible*, plus how we can verify and test that functionality. Whenever milestones are delivered, we refer to this document to ensure that everything has been delivered as expected. | |
| Below we provide an **example roadmap**. In the descriptions, it should be clear how your project is related to Substrate, Kusama or Polkadot. We *recommend* that teams structure their roadmap as 1 milestone ≈ 1 month. | |
| > :exclamation: If any of your deliverables are based on somebody else's work, make sure you work and publish *under the terms of the license* of the respective project and that you **highlight this fact in your milestone documentation** and in the source code if applicable! **Projects that submit other people's work without proper attribution will be immediately terminated.** |
Comment on lines
+165
to
+169
| ### Team LinkedIn Profiles (if available) | ||
|
|
||
| - https://www.linkedin.com/{person_1} | ||
| - https://www.linkedin.com/{person_2} | ||
|
|
There was a problem hiding this comment.
Suggested change
| ### Team LinkedIn Profiles (if available) | |
| - https://www.linkedin.com/{person_1} | |
| - https://www.linkedin.com/{person_2} |
Comment on lines
+151
to
+154
| Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. | ||
|
|
||
| If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. | ||
|
|
There was a problem hiding this comment.
Suggested change
| Please describe the team's relevant experience. If your project involves development work, we would appreciate it if you singled out a few interesting projects or contributions made by team members in the past. | |
| If anyone on your team has applied for a grant at the Web3 Foundation previously, please list the name of the project and legal entity here. |
semuelle
added
the
changes requested
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Project Abstract
QueryWeb3 aims to address the fragmentation of information and data across various projects within the Polkadot and Kusama ecosystem. By aggregating data, we improve information retrieval and transaction efficiency, enhance user experience, and increase user satisfaction.
Grant level
Application Checklist
project_name.md).@lechangxu :matrix.org(change the homeserver if you use a different one)