I assume we should only submit the class comment itself and not an
actual fileout? It's a bit awkward to fileout a class comment by itself
without resorting to a changeset -- and it would in turn be awkward to
create a different changeset for every single class comment done.

I recently sent five new class comments to Stefan Matthias Aust, which I
believe he has already sent to you to be added to the update stream. I
will send them to the list under [CCC] for completeness (and further
commentary of course).

-- Dwight

Dan Ingalls wrote:
> 
> >May I suggest that all Class Comment Challenge contributions have "[CCC]"
> >in the subject line so they can be filtered and retained for posterity?
> >This is a noble undertaking, so let's not lose any of the input.
> 
> Sorry to be slow in responding.
> 
> I think this is a fine idea.  I will commit to weekly turnaround of any class comments submitted this way.  Allow me to tweak the suggestion:
> 
> 1.  Submit only one per message and use a subject line of the form:
> 
>         [CCC] PenPointRecorder class comment
> 
> 2.  Do your best to survey prior submissions to avoid duplication -- this should be pretty easy if we follow rule 1.
> 
> 3.  Mail to the Squeak List -- not me.  I know this might mean a couple of hundred extra messages, but what a great problem to have!