[development] Site credits module

Kevin Reynen kreynen at gmail.com
Sun Apr 15 20:34:09 UTC 2007

I suggested the equivalent of a phpinfo() page at last Sacramento
Drupal user meetup and it did not go over well.  You'd have thought I
suggested using a common admin password for all Drupal sites instead
of just allowing a site admin the OPTION of showing other people what
modules a site is using.  Someone there (sepeck?) said that enabling
the the Drupal module reports the module sites are running back to a
central server...

"Drupal - Lets you register your site with a central server and
improve ranking of Drupal projects by posting information on your
installed modules and themes"

So someone has the module information for a number of sites, but I've
never seen it.  I don't really buy the "making it easier for hackers"
argument against sharing this information.  Anyone who checks their
logs knows how often bots are scanning their servers for known,
exploitable scripts.  Creating a standard sitemap-like
(http://www.sitemaps.org/) format/location for other developers to see
what's being used and who's doing it would be a big benefit to the
community and IMHO wouldn't be giving the "bad" guys information that
could get another way.

The request to know what modules are popular is a fairly common one
from people new to Drupal.  The response at SacDUG seemed to be that
developers should monitor the issue queue for several months before
installing any module.  That's not really realistic advice for most
people looking at Drupal as a framework for their site.

I don't have the ability to share the information collected by the
Drupal module, but I'd be willing to install a module like this on my

- Kevin Reynen

On 4/14/07, Khalid Baheyeldin <kb at 2bits.com> wrote:
> On 4/13/07, Moshe Weitzman <weitzman at tejasa.com> wrote:
> > >     <h1>Site documentation for Example.com <http://Example.com></h1>
> > >
> > >     <h2>Goals</h2>
> > >     [insert site goals here; why does the site exist? who's its target
> > >     market?]
> > >
> > >     <h2>Overview of architecture</h2>
> > >     [insert overview of architecture here; how various pieces fit
> > >     together and why]
> > >
> >
> >
> > I have been thinking about a related module that might make sense to fold
> > into yours. ideally mine would be in core one day. the idea is to tell the
> > story of a site's construction.
> >
> > i call this fictional module 'credits' or 'colophon'. and admin enables
> this
> > and a page shows up at a known path like /credits. there, the admin can
> fill
> > in some summary info about the site and the designers, developers,
> clients,
> > etc. who work on the site. the role of each might optionally be detailed.
> >
> > in addition i would add a more drupal specific section where admin can
> > optionally disclose what modules/themes are in use and can make comments
> > about innovative use of each.
> >
> > i would even  have this module expose a microformat so that this data
> could
> > be aggregated and presented somewhere, one day. i did a bit of research
> and
> > didn't see any prior art for web site credits microformat.
> >
> > sorry for hijacking this thread a bit.
> >
> Colophon is the common name for such pages on many sites.
> The feature module used on Drupal.org can be a base for what you want.
> It has "categories" that show up as heading (could be designers, developers,
> ...etc.) and under it there are descriptions.
> A few checkboxes can be added to say "show Drupal version number", and "show
> enabled modules".
> --
> 2bits.com
> http://2bits.com
> Drupal development, customization and consulting.

More information about the development mailing list