During the discussion on group creation operations, we found some text that uses the term leader to describe two different concepts: on one hand the leader that provides the list of participating processes, on the other hand the leader that receives monitoring and failure notifications for the group. The two roles are not necessarily active at the same time for a given proc, this overloading is unclear and should be avoided.
This is not clear: leaders are by definition (they provided a list of members) leaders, why would they need to pass an extra attribute to declare themselves leaders a second time?
Originally posted by @abouteiller in #520
During the discussion on group creation operations, we found some text that uses the term leader to describe two different concepts: on one hand the leader that provides the list of participating processes, on the other hand the leader that receives monitoring and failure notifications for the group. The two roles are not necessarily active at the same time for a given proc, this overloading is unclear and should be avoided.
Originally posted by @abouteiller in #520