hyperledger-labs
Support new way of managing channels for HF since 2.3 (no system channel)
See: https://hyperledger-fabric.readthedocs.io/en/latest/create_channel/create_channel_participation.html
This is now even more significant due to v3.0.0 dropping support for ordering service system channels.
It won't be possible to support v3.0.0 and subsequent v3.x versions without this.
Personally, I would've appreciated a big fat warning disclaiming that Fablo still used system channels. I was in the process of using Fablo to bootstrap a production network and now I feel like I shouldn't because of this.
Thanks @joaormatos for your comment. The implementation of the warning, starting from a given Fabric version should be fairly easy - feel free to contribute, I can give you some guidance if you want.
Fablo is not designed to bootstrap production network, but I'd say the main issues are (1) how certificates are created and handled, (2) lack of decentralization, and (3) the fact that it uses Docker. The main goal for Fablo is local development + CI processes. For production use cases I suggest the Bevel operator.
Also, internally we have a PoC of Fablo running Fabric v3.0, with no system channel. It should be released in a month.