Weāve had multiple discussions about how to proceed and unfortunately, we cannot come up with a solution.
The nature of the problem is that creating a build requires quite a bit of trust. It would be easy to add code to the build that sent private keys to a remote database, for instance. We canāt seem to coordinate the work of experts like @backpacker with people we trust like sigmike in a way that produces secure builds.
The developers we trust know nothing about OS X. This is an open source project working on decentralised infrastructure. Our culture revolves around the values associated with Linux and is far from the centrally controlled world of Apple. With a small team and small budget, this has been difficult for us to manage, as all OS X users of NuBits and B&C Exchange are aware.
There is no question in my mind that NuBits and B&C Exchange should support OS X. It is equally clear that neither myself nor anyone on the team can make the builds. I am utterly ignorant of all things Apple and as a result have nothing to offer in this effort. But the code is open source, so anyone anywhere on the planet can make OS X builds at any time, as @backpacker has demonstrated. Trusted builds are another matter.
The combination of the fact that the source code needed to create builds is completely accessible to all at all times and that our team has no expertise in OS X builds means the responsibility for creating OS X builds should be outsourced beyond the team.
I am happy to facilitate payment to someone creating OS X builds from development funds for each organization, but that will be the extent of my involvement and responsibility for OS X builds. I wonāt be making any attempts to coordinate OS X builds going forward. As a decentralised organization, that responsibility can and should be taken up by others.
