kwaeri-cli-steward 
A Massively Modified Open Source Project by kirvedx
The @kwaeri/steward component for the @kwaeri/cli user-executable framework
TOC
The Implementation
kwaeri/steward is responsible for discovery and delegation between the kwaeri/cli and service providers.
The steward was originally included in the entry point to the platform under the directory [from root] node-kit/core/. In an attempt to standardize implementation - by separating concerns - as well as to ease maintainence of each component of the platform, the steward was migrated to its own component module.
Getting Started
NOTE
kwaeri/steward is not ready for production. This module has been published for testing and development purposes. You're free to try out anything that may already be available, but please be aware that there are likely to be many pieces of the platform not working properly - or at all. As completion of the new platform and tooling nears completion, updated documentation and complete examples will be made available.
Installation
kwaeri/node-kit wraps the various components under the kwaeri scope, and provides a single entry point to the node-kit platform for easing the process of building a kwaeri application.
kwaeri/cli wraps the various CLI components under the kwaeri scope, and provides a single entry point to the user executable framework.
To Install kwaeri/steward specifically:
npm install @kwaeri/stewardUsage
The Steward component is something leveraged by the CLI explicitly in its handling of commands passed to it by the end user.
To leverage the Steward component directly, you'll need to include it:
// INCLUDES
import { Steward } from '@kwaeri/steward';
// ...To be continued...
NOTE
As mentioned earlier, the plan is to continue development of the myriad components of the node-kit platform - the Steward component included - and ultimately ease the process of development, maintainence, and usage of each individual component as they are decoupled from one another.
How to Contribute Code
Our Open Source projects are always open to contribution. If you'd like to cocntribute, all we ask is that you follow the guidelines for contributions, which can be found at the Massively Modified Wiki
There you'll find topics such as the guidelines for contributions; step-by-step walk-throughs for getting set up, Coding Standards, CSS Naming Conventions, and more.
The project also leverages Keybase for communication and alerts - outside of standard email. To join our keybase chat, run the following from terminal (assuming you have keybase installed and running):
keybase team request-access kwaeriAlternatively, you could search for the team in the GUI application and request access from there.
Other Ways to Contribute
There are other ways to contribute to the project other than with code. Consider testing the software, or in case you've found an Bug - please report it. You can also support the project monetarly through donations via PayPal.
Regardless of how you'd like to contribute, you can also find in-depth information for how to do so at the Massively Modified Wiki
Bug Reports
To submit bug reports, request enhancements, and/or new features - please make use of the issues system baked-in to our source control project space at Gitlab
You may optionally start an issue, track, and manage it via email by sending an email to our project's Service Desk.
For more in-depth documentation on the process of submitting bug reports, please visit the Massively Modified Wiki on Bug Reports
Vulnerability Reports
Our Vulnerability Reporting process is very similar to Gitlab's. In fact, you could say its a fork.
To submit vulnerability reports, please email our Security Group. We will try to acknowledge receipt of said vulnerability by the next business day, and to also provide regular updates about our progress. If you are curious about the status of your report feel free to email us again. If you wish to encrypt your disclosure email, like with gitlab - please email us to ask for our GPG Key.
Please refrain from requesting compensation for reporting vulnerabilities. We will publicly acknowledge your responsible disclosure, if you request us to do so. We will also try to make the confidential issue public after the vulnerability is announced.
You are not allowed, and will not be able, to search for vulnerabilities on Gitlab.com. As our software is open source, you may download a copy of the source and test against that.
Confidential Issues
When a vulnerability is discovered, we create a [confidential issue] to track it internally. Security patches will be pushed to private branches and eventually merged into a security branch. Security issues that are not vulnerabilites can be seen on our public issue tracker.
For more in-depth information regarding vulnerability reports, confidentiality, and our practices; Please visit the Massively Modified Wiki on Vulnerability
Donations
If you cannot contribute time or energy to neither the code base, documentation, nor community support; please consider making a monetary contribution which is extremely useful for maintaining the Massively Modified network and all the goodies offered free to the public.
