Member roles for data re-partitioning

First approach at defining member roles which can be used to control the responsibilities that a node has when it becomes a cluster member
"should be able to will have access read and write"? That sounds like three sentences thrown in a bag and shaken to see what comes out...