Hi, I wonder why first and last name are not good enough. I have found the model clear and privacy aware. Such image id is complemented with remote credentials in remote repositories (SmalltalkHub, GitHub, etc) and I deploy distinct images for distinct projects or releases (which is now easier with PharoLauncher), so I fail to see other use cases.
Cheers, Offray On 27/12/17 08:05, Cédrick Béler wrote: > Hi all, > > For now, it is asked (by convention) a string containing our first name and > last name (when code is submitted). > Just wandering if you could have a better representation of a user of a Pharo > image. > > Could we imagine a user id instead ? > That shouldn’t be heavy to deal with and eventually one could add more > functionalities (one being the authentification to a pharo based application). > > The difficulty is to find a proper universal user id. I would have used > something that encode date and place of birth in the id but it suffers some > privacy related issues. Any ideas ? > Another question is if an image may be used by several people ? To me > allowing one user is ok for a developer image but it might be interesting to > switch user spaces if it’s for a pharo application ? > > Cheers, > > Cédrick >
