Skip to content
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

Substrate and FRAME Schedule #643

Merged
merged 9 commits into from
Jul 24, 2023
Merged

Substrate and FRAME Schedule #643

merged 9 commits into from
Jul 24, 2023

Conversation

shawntabrizi
Copy link
Contributor

No description provided.

@nuke-web3
Copy link

Epic. Just a bit more now:

Who is delivering each of these included lessons?

What lessons do we want to require Founders Track members to attend? (If more granular than morning/afternoon, we need hours each lesson will run)

@shawntabrizi
Copy link
Contributor Author

Founders do not need to attend any of these. I have been told that @aaronbassett will present a founders view of Substrate / FRAME, and the content here is probably too technical.

As for speakers, I think it will be the same distribution as last time.

@aaronbassett
Copy link
Member

They had asked me to do that, but then walked it back. Last message I received about it from @mastermaxy was:

We're changing our approach; instead of the birds-eye session we asked you to do on the 24th, we'll instead have the Founders students attend the first lectures of each module (Substrate, Frame, polkadot, xcm)

@nuke-web3
Copy link

As for speakers, I think it will be the same distribution as last time.

Forgive me, IIRC this was all you Shawn, correct?

We're changing our approach; instead of the birds-eye session we asked you to do on the 24th, we'll instead have the Founders students attend the first lectures of each module (Substrate, Frame, polkadot, xcm)

Anything need to be tweaked here based on founders relevant content being in the morning then?

And can we lock in some time allotted for #649 ( I do recall "nice-to-have" and Bhargav is on site just for this content)s

Copy link

@nuke-web3 nuke-web3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM enough to merge as is.

We will need to adjust for a few outstanding incoming parts of content as mentioned in this thread, along with a very shortly to be slotted set of a security practical lessons @VinceCorsica and team are just about to file an issue/PR for.

@shawntabrizi shawntabrizi changed the title FRAME Schedule Substrate and FRAME Schedule Jul 24, 2023
Copy link

@nuke-web3 nuke-web3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is gonna be GREAT! tysm

@nuke-web3 nuke-web3 merged commit 9da6533 into main Jul 24, 2023
@nuke-web3 nuke-web3 deleted the shawntabrizi-frame-schedule branch July 24, 2023 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants