- Add team member to:
- bsdlabs GitHub Organization and @everyone team.
- @FreeBSDHelp team (via TweetDeck).
- @FreeBSDHelp Analytics with
Organic analyst
role. - FreeBSD Discord
@community
role
- YOU: Create a pull request(PR) adding yourself to the "Team" section in this document with:
- Background and bio/summary.
- Location (country is fine) & timezone.
- Some links (twitter, homepage, etc).
- Team join date.
- YOU: Get your environment setup. Recommend:
- YOU: Touch base and intro yourself to the team.
- YOU: Send an tweet out to the world on @FreeBSDHelp introducing yourself.
- YOU: Review this document, make at least onne non trivial edits (via pull request) to to clarify things or add detail.
- YOU: Run wild for a month, tweak and update the doc with Q/A (FAQ) and other things that come up as you go.
- YOU: Get help, ask questions, participate in the team.
- Evolve this onboarding process.
- Someone should have invited you to the Tweetdeck team- you'll get an email like this:
- If you click "Login to Twitter", it should take you directly to the TweetDeck homepage. I'd also recommend grabbing the BetterTweetDeck browser extension.
- Once you're at the TweetDeck homepage, go ahead and click "Add Column" and add a "Home" column with the @FreeBSDHelp account, like this:
- You should now see a column with the "Home" label:
- If I were you, I'd pop in columns for Notifications, Messages, and at least one List, so you can see everything at once:
You're all set! Bonus points if you used a *BSD to do this- I didn't, lmao.
- Someone should have invited you to the GitHub repo- you'll get an email like this:
-
Click "Join @bsdlabs" and you're in! You can edit the Team and FreeBSDHelp pages to add yourself to the team. Make sure you check out the Guidelines page too!
-
For non-trivial changes to documentation:
More bonus points if you used a *BSD. :D