By necessity you have had to be very focused on the technical deliverables otherwise we don’t have anything to package or distribute. However as you have rightly pointed out documentation for safedrive as a decentralised file system, safegit/plume & dweb commercialization requires both technical (which you understand) & commercial thinking/documentation (where I can best assist). This includes writing product type stuff (product, price, promotion, place), operating procedures (Quality business operating system), Origination/Licensing/partnership/funding Agreements … related to your tech stuff which given your progress is a necessary focus and mindset eventually.
What we are all doing is completely new so we all need to learn from each other and together as we go forward. Working on the complimentary documentation to commercialisation will enable us to understand each other’s requirements to focus/progress y/our deliverables.
It helps also if we have a common outcome to focus on to align our thinking, narrative and agree a common language/story, documentation, system /IT actions etc. This is where I think the safe://commons design path, which by necessity must incorporate safedrive as a decentralised file system, safegit/plume & dweb components as part of Quality Business Operating system (QBOS) to enable a mutual AGI strategy, could assist. This context could be the best way to define what I need to learn on the tech front and help you identify suitable tasks in the short term! I will need to PM my thoughts here due to confidentialities. Also happy to help with any opportunities you feel are key.
As we move forward we will need a way to share and manage safe://commons documentation. To assist this need I have established a Commons Central Library which will sit directly behind safe://commons(sense) with the following structure (which we can progressively improve)
i. Commons Central Directory - which is where we can place/manage our (commercial & technical) working docs and where they can be deployed as pre-defined product outcomes which are set up as a “Curated set of working docs & links that persist”. NB a “repeatable framework of terms and mechanism” is a key ODI definition of a data trust.
ii. Commons Central Binary Library – where we can put technical documentation associated with establishment and management of the binary library David has spoken of previously. If I understand correctly could this be a place where we provide a “permissioned centralised view/access” to a safegit (decentralised IP) library catalogue to assist overall network learning & ability for any Community to access improvements easily?
In the first instance we could use this to assist us and others who contribute.
I hope you have had a good break and this helps you get back into it. PS Is it still hot OT? 