pallet-membership offers ability to store and modify membership data. It provides hooks when membership changed, but does not offer any public interface to read membership data.

This means the user of pallet-membership is likely need to store the membership data again, like pallet-collective does here

This is just waste space. There should be some kind of trait Membership to allow query membership data from pallet-membership directly without duplicate data.