...
- Email the Grouper-Users List asking for input
- Ask for input at the face-to-face Grouper WG at 2012 SMM
- Reach out to specific campuses asking for input
- Schedule a webinar to discuss UI planning with the community
- Ask the UI experts at U-Chicago for their input on the UI and also on the process of involving the community
- Create a users group who to review the user interface as it is being developing
Consider chunking things into phases along these lines:
Date(s) | Activity |
|---|---|
April 1 - May 31 | Gather community requirements and requests in table above. Weekly reflection on grouper-dev list of new requests and any discussion of them. Counter proposals? Acceptable? Relative priority? Do others want to add their names as Requesters? |
April 23 | I2 SMM Grouper WG F2F |
May 1 | Float initial proposal for technology stack to be used to build v2.2 UI. Post to grouper-dev. |
May 1-14 | Drive discussion on grouper-dev of tech stack, with intent to settle as much of it as possible during this period. |
May 18? | IAM Online focused on Grouper v2.2 UI planning & requirements |
May 15 | Float initial proposal for UX process to grouper-dev |
May 15-31 | Drive discussion on grouper-dev of UX process with intent to settle it during this period. |
June 1-15 | Finalize acceptance status of each request by grouper-dev and assign each to a priority class. |