Wad, you're right that Dansguardian is a can of worms but it is a very important can of worms that needs to work w/ minimal configuration, at least initially.
I would say that the initial install should set a medium level of restriction and then leave it to the local deployment teams to tweak it to cultural norms. On Fri, 2008-10-03 at 00:17 -0400, John Watlington wrote: > On Oct 2, 2008, at 11:51 PM, Bryan Berry wrote: > > > Greg, > > > > We will be setting up two labs here in Nepal, one in the next couple > > weeks and likely one in the first week of November at Nepal's Dept of > > Education. Depending on our experiences in those labs, we want to roll > > out a new version of the XS in November to our two pilot schools and > > possibly a new pilot school. > > > > This mirrors our priorities > >> A stable and scalable eJabber is critical as are basic XS features > >> like: > >> - Caching > >> - Filtering (is DanGuardian built in and shipped with the XS ?) > >> - NAT > > > > w/ two exceptions. We still find it a bear to install the XS from > > scratch. That could be our fault but it needs to be easier to set up > > ejabberd properly. It also needs to be easier to get dansguardian > > up and > > running. As far as I can tell dansguardian is not pre-installed on the > > XS in XS 0.4. > > What default permissions should be provided for DansGuardian ? > What list of banned sites and keywords ? > > No real disagreement. But one of the issues with DansGuardian is > that the > configuration reflects local mores, and it is difficult to provide a > default. > How do we ensure that a deployment provides the configuration files ? > > Cheers, > wad > _______________________________________________ Server-devel mailing list [email protected] http://lists.laptop.org/listinfo/server-devel
