Updating timeline #584
Closed
Updating timeline #584
Conversation
This file contains hidden or 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
added 13 commits
January 23, 2021 08:56
Adding template for grant proposal
Adding ChainJS for Polkadot draft proposal
Corrected title
formatting
added ecosystem fit section
Removed instructions
removed instructions
Added more narrative to future plans
Added Kusama support into the grant application, and added more description of the difference between ChainJS and Polkadot.js
Updated pricing
Lowering price
|
|
Member
|
Hi Mark, thanks for the update. Correct me if I'm wrong, but this should only update the timeline of your existing grant, right? If so, could you create a PR with the changes from a more recent fork? That way, the diff will immediately show the changes made to the file. |
Author
|
Hi Sebastian,
I’ll take a look - apologies. I updated the team list, timeline and the FTE. But left the pricing and all the description.
Are those the other changes you’re seeing?
Marc
… On Aug 18, 2021, at 7:33 PM, Sebastian Müller ***@***.***> wrote:
Hi Mark, thanks for the update. Correct me if I'm wrong, but this should only update the timeline of your existing grant, right?
If so, could you create a PR with the changes from a more recent fork? That way, the diff will immediately show the changes made to the file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Contributor
|
Currently the PR will add a completely new file and probably result in a merge conflict. |
Author
|
Just did it again - was that right?
… On Aug 19, 2021, at 8:05 AM, David Hawig ***@***.***> wrote:
Currently the PR will add a completely new file and probably result in a merge conflict.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#584 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMMY3APQMQIBH32JBRUWX3T5SULDANCNFSM5CL3HQXA>.
|
Member
|
Yes, thanks. Closing this one in favor of #587. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
#228