Jalexander added a comment. >>! In T607#10078, @mmodell wrote: > One thing I can do, at least it doesn't look very difficult at first glance, > is to enable 'advanced search' on the wiki username field. That would not > involve any hacks or long term maintenance issues, at least in the sense that > it would be isolated to an extension instead of patching the phabricator > core. It would also nicely solve the problem of finding a specific wiki user > and confirming that they signed document X. > > The 'discovery' use case that @chasemp mentioned would be better served by > the patch that I pasted above, but as @chasemp said, it would be better if we > can find a way to serve that use case without hacking the core. One solution > might be to just clone the user search code and make a separate > controller+view that does the same thing. Although this would be duplicating > the code it would avoid dealing with merge conflicts when upstream changes > touch the code we would be modifying..
Great, that gives me a bit of a better understanding of the question. While some of the on going (future) work would certainly be 'verify if he's signed' in the end what you are calling discovery is, indeed, the most important. At the start we have almost 900 users who will have to sign (because they already have advanced rights) in relatively short order. We need to see as they are coming in so that they can stop being bothered about it and so that we know when there may be issues. Searching for each individual user would become cumbersome and complicated. This is why my expectation has always been seeing it on the list of signatures itself (it is, indeed, the only thing we really 'need' to see on the list of signatures. We need to store their real name and email but I don't need access to it on a regular basis and I could care less about their Phabricator username. On the on going basis the discovery mode (or automated emails about new signatures... though we really don't want that for the first couple months) is also likely to be the most common method just because it makes it easiest to see when there has been a chance and allow us to do the required actions so that they can get the rights they were selected for by the community. TASK DETAIL https://phabricator.wikimedia.org/T607 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. To: Jalexander Cc: wikibugs-l, Qgil, Jalexander, mmodell, chasemp _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
