> When contributing it is associated to licence so I just find the actual
model a bit weak.
I don't think that this is the case anymore. Pharo itself (and more and
more pharo projects) are moving to git, so the Author string is not really
used outside of the given image --- the author is based on
Of course this can be enough but this could be more objectified. A string
cannot be called a model to me.
For now nothing prevents from having somebody use the id of someone else. When
contributing it is associated to licence so I just find the actual model a bit
weak.
Then, additional functi
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 wit
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
