Open ph0ph0 opened 2 years ago
hi @ph0ph0 - thanks for submitting. please add the the milestones, deliverables, and costs to your application. I understand that you anticipate discussing the topics, but we need a proposal of of topics to get the discussion going.
thanks!
Thanks for the feedback @alxflw , I have updated my proposal! :)
Hey @alxflw, do you have any updates on this? Thanks!
hey @ph0ph0, yes - I just received some feedback and wanted to ask you if you would be open to the following:
@alxflw thank you very much for your feedback! I have made some changes and replaced the articles that you asked me to skip with new ones. Let me know what you think!
Hey @alxflw, was wondering if you might have any news on this please? Thanks!
hey, sorry for the delay. we'll get back to you shortly with a decision!
No worries at all, thanks!
Hi @ph0ph0, thanks for your patience!
For the milestones, we'd love to see the view-based milestones aggregated across your entire set of articles versus having a view-based payout milestone for each article. Would you mind reworking the proposal here to reflect that?
Ultimately could just add one additional milestone that would denote this. Thanks!
@chrisackermann no worries at all, thanks very much for getting back to me! :)
I'm not sure I fully understood your request, I have added a column "USD proposal per cumulative views across all articles milestone", is this ok?
Also, I added two new articles to the bottom, "How to write tests for smart contracts" and "How to build a simple oracle for smart contracts on Flow" :)
Interested to hear what you think!
Hi @ph0ph0 - thanks for making the updates! Sorry for the confusion - I'm looking for the cumulative milestone to replace the individual view-based milestones for every single article. Could we remove that column named 'USD proposal per views per article milestone' in this case?
I think the two additional articles look great.
@chrisackermann thanks for the feedback and clarification! I have made the suggested changes :)
Hi @ph0ph0 - sorry I'm still seeing the 'USD proposal per views per article milestone' column above. Can you please:
1/ Remove the USD proposal per views per article milestone column 2/ Add a set of adoption milestones for each of the levels noted in the current USD proposal per cumulative views across all articles milestone column
Here's an example from another grant project that you could follow (see the last 2 milestones in their table): https://github.com/onflow/developer-grants/issues/28
Thanks!
@chrisackermann apologies, I had removed the column but hadn't saved my changes...
I have now made the requested changes
Thank you!
No worries, thanks @ph0ph0!
Could we also simplify to perhaps 2 or at max 3 levels instead?
@chrisackermann sure - done! :)
Hi @ph0ph0 - thanks for your patience! Just wanted to let you know that we've accepted your proposal and will be following up directly on next steps. Thanks!
Amazing thank you @chrisackermann!!!
Flow Educational Developer Articles
Grant category
Educational material
Description
This grant aims to increase the availability of Flow/Cadence text-based technical educational content available to developers. The grant will allow the author to write a number of articles that tackle a range of topics that vary in complexity. The aim is to have a broad gamut of articles produced over time that cover many subjects ranging from beginner to expert, although not necessarily in any order. Each article is likely to be independent of the others, unless stated that it is part of a series.
My hope is that by writing educational content focused on Flow/Cadence, we might jump-start the community into writing their own content as people learn from and improve upon concepts communicated in our written articles. It will also aid our efforts in Discord by hopefully reducing the number of duplicate questions.
Problem statement
There are currently some brilliant sources of educational material available for the Flow ecosystem, including the developer docs, Joshua Hannan and Ben Ebner's medium articles, and Jacob Tucker's video series. However, unlike other ecosystems and languages, there is a lack of written material available on the internet that covers tips, tricks, principles and advanced concepts in Flow and Cadence.
Further, Flow/Cadence has a very limited presence on Stack Overflow, primarily because Discord is the first port-of-call for many developers when they have questions. The result of this is that huge volumes of information are lost in Discord, and the same questions are often asked by different people.
The target audience for this project would be all Flow/Cadence developers ranging from beginner to advanced.
Proposed solution
The proposed solution is to create a knowledge-base that is easily found via a google search. The articles will be written in a tech focused blogging platform such as https://hashnode.com/ or dev.to.
Text is the primary medium used in education, and it allows students to easily progress at their own pace. Text documents can be accessed easily, even with a poor internet connection, and the content within the document can be searched. Further, keeping articles up-to-date as new information emerges is a possibility. The greatest strength of textual information is that it can be indexed by search engines and therefore presented to developers when most relevant.
The project will involve a series of articles (not necessarily a set number of articles, could be on-going if agreed) that address topics as simple as "How to Get Started with Flow" through to more complex topics such as "Elliptic Curve Cryptography and Hashing in Flow".
Impact
In what ways does this benefit the broader Flow developer ecosystem?
The more knowledge shared amongst a community the better, as it allows the members to grow and innovate by building upon the contributions of others. It can make the learning experience for developers of all levels frictionless, therefore reducing drop-off. The Flow community already has a great mindset for helping others, and if this could extend beyond seemingly ephemeral Discord messages into more permanent, easily searchable online content, then the whole community would benefit.
The other impact is that if information was more easily found online, then it may reduce the load on contributors in Discord, as fewer duplicate questions might be asked. This will hopefully lead to more productive conversations in Discord.
Milestones and Funding
A series of topics can be agreed between the Flow team and the author (myself) or alternatively topics can be proposed on a one-by-one basis as the next article is due to be written.
1000 views: $100
10,000 views: 500 dollars
100,000 views: $3000
1,000,000 views $6000
Team