Tools: * IRC * meetbot * mediawiki * mailing lists * blog/Planet (read, write) * ticket tracker (read, write, manage) * version control (read, write, manage) * Etherpad --------- Tools: List top 5 you need, then mark where you are and where you need to be 0 1 2 3 4 5 _________ [--------------------------------] _________ [--------------------------------] _________ [--------------------------------] _________ [--------------------------------] _________ [--------------------------------] 0: Never heard of it 1: Can rote-follow a tutorial but can't use it without instructions 2: Can use it as intended, with coaching/questions/help 3: Is a comfortable part of my daily routine; I don't think about it 4: Have tweaked & customized it to fit me 5: I wrote it / am paid to teach others how to use it Communications: too soon too late * question-timing [----------------O----------------] too nice too harsh * tact filter [----------------O----------------] too async too unitask * asynch/multitask [----------------O----------------] Bloodhound exercise: Can you follow threads that hop media/location? Breadcrumb evaluation: Did you leave a followable trail? Other comments: ---------- Some options for future learning: Compare how multiple FOSS projects practice $discipline (develop "first 15 minutes" in your chosen field) Workshops: * foo * bar * baz * fill in with modules RHU offerings: * foo * bar * baz * fill in with Tomislav Books and further readings: * foo * bar * baz * fill in with TOS reading list Practices & skills: * Release cycle * Feature proposal * Translation * Public collaborative writing (PR) * Licensing * Events/local presence * Packaging * Design (remote communication with visuals) * Test/sprint days * Hackathon attendance & organization * (may need to merge with "workshops" if enough of these overlap POSSE modules) ----- RHU gameplan, upcoming check-ins: Q1:____________________________ Q2:____________________________ Q3:____________________________ Q4:____________________________