Process starts at Fridays.
Moderator looks through the [Initial] Issue List.
If the [Initial] Issue List is ready, then start the Discussion cycle.
If the [Initial] Issue List is not ready, then don't start the Discussion cycle on this Friday -  this alternative branch is the default branch (branch with the strikethrough mark on the arrow), meaning that if the moderator does not review the Issue List and/or does not give the decision to start the Discussion, then by default the process will end here.

Discussion cycle.
Moderator will announce the Issues for discussion, the announcement will be sent as a Message to all the Voting Members, as a result of the announcement the Issue List shall be marked by a new state named [In discussion]. The basis for the announcement is either the [Initial] Issue List or the [Not Ready] Issue List, also during subsequent Discussion cycles one of the source data objects will be Issue votes [Final 2].
After the announcement, there will be 3 parallel branches (the Parallel Gateway is missing from the diagram).

One parallel branch is for moderating e-mail discussion, that activity (user task, would be better modeled as a subprocess task) will go on until it will be interrupted after 7 days by the interupting timer event.

The second parallel branch waits until the intermediate timer event fires after 6 days and then the Moderator will send the E-mail Discussion Deadline Warning as a message using a text from the Warning Text template document to all the Voting Members. The e-mail warning applies to the Issue List [In discussion], that will be included in the e-mail.

In the third parallel branch, the moderator will Check Calendar for Conference Call, if it is a Discussion Week then moderator waits until Thursday 9am and then Moderates Conference Call Discussion. If it is not a Discussion Week, then this particular conference call will not happen.

After 7 days have passed from the discussion announcement, the 3 parallel threads will converge and the Moderator will Evaluate Discussion Progress.
The Discussion subprocess will loop it there is no discussion of the issues or no sufficient solutions to the issues have been proposed.
Ready issues will be marked into the [Ready] Issue List, not ready issues will be marked into the [Not ready] Issue List. Essentially each issue in discussion will get marked with a new state: either [Ready] or [Not ready]. 

If the [Ready] Issue List is nonempty, then 
the Moderator will Announce Issues for Vote and the Collect Votes subprocess will be started. The affected issues in the [Ready] Issue List will be marked with a new state [In voting]. If the voting round is not the first round, then the [Adjusted] Issue Votes will be used for the announcement as well. The voting announcement message will be sent to all the Voting Members.