| 01:48.28 | shalkie | jlp_znc: Mmmm... Needs more Holly |
| 01:49.14 | shalkie | Perhaps some Queeg quotes. ;) |
| 01:50.21 | shalkie | "This is mutiny, Mr. Queeg" |
| 03:22.07 | *** join/#utah tiwula (~lane@2605:e000:141a:cc1b:a437:be1e:6caa:dc4d) |
| 05:53.27 | *** join/#utah tiwula (~lane@2605:e000:141a:cc1b:a437:be1e:6caa:dc4d) |
| 15:19.12 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 16:56.05 | *** join/#utah tiwula (~lane@12.150.74.18) |
| 17:03.00 | jlp_znc | I love Queeg. |
| 17:03.17 | jlp_znc | "If you want to eat, you have to WORK!" |
| 18:16.33 | jfindlay | I'm starting to wonder if software 'engineers' even know how to git |
| 18:16.53 | jfindlay | everywhere I look, I see them using it like it's SVN or even worse |
| 18:18.43 | jfindlay | I should take git away from them and give them CVS: 'here you go; here's the tool that matches your use patterns' |
| 18:19.09 | jfindlay | some of them even talk about svn as if it's better than git |
| 18:20.10 | romanovic | that's scary. what's their excuse? are there any constraints on branching/release strategy? or are they just SCM boomers |
| 18:21.13 | jfindlay | I've spent many hours trying to explain how git branching works and the result is always the same dumbfounded dismissiveness |
| 18:21.26 | jfindlay | unwillingness to learn |
| 18:21.58 | jfindlay | the primary way to move commits around is by cherry pick |
| 18:22.41 | jfindlay | the codebase fragments between releases because regular merge forwards are too difficult |
| 18:23.19 | jfindlay | an existential fear of merge conflicts |
| 19:01.34 | *** join/#utah cstead_ (sid219570@gateway/web/irccloud.com/x-tbwuecxsgjinpoci) |
| 19:43.58 | *** join/#utah moccos (~moccos@104.243.62.132) |
| 21:11.41 | *** join/#utah emcnabb (~emcnabb@hs-nc-1fff767f54-29977-1.tingfiber.com) |
| 21:48.38 | *** join/#utah josephscott (~josephsco@74.114.153.251) |
| 21:49.37 | *** join/#utah keldwud (41821c54@unaffiliated/keldwud) |
| 21:52.38 | keldwud | trying to make sense out of the changes in docker with the mirantis acquisition. I've read a github thread, a docker press release and a mirantis press release but still not understanding the bigger picture |
| 21:52.51 | keldwud | anybody got it figured out yet? |
| 21:52.55 | keldwud | programmerq? |
| 21:53.54 | programmerq | what's your question? |
| 21:54.40 | programmerq | mirantis acquired Docker Enterprise Edition, which is basically: Docker Trusted Registry, Universal Control Plane, and the enterprise edition of the docker engine. |
| 21:55.14 | keldwud | specifically, what is the future of docker-ce, docker swarm, docker's relationship with kubernetes, docker hub |
| 21:55.27 | programmerq | docker-ce is owned by docker inc. |
| 21:55.45 | programmerq | the writing on the wall for swarm mode has been that there isn't really new dev going into it. |
| 21:55.57 | keldwud | and is this thread pretty accurate? https://github.com/docker/swarm/issues/2965 |
| 21:55.59 | programmerq | mirantis said they'd support it for 2 years for enterprise customers |
| 21:56.28 | keldwud | and thank you for taking time to answer all of my questions <3 |
| 21:57.08 | keldwud | just want to make sure I have a clear picture of the technologies and what will still be supported, etc |
| 21:57.17 | programmerq | the open source project hasn't announced any formal plans to my knowledge. that github thread is lots of speculation and is an accurate representation of the speculation that's going on. |
| 21:57.35 | keldwud | ok that was what I wanted to confirm is if that thread is mostly just speculation |
| 21:57.42 | programmerq | to my knowledge, the open source project hasn't announced plans to remove swarm-- I don't think they have any reason to. |
| 21:57.43 | keldwud | which is what it felt like |
| 21:58.05 | programmerq | but at the same time, they haven't really announced the future plans, just a vague "docker inc will support developers" -- whatever that means. |
| 21:58.12 | programmerq | I left shortly after the acquisition |
| 21:58.16 | programmerq | so I may be a bit out of date. |
| 21:58.42 | programmerq | but I still pay attention and haven't see anything clear on the future of docker open source other than it doesn't appear that it will go away |
| 21:58.44 | keldwud | *I'm* a bit out of date apparently since I hadn't realized you transitioned |
| 21:58.54 | keldwud | that's what I get for falling off the map for 6 months |
| 21:59.22 | programmerq | there is just enough dev velocity from all companies involved that docker-ce and the related components are not at risk of being discontinued. |
| 21:59.45 | programmerq | so the big thing for swarm mode is a question of what your needs are for commercial support-- nobody offers it really. |
| 22:00.02 | programmerq | any anyone that does will nudge you to k8s |
| 22:00.22 | programmerq | if you don't need commercial support, or you have a small project, it's still a fine choice because it kind of works really really well out of the box for a lot of usecases. |
| 22:00.39 | programmerq | k8s is the clear winner due to its capabilities, but it is no afternoon project by any means. |
| 22:00.51 | programmerq | either you use a hosted k8s, minikube on your laptop, or you pay a team to manage it. |
| 22:01.03 | programmerq | (a bit of an oversimplification, but not by much) |
| 22:01.36 | programmerq | swarm will likely stick around as being that thing in the sweet spot that it honestly was designed to fill. |
| 22:01.48 | programmerq | but don't expect commercial support or features in the foreseeable future. |
| 22:02.52 | programmerq | stepping away for a bit, but will be back in case you have followup questions. |
| 22:06.19 | *** join/#utah keldwud (41821c54@unaffiliated/keldwud) |
| 22:06.29 | keldwud | thank you, you answered my questions sufficiently |
| 22:07.19 | *** join/#utah tiwula (~lane@8.46.73.118) |
| 22:13.54 | jfindlay | ~napoleon jlp_znc |
| 22:13.55 | infobot | ACTION makes jlp_znc buy a lotto ticket for Napoleon |
| 22:24.33 | jlp_znc | ~systemd jfindlay |
| 22:24.33 | infobot | ACTION kills all of jfindlay's processes |
| 23:01.06 | *** join/#utah cstead_ (sid219570@gateway/web/irccloud.com/x-idpbgpnivesrurqv) |