Minor updates to capture current status and new projects.
This commit is contained in:
parent
6422d3f978
commit
c856789477
2 changed files with 46 additions and 0 deletions
|
@ -55,6 +55,12 @@ products and income. GS has a coarse-grained roadmap towards the mission.</p>
|
||||||
|
|
||||||
<p>Current Status: <strong>Bootstrapping</strong></p>
|
<p>Current Status: <strong>Bootstrapping</strong></p>
|
||||||
|
|
||||||
|
<p>Current Estimate: <strong>Behind!</strong></p>
|
||||||
|
|
||||||
|
<p>Development moves forward, as does planning the business. Development is
|
||||||
|
behind pace -- a busy schedule and a young child are difficult to wrangle! How
|
||||||
|
does a one year bump, if that were to happen, impact the overall roadmap?</p>
|
||||||
|
|
||||||
<dl>
|
<dl>
|
||||||
<dt>Bootstrapping (2024)</dt>
|
<dt>Bootstrapping (2024)</dt>
|
||||||
<dd>Establish open source libraries and build the first product. Establish
|
<dd>Establish open source libraries and build the first product. Establish
|
||||||
|
|
40
src/oss.html
40
src/oss.html
|
@ -108,6 +108,46 @@ Maven/Ivy repositories at this time.</p>
|
||||||
</dl>
|
</dl>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
<section id="incubator">
|
||||||
|
<h2>Incubator</h2>
|
||||||
|
<dl class="project-list">
|
||||||
|
|
||||||
|
<dt><a href="https://git.garrity.co/garrity-software/gs-crypto">gs-crypto</a>
|
||||||
|
(Scala 3) (Library)</dt>
|
||||||
|
<dd>Based on JVM standard implementations and Bouncy Castle. Working to define
|
||||||
|
some crypto interfaces for GS projects in a way that works well with
|
||||||
|
Scala.</dd>
|
||||||
|
|
||||||
|
<dt><a href="https://git.garrity.co/garrity-software/smolban">smolban</a>
|
||||||
|
(Scala 3) (Application)</dt>
|
||||||
|
<dd>Fun side-project to create a small/minimal Kanban oriented system. Light on
|
||||||
|
process, helps prove out certain concepts in a non-critical
|
||||||
|
application.</dd>
|
||||||
|
|
||||||
|
<dt>torii (Scala 3) (Application) (Library)</dt>
|
||||||
|
<dd>No code is yet pushed. The intent is to create a reusable
|
||||||
|
Authentication/Authorization featureset for GS software and anyone that
|
||||||
|
wants to use it.</dd>
|
||||||
|
|
||||||
|
</dl>
|
||||||
|
</section>
|
||||||
|
|
||||||
|
<section id="commentary">
|
||||||
|
<h2>Commentary</h2>
|
||||||
|
|
||||||
|
<p>2024-06-10</p>
|
||||||
|
|
||||||
|
<p>During application development I keep getting hung up on different
|
||||||
|
dependencies such as crypto, the concept of a user, different core model types,
|
||||||
|
and other general things. While I've drafted suitable implementations before,
|
||||||
|
I want them in a clean, tested, well-organized set of packages.</p>
|
||||||
|
|
||||||
|
<p>I'm currently in the middle of a multi-week hiatus due to multiple types of
|
||||||
|
travel and other extreme schedule impact. Development set to resume in the
|
||||||
|
latter half of June.</p>
|
||||||
|
|
||||||
|
</section>
|
||||||
|
|
||||||
</main>
|
</main>
|
||||||
|
|
||||||
<!-- Footer ------------------------------------------------------------------->
|
<!-- Footer ------------------------------------------------------------------->
|
||||||
|
|
Loading…
Add table
Reference in a new issue