(open-source) skill inter-dependency
( ఠൠఠ )ﾉ Ever feel like you need to learn 10 other skills when trying 1 new thing in tech land?
I just did --
As my last post talked about, I'm slowly checking out ways to participate in development at Mozilla.
I've been surfing around all the different groups and projects to find one that I'd want to sink my n00bie teeth into. I thought SUMO (support.mozilla.org) would a nice one since it's a project that has wide community exposure for low-tech level support. It felt like a good way to build familiarity with Mozilla internal and external culture--and a good way to participate at various technical levels.
I'm not a Mozilla employee, but I do want to find a project I can participate in and grow with. I'm NOT wanting to do a touch and go, add a line to my resume, and disappear.
SUMO uses the Kitsune platform, and of course, me being me, I found possible edits to their docs. That aside, I also followed the doc to clone the repo and see about hacking Kitsune locally.
Enter Docker.
I've never used it, and all the passive mythology is that it just works. I actually thought it is some magical tool that just works. In reality, there is much more. First off, installing it comes with a bunch of options. Then, after installation, Docker dashboard is loaded with information.
Docker aside, now the project comes with MakeFiles and yml and so many other script files. There are much more components at work. What is doing what? What is calling what? What's the flow?
Next steps:
- Should I go learn more about Docker so I'm more comfortable with what's been spewn out by it?
- Should I re-clone, branch this time, and try following the docs exactly as written?
- Should I message the SUMO on Matrix and ask for help?