-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
84 lines (82 loc) · 4.64 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
<!DOCTYPE html>
<html><head>
<meta name="generator" content="Hugo 0.100.0" />
<meta lang="en" charset="UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1"/>
<link rel="icon" type="image/x-icon" href="/images/osc-logo.png">
<link rel="stylesheet" href="/css/main.css"/>
<title>OpenSourceCorp</title>
</head>
<body><div class="sidenav">
<a href="/">
<img src="/images/osc-logo.png" style="width:120px;height:100px;" alt="OSC Logo"/>
</a>
<h3>Navigation</h3>
<ul>
<li><a href="/index.html">Home</a></li>
<li><a href="/wiki/index.html">Wiki</a></li>
<li><a href="/blog/index.html">Blog</a></li>
<li><a href="https://github.com/opensourcecorp">Project SCM</a></li>
</ul>
</div>
<div id="content" class="content">
<h2>OpenSourceCorp - The Free and Open-Source Enterprise</h2>
<hr>
<p>Here at OpenSourceCorp, we strive to provide an opinionated perspective on how
software systems work “in real life”. We don’t have some grand monetization
vision for ourselves, nor do we propose anything particularly novel in <em>what</em> we
do. What we do is collaborate to write application code that runs on
infrastructure deployed via CI/CD pipelines, secured via applicable industry
best-practices, and supported by comprehensive documentation.</p>
<p>The novel component that we provide is that we do all of this work <em><strong>100% in
the open</strong></em>.</p>
<p>We do this because we have developed a general frustration with <em><strong>how</strong></em> modern
teams are expected to learn different things – especially how so many tools,
technologies, and processes are used in concert with each other in a broader
enterprise ecosystem. There are plenty of tutorials and “getting started” guides
for any number of tools or topics, but while several of these have supplements
for their use in a larger ecosystem, they’ve never feel like quite enough to
document the holistic lifecycle of a use case. The most valuable learning
material for <em>real</em> use cases happens within company walls with propietary
software – where if you’re not an employee, you don’t get to learn.</p>
<p>Take any given, relatively-complex software, like <a href="https://kafka.apache.org/">Apache
Kafka</a> or <a href="https://www.vaultproject.io/docs">HashiCorp
Vault</a>. Their respective documentation portals
are very comprehensive, and provide a wealth of use cases, simple & complex
configurations, and more.</p>
<p>But what if you’re self-hosting a production-quality cluster at your company?
How do you <em>actually</em> deploy that cluster, and not rely on manually launching it
via the (usually very good) installation instructions? Do you bootstrap some EC2
machines in a CloudFormation template for an AWS deployment? Do you do that
bootstrapping with raw shell code, <a href="https://docs.ansible.com/">Ansible</a>, or
something else?</p>
<p>Or maybe you stuff containers into <a href="https://kubernetes.io/docs/">Kubernetes</a>?
The docs for Vault, for example, provide a <a href="https://www.vaultproject.io/docs/platform/k8s/helm">Helm
chart</a>, sure – but what if
your team/company doesn’t use Helm?</p>
<p>Or, isn’t <em><strong>allowed</strong></em> to use Helm? We haven’t even touched on the security
considerations that your company might take against any tools, and those
considerations vary wildly for the <em>same</em> tool across orgs. A version bump for a
Java library might be a few hours of testing & validation in some orgs, but
(literally) <em>years</em> of security review in others, <em>before</em> you’re even allowed
to start doing those same upgrade validations.</p>
<p>All of this begs the same question again – <em><strong>how do you actually work with
this stuff in real life?</strong></em></p>
<p>These, and ever more questions, are what OpenSourceCorp aims to provide answers
& perspective for. Real code, real solutions, for real enterprise challenges.</p>
<p>If you’d like to get involved, reach out to us!</p>
<hr>
<h3 id="site-roadmap">Site Roadmap</h3>
<ul>
<li>Wiki section for the site</li>
<li>“About” page (which might partially be <em>this</em> page’s contents moved)</li>
<li>Core values</li>
<li><code>osc-infra</code> arch diagram</li>
<li>Contribution/onboarding model</li>
<li>Target platform commentary – “why not (strictly) Kubernetes/AWS/etc.”, etc.
Maybe that’s part of core values though.</li>
<li>Partnership model (i.e. how do we get other OSS projects to USE our platforms,
to help enhance the value of doing everything in the open)</li>
</ul>
</div></body>
</html>