Just to reiterate what I said the other day: I'd like to have the #olpc logs published. If someone sets up a bot to do it, and especially of we and sl can agree on a similar policy for both sets of channels, that would be handy.
I would include "This channel is logged at <URL>" at the start of every chantopic, as a service first and a warning second. Public IRC channels a private place to chat, and quite a valuable resource for capturing the momentum of the collective conscious. --SJ On Thu, Feb 5, 2009 at 8:39 AM, Greg Dekoenigsberg <[email protected]> wrote: > > On Thu, 5 Feb 2009, Morgan Collett wrote: > >> On Thu, Feb 5, 2009 at 14:19, Tomeu Vizoso <[email protected]> wrote: >>> On Thu, Feb 5, 2009 at 13:11, David Van Assche <[email protected]> wrote: >>>> So... to log or not to log, that is the question.... ? >>> >>> What if everybody that has ever posted in a sugar mailing list and is >>> against publishing logs explained here how if logs were public it >>> would harm her/his ability to keep contributing? >> >> s/mailing list/IRC channel/ >> >> (others made this mistake in this thread too...) >> >>> I think we should not question their opinions, but as a community >>> evaluate how making logs publics may harm our current contributors. >> >> I've always considered IRC as a public medium, with many lurkers who >> may or may not be publishing the logs. Right now there are 75 logged >> on to #sugar, many of which I've never seen participate. They could be >> representing journalists, future employers, governments, skynet... >> Making future, or past, logs available publicly would not harm me. >> >> When I first got involved in OLPC, things were changing so fast that >> typically issues (like jhbuild failing) were raised and resolved on >> IRC and never hit the mailing lists, so I used to read the #olpc and >> #sugar scrollback on a daily basis. I learned a huge amount this way. >> I no longer read everything(!) but often have a quick scan to see if >> there was anything relevant to me. >> >> I think there are three options, going forward: >> >> #1. Publish the logs officially, hosted on a sugarlabs server and >> linked from the wiki, for at least #sugar if not #sugar-meeting as >> well. Explain that no other channels are officially logged in this >> way, and that people are welcome to use (for example) >> #sugar-meeting-offtherecord if they want to avoid their logs being >> published. Or #no-you-cant-have-a-pony. >> >> #2. A community member, whether a Sugar Labs member or otherwise, >> publishes logs at an unofficial location (including >> people.sugarlabs.org, or a non sugarlabs domain). If nobody else does >> #1 above or this #2, I'll probably do this at some point, unless #3 >> below kicks in. >> >> #3. Sugar Labs officially bans logging the channels #sugar and/or >> #sugar-meeting. >> >> OLPC never banned logging, but a couple of people asked me not to >> publish logs when I first spun up xobot. Recently I think it was SJ, >> but I can't find the reference, who said that the appropriate #olpc* >> channels should be published as a resource. > > #3 is basically impossible. > > And if even one person chooses #2, then we may as well save them the work > by doing #1 anyway. > > My last word on the topic. :) > > --g > > -- > Got an XO that you're not using? Loan it to a needy developer! > [[ http://wiki.laptop.org/go/XO_Exchange_Registry ]] > > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > [email protected] > http://lists.sugarlabs.org/listinfo/iaep > _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) [email protected] http://lists.sugarlabs.org/listinfo/iaep
