I have mixed feelings but in general I think it would be good to log. Knowing that it is logged will affect how I interact with it - I would say fewer personal things - but I have learned a huge amount from #sage-devel and it could be of great use to other people.
So, overall, +1 to a formal log. -Marshall On Sep 23, 7:29 pm, Robert Bradshaw <[email protected]> wrote: > On Sep 23, 2009, at 2:24 PM, William Stein wrote: > > > > > > > On Wed, Sep 23, 2009 at 2:20 PM, Rob Beezer > > <[email protected]> wrote: > > >> +/- 0 to logging. I can argue both sides. > > >> On the one hand, I know I have seen things on #sage-devel that I > >> think > >> would be better off not being posted and indexed - in particular, a > >> flamer and a naive-sage-support-poster being critiqued. Nothing > >> necessarily wrong with that, mostly folks blowing off steam, but > >> better I think to be "of the moment" than on the Internet Archive. I > >> imagine logging will have some influence on the informality of the > >> discussions (which I would miss). > > >> But, as has been demonstrated the past couple of days, a lot of > >> valuable information flows by. I often cut out tidbits to save for > >> later - such as when Citro and Alexander were doing release > >> management > >> together. Others cut/paste from IRC onto tickets when the discussion > >> is technical, serious and applicable. > > >> Is it not relatively easy for an individual to log by themselves > >> locally? Maybe not an ideal compromise, but still a middle ground. > >> But of course, that doesn't give the new developer any history. > >> Maybe > >> Harald is proposing a formal logged channel and an informal non- > >> logged > >> channel, which would be another middle ground. > > >> Disclaimer: 100% of my IRC experience is on #sage-devel > > > For the Sage project I think it would *best* if we changed our > > behavior on #sage-devel and make the #sage-devel logs public and > > searchable. The benefit to the project overall is that less gets > > discussed "in secret", process -- such as release management -- gets > > archived, etc. If people want to blow of steam or behave in a less > > than archivable way, they should do so elsewhere (e.g., #sage-flame). > > > Also, by making the #sage-devel logs public, many more people will > > benefit from what happens there. > > +1 I've benefited from IRC logs of other projects when trying to > troubleshoot things. > > > I would go so far as to recommend > > that we auto-email the logs each day to sage-devel. > > Note that typically less than 20 people are logged into #sage-devel at > > any time, and there is no posted log, so the people that benefit from > > #sage-devel are about 2% of the subscribers to the sage-devel mailing > > list, which isn't much. > > -1 to the idea of auto-emailing to sage-devel. If you want, we could > make a sage-logs group like sage-trac, but sage-devel is high-volume > enough as it is. Personally, this is one more email I'd delete every > time it came in (I'd would like to be able to search them if I was > looking for something). > > - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
