Time  Nick    Message
23:30 pameyer for tonight, none of the above - heading out soonish
23:26 pdurbin or open a new issue
23:26 pdurbin or start a thread on the mailing list
23:26 pdurbin pameyer: you should feel free to comment on any issue, of course
23:22 pdurbin besides, you'd have to tell them your "burrito" key
23:22 pdurbin meh, most users would probably want to sign up via the GUI, I would imagine
23:21 pameyer but I'll check out the survey
23:21 pameyer I was thinking along the lines of "have http://guides.dataverse.org/en/4.2.4/installation/administration.html#user-administration" point users to the API page...
23:18 pdurbin there's stuff about creating and editing users in that survey
23:16 pdurbin pameyer: actually, maybe you should start by filling out this survey: https://github.com/IQSS/dataverse/issues/840#issuecomment-145844868
23:09 pameyer pdurbin: is https://github.com/IQSS/dataverse/issues/2211 the right place of a suggestion in the admin guide about this?
23:05 pameyer using psql for user management is more of a last-resort approach.  I wouldn't recomment it either (even if I have to resort to it sometimes)
23:01 pdurbin I wouldn't actually recommend hacking on users with psql. It's possible but you have to keep multiple tables in sync.
22:59 pdurbin pameyer: well, what are you wanting to do? You can create users via API if you want.
22:57 pameyer worst comes to worst there's always psql
22:57 pameyer pdurbin: you did
22:53 pdurbin related: https://github.com/IQSS/dataverse/issues/2667 but the main issue I this one, I think: https://github.com/IQSS/dataverse/issues/840
22:51 pdurbin pameyer: told ya
22:01 pameyer pdurbin: I see what you were talking about for user management UI...
21:10 pdurbin bencomp: "Dataverse under Docker": https://docs.google.com/document/d/1sUf8ReWJv2rwjSmhYF7E3CXNwiemIm9P7AXNUaBA2zY/edit?usp=sharing
17:11 pdurbin cool. notes from yesterday's call have been posted to http://dataverse.org/community-calls