Fabric v3: Migrate away from docker chaincode builder
Replace the built-in docker chaincode builder with better fit-for-purpose approaches depending on user's objective:
- binary chaincode builder for users trying out Fabric
- chaincode-as-a-service for chaincode iterative development
- k8s chaincode builder for production environments on kubernetes
@denyeart sir is this being worked upon, can we connect for this ?
@aruns05 This is not being worked on but we'd accept new design proposals. Due to the impact this one will likely require an RFC proposal over at https://github.com/hyperledger/fabric-rfcs but discussion can begin here.
@aruns05 I'll refer you to the developers that were advocating for this feature - @mbwhite @jt-nti
@aruns05 @denyeart @mbwhite would it be worth scheduling a chat about it on a community call?
@aruns05 The next Fabric contributor meeting is this Wednesday July 19th, 13:00 UTC. I'll put this topic on the agenda. Contributor meeting details can be found at: https://wiki.hyperledger.org/display/fabric/Contributor+Meetings