Skip to content

Instantly share code, notes, and snippets.

View tpepper's full-sized avatar
🏠
Working from home

Tim Pepper tpepper

🏠
Working from home
View GitHub Profile

DRAFT / WIP / PoC

Social Media Guidelines for Open Source Devs

Be on social media AND protect project (and employer) interests

  1. Know your responsibility: Your content and conduct on the internet and social media is your responsibility. Adhere to applicable codes of conduct, laws, etc. Respect copyrights/trademarks. As a leader how you communicate matters as much as what.
@tpepper
tpepper / k8s_prmt_misc.md
Last active February 11, 2019 19:24
Kubernetes Patch Release Management Team misc
Action Example flow for 1.13.3 Possible wrapping
Make sure you have latest release tooling cd ~/go/src/k8s.io/release && git pull same
Configure branch n/a make releasebranch release-1.13 Stores locally in a .releasebranch file for subsequent commands.
Mock build staging ./gcbmgr stage release-1.13 This may fail (eg: CI not fully green), and if so gives hint on suggested buildversion for explicit use. make mockstage
Mock build staging , optionally running on explicit commit (CI not green, looks like flake) ./gcbmgr stage release-1.13 --buildversion=v1.13.3-beta.0.37+721bfa751924da ./gcbmgr tail eaa329ae-b013-4feb-9194-68fe8597b497 make buildversionexception=v1.13.3-beta.0.37+721bfa751924da Stores locally a .buildversionexception file holding the exception string. make mockbuild
Mock build staging success? Visually confirm yes same
Mock release ```./gcbmgr release release-1.13 --buildve
@tpepper
tpepper / new-to-k8s.md
Last active May 8, 2019 04:38
Kubernetes New Comers

Kubernetes New Comers

Folks new to kubernetes and wanting to contribute to the open source project frequently ask "what should I do". Here is my general advice:

  1. If you have an area of interest/experience/passion, look for a match in the SIG list, engage in a SIG or WG or two via their regular meetings, slack channel, mailing lists, etc. Watch what they’re up to, see where your intents and needs match theirs, and contribute to those where you’re capable.
  2. Consider looking at the overarching topics, like docs / contributor experience / release, as areas to get a broad view of the project and perhaps find contribution possibilities.
  3. Don't aim to boil the ocean with huge initial contributions. Look for basic "chopping wood" and "carrying water" areas to get some initial orientation and make notable contributions to the overall community and project health. You don't yet know what you don't know, so be humble, expect to make mistake