opensourcecorp.github.io/index.xml at main · opensourcecorp/opensourcecorp.github.io · GitHub

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
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenSourceCorp - The Free and Open-Source Enterprise on OpenSourceCorp</title>
    <link>https://www.opensourcecorp.org/</link>
    <description>Recent content in OpenSourceCorp - The Free and Open-Source Enterprise on OpenSourceCorp</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Sep 2022 01:45:00 -0500</lastBuildDate><atom:link href="https://www.opensourcecorp.org/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Progress Report 2022-09-05</title>
      <link>https://www.opensourcecorp.org/blog/posts/2022-09-05-progress-report/</link>
      <pubDate>Mon, 05 Sep 2022 01:45:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2022-09-05-progress-report/</guid>
      <description>Wooooo boy howdy, what a STRETCH it&amp;rsquo;s been. Lots of things in life &amp;amp; work have come up and kept me away from working on OSC, but I wanted to throw out something quick to let folks know that neither I nor the project are dead.
rhad has been under a lot of recent work. It is now version v0.3.0. While most of the updates were a lot of internal refactoring that aren&amp;rsquo;t going to be very visible to users, the minor-version bump is because rhad now runs go vet as part of its Go linter runs.</description>
    </item>

    <item>
      <title>Progress Report 2022-06-20</title>
      <link>https://www.opensourcecorp.org/blog/posts/2022-06-20-progress-report/</link>
      <pubDate>Mon, 20 Jun 2022 15:00:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2022-06-20-progress-report/</guid>
      <description>Some heavy updates in this one, so buckle up for what&amp;rsquo;s changed!
Secrets management Up until now, OSC has been strictly leveraging an implementation of Salt&amp;rsquo;s Pillar functionality for secrets management &amp;ndash; and that implementation is the default, which is &amp;ldquo;store all secrets on the configmgmt disk&amp;rdquo;. While this has worked fine (and can be a valid strategy in some enterprise environments), it&amp;rsquo;s not what you would call &amp;ldquo;best-practice&amp;rdquo;. If the configmgmt subsystem itself is ever compromised, every single piece of sensitive data is accessible to the attacker at once &amp;ndash; default Pillar data is just stored in plaintext on disk.</description>
    </item>

    <item>
      <title>About OSC</title>
      <link>https://www.opensourcecorp.org/wiki/about/</link>
      <pubDate>Mon, 06 Jun 2022 10:39:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/wiki/about/</guid>
      <description>Originally named &amp;ldquo;Project Optimus&amp;rdquo; and started in March 2021 by Ryan Price, OpenSourceCorp (OSC) was first intended as a dumping ground for all of Ryan&amp;rsquo;s own disparate, growing code repos. As he started to add new codebases, he thought it might be more valuable to readers to try organizing the content into something more cohesive. After a lot of spooling on how that might look &amp;amp; act, OSC was publicly announced in July 2021.</description>
    </item>

    <item>
      <title>Progress Report 2022-06-05</title>
      <link>https://www.opensourcecorp.org/blog/posts/2022-06-05-progress-report/</link>
      <pubDate>Sun, 05 Jun 2022 21:20:16 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2022-06-05-progress-report/</guid>
      <description>Not too long between updates this time, but I&amp;rsquo;ve got a few neat pieces of news to share.
First and foremost, you may recall that I said we&amp;rsquo;d gotten a domain name (opensourcecorp.org) in a previous post. For some time now, it&amp;rsquo;s really just had some redirect rules to point folks to the GitHub Org, and to the GitHub Pages site for blog posts.
But now, it&amp;rsquo;s a real-ass website! You might even be reading this post on it right now!</description>
    </item>

    <item>
      <title>Progress Report 2022-05-15</title>
      <link>https://www.opensourcecorp.org/blog/posts/2022-05-15-progress-report/</link>
      <pubDate>Sun, 15 May 2022 12:00:00 -0600</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2022-05-15-progress-report/</guid>
      <description>(Checks date of last post, sweats profusely)
Not a ton of changes in this update, I&amp;rsquo;ve had a lot of things come up these past few months that have prioritized my attention (a few conference talks to prepare for, dog &amp;amp; personal health issues, house repairs, work-work, etc). But some impactful updates nonetheless!
All OSC infrastructure repos have now been consolidated into a single monorepo, osc-infra. This implies that you should expect old links to the individual infra repos to be broken.</description>
    </item>

    <item>
      <title>Progress Report 2022-02-27</title>
      <link>https://www.opensourcecorp.org/blog/posts/2022-02-27-progress-report/</link>
      <pubDate>Sun, 27 Feb 2022 12:00:00 -0600</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2022-02-27-progress-report/</guid>
      <description>More radio silence as ever more work has been done across OSC. As you&amp;rsquo;ll see from the list below though, this is a really big set of changes/new stuff!
The conflation of infrastructure repos with application repos has grown to be a potential source of confusion for readers. As such, OSC should shortly be moving from a mono-org source, to orgs separated by identifier (opensourcecorp-infra, opensourcecorp-apps, etc). This should make it more clear what type of repo you&amp;rsquo;re looking at when you&amp;rsquo;re browsing a certain org.</description>
    </item>

    <item>
      <title>Progress Report 2022-01-02</title>
      <link>https://www.opensourcecorp.org/blog/posts/2022-01-02-progress-report/</link>
      <pubDate>Sun, 02 Jan 2022 19:30:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2022-01-02-progress-report/</guid>
      <description>Happy New Year!
Over the holiday season, I&amp;rsquo;ve had about a week of dedicated time to do a lot of net-new work for OSC, as well as to go back and do some much-needed cleanup &amp;amp; consolidation across several of the core codebases.
First &amp;amp; foremost, we&amp;rsquo;ve now got a working OCI image registry! gnar needs one for custom images, so it turned into a priority pretty quick. The registry is called photobook, which is our implementation of the Harbor registry software.</description>
    </item>

    <item>
      <title>OSC local bootstrapper available</title>
      <link>https://www.opensourcecorp.org/blog/posts/2021-12-11-local-bootstrapper-available/</link>
      <pubDate>Sat, 11 Dec 2021 16:00:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2021-12-11-local-bootstrapper-available/</guid>
      <description>OpenSourceCorp (OSC) development continues to chug along. Below are some of the updates we&amp;rsquo;ve been hard at work on, when time presents itself.
One of the net-new things we&amp;rsquo;ve worked on recently is the introduction of a (working) service-discovery implementation via HashiCorp Consul (named &amp;ldquo;faro&amp;rdquo;, which means &amp;ldquo;lighthouse&amp;rdquo; in a few Latin-root languages). Updates to aether allow for each platform/app to easily register themselves with the Consul cluster, and be discoverable via clean domain names and not IP addresses anymore, with two foundational exceptions that still need known IPs at their first launch (faro itself, and aether).</description>
    </item>

    <item>
      <title>OSC updates: hosting decision &amp; live services!</title>
      <link>https://www.opensourcecorp.org/blog/posts/2021-10-04-deployment-update/</link>
      <pubDate>Mon, 04 Oct 2021 21:15:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2021-10-04-deployment-update/</guid>
      <description>OpenSourceCorp (OSC) development has slowed down in recent months as Ryan (founder &amp;amp; maintainer) has gotten caught up in work-work. However, with renewed motivation (looming conference talk at SaltConf21, presenting on OSC!), we&amp;rsquo;re back at it again!
One of the chief goals of OSC has been to have its services live on an as-unmanaged-as-possible platform, in the service of helping to teach the community all about the core functionality of computing, storage, networking, and security.</description>
    </item>

    <item>
      <title>New architecture diagram!</title>
      <link>https://www.opensourcecorp.org/blog/posts/2021-07-25-new-arch-diagram/</link>
      <pubDate>Sun, 25 Jul 2021 20:00:00 -0600</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2021-07-25-new-arch-diagram/</guid>
      <description>OpenSourceCorp&amp;rsquo;s home repo has a new architecture diagram up! This diagram provides a high-level layout of the architecural flows for the current &amp;amp; future core OpenSourceCorp platforms. It&amp;rsquo;s pretty rough at the time of this posting, but I&amp;rsquo;m not exactly a designer :)
If you peruse the various repos across OSC, you&amp;rsquo;ll notice that most are still empty placeholders, not-yet-functional, or still need some serious work &amp;ndash; but many have continued to receive updates to their codebases (still just me over here!</description>
    </item>

    <item>
      <title>Announcing OpenSourceCorp!</title>
      <link>https://www.opensourcecorp.org/blog/posts/2021-07-05-announcing-opensourcecorp/</link>
      <pubDate>Mon, 05 Jul 2021 23:50:00 -0500</pubDate>

      <guid>https://www.opensourcecorp.org/blog/posts/2021-07-05-announcing-opensourcecorp/</guid>
      <description>Today, I&amp;rsquo;m very excited to finally announce the public launch of OpenSourceCorp &amp;ndash; the free and open-source enterprise. This is something I&amp;rsquo;ve been working towards for a few months now, and while it&amp;rsquo;s been public the entire time, it&amp;rsquo;s finally in a spot worth sharing with the rest of the world.
My contributions to the open-source community all started with an ndJSON logging framework for R that I wrote at work, to solve a very specific set of challenges I was having.</description>
    </item>

  </channel>
</rss>