I like this proposal, and would like to be in the conversation... It would be helpful to send out a survey with those questions (and more) and dump the results in an LLM and argue about the responses collectively in that discussion.

There is a divide in the open exchange between tech examples, etc and integrations, drivers, etc that cultivate maintenance because they are in use and chasing versions... your work is in this category for sure with the python dbi driver, lately go, etc.    These projects need to be pulled from Open Exchange immediately, or just be placeholder that point to an opencollective (as an example), I think OpenExchange is giving the illusion that OSS is being supported in some way, but not in the ways you listed above.  There is also a proliferation of github projects out there with the two words "intersystems" and "community" slammed together in some shape or form out there that gas light this subject.

Id pipe up during this call and probably blather on about the following:

Are there any examples other than the above that are based on a derivative proprietary work ?
What are the previous attempts at this ? I think Globals java was Open Sourced, Id like to undrstand the legal behind that and understand the shortcomings/successes of that...I think rzf may be something on the horizon, any others ?

Id like to understand what went on with the VSCode extensions as an example and have that play out differently with oss too.

I have fallen in the trap of being in between these worlds, OSS and proprietary software and want to share the experience... in a nutshell, I got these two responses:  InterSystems: you cant resell that.  OSS (spark library), Apache2: you cant distribute that.

Ultimately I think what needs to happen is we go out on our own and provide incontraverable value and have some thick skin, knowing that intersystems can fork it at anytime and "do it better" or resist "selling" the project in any shape or form.  We'd also need to dismiss any wind that internally at InterSystems "its in the backlog" and not let that deter development.

InterSystems would have to look at the community output/features/governance, along with the 5 pillars you listed above, and know that they would be better off funding the project externally than doing it themselves. Also, if its important enough, allowing for them to provide priorities in the development... we would need to be meticulous around the release cycles of IRIS too.

Ill tell you that when I saw your post about the Go Library and immediately framed a project that I well know could take advantage of your library with a ++, and would push InterSystems hand in this regard... it may be a cool excercise to see what would happen if the Go library were forked immediately under an Apache2 license or something.  I have a good idea here.

The elephant in the room is the legal needed to avoid violating agreements ourselves, crossing InterSystems boundaries to maintain a healthy collaboration, or allowing some other company to fork it and bury it in their monitoring app or something without acknowleding the component in their solution... The open collective pilot would help shake out some gaps for sure.

I think we could all use our Global Masters points to score a bunch of socks or something and sell them on ebay to start an initial fund to derive percentages, org structures, yadda yadda.

Im in, and would prioritize attending and contributing to the discussion.

same

I use this one quite a bit...

Set tSC=##Class(Security.Users).Create("user","%SQL","pass","NAMESPACE","","","",0,1,,,,,,1,1)