John D. Ament wrote on 6/28/17 6:28 AM: > On Fri, Jun 23, 2017 at 8:53 AM Sam Ruby <ru...@intertwingly.net> wrote: > >> On Fri, Jun 23, 2017 at 7:54 AM, Shane Curcuru <a...@shanecurcuru.org> >> wrote: ...snip...
>> 2) replace the dropdown with a pencil icon, and have clicking on that >> create a dialog box that walks you through the potential operations. >> > > I guess the question is whether or not I'm coming in and it's already > editable. A dialog breaks the flow, especially since you're not changing a > lot of details about a user. Their name should be coming from LDAP, so its > literally the contents of the drop down. That's the big question: how do we clearly keep editing operations simple and straightforward, but ensure that users understand when they do X (click Submit, select name from combobox, whatever) that it will actually write that operation. Dialog boxes make this implicitly clear, but I agree break the flow. I just want to be sure that whatever metaphor we have for "Make this change now" is consistent. ...snip... >>>> - How to find existing committers >>> >>> The search box isn't completely clear to me: if you're just finding >>> committers within a PMC, how is this faster than CTRL-F to use the >>> browser search? >> > > The search box should be limiting the displayed users to only those who > match. There may be multiple matches. Browser based search doesn't have > all of those features. It also wouldn't be able to match in a drop down > box. Good point, that is definitely valuable. ...snip... >>> No, please do not use emeritus. While some PMCs use it as a social >>> convention, from the board's point of view, individuals are either on a >>> PMC or not on the PMC - there is no other state. >> > > That's fine, as long as all the chairs agree as well. Let me rephrase. Immaterial of what some PMCs may think, the ASF either considers an individual to be on a PMC, or not on the PMC. There is no emeritus state within projects as far as the *Foundation* is concerned. So any UI needs to clearly track in PMC / not in PMC, which is what ends up being reflected in committee-info.txt or LDAP. *If* someone wants to build UI and another per-PMC storage location to list emeritus members from that PMC, that's fine. But the core UI needs to first handle add/delete operations (and hopefully handling the 72 hour NAK period intelligently). ...snip... -- - Shane https://www.apache.org/foundation/marks/resources
