You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement the Workflow rules checked for in the model within the GUI.
This way, people only see the actions relevant to their situation.
None of the URLs have changed and the only modifications to the
context environment so far have been additive - thus up to here
there have been only a couple of minor backend changes. Namely,
enforcing the already implicit policy of only opening up at most
one of each Commitfest type at any given it. And allowing for
re-entrancy of a Patch to a Commitfest.
The UI does enforce a "Commit or Reject" policy for Patch resolution.
Staff can still use Returned with Feedback. The author is expected
to Withdraw their patch if they do not plan to act on the feedback,
or move it back to Parked and Waiting on Author. Or they can
Withdraw and create a new patch in the future. While the Workflow
is not against giving people options, the volume of both rejected
and returned resolutions is too small to warrant distinguishing them.
Hopefully the finished UX is intuitive. The core three actors in the
Workflow - author, reviewer, committer - have their core actions in
columns left-to-right (though the columns are action-type oriented,
not actor oriented). The headers are the verbs for the actions
in the second row. The third row is actor-oriented listing the
author(s), reviewer(a), and committer along with related membership
actions.
The fourth column is where the new movement implementation appears,
making /close/next obsolete, especially with the addition of Parked.
Having run out of actor categories the empty cell in the bottom-left
becomes a perfect place to display the core information from the
key-value table (which has been hidden). Namely, the status of the
Commitfest and Patch this POC pertains to, the version (hyperlink
on the label to the Edit screen), the topic (also with a label
hyperlink to Edit), the Subscribe/Unsubscribe button, and the
last modified timestamp.
Emails, CFBot, and Links also brought over in a key-value table;
while History is also hidden but part of the final design. The
hidden key-value table is being phased out. The key elements from
it that need to be figured out are:
- Status (is a form of History and that should get a re-work)
- Created (doesn't seem actionable, especially now with Parked)
- Latest Email (redundant with Email content?)
ID doesn't seem to useful and can be gotten from the URL if needed.
Title is already at the top of the page.
All other fields are incorporated into the Workflow UI.
0 commit comments