Thanks @teocomi what's the nature of the 'potential evil'? What's CI/CD and and how does keeping part of the project closed avoid the problems? I'm curious.
Thanks @teocomi what's the nature of the 'potential evil'? What's CI/CD and and how does keeping part of the project closed avoid the problems? I'm curious.
Long story short, there's a history of open source companies being hugged to death by big cloud providers (e.g. Redis, Mongodb, the whole Elastic Search kervuffle). We are just taking these small measures so we can keep Speckle as permissively licensed as possible.
BTW we're happy to give access to our distribution pipelines to close contributors!
@teocomi I can't pretend I understand your answer, but then I also don't actually need to :-)
Can someone link to an explanation of CI / CD ?
Hey Duncan, more than happy to jump on a call to chat it through if you'd like :)
By CI/CD I just mean some of the DevOps scripts that automatically deploy the server and build installers for our connectors.
We're a team of 9+ ppl working full time on Speckle, and we'd love to continue doing so. This means we need to navigate a very delicate line between building an awesome OSS product, paying ourselves, and defending ourselves from potential competition. And we want to be super transparent about this, so any questions or concerns just ask! We have actually just discussed making Manager OSS sometime soon.
If you or anyone here has experience running a business on an OSS product, we'd love to hear their advice!
@teocomi regarding OSS business have you spoken to Lindsay https://xeolabs.com/ and https://xeokit.io/blog_creoox_becomes_xeokit_sales_partner.html
I also recommend the podcast from https://sustainoss.org/
@duncan Found there was quite a lot of good points in Sustain-In-2021-Event-Report.
https://sustainoss.org/assets/pdf/Sustain-In-2021-Event-Report.pdf
Thank you for the link @duncan as I started reading the report, specifically about peer support I thought about the OSArch forum and other CAD forums I have participated in. One asks a question about functionality for example and that is followed by a 'back and forth' discussion, with a good resolution (usually) and then we move on... What would be better is to conclude the discussion by summarising and filing into a How to book, especially about BlenderBIM.
One could argue that searching the forum is good enough but that takes a lot of time and is daunting for many potential BlenderBIM users.
Each summary, for consistency could take the same form, 1. state the problem/need 2. step by step solution 3. links to further reading or video, 4. versions of Blender, BlenderBIM, date and 5. credits. It is important to use plain language and simple concepts to be as accessible as possible to all users.
If we ask a question and get help that resolves our question, then it is beholding on us to summarise and add this to collective knowledge, it also shows respect to those that have taken time to help.
Is this helpful?
@Nigel great that you read the report - I haven't made the time yet.
What you're saying makes perfect sense and does happen a bit https://wiki.osarch.org/index.php?title=Category:BlenderBIM_Add-on
Could the result of most discussion be incorporated into the pages in that category? It's all about a commitment to sharing/teaching being as strong as a commitment to learning. Sounds like you're on board with how important that is - so that's a damn good place to start.
Login or Register to reply.