On Sun, Jan 25, 2015 at 2:24 PM, Chris Ilias <[email protected]> wrote: > On 2015-01-25 1:31 PM, Majken Connor wrote: >> >> 1. Trying to keep up with a project by reading IRC logs (or watching >> meeting videos) is a lot to ask for many people. This takes a lot of time >> and someone could end up spending all their day reading logs and watching >> videos to stay informed. We need to make sure that sharing the logs >> addresses the case of people who hang out regularly and just want to catch >> what they missed. We need to make sure that teams do *not* say "if you >> want >> to follow us, read the logs." > > <snip> >> >> >> Mozilla has a dearth of good note takers, in terms of solving transparency >> I would be more in favor of trying to solve that problem, not using public >> logs to solve it. I am in favor of having logs accessible for Mozillians >> to >> solve the problem of people who do follow the team missing conversations >> when they're disconnected. > > > > The same discussion came up on sumo, and I think the same argument I made > there also applies here. By making the raw data public, any volunteer who > wasn't there to take notes can read the logs and create good notes. > > I think that solves both problems above. It's also a great example of how > being public enables more people to contribute.
Also... "The posting of the chat logs, email discussions, and summary digests on a public Web site embody the spirit of the free software movement and serve as a point of entry, exposure, and enculturation for both new and experienced open source software developers." - University of California, Communicating and Mitigating Conflict in Open Source Software Development Projects (http://www.ics.uci.edu/~melliott/commossd.pdf) _______________________________________________ governance mailing list [email protected] https://lists.mozilla.org/listinfo/governance
