Why is the CA named 'membersrvc'?

[christo4ferris]

Description

Why is the CA named 'membersrvc'? First, the name is long and awkward which means moar unnecessary typing for users/developers (sure, auto-complete, but seriously). Secondly, 'membersrvc' doesn't really describe what this component is. It is a certificate authority (CA). In the documentation, we call it the CA. Why not name it that?

I would propose that we rename that component's image hyperledger/fabric-ca, and the binary fabric-ca. This makes it clear what the component is, and ties it to the 'fabric'.

Describe How to Reproduce

N/A

[christo4ferris]

@hyperledger/fabric-maintainers @smithbk @mastersingh24 thoughts?

[mastersingh24]

the original "naming" of the "block" in the architecture diagram was "membership services" most likely because permissioned networks have "members". I am agnostic as to what we call it now, although the current implementation is basically a set of CAs

[christo4ferris]

we seem to be very inconsistent in how we refer to this. In many places, it is referred to as the CA.

[ProgramErgoSum]

The fabric-ca is a good suggestion.