[Architecture] Summary of Wednesday's UIOptions/PGA architecture/roadmap community meeting

Colin Clark colinbdclark at gmail.com
Fri Jun 7 14:31:51 UTC 2013

Hi Antranig,

On 2013-06-07, at 6:14 AM, Antranig Basman <Antranig.Basman at colorado.edu> wrote:

> The early part of the meeting presented the roadmap and surrounding community and design structure for the group of interfaces that will be managed by the core UIOptions code as part of the overall PGA ecosystem - this includes deployments such as UIOptions as part of work for FLOE as well as tools such as the PCP and PMT for the GPII. I've uploaded a whiteboard snapshot which sketches the relationship between various tools at the different levels of the "user sophistication/intrusiveness" spectrum:
> http://wiki.fluidproject.org/download/attachments/34575412/PGA+Tool+Ecosystem+Whiteboard.jpg
> The level of technical complexity (which could be inversely correlated with "invitingness" to a user who needs an interface with minimal intrusion into their workflow) scales towards the right of the diagram, as illustrated by the buckets with increasing numbers of chili peppers.

This whiteboard diagram by Dana, Joanna, and Jess has been posted along with another related diagram to the Fluid wiki:


As far as I know, they're planning to post more description and background information to this page. In the meantime, your summary is very helpful.

> At the left is the "Discovery Tool", positioned as the overall entry point to the ecosystem, with the maximum level of "invitingness" and ability to get the user as far as possible into the world of desirable customisations with the absolute minimum of interaction.

The latest (and still very much in-progress) wireframes for the Discovery Tool are located here:


I hope this helps,


Colin Clark

More information about the fluid-work mailing list