I just got this very justified bug report. The entire install procedure really needs overhauling. Can I have a volunteer to spearhead this, please? If I don't get one within a week then I'll ask around more widely. Please don't volunteer unless you are committed to producing some real changes within, say, two weeks of starting.

I'm feeling the need to expand the team anyway since the workload does seem to be getting greater than we can manage in a reasonable timeframe. I am feeling the burden falling quite heavily on me, and this is meant to be a team effort.

Kake

----- Forwarded message from Guest via RT bug-OpenGuides@rt.cpan.org -----

From: "Guest via RT" bug-OpenGuides@rt.cpan.org Date: Tue, 30 Sep 2003 19:04:10 -0400 (EDT) To: "AdminCc of cpan Ticket #3916": ; Subject: [cpan #3916] Config.pm leaks database password

This message about OpenGuides was sent to you by guest <> via rt.cpan.org

Full context and any attached attachments can be found at: <URL: https://rt.cpan.org/Ticket/Display.html?id=3916 >

In most standard installs, perl module files will be installed world-readable; therefore it is not appropriate to store the database password in Config.pm.

(I'm not actually sure why this file exists at all; surely we should be using the relevant wiki.conf anyway? storing configuration data in a perl module strikes me as exceedingly horrid)

----- End forwarded message -----