1. Join a mail list for a project that you like most, 2. get savvy with git (or svn if applicable) as well as the build technology for the project in question, 3. then as you see something that could be done and can achieve it yourself (with tests hopefully), donate it back.
Make sure to ask the project team in question as to how to donate it back (re #3). Also, start small because you don't know how enthusiastic teams are for receiving potentially unsolicited commits. Not Apache, but look how backlogged teams can be: https://github.com/gorakhargosh/watchdog re work (130 issues, 22 pull requests). You don't want to donate something to a team that can't consume reasonably quickly. - Paul On Sat, Feb 3, 2018 at 11:03 PM, Thaddeus Brown <tatbrown...@gmail.com> wrote: > I would like to know how I could become a member or show a contribution? > -- Paul Hammant DevOps <https://devops.paulhammant.com> Let me give your enterprise a step by step plan to get out of the hell of crazy branching models (ClearCase maybe?) and into the world of high-throughput CD on DevOps foundations.
