Onboarders, please say hello to your co-volunteers

[grecinto]

Hello newcomers,

Happy 4th of July! :)

FYI, there are about 12 volunteers who signified interest on this SOP project on LinkedIn. I hope you are having a good time learning about the project.

I will be honest, I am not a big leader of projects, especially Open Source ones like SOP. But here is, I feel like each one of you is a leader. We are all on this together, I am just a maintainer, but I feel like we are all on the same level here. ;)

Pls feel free to move around, learn the SOP project, product features and code set. Ask if there is something you'd like to learn and is blocking, somebody like me can definitely explain/unravel the mystery(ies).

Yeah, SOP is totally new, from the ground up software. We're breaking grounds, re-architected Storage engine, (realtime scalable) orchestration, and infused few things like Redis caching as L2 to come up with a break-through technology.

This stuff benefitted from being incubated out of the office, thus, a lot of the algorithms despite home-cooked, performs really well on what they are intended to do. And yeah, all of them (algorithms/solution) are home-grown and thus, 'not seen before, are not the traditional as discussed on books. BUT gladly, they were written with design patterns in mind..

Example, the btree data structures & algorithms in package "btree". That is a b-tree broken apart and infused with "repository" pattern. And thus, this version is able to perform also as a "controller", other than being a b-tree manager.

Anyway, those are already stable and not needing to be changed. :)
Most of the work or tasks today are about to bring the SOP product into production. Please find the items in "discussion" area to see what are the tasks needed to productize the product. And if you find an item you would like to work on, please comment on it so we can coordinate. FYI, I intend to work on the "automated test of Replication & Drive Reinstate" next as it is the most important piece today. And if anybody has expertise on Python installers, please feel free to take on the Python Wrappers installer. Rest are free for all. :)
Also, I feel like "we" will allow duplicate work on each item, why not? BUT it seems the group will also want efficiency, so, despite it is ok, it is better to take on "free items", nobody is working on yet. This way, we spread our efforts cover more grounds.

Just a brain dump, we need to know where we are & the roadmap ahead, at least, coming from the maintainer's plans before all of you signified interest to join... :)

At high level, SOP is robust, stable and ready to go, but there are a few bits still needed to wrap up this V2 release (V1 was the c# version, which was retired).

• Automated tests to simulate and probe the Replication & Drive Reinstate features. It is stable & shown very good behavior, BUT I have yet to write coverage on this area. Thus, 'am not comfortable shipping it without coverage.
• Python wrappers (that allows Python developer to use SOP library) installer.

And, here are the other tasks/items beyond V2:

• Business side development! SOP needs somebody who can champion pushing adoption to the IT industry, getting Investors to fund the project, getting IT team(s) early adopters (usually, investors help in this area!), etc...
• Documentation experts, API doc, product usage "manual"...
• Testers/Test Automation, benchmarks
• Dotnet c# wrappers to allow dotnet c# developers to be able to use SOP library.
• Java wrappers for Java developers SOP usage.
• Scala wrappers for Scala developers SOP usage.
• Rust wrapper for Rust developers SOP usage.
• Installer for each language wrapper:
  - Java wrappers installer
  - Dotnet c# wrappers installer
  - Scala wrappers installer
  - Rust wrappers installer
• Tools!!!! This area is totally empty. We need to identify & prioritize the tools needed to be implemented. Example, Data browsing & "adhoc query" tools to allow data visualization.
• IDE copilot, e.g. - schema browser, data visualization that is installable in IDE like VSCode, to aid in coding and better experience working with SOP library and databases.
• ETC...

---

And yes, please feel free to voice out your feedback in above & in general. I think we can just use replies on this topic here, as a threaded discussion. It also serves as a record of team meeting and notes. What do you think? :)

Kind Regards and Enjoy! :)
P.S. - Yeah, my idea of open source and volunteerism, is self driven. Own the project (community ownership, MIT license), I will support you fully. And I hope each one does the same thing.
Be honest, there is no bad idea, be upfront and brave to say it out loud. Say sorry after, if anybody offended anybody. And be forgiving,...
Breakout the "restrictive" and dog eat dog culture we've learnt in the IT office. Learn/expand that volunteerism spirit. And big thanks for adding "stars" to the project. It helps w/ visibility & smooth adoption, in time.

[grecinto]

Closing, onboarders can still access the closed page.