internal help , no problemo I can do that too. Its an opportunity to see how pharo internal help system works , last time I checked it seemed simple enough.

Class docstrings first seems like a good priority.

I love your work with pharo and I was itching to contribute back to the community. I love smalltalk mainly because of the great environment and I think that there is still a lot more to be done to improve it and make it even more user friendly , I only hope I play my own small part in this. 


From: Camillo Bruni <camillobruni@gmail.com>
To: "Pharo-project@lists.gforge.inria.fr Development" <Pharo-project@lists.gforge.inria.fr>
Sent: Friday, 23 November 2012, 15:02
Subject: Re: [Pharo-project] Helping with Athens development


On 2012-11-23, at 09:57, dimitris chloupis <thekilon@yahoo.co.uk> wrote:

> Thank you Igor , this was the type of answer I wanted . Ok I think I will work first on documenting the code and creating a pdf that helps the user understand how to use Athens.

if you could, it would be nice to have the text also for Pharo's internal help system.
In my opinion that is more smalltalk-like, since we ship everything together :)

> After I gain a very good insight through documentation of how Athens works I start contributing code. I assume for documenting code (adding doc strings to methods missing them) files out and attaching them here will do or you want me to upload to my own project in ss3 ?

I guess the highest priority here is class comments, that is kind of a must
(though I catch myself too often not adding one).

nice to see additional support for athens!