3 ms·
> M3O is built on existing public cloud infrastructure using managed kubernetes along with our own infrastructure automation and abstraction layer for existing
by dijit 5y ago
> M3O is built on existing public cloud infrastructure using managed kubernetes along with our own infrastructure automation and abstraction layer for existing third party public APIs. We host the open source Micro project as our base OS and use it to power all the Micro Services, which provide simpler building blocks for existing cloud primitives.
Forgive me if this sounds a bit negative... but, aren't you just reselling another cloud provider at this point?
Why would I use you and not go directly to EKS or GKE?
EDIT: Looks like you use digital ocean.. but please don't use commit messages like 'fix' https://github.com/m3o/platform/commit/5c006d3390cf680d58f11b2313bc0dbf9594e1a7 https://github.com/m3o/platform/commit/5c006d3390cf680d58f11...
- undecisive 5y ago> but please don't use commit messages like 'fix' :o I mean, I get it - I would avoid undescriptive commit messages myself, and I might mandate it for projects I own or am in some way responsible for. But I would never complain about it in some stranger's project. Of all the things to complain about...
- dijit 5y agoMaybe I'm a bit triggered because when taking over a project I was greeted by: https://imgur.com/a/iuWUcjr https://imgur.com/a/iuWUcjr It's a bit odd to call it a "strangers" project. I mean, you're right, it is, but it's open source, so we can comment on how that project is being managed. Surely they're hoping for some kind of contribution and things like that make me shy away a bit. It also seems minorly unprofessional to show what amounts to laziness publicly. I would be chewed out if I did that internally and we have higher standards for what the public see than what our own devs see.
- hdjjhhvvhga 5y ago> please don't use commit messages like 'fix' You may consider editing your edit.
- dijit 5y agoI have considered it. On the one hand it seems overly pendantic and petty. On the other it may harm perception of the products maturity and dampen desire of others to work with it. Additionally it is an anti-pattern which rejects the notion that commits are teaching tools (effectively nuking git-blame). Thus the feedback, while petty, is constructive. So I think it stays. Thank you for your feedback.
- hdjjhhvvhga 5y agoNo, I feel you and I agree with the message completely - there is no place for non-descriptive commit messages in today's world. Collaborating with people who are doing that is difficult. However, the comment seems misplaced, just like someone else noted in this thread.