My reasoning is that first, I think that book edits are not likely to be of
interest to the general TOS audience as the comments can get quite specific.
There may also be a lot of them. I know that I have multiple comments on the
"Getting the Code" chapter. I would prefer that we avoid the situation where
folks start ignoring TOS posts because it gets cluttered with detail-level
stuff they're not interested in. It also lets the folks on the forum focus
at that detailed level. (Hmmm, sort of like levels of abstraction now that I
think of it. :-) ) 

Second, I trust Karsten. He has been working in the OSS world and organizing
communication within that world for longer than I. So if he indicates that a
forum is going to make communication easier and thereby also make getting
our task done easier, I'm inclined to at least try his approach out. One of
the interesting interplays that we have in TOS is the balance between the
profs, the OSS folks, the students and others. We all have areas that we're
familiar with and fitting all these areas together is very fun. As part of
that, the community has a wonderful sense of respect for the opinions of
others and an openness for accepting the expertise of the others. TOS is
also a place to try out new ideas, so if the forum doesn't work, we will all
have learned something. And the same goes for if it does work. And either
way we will have had some fun! 

Just my thoughts for the moment.
Heidi



-----Original Message-----
From: [email protected]
[mailto:[email protected]] 
Sent: Friday, September 17, 2010 9:03 PM
To: [email protected]
Cc: Teaching Open Source Mail list - [email protected]
Subject: Re: [TOS] forums.teachingopensource.org

On Fri, Sep 17, 2010 at 5:35 PM, Heidi Ellis - 
[email protected] wrote:
> +1 for a forum.
> And better to not have all that chatter going on the main TOS list.
> Heidi
>

Could you share your reasoning?



_______________________________________________
tos mailing list
[email protected]
http://teachingopensource.org/mailman/listinfo/tos

Reply via email to