-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
META Workshop/Talks Ideas #67
Comments
Ideas of talks ->
|
@DIGIX666 |
I saw it more as est of discussing the subject, talking about how it would be set up and how it would work. But it's probably complicated because it's not supported yet Thanks for you comment :) |
Hey, here are some ideas:
If more ideas cross my mind I'll make sure to add them |
Talks"Monorepo Architecture: A Backbone of Gno.land"
"Authority Through Contribution: Decentralized Governance Redefined"
Presentations"The GitHub of Blockchain: Transparency and Reusability on Gno.land"
"GnoWeb: Simplifying Decentralized User Interfaces"
|
From 0 to Gnome: Showing all the different ways to contribute to gno.land. From solving current issues to making something that can serve gno ecosystem and its users. Since there is a big part of the blockchain community that aren't coders themselves, there can also be part of a presentation on how to contribute to documentation, help manage the community within Discord or X and all this can be part of some developer advocate or ambassador program. The audience here differs but I think it will capture most of web3 community. In the future, if gno plans to organize hackathons they can help onboard the devs. Leon already mentioned something about this but not sure in which way it will go. |
PresentationsFrom Go to Gno
Why We Need Gno
|
I am aiming to add the whole talk here within 24 hours, but I have put one together that started off with the idea of "It's just Go", though I'm not sure that should be the title. Something more descriptive might be "gno.land; distributed applications with Go" Conceptually, the talk focuses on introducing Gno through the hook that it's just Go. Yes, interpreted instead of compiled. Yes, some changes to ensure determinism, but fundamentally? It's just Go. The content covers why this is important quickly, then dives right into the meat -- an example application, simple enough to get the gist of in a couple slides, showing the code -- it's just Go, after all. Then a quick demonstration of the deployed application in operation (or if the internet access is not good enough to do this reliably, there is a recorded screencast video of it as a backup). Then a quick recap. Go, interpreted, determinstic == Gno. Gno + gno.land == highly accessible distributed applications Final slide with contact information, and a URL that they can go to in order to get a little more info about the demo app (including links to the deployed contract source code, links to use it themselves, and some instructions or links to instructions about simple stuff like wallets). Total time should be right at 5 minutes. |
Audience: Students and new graduate dev Presentation:
|
Share ideas for talks, workshops, or presentations, like:
Goals
cc @leohhhn
The text was updated successfully, but these errors were encountered: