we probably don't need a wiki. Content management ahoy! Just my 5 cents.
Best-F On Jan 11, 2012, at 9:50 AM, Bill Ricker wrote: > On Tue, Jan 10, 2012 at 3:37 PM, Tom Metro <[email protected]> wrote: > >> I'll reiterate a prior recommendation to use Wikispaces. It's been >> working fine for BLU and a few other projects with minimal maintenance >> effort. (Much nicer wiki UI than kwiki, too.) If you set it to require a >> login (OpenID) you pretty much eliminate spam. >> >> The big downside to it is that you have to pay in order to use a fully >> custom domain, otherwise you get a subdomain, which you could redirect >> to from your desired domain. >> > > Tom's offer is very much appreciated. My previous reply was along the lines > that we'd had so little wiki-ish authoring activity (aside from the > spammers) that I doubting the conversion was worth the effort and cost, was > wondering if we'd have a better fit moving to a Content Management System > (such as the minimalist WEBDAV that pm.org supplies -- that Jerrad and I > used on Advent 2.0 -- or something fancier, hopefully Perl based, maybe > runnable where our wiki is now (Quinlan's)). > > For FAQ/contact pages and a monthly calender update we don't need much -- > and only the few who actually do the editing need write access. That's all > that's really happening now. > > I would like comment on those requirements -- do we need a wiki ? if so, > what is who going to do with it that they haven't lately ? > > -- > Bill > @n1vux [email protected] > > _______________________________________________ > Boston-pm mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/boston-pm _________________________________________ -- "'Problem' is a bleak word for challenge" - Richard Fish (Federico L. Lucifredi) - flucifredi at acm.org - GnuPG 0x4A73884C _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
