There are few usability issues. For the actions on a particular row, the double click is highly unconventional. That is evidenced by the fact that you have to tell people how to do it. I would suggest having a pull down on each row or use the standard sort of select,act style of interface where each row can be selected and there are several action buttons at top or bottom.
I also find that the + buttons don't work. Instead of allowing me to add something, the inexplicably turn into search boxes. It isn't clear what is being searched since the box appears after all the other data. It would make more sense if the + were slightly outside the content list and clicking it caused a number of text entries to appear that allow me to enter required information. I also find that the podling proposal link look like a content header because it is soooo close to the green explanation for how to add things. Removing the usage documentation (because it should be superfluous if the UI is properly discoverable) would allow this link to make more sense, but I would still want a separation from textual content and the list of people. On Sat, Jun 10, 2017 at 5:20 PM, John D. Ament <johndam...@apache.org> wrote: > I've put together a few podling status pages based on where some podlings > are, to demonstrate what it could look like. > > Juneau: https://whimsy.apache.org/roster/ppmc/juneau > AriaTosca: https://whimsy.apache.org/roster/ppmc/ariatosca > OpenWhisk: https://whimsy.apache.org/roster/ppmc/openwhisk > > These are just a couple of examples. Some things I still feel are missing: > > - List of repositories. For github it's easy, we can just link to a > search. Can't say the same for ASF hosted (yet) > - Migration. Haven't decided what I want to support, but the yaml files > are out there in > https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/ > if > anyone wants to edit theirs > - Anything missing? > - Do we need public access, or is committer access OK? >
