Split the deck into modules

[benhylau]

Goes into too much technical details as an intro deck, but not sufficiently for a technical audience. It may be better to split this into two separate decks and two separate sessions.

[dcwalk]

Hey! I think just splitting the deck might not be the way to best approach intro and outreach materials. I have all my notes but have been struggling to figure out how to pull them in...

Basically I almost think we need a few 'module' style presentations covering beginner to advanced topics, but ALSO, like a script with some exercises/questions... if we want this to stand alone as a resource for others to make use of.

[benhylau]

Agree with breaking this into topic-specific modules. Let's discuss what how to modularize the content on this ticket. I have changed the ticket title to reflect this.

As for notes, you can file them as issues?

Meanwhile I will continue adding content to the .101 deck, we can break them into modules when we have some agreement on this.

[Famicoman]

I'm very interested in working on these decks with you guys, but may refrain from pull requests (or normal changes if @benhylau adds me to the org) until the structure has changed as you guys are discussing.

[dcwalk]

👌 sounds good @Famicoman! I think after tomorrow's discussion we'll have a sense of how we want to split it up and from there it should be easier to start adding stuff in!

Even within the org we are using PRs for now to submit changes (our rather scant contributing guidelines)

[benhylau]

My takeaway from Tuesday...

• We need two types of content: Post & Deck
• Posts hold permanent content we can easily reference (e.g. for onboarding)
• Decks are presentation material that evolve over time, and we will run these presentations periodically

• Regardless of which type of content, it should be modular and have a definite spot on this graph

  Level (e.g. Beginner vs. Advanced, General vs. Specific)
  
  ^
  |
  |
  +--------> Topic (e.g. History, Mesh protocols, Social relevance & impact, Antennas,
                         Node installation, Reference node set up, Mesh for IoT)

• The content + periodic workshops should provide a path for whoever is interested, regardless of background, to self-educate and peer-educate in the areas of their interest
• We will deploy a Wekan instance to allow anyone to contribute to the mesh in flexible ways, since anyone can pick-up or join a task they are interested in, and input their ideas as a backlog item even if they cannot work on it themselves
• The Wekan Kanban should supersede the more rigid Working Groups we currently have

@YKCzoli @garrying @dcwalk @structur @WilliamRutherford I probably missed a bunch of stuff. Please add. And let's start inputting module topics here?

[Famicoman]

How is repo organization going to be done? A new repository for each slidedeck? Will the same be done for posts or will that he more wiki-like and in one repository with straight markdown files?

Also, any thought into what topics need to be covered and which ones before others?

[dcwalk]

Much delayed, we are swinging back around to this! On our snazzy new Wekan board we have some meta discussion on this card.

I'm working on a PR likely for tomorrow to reflect this and welcome feedback there @Famicoman et al.!