Difference between revisions of "Talk:PKC documentation"
Jump to navigation
Jump to search
Line 8: | Line 8: | ||
''' #1API integrations | ''' #1API integrations | ||
: restAPI | : restAPI [[restAPI example | example]] | ||
:: integrate several open source or with open APIs to PKC | :: integrate several open source or with open APIs to PKC | ||
::: TOP - metrics on performance and CpL | ::: TOP - metrics on performance and CpL |
Latest revision as of 09:52, 14 September 2022
Draft Plan (proof of concept
To prove a multiple environment engine, secured by DAO essence, conducting a new developed society through “Science of Governance”
#1API integrations
- restAPI example
- integrate several open source or with open APIs to PKC
- TOP - metrics on performance and CpL
- Fossil - Use Fossil's SQlite relational engine, and Version control semantics to manage data assets and drive the commit workflow of Git
- GitHub - Ability to deploy through PKC,
- GIT - create CICD environments to Github, from Editors
- VSC - Ability to program and deploy through
- Matomo - metrics on history records
- other apps and services
- quantUX
- WEb3D
- integrate several open source or with open APIs to PKC
- QuantUX widget experiment (Guntur)
- Apollo Spreadsheets (Pedro’s team 1 developer?)
DID
- #4 E-ID - Auth, smart contract, Blockchain
- Keycloak (done)
- simulated packages (Working with Donald Gao)
- #5 E-Land -
- #6 E - Catalogue - (future clients such as LKPP)
Only visual simulated packages
#13 Content
- Build a new frontEnd design (UI/UX) “new skin” (Consider other Web3 Project Management Website Skins, for example:Wonderverse and Jira)
- Create interesting content to introduce new members to the PKC multiple programs
- Create presentation of everything we want to build with PKC
- Expand online self accountable and self pace education
- Measure capacity of students and work force (CpL)
- Create a promo video explaining the benefits to the world and the future of PKC
Internal
Essential for us, not to the proof of concept
#8 Security
- Finish the CICD - project was very open and Haviz had no control
#9 Testings #10 Deployments - Everyweek after CICD is set up in 2 stages
- From Dev to QA (Approved my Pedro and Haviz)
- From QA to Production (approved after Pedro stress testing and final approved by Ben)
#11 Documentation - Create a proper documentation
- Create flows of all component relations
- Create design portfolio of all components
- Create a DDT protocol
- Create technology documentation and implementation (including Open API doc)
#12 Core Development - stable the app
#14 Operations - Correct daily issues