This package, in the last core image is modified but not commited so when following the steps from the HowToContribute wiki page, in the part of creating a mcz package with the change the mcz generate will include the other uncommited changes. Should I use a changeset instead in order to not commit changes that I don't want?
First, you should update your image. It should be a core. Your change must be produced for Core. Then, implement your fixe. If more than one package is touched, then produce a slice. You should save your fix in PharoInbox using Monticello. Last step, make sure your fix load in a fresh and updated core image; add an issue in the google website; send an email to the mailing list.
What is the goal with the Author class?
A reification of author. Authors should not be strings passed around.
Author has name and initials, what will be the intended use of them?
It is true that we should not use initials anymore, but essentially for legacy purpose, we cannot remove them. We could envision future version of the class Author that includes email, squeak source account, ...
I can unify all the message sends to Author in the core image, also I can unify the initials and name usage, but I need to know the intended goal for this class.
The only use of Author is for managing the name/initial used in the .changes and monticello. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.