Hi all,
John, for the video, are my comments above. In short, you can make shory videos and someone (myself or others) can out them together into a larger video, voice over that and add text (add context). But in order to be able to collaboratively make a video, we need to share a script. You are the technical guy, so you decide most of the script or storyline. That script can be just a series if booletpoints in chronilogical order. If you make the script before it will help you plan your shots, because you'll need to illustrate what you want to talk about. The person who edits the larger video will follow the script to compose the narration and stitch the short videos together.
A larger video is better than a bunch of shorter videos on a webpage containing text. That's because you make that content site-specific. You can't propagate it on social media or use it to grow the project.
For the website we need to understand what type of website we're talking about. This is the website of the Exchange Firm, the commercial side of the project. It doesn't need to have collaborative features, just presenting a product or a service, a transaction module, a service module for support (which can be a link to an open forum).
Back to our structure. Every project has a collaborative innovation network, which MUST live on the Sensorica website, otherwise it is not considered a Sensorica project and no support from the network can be deployed free of charge. Every project can have a commercial side, an Exchange Firm, which can have it's own web identity but MUST refer to the Sensorica side open and collaborative innovation network. Every project has a Custodian, a non profit organisation that makes sure that the relation between the open innovation network and the Exchange Firm is well maintained. The Custodian offers other services to the project and the entire OVN.
A project that doesn't have these features is not a Sensotica project and it is not allowed to function within the network.
So, the GrowSense.io website can only be the commercial side of the project, if GrowSense is a Sensorica project. All collaboration on the tech should happen on the Sensorica website. Therefore, there are two digital environments to create and maintain: the GrowSense web presence and identity with ecommerce capabilities and the open innovation digital environment, which lives on the Sensorica website.
Another comment about the GrowSense project, must engage in activities for growing the community. John has called for help on multiple occasions and he recently hinted to fatigue. This project relies mostly on John for development, with a bit of help from Ken. That is unsustainable and non-resilient.
I know this project has quite a bit of funds, which are not interested in doing technical work. Most of us are lacking the proper skills for technical work. But here's the thing. If we din't add more people for technical development we might lose this project. I am sounding the alarm to tell you that we can make things better, if not we might lose it, and you have been warned.
What can we do?
We already have a methodology in place that, has never been properly deployed. We just need to follow the steps, as if we're starting a project from scratch. This will lead us building a stronger community around this project.
My opinion, I would immediately stop any tech development and commercial development and build an organisational basis for GrowSense. Without an organisation we have no project and no product. The organisation comes first, and GrowSense is only hanging on a thread.
I can facilitate this work, but I cannot drive it. Those who want to contribute manifest our interest here and contact me if you have questions.