On Wed, Aug 12, 2009 at 9:28 PM, Ronald Spengler <ron.spengler at gmail.com>wrote:

> That's right! It was fancy... or feline? Something like that.
> "Release soon" is, of course, my own thing. Sorry that I tried to sneak
> that in. My mom, see, she's having this problem that I don't really
> understand about blocks not being true closures? and I was hoping, well...
> my mother is a thundering tyrant and I'm afraid for my life. You understand.
>

Tell her blocks *are* real closures now :)


>
> I would like to retract my statement about consistent style in class
> comments. That's actually, thinking about it, asking waay too much. I should
> have thought about that before I said it. Having comments for each class in
> the first place would be a fabulous start.
>
> I meant the original statement as kind of a gag, as if one reads between
> the lines, it really says: "Let's at least add one good comment before we
> ship it."
>
> I know that if we put our heads together, I can pull that off!
>
>  - Ron
>
> On Wed, Aug 12, 2009 at 8:15 PM, Andreas Raab <andreas.raab at gmx.de> wrote:
>
>> Ronald Spengler wrote:
>>
>>> As the FNG, class comments are very important to me. I propose:
>>>
>>> We should ship a release soon. That's maybe the most important thing in
>>> the universe right now.
>>>
>>
>> Personally I'm not in a hurry to finalize a new release. That's mostly
>> because I would like to concentrate on the contribution process for now and
>> make sure it's being accepted and the kinks worked out. Once we start
>> looking at release issues there will be a whole new set of issues that I'd
>> like to separate from the main contribution process.
>>
>>  That said, as the FNG, I would like to propose a general standard:
>>>
>>> - There should be an informative class comment for each class in the base
>>> image.
>>>
>>
>> I agree with this goal.
>>
>>  - Within reason, classes which are in the core image should have a
>>> comment written in a consistent style (e.g., "I represent...")
>>>
>>
>> I'm a bit hesitant on that one.
>>
>>  - It's okay to ship a release without meeting the above two objectives,
>>> as long as we make progress toward the above two objectives.
>>>
>>
>> Obviously. Having the above as requirements for a release makes little
>> sense.
>>
>>  I personally would not mind wandering the image, looking for crappy or
>>> missing class comments, fixing them where I can, and asking the list for
>>> advice where I can't. I imagine that I could learn a lot that way:)
>>>
>>> What do the lovely people of squeak-dev think?
>>>
>>
>> Sounds good. Give it a shot. Pick a package, work through the comments,
>> ask questions and see how people like the result. I recommend taking a
>> package that isn't too big and that fits your interests.
>>
>>  For those not-in-the-know, the 'NG' in FNG stands for New Guy. I can't
>>> remember that the 'F' stands for.
>>>
>>
>> Fancy. It stands for fancy.
>>
>> Cheers,
>>  - Andreas
>>
>>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090813/002fa201/attachment.htm