# Open-Source Dev Onboarding

## Motivating stories

- Rabble:
- Nothing new in website
- repo, READMEs don't work
- feels therefore like "vaporware"
- Jack
- Bunch of references to old version (during transmission time)
- In RSM docs, what we found where to look it was really solid and well structured--and extremely esoteric (could be more like DSL--working towards a higher level expression); recommended patterns and how to accomplish tasks, were not visible (doesn't remember the scaffold) though did pull what was out there;
- Did participate in DevCamp8, but struggling to keep up and have enough attention (with a new kid); was way off our time zones, videos were helpful but harder to engage; nice to do live sessions with a support group (there was one in my time zone)
- Overall experience was good to the extent I was able to engage with it
- Core Concepts was great
- People in my work space like
- Sounds like wells structured and improving dev journey and outer most layer can't figure out anything or exactly what they want--and lot of that noise will be handled by putting the right rigor and focus on that public first experience; that outer most level is what is rough
- Main point on that; big difference between knowing things are available somewhere vs. the public journey of all the requisite things to get you from: getting it: 1. running on your machine, 2. building your first app, and 3. architectural understanding of how to do it;
- Knowing this NPM is ready
- I love vidoes, podcasts, documents that explain;
- I like to understand context and architecture--and I like
- Harlan
- 1 year old experience follows:
- Story about trying to contribute to holochain core; there was a bug that showed up on mac--running test on mac and linux; bug was just mac (time esoteric stuff0; tried to contribute fix, and 1st wanted to see my branch running on CI--but CI wasn't running on mac (disabled); but at least wanted for it to pass on linux--but that didn't pass either because wasn't a team member)
- Wow, it is open source but I can't see if my branch is red or green on Ci
- Everything was run in a container and patched together (Eric--it is really hard)
- Trying to figure out how to run the tests on my machine (Eric--not hard, doable but take a long time (and eats all CPU) and designed to run in the nix shell)
- Tons of output in the test run, generally an anti-pattern; too much to find out if the CI was correctly/incorrectly passing
- Made PR, wasn't running on CI, not merged, but someone did attack the same problem and fix the issue (unsure if they cleared the PR out)
- It would be great to run the PR on multiple platforms
- Favorite thing is learning through doing (svelte kit); just want an example
- npm init @holochain (YOU DO GET THAT)
- Duke
- Information Discoverability: Couldn't find the Discord link at all, even knowing it exists and searching
- Tried to tackle it like every other system I have over last 10 years; 1. get it running 2. forget walktrhoughs 3. show me the reference and i'll start doing things--completely impossible
- no discoverability of what is important and non-important
- even discord was buried on page 4
- walkthroughs-- [get involved](https://developer.holochain.org/get-involved) (Didn't see Core Concepts) are for beginners! i don't want to do that
- What I really wanted: grab a few binaries and use hc to start it out; (maybe current answer is Holochain launcher) want to see things on the command line, type things in, and see files--really wanted a rails generate (Hc generate integrity zone in a set directory structures--not acorns 2 years ago)
- Scaffolding didn't really do that (does that in UI and not command line)
- Next step is in the roadmap
- Nix thing--won't bother complaining--is getting better
- There is a really question about UI v. command line (Guillem says it trivial to do both--Harlan thinks devs would go to command line, Duke says 80% as well, Jack when not a GUI would still want a command line-like display)
- Biz logic to data base level (rather than biz logic to UI)
- It is more towards the data base rather UI
- What I really want is (brew install hc) but that isn't there, what are all versions, what are the binaries I can download
- Zippy: Can do from crates.io
- Currently need
- cargo install holochain
- cargo install hc
- cargo install lair_keystore

- when been looking at rust docs: core team refuses to put examples in readme, because have to compile with a bunch of
- had much better time w/ cloning and then start building
- Discord
- in the docs
- Jill
- Apple M1, nix is still broken so have to use entirly new computer
- what is the list of all dependiesn to get a working environ so i can at least get a working environ, w/ cargo + all crates
- Guillem: Devs coming itrying nix shell (nbroken) there is a need to get it fixed, then Stefan/Jost can solve those problems but there is no place/context to do that (only Kesra and MM); but no one is connecting to those new devs
- Eric
- Really hard, whole point of Kesra is about low noise
- How to open that surface area and not overwhelm Stefan\
- AND need to have people not blocked (like Jill on M1)
- Hdk docs don't have examples because they are all in the Holochain repo as tests.

- Guillem
- developer.holochain.org/install
- Delete on #2 on Next steps (and deprecate the repo)
- /learning
- another reference
- What to do with GYM and Playground
- Not Holochain repo, just Holochain playground
- Could get baseline
- GYM has been 4 months out of date
- Someone on HC team should take ownership,
- Open question: What repo should it be in?
- Currently an open source project
- Could be Holochain contributing back to a community project
-
- we need a repo

- Michael Hueschen

I think I am perhaps an odd cat in term of giving feedback on that. I don't read a lot of Holochain comms stuff because I generally don't read much comms stuff from projects because I suppose I don't find it very interesting. I tend to just look at the updates to the various software packages as they roll out, like reading https://github.com/holochain/holochain/blob/main/CHANGELOG.md#20220831015922

I read the dev pulses occasionally, but I tend to be a little frustrated at the non-technical aim of them. I suppose I am "very technical" so I tend to prefer stuff which is pretty technical and doesn't use as much "baby talk" or "translating terms into metaphors/frames which non-technical folks can more easily grasp". I tend to find that just makes it harder for me to get at the actual technical detail underlying the explanation, so I tend to avoid

## Existing Flows

(not organized)
- Holochain newsletter
- Holo.host website
- Social channels
- holochain.org

- Github readmes
- Local Meetups

- developer.holochain.org -> Dev.HC
- developer.holochain.org -> HDK docs
- Dev.HC -> Wednesday workshops
- Dev.HC -> Holochain in Action

- Holochain Gym (maybe mattias? TBD)
- Scaffolding (easy and handed off to Mattias)

## Questions

- Should we direct people to the forum or to Dev.HC?
- Community dashboard?
- Different flows: Two classes: 1) Open source flows & 2) Direct educational experiences or personal
- Do we have all redux references removed/sanitized?
- How do we do balance the difference between people who lean towards command line and others who just want to work w/ javascript in the browswer

## Things to do

- Github repository sweep to archive old repos
- Holochain org
- Holochain-open-dev org
- https://github.com/holochain/dpki
- Scaffolding tool:
- CLI
- Manage an existing app